さらに、Xhs1991 PT-AM-CPEダンプの一部が現在無料で提供されています：https://drive.google.com/open?id=16zqov8xvb4VNBIxiLmmpJNnSD5gqvLnF
Xhs1991 はプロなウェブサイトで、受験生の皆さんに質の高いサービスを提供します。プリセールス.サービスとアフターサービスに含まれているのです。Xhs1991のPing IdentityのPT-AM-CPE試験トレーニング資料を必要としたら、まず我々の無料な試用版の問題と解答を使ってみることができます。そうしたら、この資料があなたに適用するかどうかを確かめてから購入することができます。Xhs1991のPing IdentityのPT-AM-CPE試験トレーニング資料を利用してから失敗になりましたら、当社は全額で返金します。それに、一年間の無料更新サービスを提供することができます。
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
練習資料は通常、試験に必要な試験問題を復習、練習、および記憶するためのツールと見なされ、それらに多くの時間を費やすことで、勝つ可能性を高めることができます。ただし、当社のPT-AM-CPEトレーニング資料は、従来の練習資料よりも条件が良く、効果的に使用できます。 PT-AM-CPE実践ガイドが非常に多くのヘルプを提供できるように、ヘルプを提供することが主な責任であると考えています。最も一般的なのは、PT-AM-CPE試験問題の効率性です。 20〜30時間勉強します。
質問 # 74
In PingAM, which OpenID Connect endpoint can be used to validate an unencrypted ID token?
正解：A
解説：
While OpenID Connect (OIDC) is built on top of OAuth2, it introduces specific endpoints for handling ID Tokens (the identity layer). In PingAM 8.0.2, when a client receives an ID Token, it is recommended to validate it locally using the provider's public keys. However, PingAM also provides a convenience endpoint for validation.
According to the "OpenID Connect 1.0 Endpoints" documentation:
/oauth2/idtokeninfo (Option A): This is the dedicated endpoint designed to receive an ID Token as a parameter.8 It validates the token's signature, checks the expiration and audience, and returns the claims contained within the token in a JSON format. This is specifically used for unencrypted ID tokens.
/oauth2/userinfo (Option B): This endpoint returns claims about the authenticated user but requires a valid Access Token in the authorization header, not an ID Token.9
/oauth2/introspect (Option C): This is a standard OAuth2 endpoint (RFC 7662) used to check the metadata and "activeness" of Access Tokens or Refresh Tokens, not the internal identity claims of an OIDC ID Token.10
/oauth2/tokeninfo (Option D): This is a legacy/non-standard endpoint that was used in older versions for Access Token validation and is not the primary OIDC validation endpoint in version 8.0.2.11 Therefore, for the specific task of validating an ID Token and retrieving its claims, /oauth2/idtokeninfo is the correct and authoritative endpoint in the PingAM 8.0.2 OIDC implementation.
質問 # 75
Which of the following components is used to return data to PingGateway or the agent to be included with the policy decision?
正解：C
解説：
When PingAM 8.0.2 evaluates an authorization policy, the primary output is a "Permit" or "Deny" decision. However, applications and Policy Enforcement Points (PEPs)-like PingGateway or a Web Agent-often require additional metadata about the user or the session to function correctly (e.g., the user's employee ID, department, or a specific preference).
According to the PingAM documentation on "Policies" and "Requesting Decisions":
The mechanism used to provide this extra information is Response Attributes. When defining a policy in the PingAM UI or via REST, an administrator can configure "Response Attributes" which map internal attributes (from the User Profile or the Session) to keys that are sent back in the policy decision payload.
How it works: If a policy is configured with a response attribute mapping uid to User-ID, when PingGateway asks "Can user X access resource Y?", PingAM responds with "Permit" AND a map containing User-ID: X.
Consumption: PingGateway or the Web Agent can then take these attributes and inject them into HTTP headers (e.g., X-User-ID) so the downstream application can consume them without having to query AM again.
Subjects (Option A), Resources (Option B), and Actions (Option D) are all input components used to define the scope of a policy; they are not used to return data to the enforcer. Only Response Attributes serve the purpose of enriching the decision response with additional context.
質問 # 76
Which of the following environment conditions are needed in an authentication policy created as part of the prerequisites for step-up authentication?
A) Authentication Level (greater than or equal to)
B) Authentication by Service
C) Authentication by Module Instance (authentication modules only)
D) Authentication to a Realm
正解：B
解説：
To implement Step-up Authentication in PingAM 8.0.2, you typically use Authorization Policies that include "Environment Conditions."14 These conditions check the "quality" of the user's current session. If the session does not meet the specified condition, PingAM generates an Advice, which triggers the step-up process.
According to the "Condition Types" reference in the PingAM 8 documentation, the conditions used specifically to evaluate how a user authenticated are:
Authentication Level (greater than or equal to): This is the most common condition for step-up. It checks if the session's Auth Level is at least a certain value (e.g., Level 2). If the user only has a Level 1 session, the policy fails and triggers an upgrade.
Authentication by Service: This condition checks if the user authenticated using a specific Authentication Tree or Chain (e.g., the user must have used the "SecureBankMFA" tree).
Authentication by Module Instance: This is used for legacy deployments where individual modules are used instead of trees. It verifies that the user successfully completed a specific module (e.g., the "DataStore" module).
Authentication to a Realm (Option D) is generally not a condition used for step-up authentication. While a policy exists within a realm, the "step-up" logic is focused on the method or level of authentication within that realm, not the fact that they are in the realm itself (which is already a prerequisite for reaching the policy engine). Therefore, the combination of A, B, and C (Option B) represents the specific environment conditions designed to evaluate the authentication context for step-up or "Quality of Service" (QoS) requirements.
質問 # 77
An OpenID Connect application makes a request for an ID token with the openid and profile scope. Which set of claim attributes are available with the profile scope?
正解：C
解説：
PingAM 8.0.2 adheres to the OpenID Connect Core 1.0 specification regarding standard scopes and claims. When a client requests the profile scope, the OpenID Provider (PingAM) is expected to return a specific set of claims that describe the user's basic profile.
According to the PingAM documentation on "Understanding OpenID Connect Scopes and Claims" and the default OIDC Claims Script (which maps internal LDAP attributes to OIDC claims):
The standard claims associated with the profile scope are strictly defined with lowercase, snake_case naming conventions. The default set includes:
name: The user's full name.
given_name: The user's first name.
family_name: The user's surname or last name.
middle_name: (Optional)
nickname: (Optional)
preferred_username: (Optional)
profile: URL to the profile page.
picture: URL to an image.
website: URL.
gender: (Optional)
birthdate: (Optional)
zoneinfo: Timezone.
locale: The user's preferred language/locale.
updated_at: Timestamp.
Option C is the only choice that correctly identifies the snake_case format (given_name, family_name, locale) required by the specification. Options A and B use camelCase or inconsistent naming that does not match the OIDC standard or PingAM's default mapping script. Option D includes preferred_locale, which is incorrect; the standard claim name for a user's language preference in OIDC is simply locale.
質問 # 78
Which feature of PingAM protects against cookie hijacking in a cross-domain single sign-on environment?
正解：C
解説：
In a Cross-Domain Single Sign-On (CDSSO) environment, PingAM must manage session cookies across multiple distinct DNS domains.2 By default, a standard SSO token could potentially be stolen and reused by a malicious actor to gain access to other domains within the same realm.3 To mitigate this specific threat, PingAM 8.0.2 utilizes Restricted Tokens.4 According to the documentation on "Securing CDSSO session cookies," a restricted token is a unique SSO token issued for each specific application or policy agent after successful user authentication.5 When CDSSO is active with cookie hijacking protection enabled, PingAM issues a "master" SSO token for the domain where AM resides and separate restricted tokens for the other fully qualified domain names (FQDNs) where web or Java agents are located.6 The restricted token is "restricted" because it is inextricably linked to the specific agent and application that initiated the redirection. Internally, AM stores a correlation between the master session and these restricted tokens.7 If an attacker attempts to hijack a restricted token and use it to access a different application or a different domain, the AM server performs a validation check on the constraint associated with the token (such as the agent's DN or IP). If the request does not originate from the authorized entity, a security violation is triggered, and access is denied. This mechanism ensures that even if a cookie is stolen in one domain, its utility is confined strictly to that domain and cannot be used for "lateral movement" across the enterprise's other protected resources. It is important to note that restricted tokens require server-side sessions to function; they are not supported for client-side (JWT-based) sessions.8
質問 # 79
......
私たちのPT-AM-CPE研究ブレーンダンプは、この点でユーザーの需要を満たすのに非常に優れている可能性があり、ユーザーが学習したことを継続的に統合する良い環境で読み書きできるようにします。 PT-AM-CPE準備ガイドは高品質です。当社のウェブサイトのPT-AM-CPE学習クイズバンクおよび教材は、選択したトピックに基づいて最新の質問と回答を検索します。 この選択は、あなたのキャリア全体の突破口となるので、PT-AM-CPEスタディガイドの高い品質と正確性に驚かされるでしょう。
PT-AM-CPE合格受験記: https://www.xhs1991.com/PT-AM-CPE.html
P.S.Xhs1991がGoogle Driveで共有している無料の2026 Ping Identity PT-AM-CPEダンプ：https://drive.google.com/open?id=16zqov8xvb4VNBIxiLmmpJNnSD5gqvLnF