P.S. Free & New PT-AM-CPE dumps are available on Google Drive shared by Fast2test: https://drive.google.com/open?id=1Yo8fJC7Hxo8zhXTJGrfqB8nqOUgrSt-w
Do you want to pass your exam with the least time? If you do, then we will be your best choice. PT-AM-CPE training materials are edited and verified by experienced experts in this field, therefore the quality and accuracy can be guaranteed. Besides PT-AM-CPE exam materials contain both questions and answers, and it’s convenient for you to have a check after practicing. We have online and offline chat service, if you have any questions about PT-AM-CPE Training Materials, you can consult us, we will give you reply as quickly as possible.
| Certification Vendor: | Ping Identity |
|---|---|
| Exam Name: | Certified Professional - PingAM Exam |
| Exam Number: | PT-AM-CPE |
| Exam Format: | Scenario-based, Multiple Choice |
| Available Languages: | English |
| Passing Score: | 66% |
| Exam Duration: | 120 minutes |
| Exam Price: | $395 / £310 / €365 |
| Related Certifications: | Ping Identity Certified Expert - PingAM |
| Certificate Validity Period: | 3 years |
| Real Exam Qty: | 100 |
| Recommended Training: | PingAM Deep Dive (AM-410) |
| Exam Registration: | Ping Identity Certification Portal |
| Sample Questions: | Ping Identity PT-AM-CPE Sample Questions |
| Exam Way: | Online proctored or onsite testing center |
| Pre Condition: | Completion of PingAM Deep Dive Course (AM-410); 3–6 months hands-on experience with PingAM |
| Official Syllabus URL: | https://backstage.pingidentity.com/university/ping/certification |
>> Downloadable PT-AM-CPE PDF <<
If you are busying with your study or work and have little time to prepare for your exam, choose us, we will do the rest for you. PT-AM-CPE exam bootcamp are edited and verified by professional experts, therefore the quality and accuracy can be guaranteed. You just need to spend about 48 to 72 hours on practicing, and you can pass the exam in your first attempt by using PT-AM-CPE Exam Braindumps of us. We offer you free demo to have a try before buying. Online and offline chat service are available, and if you have any questions about PT-AM-CPE exam bootcamp, you can have a conversation with us.
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
NEW QUESTION # 84
Which statements are correct in relation to an OAuth2 token exchange impersonation pattern?
A) The client may want to act as the subject on another service.
B) The client is used by a subject to act on behalf of another subject.
C) The requested token exchange involves a subject token only.
D) The requested token exchange involves a subject and actor token.
Answer: D
Explanation:
In PingAM 8.0.2, the OAuth 2.0 Token Exchange (RFC 8693) supports two primary patterns: delegation and impersonation. Understanding the difference between these is critical for secure microservices architecture.
According to the "Demonstrate Impersonation" section of the PingAM documentation, impersonation is a pattern where a client (the "Actor") acts as another identity (the "Subject") in a way that the downstream resource server sees only the Subject's identity.
Statement A is correct: In an impersonation flow, the client (which has been authorized by the user or is a trusted service) requests a token where it effectively "becomes" the subject to interact with another service. The downstream service treats the request as if it were coming directly from the subject, often with the same set of permissions.
Statement D is correct: To perform a token exchange for impersonation, the client must provide specific parameters to the /oauth2/access_token endpoint. It provides the subject_token (representing the identity to be impersonated) and the actor_token (representing the identity of the client/service that is performing the impersonation). PingAM validates both tokens to ensure the "Actor" has the permission to impersonate the "Subject." Why other statements are incorrect: Statement B describes delegation (where an actor acts on behalf of a subject but maintains their own identity in the act claim). Statement C is incorrect because a token exchange inherently requires proving who the requester is (the actor) and whom they represent (the subject). Without both tokens, the AM server cannot verify the authorization relationship required for impersonation. Therefore, the combination of A and D accurately reflects the impersonation pattern in PingAM 8.0.2.
NEW QUESTION # 85
Examining the following JSON object, what is a valid value for the type part (shown in bold font) of the claim value in a PingAM implementation?
JSON
JSON
"act": {
"sub": "(type!subject)"
}
Answer: C
Explanation:
The JSON object structure provided refers to the Actor (act) claim used in OAuth 2.0 Token Exchange (RFC 8693) within PingAM 8.0.2. This claim is essential for scenarios involving delegation or impersonation, where one entity (the actor) is performing an action on behalf of another (the subject). In PingAM, the sub (subject) field within the act claim follows a specific internal format: (type!subject).
According to the PingAM 8.0.2 documentation regarding Token Exchange Configuration, the type part of this string is a mandatory prefix that identifies the category of the identity acting as the delegate. The documentation explicitly defines two primary valid values for this type field:
usr: This specifies that the subject is a user/identity from an identity store. For instance, if a user is acting on behalf of another user, the claim would appear as "(usr!username)".
age: This specifies that the subject is an OAuth 2.0/OpenID Connect-related agent or client. Examples include an OAuth 2.0 client, a Remote Consent Service agent, or a Web/Java Agent internal client. An example would be "(age!myClientID)".
While "user" and "agent" are the descriptive terms for these categories, the actual technical values recognized and emitted by PingAM in the claim string are the three-letter shorthand codes. Therefore, usr (Option B) is the correct valid value. Choosing "user" (Option D) would be technically incorrect in the context of the exact string format required by the AM engine. This formatting ensures that when the token is introspected or validated, the resource server can correctly parse whether the actor is a human user or a machine client.
NEW QUESTION # 86
Which organization sets, maintains, and governs the SAML2 standard?
Answer: C
Explanation:
PingAM 8.0.2 is strictly compliant with various identity standards to ensure interoperability between different vendors and platforms. The Security Assertion Markup Language (SAML) V2.0 is the cornerstone of modern XML-based federation.7 According to the PingAM "SAML 2.0 Introduction" and "Supported Standards" documentation, the SAML 2.0 standard is developed and maintained by OASIS (the Organization for the Advancement of Structured Information Standards).8 Specifically, the OASIS Security Services Technical Committee (SSTC) is responsible for the specifications that define the SAML core (assertions and protocols), bindings (how SAML messages are mapped onto transport protocols like HTTP), and profiles (how SAML is used to solve specific use cases like Web Browser SSO).
Knowing the governing body is important for administrators when reviewing the "Technical Metadata" and "Schema" sections of PingAM, as AM's implementation follows the OASIS SAML 2.0 standards for XML signing, encryption, and assertion structure. Other organizations listed, such as the IETF (Internet Engineering Task Force), govern protocols like OAuth2 and OpenID Connect, while the W3C (World Wide Web Consortium) handles general web standards like XML and WebAuthn. However, for SAML2, OASIS remains the authoritative governing body.
NEW QUESTION # 87
Samantha decides to implement SAML2 auto-federation to link accounts on the service provider (SP) with the corresponding account in the identity provider (IdP). Which of the following statements describe characteristics of auto-federation?
A) Linking is based on a common NameId format value.
B) Linking is achieved by using a common attribute value.11
C) The user must log in to the IdP only to link accounts.
D) The user must log in to both the SP and the IdP to link accounts.
Answer Selection:
Answer: C
Explanation:
Auto-federation is a feature in PingAM 8.0.2 designed to simplify the user experience by automatically linking an IdP identity to an SP identity without manual intervention or a specialized "linking" page.12 According to the PingAM documentation on "Link Identities Automatically with Auto-Federation":
Linking Mechanism (Statement B): Auto-federation does not rely on the SAML NameID. Instead, it uses a common attribute value found in both the SAML assertion and the SP's local identity store. For example, if both systems share an "Email" attribute, the SP can be configured to use the mail attribute from the incoming assertion to search its own datastore. If a match is found, the accounts are linked. This is significantly more flexible than relying on NameID formats (disproving Statement A).
User Experience (Statement C): One of the primary benefits of auto-federation is that it supports a "Just-in-Time" experience. The user only needs to log in to the Identity Provider (IdP). When they are redirected to the SP, the SP performs the attribute-based lookup and creates the session immediately. The user is never prompted to log in at the SP side just to "prove" who they are for the linking process (disproving Statement D).
Because auto-federation relies on matching attributes and only requires a single login at the IdP, the correct statements are B and C. This makes Option B the correct choice. This feature is particularly useful in Large-Scale B2B or B2C scenarios where pre-mapping thousands of users manually would be impossible.
NEW QUESTION # 88
Which of the following tab pages in the PingAM admin UI can be used to configure the OAuth2 and OpenID Connect may act scripts used for token exchange requests?
A) The OAuth2 provider service > Advanced tab page
B) The OAuth2 provider service > Core tab page
C) The OAuth2 client profile > Advanced tab page
D) The OAuth2 client profile > OAuth2 Provider Overrides tab page
Answer: D
Explanation:
The May Act script is a critical component of the OAuth 2.0 Token Exchange implementation in PingAM 8.0.2. It allows for the validation of impersonation or delegation requests. Because token exchange can be configured both globally for all clients and specifically for individual applications, the script can be attached at two different levels in the Administrative UI.
OAuth2 Provider Service > Advanced Tab (A): This is the global configuration level. If you want to apply a standard "May Act" validation script across the entire realm for any client performing a token exchange, you configure it here. This script will be the default unless specifically overridden.
OAuth2 Client Profile > OAuth2 Provider Overrides Tab (D): PingAM allows for granular control per client. If a specific "Confidential Client" (like a backend microservice) requires unique logic for determining who it can act as, you can specify a different script or override the global setting. This is done in the "OAuth2 Provider Overrides" tab within that specific client's configuration profile.
Why other options are incorrect: The Core tab (B) is used for basic settings like issuer names and token lifetimes, not for advanced scripting hooks. The Advanced tab of the Client Profile (C) contains settings like TTLs and Logout URLs, but the specific ability to override "Provider" level logic (like the May Act script) is moved to the specialized Overrides tab to keep the interface organized. Therefore, the correct locations are A and D, as identified in the "Token Exchange Configuration" guide for version 8.0.2.
NEW QUESTION # 89
......
Reliable PT-AM-CPE Exam Materials: https://www.fast2test.com/PT-AM-CPE-premium-file.html
P.S. Free 2026 Ping Identity PT-AM-CPE dumps are available on Google Drive shared by Fast2test: https://drive.google.com/open?id=1Yo8fJC7Hxo8zhXTJGrfqB8nqOUgrSt-w