此外，這些Fast2test PT-AM-CPE考試題庫的部分內容現在是免費的：https://drive.google.com/open?id=1dpsHWieoie4hvpZquZB6O5of3iOxnO2A
Ping Identity PT-AM-CPE 認證考試已經成為了IT行業中很熱門的一個考試，但是為了通過考試需要花很多時間和精力掌握好相關專業知識。在這個時間很寶貴的時代，時間就是金錢。Fast2test為Ping Identity PT-AM-CPE 認證考試提供的培訓方案只需要20個小時左右的時間就能幫你鞏固好相關專業知識，讓你為第一次參加的Ping Identity PT-AM-CPE 認證考試做好充分的準備。
| 主題 | 簡介 |
|---|---|
| 主題 1 |
|
| 主題 2 |
|
| 主題 3 |
|
| 主題 4 |
|
| 主題 5 |
|
Ping Identity PT-AM-CPE認證考試是IT人士在踏上職位提升之路的第一步。通過了Ping Identity PT-AM-CPE 認證考試是你邁向事業頂峰的的墊腳石。Fast2test可以幫助你通過Ping Identity PT-AM-CPE認證考試。
問題 #31
Which of the following best describes the relationship between users and realms?
答案：C
解題說明：
In PingAM 8.0.2, Realms are the primary organizational units used to group configuration, policies, and identities.13 A common misconception is that a user is "locked" into a single realm. However, according to the "Realms" and "Identity Stores" documentation, the relationship is highly flexible.
A Realm does not actually "contain" users in a physical sense; instead, a realm is configured with one or more Identity Stores (such as an LDAP directory or a database). Multiple realms can be configured to point to the same underlying Identity Store. Therefore, if a user profile exists in an LDAP directory that is shared by "Realm A" and "Realm B," that user is effectively a member of both realms. They can authenticate to either realm and receive different policies or session properties based on the realm-specific configuration.
Key points from the documentation:
Logical Partitioning: Realms provide a way to apply different authentication logic (different trees) to the same set of users.14 Multi-tenancy: An organization can create separate realms for different departments or customer groups, even if they overlap in the back-end user database.
Identity Store Mapping: Because a realm maps to an identity store, and an identity store can be reused across realms, a user's membership is determined by where the realm is "looking" for data.
Thus, Option A is the correct description of the architecture: a user can be a member of one or more realms depending on how the administrator has mapped the identity repositories.
Would you like me to proceed with more questions, or would you like to focus on a specific area such as OAuth2 Grant Flows?
問題 #32
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?
答案：D
解題說明：
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.
問題 #33
An OpenID Connect application makes a request for an ID token with the openid and profile scope. Which set of claim attributes are available with the profile scope?
答案：A
解題說明：
PingAM 8.0.2 adheres to the OpenID Connect Core 1.0 specification regarding standard scopes and claims. When a client requests the profile scope, the OpenID Provider (PingAM) is expected to return a specific set of claims that describe the user's basic profile.
According to the PingAM documentation on "Understanding OpenID Connect Scopes and Claims" and the default OIDC Claims Script (which maps internal LDAP attributes to OIDC claims):
The standard claims associated with the profile scope are strictly defined with lowercase, snake_case naming conventions. The default set includes:
name: The user's full name.
given_name: The user's first name.
family_name: The user's surname or last name.
middle_name: (Optional)
nickname: (Optional)
preferred_username: (Optional)
profile: URL to the profile page.
picture: URL to an image.
website: URL.
gender: (Optional)
birthdate: (Optional)
zoneinfo: Timezone.
locale: The user's preferred language/locale.
updated_at: Timestamp.
Option C is the only choice that correctly identifies the snake_case format (given_name, family_name, locale) required by the specification. Options A and B use camelCase or inconsistent naming that does not match the OIDC standard or PingAM's default mapping script. Option D includes preferred_locale, which is incorrect; the standard claim name for a user's language preference in OIDC is simply locale.
問題 #34
Consider the following LDAP connection string:
DS1.example.com:389|01, DS2.example.com:389|01, DS2.example.com:389|02, DS1.example.com:389|02 This connection string can be used in:
A . Identity Store
B . Core Token Service
C . Configuration Data Store
Which of the above options are correct?
答案：B
解題說明：
The connection string format HOST:PORT|SERVERID|SITEID is a specific syntax used in PingAM 8.0.2 for Affinity Load Balancing, a feature almost exclusively associated with the Core Token Service (CTS). In high-volume deployments, the CTS handles thousands of session updates per second. To avoid replication lag issues-where an AM server might try to read a session token from a directory server (DS) before the update has replicated from another DS node-PingAM uses "Affinity."16 According to the "CtsDataStoreProperties" and "CTS Deployment Architectures" documentation, this specialized string allows the AM instance to prioritize connections based on the Server ID and Site ID.17 The pipe (|) characters signify the optional affinity parameters:
01/02: These represent the Server IDs of the underlying Directory Servers.
Affinity Logic: By providing these IDs, PingAM can ensure that it always routes requests for the same CTS token to the same directory server node.18 While standard Identity Stores (Option A) and the Configuration Data Store (Option C) use LDAP connection strings, they typically utilize a comma-separated list of host:port pairs or rely on a hardware load balancer. The specific use of server and site IDs within the connection string itself to manage LDAP request routing is a hallmark of the CTS affinity configuration.19 The documentation explicitly states that "Each connection string is composed as follows: HOST:PORT[|SERVERID[|SITEID]]" within the context of CTS external store configuration.20 Therefore, this complex string is specifically designed for the Core Token Service to ensure data consistency and high performance in clustered environments.
問題 #35
In an authentication tree process, considering best practice, where can the collected context data for mobile devices be persisted for subsequent risk analysis?
答案：B
解題說明：
In PingAM 8.0.2, the Intelligent Access engine (Authentication Trees) uses a specific data-passing mechanism to move information between individual nodes within a single journey. When a journey involves collecting context-such as device metadata (OS, version, screen resolution), location data (IP, geofencing), or risk signals-this information must be stored temporarily while the tree evaluates the next steps.
According to the "Authentication Node Development" and "Nodes and Trees" documentation, PingAM uses two primary transient storage objects during the authentication flow:
Shared State: This is the primary map used to share data between nodes in the same tree. Contextual data collected by nodes like the Device Profile Collector or Browser Capabilities nodes is stored here. It exists only for the duration of the authentication journey.
Transient State: Similar to shared state, but often used for sensitive data that should not be visible to certain types of nodes or scripts.
The documentation identifies Shared Node State (Option B) as the best practice for persisting collected context during the tree process.
Session State (Option A) is only available after the authentication is successful and a session has been created. It is not suitable for data needed by nodes within the tree to make a decision (like a risk engine node).
User Profile (Option C) is for long-term persistence (LDAP/PingDS). Storing transient device context there would cause unnecessary database write overhead and privacy concerns.
Browser Cookies (Option D) are limited in size and pose security risks if used to store raw device data that could be tampered with by the client.
Therefore, for real-time risk analysis within a journey, nodes write data to the shared state, where subsequent nodes (like a Scripted Decision Node or Adaptive Risk Node) can retrieve and analyze it.
問題 #36
......
數千家公司均依託 Ping Identity 標準來提供一個可靠的員工業績評估。此外，數十家擁有自己認證專案的公司也非常信賴 Ping Identity 認證，以確保員工具備扎實的技能功底。此舉可以為公司節省大量的時間和開銷。要想順利的一次通過 PT-AM-CPE 認證，選擇一部優秀的題庫非常必要，Fast2test 的專家一直致力於為客戶提供 Ping Identity 認證的全真考題及認證學習資料,助您一次通過 Ping Identity PT-AM-CPE 認證考試。
PT-AM-CPE PDF題庫: https://tw.fast2test.com/PT-AM-CPE-premium-file.html
P.S. Fast2test在Google Drive上分享了免費的、最新的PT-AM-CPE考試題庫：https://drive.google.com/open?id=1dpsHWieoie4hvpZquZB6O5of3iOxnO2A