順便提一下，可以從雲存儲中下載PDFExamDumps PT-AM-CPE考試題庫的完整版：https://drive.google.com/open?id=1IwsxBDquSoVQ_u7BuTaxWDnZPMPHEXwr
我們PDFExamDumps的 Ping Identity的PT-AM-CPE的考題資料是按照相同的教學大綱來來研究的，同時也不斷升級我們的培訓材料，所以我們的考試培訓資料包括試題及答案，和實際的考試相似度非常高，所以形成了我們PDFExamDumps的通過率也是非常的高，這也是不可否認的事實， 由此知道PDFExamDumps Ping Identity的PT-AM-CPE考試培訓資料對考生的幫助，而且我們的價格絕對合理，適合每位IT認證的考生。
| 主題 | 簡介 |
|---|---|
| 主題 1 |
|
| 主題 2 |
|
| 主題 3 |
|
| 主題 4 |
|
| 主題 5 |
|
PDFExamDumps有龐大的資深IT專家團隊。他們利用專業的IT知識和豐富的經驗制訂出了各種不同的能使你順利地通過Ping Identity PT-AM-CPE認證考試的培訓計畫。在PDFExamDumps你可以找到最適合你的培訓方式來輕鬆通過考試。無論你選擇哪種培訓方式，PDFExamDumps都為你提供一年的免費更新服務。PDFExamDumps的資源很廣泛也很準確，選擇了PDFExamDumps，你通過Ping Identity PT-AM-CPE認證考試就簡單多了。
問題 #51
When developing a PingAM may act script for OAuth2 token exchange patterns, which variables are made available for use in the script?
答案：D
解題說明：
The OAuth2 May Act script type in PingAM 8.0.2 allows administrators to programmatically determine if a token exchange request (impersonation or delegation) should be allowed by adding a may_act claim to the token.
According to the "Scripting" and "Token Exchange Scripting API" documentation, when this script is executed, the AM engine provides a specific set of "Bindings" or variables. These allow the script to inspect the context of the request before deciding to modify the token. The documented variables for the OAuth2 May Act script are:
clientProperties: A map of the OAuth2 client's configuration properties.
identity: The identity object for the user/subject.
logger: The logging object for debugging within the script.
requestProperties: Properties of the incoming HTTP request.
scopes: The set of scopes requested or associated with the token.
scriptName: The name of the script being executed.
session: The user's SSO session (if available).
requestedToken: This is the most important variable; it represents the token being issued. Methods like .addMayAct() or .setMayAct() are called on this specific object.
Why other options are incorrect:
Option B correctly lists the bindings.
Options A and D are incorrect because they use the variable name token. While token is a common variable name in other OAuth2 script types (like the Access Token Modification script), the Token Exchange script specifically uses requestedToken to distinguish the new token from the subject_token or actor_token provided in the request.
Option C uses scopeList, which is not the standard variable name for the scopes in this specific script context; the documentation defines it as scopes.
問題 #52
Which of the following is an incorrect statement about session upgrade outcomes?
答案：A
解題說明：
In PingAM 8.0.2, a Session Upgrade occurs when a user is required to authenticate at a higher security level (Auth Level). The outcomes of these upgrades depend on the session storage (server-side vs. client-side) and the parameters used.
Statement B is incorrect because it claims that a new token is issued only when the current session does not meet requirements. In reality, if a request explicitly includes a parameter like ForceAuth=true or prompt=login, PingAM will force a re-authentication and issue a new session token regardless of the current session's state.
According to the "Session Upgrade" and "Step-up Authentication" documentation:
Statement A is correct: When ForceAuth=true is used, the AM engine ignores the existing session's Auth Level and forces the user through the tree. A new session/token is generated upon success.
Statement C is correct: This describes the standard "Advice" flow (e.g., from a policy). AM creates a new session, copies existing properties from the old one, and replaces the token.
Statement D is correct: In client-side sessions, since the state is in a JWT cookie, any change (like an Auth Level increase) requires the issuance of a brand-new signed JWT to replace the old one.
Therefore, because PingAM allows for forced re-authentication even when requirements are met, the restrictive "only when" condition in Statement B makes it the incorrect (and thus the target) answer. This behavior is key for security scenarios where a fresh proof of presence is required regardless of previous activity.
問題 #53
When defining a policy and specifying a resource pattern, which of the following statements is true concerning the difference between the wildcards * and -*-?
答案：A
解題說明：
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.
問題 #54
In a default PingAM configuration, what type of keystore stores the secret ID named storepass, which contains the encrypted password of the default-keystore secret store?
答案：D
解題說明：
In PingAM 8.0.2, the management of sensitive data such as passwords and cryptographic keys is handled through a unified Secret Store framework. This framework abstracts the source of the secret from the component that consumes it using Secret IDs. One of the most critical secret IDs in a standard installation is storepass.
The storepass secret ID is specifically used by the default-keystore (which is typically a "Keystore secret store" pointing to keystore.jks or keystore.p12). Before AM can access the keys within the default-keystore to sign tokens or encrypt data, it must first unlock the keystore itself using the password mapped to the storepass secret ID.
According to the PingAM "Secrets, certificates, and keys" documentation, in a default file-based configuration, PingAM initializes a Filesystem secret store as its primary global store. This store is configured to look into a specific directory within the AM configuration path (usually .../openam/secrets/). Inside this directory, AM expects to find files named after the secret IDs they contain. For the storepass ID, there is typically a corresponding file (such as storepass or .storepass) containing the cleartext or encrypted password required to open the primary keystore.
While AM can be configured to use an Environment and system property secret store (Option B) for high-portability cloud deployments, the "out-of-the-box" default behavior during a standard installation relies on the filesystem. Option A is incorrect because the storepass is the key to the keystore, not a secret inside it, and Option D refers to specialized hardware integrations not used in a default software-only setup. Therefore, the Filesystem secret store is the correct technical answer for the default location of the storepass.
問題 #55
Which authentication node can you use in PingAM to add a key:value property to the user's session after successful authentication?
答案：B
解題說明：
In PingAM 8.0.2 Intelligent Access, the Set Session Properties node is a specialized utility node designed to modify the session object once it is created.
According to the "Authentication Node Reference":
During an authentication journey, data is typically stored in the sharedState. However, sharedState is transient and is destroyed once the tree finishes. If an administrator wants to take a piece of information (e.g., a "Risk Score" calculated during the tree, or a "Branch ID" retrieved from a legacy system) and make it a permanent part of the user's session, they must use the Set Session Properties node.
Functionality: This node allows you to map a value from the sharedState or transientState to a session property name. After the tree reaches a Success node, these properties are persisted in the session (either in the CTS for server-side sessions or the JWT for client-side sessions).
Usage: Once set, these properties can be retrieved later for Response Attributes in policies, or by applications using the /json/sessions endpoint.
Option A (Get Session Data node) is used to retrieve existing properties from an active session, not set them. Option B is incorrect because while webhooks can trigger external logic, the native way to modify the session within a tree is a node. Option C (Provision Dynamic Account node) is for creating user entries in the Identity Store (LDAP), not for managing session-level properties. Therefore, Set Session Properties (Option D) is the correct technical tool for this requirement in version 8.0.2.
問題 #56
......
PDFExamDumps 考题大师始终致力与为客户提供 PT-AM-CPE 认证的全真考题及认证学习资料，該模擬試題可以在不同的電腦中使用，這對於考生來說沒有任何限制。我們的 PT-AM-CPE 權威考試題庫軟體是 Ping Identity 認證廠商的授權產品，全新的收錄了 Ping Identity 認證考試的所有試題，並根據認證的不斷變化而動態更新，參考資料的考試試題都是最新推出的。能够帮助你一次通过 Ping Identity PT-AM-CPE 认证考试。
PT-AM-CPE測試: https://www.pdfexamdumps.com/PT-AM-CPE_valid-braindumps.html
BONUS!!! 免費下載PDFExamDumps PT-AM-CPE考試題庫的完整版：https://drive.google.com/open?id=1IwsxBDquSoVQ_u7BuTaxWDnZPMPHEXwr