ちなみに、CertJuken PT-AM-CPEの一部をクラウドストレージからダウンロードできます：https://drive.google.com/open?id=1MipxWUzfEZeyTPor9jQ9S98omcJFiboA
CertJukenは多種なPing Identity認証試験を受ける方を正確な資料を提供者でございます。弊社の無料なPT-AM-CPEサンプルを遠慮なくダウンロードしてください。
| Certification Vendor: | Ping Identity |
|---|---|
| Exam Name: | Certified Professional - PingAM Exam |
| Exam Number: | PT-AM-CPE |
| Passing Score: | 66% |
| Exam Duration: | 120 minutes |
| Available Languages: | English |
| Certificate Validity Period: | 3 years |
| Exam Price: | USD 300 |
| Exam Format: | Scenario-based, Multiple Choice |
| Related Certifications: | Ping Identity Certified Professional |
| Real Exam Qty: | 100 |
| Sample Questions: | Ping Identity PT-AM-CPE Sample Questions |
| Exam Way: | Proctored exam (online or at testing centers) |
| Pre Condition: | Recommended experience with PingAM in production environments |
| Official Syllabus URL: | https://www.pingidentity.com/en/training/certification.html |
>> Ping Identity PT-AM-CPE専門試験 <<
IT業界での先駆者として、我々CertJukenの目的はIT認定試験に参加する皆様に助けを提供することです。我々のエリートたちは目標を達成するために、昼も夜も努力してPing Identity試験の数年以来のデータの分析と整理に就職しています。彼らの真面目な態度があって、我々のPT-AM-CPE対策を利用するお客様のほとんどはPT-AM-CPE試験に合格できます。
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
| トピック 5 |
|
質問 # 75
Which of the following components is used to return data to PingGateway or the agent to be included with the policy decision?
正解：D
解説：
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
A multi-server PingAM deployment is scheduled for upgrade. What measure can be implemented to prevent external user access during this process?
正解：A
解説：
According to the PingAM 8.0.2 Upgrade Guide and best practices for high-availability environments, performing an upgrade on a multi-server cluster requires a controlled redirection of traffic. While several methods can technically stop traffic, the load balancer is the primary tool for managing availability during maintenance.
In a production environment, PingAM instances are typically situated behind a load balancer that performs health checks and distributes user requests. By disabling access from the load balancer (specifically, by draining connections or marking nodes as "out of service"), administrators can gracefully prevent new external users from reaching the servers undergoing the upgrade. This approach is superior to shutting down the PingAM instances (Option A) immediately, as it allows existing sessions to complete their current operations or be handled by other nodes in the cluster if a "rolling upgrade" strategy is being used.
Shutting down the PingDS instances (Option B) is dangerous, as the directory service is required by PingAM for both configuration and user data; losing the data store while the AM application is still active can lead to severe system errors and data corruption. While a firewall (Option C) can block traffic, it is generally a "blunt instrument" that does not provide the sophisticated session management or health-probe handling that a load balancer offers. The load balancer allows for a "Maintenance Page" to be displayed to users, providing a better user experience during the downtime. Therefore, for a professional multi-server upgrade, managing the traffic flow at the load balancer layer is the verified best practice in PingAM 8 documentation.
質問 # 77
What should be executed to ensure a successful upgrade when PingAM requires a version upgrade?
正解：A
解説：
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.
質問 # 78
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)"
}
正解：C
解説：
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.
質問 # 79
What is the purpose of the SAML2 account mapper on the service provider (SP) side?
正解：D
解説：
In a SAML 2.0 Federation flow, once the Service Provider (SP) receives and validates a SAML Assertion from an Identity Provider (IdP), it must determine which local user account the assertion corresponds to. This is the role of the SAML2 Account Mapper.
According to the PingAM 8.0.2 documentation on "Federate Identities" and the "SAML 2.0 Reference":
The SP-side account mapper (specifically the SPAccountMapper interface or its scripted equivalent) is responsible for mapping the remote user (identified in the SAML assertion) to a local user profile in the SP's identity store.
This mapping can be achieved in several ways:
Account Linking: Finding an existing link between the NameID in the assertion and a local DN.
Attribute Matching: Using an attribute from the assertion (like mail) to search the local directory for a matching user.
Auto-Federation: If configured, creating a link or a new profile automatically based on the incoming data.
If the account mapper cannot find a corresponding local profile, the SP cannot create a local session, and the SSO process will fail, typically with a "User not found" or "Local identity not found" error. Thus, the purpose is strictly the identification of the local subject based on the remote assertion (Option D). Options A and B are incorrect as they describe aggregation or account merging which are not the primary function of the SAML mapper. Option C describes "Attribute Mapping," which is a separate step (handled by the Attribute Mapper) that occurs after the identity has been successfully mapped.
質問 # 80
......
PT-AM-CPE一発合格: https://www.certjuken.com/PT-AM-CPE-exam.html
無料でクラウドストレージから最新のCertJuken PT-AM-CPE PDFダンプをダウンロードする：https://drive.google.com/open?id=1MipxWUzfEZeyTPor9jQ9S98omcJFiboA