[Mar 07, 2026] PT-AM-CPE Test Engine files, PT-AM-CPE Dumps PDF
Latest Ping Identity PT-AM-CPE PDF and Dumps (2026) Free Exam Questions Answers
NEW QUESTION # 41
Which of the following needs to be configured in order to use social authentication in PingAM?
- A. A data store
- B. A realm policy
- C. An OAuth2 client
- D. A realm service
Answer: C
Explanation:
Social Authentication in PingAM 8.0.2 allows users to log in using identities from external providers like Google, Apple, or LinkedIn. This process relies on PingAM acting as an OAuth2 Client or OpenID Connect Relying Party (RP) toward the social provider.
According to the PingAM "Social Authentication" and "Social Identity Provider Client Configuration" documentation, for PingAM to successfully hand off authentication to a social provider, you must configure an OAuth2 Client (specifically a Social Identity Provider client) within the PingAM realm. This configuration includes:
Client ID and Client Secret: Obtained from the social provider's developer console (e.g., Google Cloud Console).
Endpoints: The authorization, token, and UserInfo endpoints of the social provider.
Scopes: The permissions PingAM is requesting (e.g., openid, profile, email).
Once this "Social Client" is configured, it is used by a Social Provider Handler node (or the legacy Social Authentication module) within an authentication tree. When the user clicks "Login with Google," PingAM uses these client credentials to initiate the OIDC flow with Google.
Why other options are not the primary requirement:
While a Data Store (A) is eventually used to save the linked user profile, the mechanism of social auth itself is driven by the OAuth2 client configuration.
A realm service (B) is too broad; while social auth is a service within a realm, the specific configuration object required is the client.
A realm policy (D) governs authorization after login, but does not enable the social login process itself. Therefore, the OAuth2 client configuration is the technical prerequisite for establishing the trust relationship with the external provider.
NEW QUESTION # 42
Which OAuth2 flow is most appropriate for a microservice requesting an access token?
- A. Client credentials flow
- B. Resource owner flow
- C. Authorization code flow
- D. Implicit grant flow
Answer: A
Explanation:
In PingAM 8.0.2, choosing the correct OAuth2 grant flow depends entirely on the type of client and the nature of the resource access. For a microservice (a machine-to-machine scenario), the Client Credentials Flow (defined in RFC 6749) is the industry-standard and documented best practice.
A microservice is categorized as a Confidential Client because it runs on a secure server where it can safely store its own credentials (client_id and client_secret). In a microservice-to-microservice interaction, there is no "end-user" present to provide consent or enter a password. Instead, the microservice authenticates as itself to the PingAM token endpoint.
According to the PingAM "OAuth 2.0 Grant Flows" documentation:
The microservice sends a POST request to the /oauth2/access_token endpoint.
The request includes the grant_type=client_credentials parameter along with the client's own authentication (such as Basic Auth with secret, or mTLS).
PingAM validates the client's credentials and scopes.
Since this is a machine-to-machine flow, PingAM bypasses the user authorization (consent) step and issues an Access Token directly to the service.
Why other options are incorrect:
Implicit flow (A) and Authorization code flow (B) are designed for scenarios where a human user is present to authenticate and authorize access.
Resource owner flow (D) (also known as the Password grant) requires the service to handle a user's cleartext credentials, which is a major security risk and is deprecated in modern security architectures.
The Client Credentials flow ensures that microservices can securely obtain the tokens necessary to communicate with other protected APIs within the ecosystem without requiring human intervention.
NEW QUESTION # 43
What is the purpose of HTTP-only cookies?
- A. Cookies can only be transmitted over HTTP
- B. Cookies can only be transmitted over HTTPS
- C. Cookies can not be read by client-side scripts
- D. Cookies can not be read by the server
Answer: C
Explanation:
In the "Additional Cookie Security" section of the PingAM 8.0.2 documentation, HttpOnly is described as a critical security attribute for session cookies (like iPlanetDirectoryPro). Its primary purpose is to mitigate the risk of session hijacking via Cross-Site Scripting (XSS) attacks.
When a cookie is marked with the HttpOnly flag, the browser is instructed to restrict access to that cookie. Specifically, it prevents client-side scripts-such as those written in JavaScript-from accessing the cookie through the document.cookie API. If an attacker successfully injects a malicious script into a page, the script will be unable to "read" the session token, even though the cookie is still automatically sent by the browser with every valid HTTP request to the server.
Option B describes the Secure flag, which ensures cookies are only sent over encrypted (HTTPS) connections.
Option C is incorrect because the server must be able to read the cookie to validate the user's session.
Option D is a common misconception; the HttpOnly flag does not restrict the transport to "HTTP-only" (non-secure) protocols; rather, it restricts the access method within the browser environment.
By default, PingAM 8.0.2 enables the HttpOnly flag for all session cookies. This is considered a best practice in modern identity management because it ensures that even if a web application has a vulnerability that allows for script injection, the user's primary authentication token remains protected from being exfiltrated by the attacker's script.
NEW QUESTION # 44
What is a SAML2 artifact?
- A. The SAML2 assertion
- B. The SAML2 binding name
- C. A value sent by the service provider to retrieve the assertion
- D. The name of a specific attribute in the assertion
Answer: C
Explanation:
In SAML 2.0, an Artifact is a reference (a "pointer" or "ticket") used in the SAML Artifact Binding.5 This is an alternative to the more common POST or Redirect bindings where the actual XML assertion is sent through the user's browser.
According to the PingAM "SAML 2.0 Bindings" documentation:
When using the Artifact binding, the Identity Provider (IdP) does not send the full SAML Assertion through the browser.6 Instead, it sends a small, opaque string called the Artifact to the Service Provider (SP).
Issuance: The IdP stores the real assertion in its own local memory/cache and sends the Artifact to the SP via the browser redirect.
Resolution: The Service Provider receives the Artifact and then makes a direct, secure back-channel call (SOAP over HTTPS) to the IdP's Artifact Resolution Endpoint.
Exchange: The SP presents the Artifact, and the IdP returns the actual SAML Assertion.
Therefore, the Artifact is the value sent to retrieve the assertion (Option D). It is not the assertion itself (Option A), nor is it a binding name or an attribute name. The Artifact binding is often used for security reasons, as it prevents the sensitive assertion data from ever passing through the user's browser, thus mitigating certain types of interception attacks.
NEW QUESTION # 45
Which multi-factor authentication methods require a separate device and an application?
- A. Push, WebAuthn
- B. WebAuthn, Open Authentication
- C. Open Authentication, Push
- D. Push, WebAuthn, Open Authentication
Answer: C
Explanation:
PingAM 8.0.2 supports various Multi-Factor Authentication (MFA) methods, each with different hardware and software requirements.7 The question asks specifically for methods that require both a separate device and a specific application.
Push Authentication: This requires a mobile device (separate from the computer used to log in) and the ForgeRock/Ping Authenticator app (or a custom app using the SDK) to receive and approve the notification.8 Open Authentication (OATH): This refers to TOTP (Time-based One-Time Password). It requires a separate device (smartphone or hardware token) and an application (like ForgeRock Authenticator, Google Authenticator, or Authy) to generate the 6-digit rotating codes.
Why WebAuthn is excluded: While WebAuthn (Option A, B, and C) can use separate devices (like a YubiKey or a secondary phone), it is specifically designed to work natively with the browser and the operating system (using the FIDO2 standard). It does not require a specific "Authenticator Application" to be installed by the user; instead, it uses the platform's built-in authenticators (like TouchID, FaceID, or Windows Hello) or a hardware key handled directly by the browser's WebAuthn API.
Therefore, the two methods that strictly fit the "Separate Device + App" criteria in the PingAM ecosystem are Open Authentication and Push, making Option D the correct answer.
NEW QUESTION # 46
Which token transformation is not supported by the REST security token service?
- A. Kerberos -> SAML2
- B. Username token -> SAML2
- C. OpenID Connect -> SAML2
- D. PingAM SessionToken -> SAML2
Answer: C
Explanation:
The Security Token Service (STS) in PingAM 8.0.2 acts as a broker that translates security tokens from one format to another, allowing for interoperability between different security domains (e.g., translating a web-based session into a SOAP-based SAML assertion).
According to the PingAM "Security Token Service (STS)" documentation and the "Rest-Based STS" reference, the service supports a specific set of input and output token types. Supported input (source) tokens typically include Username Tokens, SAML2 Tokens, X.509 Certificates, Kerberos Tokens, and the internal PingAM Session Token (SSOToken). The service can transform these into output (target) tokens such as SAML2 Assertions or OIDC ID Tokens.
Analysis of the options:
Option A (Username token -> SAML2): Supported. This is a common use case where a client provides a username and password (WS-Security format) and receives a SAML2 assertion.
Option B (Kerberos -> SAML2): Supported. Used in Windows Desktop SSO environments where a SPNEGO/Kerberos token is exchanged for a SAML assertion for cloud applications.
Option D (PingAM SessionToken -> SAML2): Supported. This allows a user who already has a valid AM session to obtain a SAML2 token for a back-end web service.
Option C (OpenID Connect -> SAML2): Not supported by the REST STS implementation in version 8.0.2. While PingAM supports OIDC and SAML2 federation generally, the specialized STS service does not list an OIDC ID Token as a valid input token type for transformation into a SAML2 assertion within its specific state machine. OIDC to SAML "bridging" is typically handled via the standard Federation service rather than the STS broker.
NEW QUESTION # 47
What does the acronym SAML stand for?
- A. Security Assertion Markup Language
- B. Strong Assertion Markup Language
- C. Scoped Assertion Markup Language
- D. Secure Assertion Markup Language
Answer: A
Explanation:
As defined in the PingAM 8.0.2 documentation under "Introduction to SAML 2.0," the acronym SAML stands for Security Assertion Markup Language. It is an XML-based framework specifically designed for communicating user authentication, entitlement, and attribute information between distinct entities. In a typical federation scenario, these entities are the Identity Provider (IdP), which asserts the identity of the user, and the Service Provider (SP), which consumes the assertion to grant access to resources.
SAML is governed by OASIS and has become the industry standard for cross-domain Single Sign-On (SSO). The "Security" aspect of the name refers to the cryptographic methods used to ensure the integrity and confidentiality of the assertions. "Assertion" refers to the specific statements made by the IdP about a subject (usually a user). These assertions can include Authentication Statements (proving the user logged in), Attribute Statements (providing data like email or group membership), and Authorization Decision Statements (indicating what the user is permitted to do). PingAM 8.0.2 fully supports the SAML 2.0 core specifications, protocols, bindings, and profiles. Understanding this fundamental terminology is essential for administrators configuring "Circle of Trust" (CoT) environments or importing metadata from external partners, as the XML namespaces and schema definitions consistently reference the "urn:oasis:names:tc:SAML:2.0" identifier.
NEW QUESTION # 48
In a PingAM cluster, how is the debug level set?
- A. It is not recommended to change the level at all
- B. On a per-instance basis in the admin console
- C. On a per-site basis in the admin console
- D. On each server in the debug.properties file
Answer: B
Explanation:
Debugging a PingAM 8.0.2 environment is essential for troubleshooting issues that occur at the engine level. In a multi-server deployment (a cluster), different servers may be experiencing different local issues (e.g., filesystem permissions or local JVM constraints). Therefore, debug settings are managed at the server-specific level rather than the global site level.
According to the "Debug Logging" and "Server Settings" documentation:
The debug level (e.g., error, warning, message, info) is configured on a per-instance basis. In the PingAM Administrative Console, an administrator navigates to Deployment > Servers > [Server Name] > Debugging. Here, they can set the "Debug Level" and "Debug Output" (file vs. console).
Setting the level per instance allows an administrator to increase verbosity on a single "problematic" node without flooding the logs and impacting the performance of the entire healthy cluster. While these settings eventually modify internal properties, the Admin Console is the primary and recommended interface for making these changes in version 8.0.2.
Why other options are incorrect:
Option A: While legacy versions of OpenAM used a local debug.properties file, modern PingAM stores these settings in the Configuration Store, though they are applied to specific server instances.
Option C: A "Site" is a logical grouping for load balancing. Setting a debug level on a site would force all servers in that site to change simultaneously, which is often undesirable for targeted troubleshooting.
Option D: Changing the debug level is a standard and recommended practice for troubleshooting, provided it is returned to a lower level (like error or warning) once the issue is resolved to save disk space and CPU.
NEW QUESTION # 49
If PingAM is deployed in Apache Tomcat under /openam, what file system backups should be taken when PingAM needs to be upgraded?
- A. Execute the PingAM backup script in /path/to/tomcat/webapps/openam/
- B. Back up /path/to/tomcat/webapps/openam/, <home directory>/openam/ and <home directory>/.openamcfg/
- C. Back up /path/to/tomcat/webapps/openam/ only
- D. No explicit backups are required for PingAM as this is done automatically
Answer: B
Explanation:
According to the PingAM 8.0.2 Upgrade Guide and the "Plan the upgrade" documentation, a successful upgrade and potential rollback strategy rely on capturing the complete state of the application across three distinct locations on the filesystem. When PingAM is deployed in a container like Apache Tomcat, the configuration is not stored within the WAR file itself but is distributed to maintain persistence across redeployments.
The three critical areas that must be backed up are:
The Web Application Directory (/path/to/tomcat/webapps/openam/): This contains the expanded binaries, JSPs, and web-level configurations. While the upgrade involves replacing the openam.war file, backing up this folder preserves any manual customizations made to the UI, CSS, or specific library additions (JARs) in the WEB-INF/lib folder.
The Configuration Directory (<home directory>/openam/ or similar): This is the most vital component. By default, PingAM stores its instance-specific configuration, cryptographic keys (keystores), and internal metadata here. For file-based configurations (FBC), this directory holds the entire system state. Even with an external PingDS configuration store, this directory contains the bootstrap file and security secrets required to connect to that store.
The Bootstrap Configuration File (<home directory>/.openamcfg/): This hidden directory contains a file (usually named after the deployment path, e.g., am or openam) that tells the PingAM binaries where the actual configuration directory is located. Without this pointer, a restored PingAM instance will behave like a fresh installation and prompt for a new setup.
The documentation explicitly warns: "Always back up your deployment before you upgrade... For AM servers, you can roll back by restoring from a file system backup of the deployed servers and their configuration directories." Relying only on the webapps folder (Option A) or assuming automatic backups (Option B) will lead to data loss or an unrecoverable state.
NEW QUESTION # 50
When making a request to the /oauth2/access_token endpoint using the JWT profile client authentication method, which parameter is used to provide the JWT value?
- A. client_id
- B. client_credentials
- C. client_assertion
- D. client_token_value
Answer: C
Explanation:
PingAM 8.0.2 supports advanced client authentication methods defined in the OpenID Connect and OAuth 2.0 specifications, including private_key_jwt and client_secret_jwt. These methods allow a client to authenticate without sending a static password/secret in the request. Instead, the client generates and signs a JSON Web Token (JWT).
According to the "OAuth 2.0 Client Authentication" and "JWT Profile for Client Authentication" (RFC 7523) documentation, when a client sends this JWT to the /oauth2/access_token endpoint, it must use the client_assertion parameter.
The request must also include the client_assertion_type parameter, which must be set to the constant value: urn:ietf:params:oauth:client-assertion-type:jwt-bearer.
Option A (client_credentials) is a grant type, not a parameter for providing a JWT.
Option B (client_token_value) is not a standard OAuth2 parameter name.
Option C (client_id) is often included in the request, but it is the identifier of the client, not the container for the cryptographic assertion itself.
When PingAM receives a request with a client_assertion, it extracts the JWT, verifies the signature using the client's public key (stored in the client's profile or retrieved via a JWKS URI), and validates the standard claims (iss, sub, aud, exp). This method is significantly more secure than simple secrets because it proves the client possesses the private key and limits the window for replay attacks through the token's expiration claim.
NEW QUESTION # 51
Which of the following parameters must be provided by the edge client when requesting step-up authentication or transactional authorization?
- A. authIndexType and authIndexValue
- B. service, authIndexType, and authIndexValue
- C. service and ForceAuth
- D. ForceAuth, authIndexType, and authIndexValue
Answer: A
Explanation:
In PingAM 8.0.2, when a client needs to trigger a specific authentication path-such as a higher-level tree for step-up authentication or a specific module for transactional authorization-it must tell the /authenticate endpoint which "Index" to use.
According to the PingAM "Authenticate over REST" and "Session Upgrade" documentation, these are governed by two mandatory parameters:
authIndexType: This defines the category of the authentication mechanism being requested. Valid values include service (for Authentication Trees/Chains), module (for individual modules), or level (to request any mechanism that meets a specific Auth Level).
authIndexValue: This defines the name of the specific instance. For example, if authIndexType is service, the authIndexValue would be the name of the Authentication Tree (e.g., StepUpMFA).
For a step-up or transactional request to succeed, the client must send these two parameters. While service (Option B and D) is a common value for authIndexType, it is not a parameter name itself. ForceAuth (Option C and D) is an optional boolean used to force a fresh login even if a session exists, but it is not a requirement for the basic routing of the request to the correct tree. Therefore, authIndexType and authIndexValue (Option A) are the fundamental parameters required by the AM engine to identify and initiate the intended authentication journey.7
NEW QUESTION # 52
What should be configured in PingAM if you are using an LDAP directory service that does not support persistent search?
- A. Enable user data caching, which will have a negative impact on performance
- B. Disable user data caching, which will have a negative impact on performance
- C. Disable user data caching, which will have a positive impact on performance
- D. Enable user data caching, which will have a positive impact on performance
Answer: B
Explanation:
Persistent Search is an LDAP control that allows a client (like PingAM) to receive real-time notifications from the Directory Server (like PingDS) whenever a user record is modified. PingAM 8.0.2 uses this to maintain its User Data Cache.
According to the "Identity Store Configuration" and "Tuning AM" documentation:
When persistent search is supported, PingAM caches user profile data in memory to speed up authentication and authorization decisions. When a change happens in the LDAP store, the directory server "pushes" the update to AM via the persistent search connection, and AM updates its cache immediately.
If the LDAP directory does not support persistent search (common in some legacy or highly restricted environments):
Cache Inconsistency: If caching were enabled, PingAM would not know when a user's attribute (like a group membership) had changed in the back-end. The cache would become "stale," leading to incorrect authorization decisions.
Required Configuration: The administrator must Disable user data caching to ensure that every request results in a direct query to the LDAP server, ensuring "Read-through" accuracy.
Performance Impact: Disabling the cache has a negative impact on performance (Option D) because every policy evaluation or session check now requires a synchronous network round-trip to the LDAP server, increasing latency and putting higher CPU/IO load on the directory.
Therefore, for directories lacking persistent search, disabling the cache is necessary for data integrity but comes at a significant performance cost.
NEW QUESTION # 53
Which organization sets, maintains, and governs the SAML2 standard?
- A. IETF
- B. WC3
- C. ISC2
- D. OASIS
Answer: D
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 # 54
What should be executed to ensure a successful upgrade when PingAM requires a version upgrade?
- A. Post-upgrade, run a set of functional and non-functional tests
- B. Post-upgrade, run a set of non-functional tests
- C. Post-upgrade, run a set of functional tests
- D. Post-upgrade, set the PingAM Version Control Flag to the correct version
Answer: A
Explanation:
Upgrading PingAM 8.0.2 is a complex process that involves updating binaries, modifying schemas in the configuration store, and potentially migrating scripts to the "Next-Generation" scripting engine. To ensure that the system is not only "running" but also "production-ready," a comprehensive testing phase is required.
According to the "Post-Upgrade Tasks" and "Best Practices for Upgrading" documentation:
A successful upgrade verification must cover two distinct categories of testing:
Functional Tests: These verify that the core features still work as intended. Can users log in? Do the authentication trees execute correctly? Are SAML assertions being generated? This ensures the "Logic" of the identity platform is intact.
Non-Functional Tests: These are equally critical in an upgrade scenario. An upgrade can sometimes introduce performance regressions, change the way memory is utilized by the JVM, or alter the connection pool behavior to the CTS. Testing for performance, high availability (failover), security (vulnerability scanning), and monitoring ensures the system can handle production loads and meets the organization's Service Level Agreements (SLAs).
While setting version flags (Option D) might be a technical step in some internal processes, it does not "ensure a successful upgrade" in the way that rigorous validation does. Running only functional tests (Option A) or only non-functional tests (Option C) leaves the environment vulnerable to either logic errors or system crashes. Thus, the verified best practice is to run both functional and non-functional tests (Option B) before redirecting production traffic to the upgraded instances.
NEW QUESTION # 55
Does the user who runs the PingAM process need to have a home directory?
- A. Yes, because this is where PingAM stores some of the configuration
- B. Yes, because this is where PingAM stores a pointer to the configuration
- C. Yes, because otherwise the process cannot listen on a port below 1024
- D. No, not at all
Answer: B
Explanation:
According to the PingAM 8.0.2 Installation Guide, the user account on the operating system that runs the web application container (such as Apache Tomcat) must have a home directory. This requirement is critical for the "Bootstrap" process of the application.
When PingAM starts for the first time or after a restart, the binaries need to know where the configuration data resides. PingAM looks for a hidden directory in the user's home directory named .openamcfg (or a similar name based on the deployment path). Inside this directory, AM creates and reads a file that contains the absolute path to the actual configuration directory (e.g., /home/tomcat/openam). This file acts as the pointer or "bootstrap" record.
If the user running the process does not have a home directory, the AM application will fail to initialize because it cannot create this bootstrap pointer. This often results in a "Configuration failed" error or the application reverting to an "unconfigured" state upon every restart. While it is possible to override the location of the configuration directory using JVM system properties (like -Dcom.sun.identity.configuration.directory), the default behavior and best practice documented for standard deployments assume the existence of a home directory for the service user. This ensures that configuration remains persistent and isolated from the web container's temporary application files. Option C is incorrect as port listening restrictions are handled by the OS kernel/root privileges, not the existence of a home directory.
NEW QUESTION # 56
Which PingAM feature only uses the PingAM keystore?
- A. OAuth2 providers
- B. Client-side sessions
- C. Authentication trees
- D. Persistent Cookie node
Answer: B
Explanation:
In PingAM 8.0.2, the management of cryptographic material has evolved toward the Secret Store framework, which allows secrets to be stored in various locations (Filesystem, HSM, or Environment Variables). However, for specific core features, the internal PingAM keystore (historically keystore.jks) remains the primary repository for the keys used to protect session integrity.
According to the "Client-side Session Security" documentation, when a realm is configured for Client-side sessions, the entire state of the user's session is encapsulated within a signed and encrypted JSON Web Token (JWT). This JWT is then stored in the user's browser cookie. To ensure that this token cannot be tampered with or read by unauthorized parties, PingAM must sign and encrypt the payload. The AM engine is hardcoded to look for the specific aliases (such as am.services.session.encryption and am.services.session.signing) within the default-keystore secret store, which points directly to the PingAM keystore.
While other features like OAuth2 providers (Option D) and the Persistent Cookie node (Option B) utilize secret stores, they are designed to be highly flexible and can be configured to use keys from any defined secret store in the realm. Authentication trees (Option C) are logical constructs and do not "use" the keystore directly, although individual nodes within a tree might. The distinction for Client-side sessions is that the feature's fundamental security model is built specifically around the cryptographic keys managed within the AM keystore to provide "stateless" session management. Administrators must ensure that the same keystore and aliases are shared across all nodes in a cluster to allow any AM instance to validate a client-side session token issued by another node.
NEW QUESTION # 57
What are the possible outcomes of the Push Result Verifier node?
- A. Success, Failure, Expired, Waiting, Retry
- B. Success, Failure, Waiting, Retry
- C. Success, Failure, Expired, Retry
- D. Success, Failure, Expired, Waiting
Answer: D
Explanation:
The Push Result Verifier node is a core component of the "MFA: Push Authentication" journey in PingAM 8.0.2. Its primary function is to check the status of a push notification that was previously dispatched to a user's mobile device (usually via the Push Sender node).22 According to the "Authentication Node Reference" for version 8.0.2, the node evaluates the state of the push request and yields exactly four distinct outcomes:
Success: This path is followed if the user has actively approved the push notification on their registered device using the ForgeRock/Ping Authenticator app.
Failure: This path is taken if the user explicitly denies or rejects the push notification on their device, indicating a potential unauthorized login attempt.
Expired: This outcome occurs if the notification reaches its "Message Timeout" limit (defined in the Push Sender node) without any response from the user.23 In standard trees, this path often loops back to allow the user to try a different MFA method or resend the push.
Waiting: This outcome is triggered if a response has not yet been received but the timeout has not yet been reached. This is used in conjunction with a Push Wait or Polling mechanism to create a "check-and-loop" logic until a final result (Success, Failure, or Expired) is determined.
The Retry outcome (mentioned in other options) is notably absent from this specific node's metadata. While a "Retry" might be implemented in the overall tree logic (for example, by using a Retry Limit Decision node after an Expired outcome), the Push Result Verifier node itself only reports the state of the specific push transaction it is tracking. Understanding these four discrete states is vital for designing resilient authentication journeys that handle user delays or network issues gracefully.
NEW QUESTION # 58
When defining a policy and specifying a resource pattern, which of the following statements is true concerning the difference between the wildcards * and -*-?
- A. The wildcard * and the wildcard -*- can be mixed liberally within the same pattern
- B. The wildcard * will match multiple levels in a path, whereas -*- will match only a single level
- C. The wildcard * will match query parameters, whereas -*- will not match query parameters.
- D. Neither the * wildcard nor the -*- wildcard can be used to match the port number
Answer: B
Explanation:
When configuring Authorization Policies in PingAM 8.0.2, defining the Resource Pattern is critical for determining which URLs the policy applies to. PingAM uses specific wildcard symbols to represent dynamic parts of a URI, but they behave differently regarding directory depth.
According to the PingAM documentation on "Policies and Resource Types":
The * Wildcard (One-Level Wildcard): This wildcard matches characters within a single path level. It does not match forward slashes (/). For example, http://example.com/* will match http://example.com/page1 but will not match http://example.com/folder/page1.
The -*- Wildcard (Multi-Level Wildcard): This wildcard is designed to match any number of characters, including forward slashes (/), effectively spanning multiple levels of a directory hierarchy. For example, http://example.com/-*- will match http://example.com/page1, http://example.com/folder/page1, and even http://example.com/deeply/nested/resource.
Statement B is the correct technical distinction. Statement A is incorrect because query parameters are typically handled by specifically enabling "Query Parameter Matching" in the Resource Type configuration, rather than being a primary distinction between these two wildcards. Statement C is technically discouraged because mixing them can lead to unpredictable or overly broad matches that are difficult to debug. Statement D is incorrect because wildcards can be used in the host/port portion of the URL if the resource type is configured to support it. Understanding the difference between single-level (*) and multi-level (-*-) matching is a fundamental skill for AM policy administrators to prevent security gaps.
NEW QUESTION # 59
Which of the following code examples inserts a may_act claim to the resulting token in a PingAM implementation?
- A. var mayAct = /* is a JSON object with may act property data */ token.setMayAct(mayAct)
- B. var mayAct = /* is a JSON object with may act property data */ token.addMayAct(mayAct)
- C. var mayAct = /* is a JSON object with may act property data */ requestedToken.setMayAct(mayAct)
- D. var mayAct = /* is a JSON object with may act property data */ requestedToken.addMayAct(mayAct)
Answer: D
Explanation:
In PingAM 8.0.2, the OAuth 2.0 Token Exchange (RFC 8693) implementation allows for complex identity delegation scenarios. The may_act claim is a specific claim used to indicate that one entity is authorized to act on behalf of another. When customizing the behavior of token exchange via the OAuth2 Token Exchange Script, developers interact with specific scriptable objects provided by the PingAM engine.
According to the "Scripting API" for OAuth2 and the "Token Exchange" developer guide, the requestedToken object is the primary interface used to modify the structure of the token being issued during the exchange. To insert the may_act claim, the API provides the addMayAct() method.
The may_act claim is technically a JSON object that contains a sub (subject) claim of the entity that is allowed to act as the subject of the token. In the scripting environment:
The requestedToken variable represents the token currently being minted.
The .addMayAct() method is the defined function signature to append this delegation metadata.
Why other options are incorrect:
Options A and D: The object name token is not the standard binding used for the target token in the Token Exchange script context; requestedToken is the correct binding.
Option C: The method name setMayAct is incorrect. The PingAM API uses the add prefix for these types of claims (similar to addActor), reflecting the underlying structure where these claims are added to the claim set of the JWT.
Using the correct syntax requestedToken.addMayAct(mayAct) ensures that the resulting Access Token or ID Token contains the correctly formatted delegation information required by resource servers to validate that the "Actor" has the permission to represent the "Subject."
NEW QUESTION # 60
Which feature of PingAM protects against cookie hijacking in a cross-domain single sign-on environment?
- A. Restricted tokens1
- B. Bound tokens
- C. Random tokens
- D. Lockout tokens
Answer: A
Explanation:
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
NEW QUESTION # 61
A PingAM administrator wants to deny access to an area of a protected application if the end user has been logged in for more than 10 minutes. How can this be achieved?
- A. Use a policy with a Scripted environment condition
- B. Use a policy with a Time environment condition
- C. Use a policy with a Current session properties environment condition
- D. Use a policy with an Active session time environment condition
Answer: A
Explanation:
To enforce complex authorization logic based on session duration, PingAM 8.0.2 administrators must move beyond the static "Out-of-the-Box" conditions.
Analysis of the options based on the "Policy Conditions" documentation:
Time Condition (Option A): This condition is used to restrict access based on the clock time of day or day of the week (e.g., "Allow access only between 9 AM and 5 PM"). It does not track the elapsed time of a specific user session.
Current Session Properties (Option B): This condition checks for the presence of specific key-value pairs in a session. While a session contains a startTime property, this condition is designed for matching static values (like department=HR), not for performing mathematical time calculations.
Active Session Time (Option D): This is not a standard default condition name in the PingAM 8.0.2 policy engine.
The Correct Approach (Option C): A Scripted Policy Condition is required for this use case. Within a Policy Condition script, the administrator has access to the session object. The script can retrieve the startTime (or creationTime) of the session and compare it against the current system time (currentTime).
Example logic in the script:
var sessionStartTime = session.getProperty("startTime");
var maxDuration = 10 * 60 * 1000; // 10 minutes in milliseconds
if ((currentTime - sessionStartTime) > maxDuration) { authorized = false; } By using a script, PingAM can dynamically calculate the age of the session at the moment of the access request and return a "Deny" decision if the 10-minute threshold has been exceeded. This provides the granular control needed for high-security environments where "session freshness" is a requirement for specific sensitive resources.
NEW QUESTION # 62
Which of the following options represents best practice for an implementation that configures an ID token in a subject condition for policies validating the token's claims?
- A. Policy evaluation only validates the claims, not the ID token. The ID token should be validated after making the policy evaluation request
- B. Policy evaluation validates the claims and the ID token. There is no need to validate the ID token before the policy is evaluated
- C. Policy evaluation only validates the claims, not the ID token. The ID token should be validated before making the policy evaluation request
- D. Policy evaluation only validates the claims, not the ID token. There is no need to validate the ID token that was obtained before the policy is evaluated
Answer: C
Explanation:
In PingAM 8.0.2, Authorization Policies can be configured to use complex conditions to determine if access should be granted. When a policy uses a Subject Condition based on an OpenID Connect (OIDC) ID Token, the policy engine looks for specific claims within that token (such as group membership or a specific user ID).
According to the "Authorization and Policy Evaluation" best practices, it is crucial to understand the separation of concerns between the Policy Decision Point (PDP) and the client. The PingAM policy engine is designed to evaluate logic-it checks if claimX == valueY. However, the policy engine typically does not perform a full cryptographic validation of the ID token's signature every time it evaluates a condition, especially if the token is passed as a string in the evaluation request.
Therefore, the best practice is as follows:
The client application or the PEP (Policy Enforcement Point) must validate the ID token (ensuring it is signed by a trusted provider, has not expired, and contains the correct audience) before sending the claims to the AM policy service for evaluation. If an unvalidated or forged token is used to supply claims for a policy request, and the policy engine assumes the input is "trusted," it could result in unauthorized access.
By validating the token first (Option C), the implementation ensures that only legitimate identity data is processed by the authorization logic. Option D is incorrect because the policy engine's primary role is decision-making based on presented attributes, not act as a full OIDC validation service during a REST evaluation call. Option B is a security risk as it ignores the necessity of cryptographic proof of identity.
NEW QUESTION # 63
What is session denylisting used for?
- A. Keeping track of restricted sessions
- B. Keeping track of session inactivity
- C. Keeping track of absolute session timeouts
- D. Keeping track of logged out sessions
Answer: D
Explanation:
Session Denylisting is a critical security feature in PingAM 8.0.2, primarily used when a realm is configured for client-side sessions.9 In a client-side session model, the session state is stored in a signed and encrypted JWT within the user's browser cookie rather than in the server's memory or the Core Token Service (CTS).10 Because the server does not "own" the session state, a logout event typically only involves deleting the cookie from the browser. However, if a malicious actor had previously copied that cookie, they could still use it until it naturally expires.
To solve this, PingAM uses Session Denylisting to keep track of logged out sessions.11 When a user logs out, or when a session is invalidated (e.g., during a session upgrade or administrative action), AM records the session identifier in a denylist stored within the Core Token Service (CTS).12 For every subsequent request, AM checks the incoming client-side session token against this denylist.13 If the session ID is found in the denylist, AM rejects the token as invalid, even if the cryptographic signature is correct and the expiration time has not passed.
The documentation emphasizes that this feature is essential for "tracking session logouts across multiple AM servers" in a cluster. Without denylisting, there would be no way to perform a "global logout" for client-side sessions that is immediately effective across all nodes.14 Administrators can configure properties such as the Denylist Purge Delay (to account for clock skew) and the Denylist Poll Interval (to balance security speed with system performance).15 By effectively managing the lifecycle of revoked tokens, session denylisting ensures that a logout is a cryptographically and operationally certain event.
NEW QUESTION # 64
Examine the following JWT client assertion in JSON format. From the subset of claims listed below, which claim can be optional?
JSON
JSON
{
"iss": "myClient",
"sub": "myClient",
"aud": "https://am.example.com/login/oauth2/access_token",
"jti": "id012345",
"exp": 1633363568,
"iat": 1633356368
}
- A. jti
- B. aud
- C. sub
- D. iss
Answer: A
Explanation:
When an OAuth2 client uses Private Key JWT or Client Secret JWT for authentication at the PingAM 8.0.2 token endpoint, it must present a JWT (JSON Web Token) containing specific claims that identify and authorize the client. This is governed by the OIDC and OAuth2 JWT Profile specifications (RFC 7523).
According to the PingAM documentation on "OAuth 2.0 Client Authentication" and the "JWT Profile for Client Authentication":
iss (Issuer): Mandatory. This must be the client_id of the OAuth2 client.
sub (Subject): Mandatory. This must also be the client_id of the OAuth2 client (as the client is the subject of the authentication).
aud (Audience): Mandatory. This must be the URL of the PingAM OAuth2 service (the token endpoint) or the issuer URL.
exp (Expiration Time): Mandatory. This protects against the long-term use of intercepted assertions.
The jti (JWT ID) (Option A) provides a unique identifier for the token. In the context of standard JWT validation, jti is used to prevent replay attacks by ensuring that a specific token is only processed once. While highly recommended for security hardening, the PingAM 8.0.2 technical reference for OAuth2 client assertions marks jti as optional unless the server is explicitly configured to require it for replay detection. Without a jti, PingAM will still validate the iss, sub, aud, and exp claims to authenticate the client. Therefore, among the choices provided, jti is the claim that can be omitted without inherently violating the base OAuth2 JWT authentication request requirements.
NEW QUESTION # 65
A user's SSOTokenID is stored in a cookie when they successfully log in. What is the name of the PingAM property used to configure this cookie?
- A. com.iplanet.am.cookie.name
- B. comIplanetAmSessionCookieName
- C. com.sun.identity.agents.config.cookie.name
- D. iPlanetDirectoryPro
Answer: A
Explanation:
In PingAM 8.0.2, once a user successfully completes an authentication journey, the server issues a session token. For browser-based clients, this token is typically delivered via an HTTP cookie. The server-side property that defines the name of this specific cookie is com.iplanet.am.cookie.name.
According to the "Global Properties" and "System Configuration" documentation, this property is found under the Session service settings. By default, its value is set to iPlanetDirectoryPro (Option B). While iPlanetDirectoryPro is the default value of the cookie name, the question asks for the name of the property used to configure it.
Administrators often modify this property for security reasons to hide the fact that they are using PingAM or to avoid conflicts with other legacy systems. It is important to note that if this property is changed in the AM server, the corresponding configuration in all Policy Agents (Web or Java Agents) must also be updated to look for the new cookie name, otherwise, the agents will not be able to find the user's session and will redirect them to login repeatedly. Option D refers to an agent-side configuration key, but the central "Source of Truth" for the session cookie name within the AM platform is the server-side property com.iplanet.am.cookie.name.
NEW QUESTION # 66
......
Ping Identity PT-AM-CPE Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
Pass Your Ping Identity Certifications PT-AM-CPE Exam on Mar 07, 2026 with 102 Questions: https://www.suretorrent.com/PT-AM-CPE-exam-guide-torrent.html
PT-AM-CPE Free Exam Study Guide! (Updated 102 Questions): https://drive.google.com/open?id=19qe3mK0NE4ahxm0iVO75OzWmJhtGbHNA