Online test version is the best choice for IT person who want to feel the atmosphere of Ping Identity real exam. And you can practice latest PT-AM-CPE exam questions on any electronic equipment without any limit. Besides, there is no need to install any security software because our PT-AM-CPE Vce File is safe, you just need to click the file and enter into your password.
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
| Topic 5 |
|
>> Latest PT-AM-CPE Test Practice <<
More and more people look forward to getting the PT-AM-CPE certification by taking an exam. However, the exam is very difficult for a lot of people. Especially if you do not choose the correct study materials and find a suitable way, it will be more difficult for you to pass the exam and get the PT-AM-CPE related certification. If you want to get the related certification in an efficient method, please choose the PT-AM-CPE study materials from our company.
NEW QUESTION # 31
Why should module-based authentication be disabled in production?
Answer: A
Explanation:
In PingAM 8.0.2, there is a critical distinction between Tree-based (or Chain-based) authentication and Module-based authentication. Module-based authentication is a legacy feature that allows a user to target an individual authentication module directly (e.g., .../UI/Login?module=DataStore).
According to the "Security Considerations" and "Hardening PingAM" documentation, module-based authentication poses a significant security risk and should be disabled in production. This is because it allows a user to bypass steps in an authentication chain (Option C).
If an administrator has designed a secure "Chain" that requires both a DataStore (password) check AND a One-Time Password (MFA) check, the intention is for these to be inseparable. However, if module-based authentication is enabled, a malicious user or a tester could bypass the MFA requirement by crafting a URL that calls only the "DataStore" module. This effectively circumvents the multi-factor security logic intended by the administrator.
To mitigate this, PingAM provides a global and realm-level setting to "Disable Module-based Authentication." Once disabled, PingAM will only process authentication requests that target a named Authentication Tree or Chain, ensuring that the user is forced through the entire sequence of nodes and logic defined by the security architect.
NEW QUESTION # 32
Which feature of PingAM protects against cookie hijacking in a cross-domain single sign-on environment?
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 # 33
If the session cookie is configured as a domain based cookie for the am.example.com domain, in which of the following domains is the cookie visible?
A . example.com
B . am.example.com
C . sub.am.example.com
D . login.am.example.com
Answer: D
Explanation:
This question tests the understanding of Session Cookie Domains and browser behavior in a PingAM 8.0.2 deployment. According to the "Secure Session Cookies" documentation, the Cookie Domain setting in a realm determines the scope of the SSO token.
Standard browser cookie rules (RFC 6265) dictate that a cookie set for a specific domain is visible to that domain and all of its subdomains. However, a cookie is not visible to a parent domain or a "sibling" domain.
In this scenario, the cookie is set for am.example.com:
A . example.com: This is the parent domain. A cookie set for am.example.com is not visible here. To make it visible to example.com, the cookie domain would have to be explicitly set to .example.com.
B . am.example.com: The cookie is directly set for this domain, so it is obviously visible.
C . sub.am.example.com: This is a subdomain of am.example.com. Under standard cookie rules, it will receive the cookie.
D . login.am.example.com: While this is also a subdomain, the question implies a specific selection.
Looking at the provided options (B and C), Option C accurately reflects the inheritance rule where the domain itself and its immediate sub-levels are covered. While login.am.example.com (Option D) is technically also a subdomain, the standard documentation examples for "Cross-domain" or "Sub-domain" visibility typically emphasize the relationship between the primary AM host and its child applications. Therefore, the combination of B and C is the most accurate representation of how the browser handles the scope of an am.example.com cookie.
NEW QUESTION # 34
To ensure the user's full name is displayed on the consent screen for an OpenID Connect application, which string should be added into the Support Claims property on the OpenID Connect tab page of the OAuth2 Provider service in PingAM?
Answer: C
Explanation:
When a client requests an OpenID Connect (OIDC) scope (like profile), PingAM 8.0.2 may present a Consent Screen to the user, asking permission to share specific claims. To make this screen user-friendly, PingAM allows administrators to map technical claim names to human-readable labels and specify localizations.
According to the PingAM documentation on "Supported Claims" in the OAuth2/OIDC Provider settings:
The format for the Supported Claims property entry is:
ClaimName|Locale|DisplayName
In this syntax:
ClaimName: The technical OIDC claim (e.g., name, email, given_name).
Locale: The ISO language code (e.g., en, fr).
DisplayName: The text that will actually appear on the UI (the "Full name" label).
Therefore, the string name|en|Full name (Option A) is the correct configuration.
Option B is incorrect because it reverses the technical name and the display name.
Option C is incorrect as it lacks the required locale component and uses full_name (which is not the standard OIDC claim name; the standard is name).
Option D attempts to perform a logic operation (+) within a configuration field where only static mapping strings are allowed. Claim composition (concatenating first and last names) is handled by the OIDC Claims Script, not by the Supported Claims UI property.
NEW QUESTION # 35
To protect against cross-site request forgery attacks, a default PingAM installation requires that some requests, such as POST requests, include:
Answer: A
Explanation:
Cross-Site Request Forgery (CSRF) is an attack where a malicious site sends a request to PingAM using the victim's authenticated browser session. Because standard HTML forms and cross-site requests cannot easily set custom HTTP headers, requiring a specific header is an effective defense for REST APIs.
According to the PingAM "Security" documentation and the "REST API" reference:
By default, PingAM 8.0.2 enforces a CSRF filter on its REST endpoints (such as /json/authenticate or /json/users). For any "state-changing" request (like a POST, PUT, or DELETE), the client must prove the request is intentional and not a forged browser-driven request. This is achieved by requiring at least one of the following headers:
X-Requested-With: Commonly used by AJAX libraries like jQuery. Its presence indicates the request was made via a script, which is generally not possible for a standard cross-site CSRF attack.
Accept-API-Version: This header serves two purposes. First, it ensures the client is targeting a specific version of the PingAM REST API (e.g., resource=2.0, protocol=1.0). Second, since custom headers cannot be set in simple cross-site <form> submissions, it acts as a CSRF token.
If a POST request is sent to the REST API without one of these headers, PingAM will reject the request with a 403 Forbidden error, even if the user has a valid session cookie.
Option B (If-Match: _rev) is used for concurrency control (preventing "lost updates" in IDM or AM configuration), but it is not the primary CSRF defense. Options A and D are headers sometimes used for "Zero-Page Login" or legacy authentication, but they do not provide protection against CSRF for the general REST API. Therefore, the combination of X-Requested-With or Accept-API-Version is the correct answer for default CSRF protection in PingAM 8.0.2.
NEW QUESTION # 36
......
The passing rate of our PT-AM-CPE training quiz is 99% and the hit rate is also high. Our professional expert team seizes the focus of the exam and chooses the most important questions and answers which has simplified the important PT-AM-CPE information and follow the latest trend to make the client learn easily and efficiently. We update the PT-AM-CPE Study Materials frequently to let the client practice more. We provide the function to stimulate the PT-AM-CPE exam and the timing function of our PT-AM-CPE study materials to adjust your speed to answer the questions. You will pass the PT-AM-CPE exam easily.
PT-AM-CPE Test Tutorials: https://www.test4engine.com/PT-AM-CPE_exam-latest-braindumps.html