
Pass Your PAP-001 Dumps as PDF Updated on 2025 With 72 Questions
Ping Identity PAP-001 Real Exam Questions and Answers FREE
Ping Identity PAP-001 Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
NEW QUESTION # 25
An administrator needs to prevent PingAccess from automatically starting on a Windows Server. Which command would accomplish this task?
- A. remove-install.bat
- B. wrapper-service.bat
- C. init.bat
- D. uninstall-service.bat
Answer: D
Explanation:
PingAccess installs as a Windows service. To remove or prevent automatic startup, theuninstall-service.bat script is used.
Exact Extract:
"On Windows, useinstall-service.batto install PingAccess as a service anduninstall-service.batto remove the service."
* Option A (init.bat)initializes environment variables but does not manage services.
* Option B (uninstall-service.bat)is correct - it removes the Windows service, preventing auto-start.
* Option C (remove-install.bat)is not a valid PingAccess script.
* Option D (wrapper-service.bat)configures wrapper options, not service removal.
Reference:PingAccess Installation Guide -Windows Service Scripts
NEW QUESTION # 26
What is the purpose of theengine.ssl.protocolsin therun.propertiesfile?
- A. To configure SSL protocols used for clustering
- B. To configure the supported HTTPS port
- C. To configure the supported ciphers
- D. To configure the supported TLS versions
Answer: D
Explanation:
The propertyengine.ssl.protocolsinrun.propertiesspecifies the TLS protocol versions that PingAccess engines will support for incoming HTTPS traffic.
Exact Extract:
"Theengine.ssl.protocolsproperty configures which TLS versions are enabled for HTTPS listeners."
* Option A (ciphers)is incorrect - cipher suites are defined separately, not in this property.
* Option B (HTTPS port)is incorrect - the port is defined in the engine listener, not here.
* Option C (TLS versions)is correct - this property controls TLS version support (e.g., TLSv1.2, TLSv1.3).
* Option D (clustering)is incorrect - clustering does not depend on this property.
Reference:PingAccess Administration Guide -run.properties settings
NEW QUESTION # 27
The application team is requesting step-up authentication only for a few specific resources while maintaining previous authentication for other resources. What change would the administrator need to make?
- A. Change the Context Root
- B. Authentication Challenge Policy
- C. Manual Resource Ordering
- D. Use context root as reserved resource base path
Answer: B
Explanation:
To enforcestep-up authenticationfor selected resources, PingAccess usesAuthentication Challenge Policies
. These policies allow different challenge methods to be applied depending on the resource.
Exact Extract:
"Authentication challenge policies define how PingAccess challenges users for authentication and are often applied when step-up authentication is required for specific resources."
* Option A (Authentication Challenge Policy)is correct - it ensures only certain resources trigger step- up MFA.
* Option Bis incorrect; the reserved resource base path is unrelated to authentication.
* Option Cis incorrect; changing the context root just changes the URL path prefix.
* Option Dis incorrect; manual ordering of resources is unrelated to enforcing MFA.
Reference:PingAccess Administration Guide -Authentication Challenge Policies
NEW QUESTION # 28
Where in the administrative console should an administrator make user attributes available as HTTP request headers?
- A. Identity Mappings
- B. HTTP Requests
- C. Web Sessions
- D. Site Authenticators
Answer: A
Explanation:
PingAccess usesIdentity Mappingsto take identity attributes provided by the authentication source (e.g., PingFederate, OpenID Connect) and map them into HTTP request headers for back-end applications.
Exact Extract:
"An identity mapping allows you to map identity attributes from the user's session to HTTP headers, cookies, or query parameters that are then forwarded to the target application."
* Option A (Site Authenticators)is incorrect because Site Authenticators configure how PingAccess communicates with applications requiring authentication, not how attributes are inserted into headers.
* Option B (Identity Mappings)is correct - this is the feature designed specifically to expose user attributes to applications via HTTP headers.
* Option C (Web Sessions)manages how sessions are stored and validated, but not the mapping of attributes into requests.
* Option D (HTTP Requests)refers to request/response processing rules, but attributes are not mapped here.
Reference:PingAccess Administration Guide -Identity Mapping
NEW QUESTION # 29
Users report the following about access to an application:
* Inconsistent behavior depending on the browser used
* Denied access
* Prompt to accept a security exception
Which configuration option should the administrator adjust?
- A. Validate Session
- B. Enable PKCE
- C. Request Preservation
- D. SameSite Cookie
Answer: D
Explanation:
Modern browsers enforce stricter cookie handling rules. If cookies are not configured correctly with the SameSiteattribute, behavior can differ across browsers, leading to inconsistent authentication and access denials. Security exceptions may appear when session cookies are blocked.
Exact Extract:
"The SameSite cookie setting defines how browsers send cookies in cross-site requests. Misconfigured SameSite values can lead to inconsistent application behavior across browsers."
* Option A (Enable PKCE)is related to OAuth flow security, not browser cookie behavior.
* Option B (SameSite Cookie)is correct - this directly explains the inconsistent browser issues.
* Option C (Request Preservation)ensures query parameters are kept, not related to cross-browser session handling.
* Option D (Validate Session)checks session state but does not address browser inconsistencies.
Reference:PingAccess Administration Guide -Web Session Cookie Settings
NEW QUESTION # 30
A company uses an internally based legacy PKI solution that does not adhere to theCertification Path Validationsection of RFC-5280. Which configuration option needs to be enabled when creating Trusted Certificate Groups in PingAccess?
- A. Validate disordered certificate chains
- B. Use Java Trust Store
- C. Skip Certificate Date Check
- D. Deny when unable to determine revocation status
Answer: A
Explanation:
Legacy PKIs often provide certificate chains that areout of orderor non-compliant with RFC-5280 path validation. PingAccess provides an option in Trusted Certificate Groups calledValidate disordered certificate chainsto allow chaining even if the order is not RFC-5280 compliant.
Exact Extract:
"EnableValidate disordered certificate chainswhen the certificate chain is not in RFC-5280 compliant order but should still be accepted."
* Option Ais incorrect; using the Java trust store is unrelated to PKI ordering.
* Option Bis correct - this setting allows PingAccess to process disordered certificate chains.
* Option Cis incorrect; date checks are unrelated to RFC-5280 path ordering.
* Option Dis incorrect; revocation status handling does not address legacy PKI ordering issues.
Reference:PingAccess Administration Guide -Trusted Certificate Groups
NEW QUESTION # 31
An administrator must onboard a new application from the application team. The application has multiple paths that will need different rules. What would be the first step in this process?
- A. Web session
- B. Resource
- C. Application
- D. Identity mapping
Answer: C
Explanation:
All onboarding in PingAccess begins with defining anApplication. Once the application exists, the administrator can defineResourceswithin it and assign different rules to those resources.
Exact Extract:
"Before you can configure resources and rules, you must first create an application in PingAccess."
* Option A (Identity Mapping)may be required later but not the first step.
* Option B (Web Session)can be shared but is not the first onboarding step.
* Option C (Application)is correct - the starting point for onboarding.
* Option D (Resource)comes after creating the application.
Reference:PingAccess Administration Guide -Creating Applications
NEW QUESTION # 32
An application requires MFA for URLs that are considered high risk. Which action should the administrator take to meet this requirement?
- A. Apply a Web Session Attribute rule to the resource.
- B. Apply an HTTP Request Parameter rule to the resource.
- C. Apply an Authentication Requirements rule to the resource.
- D. Create an Authentication Requirement named MFA_Required.
Answer: C
Explanation:
PingAccess allows fine-grained authentication enforcement by applyingAuthentication Requirement rulesat the resource level. These rules can invoke MFA flows based on request context or policy.
Exact Extract:
"Authentication requirement rules determine whether PingAccess challenges a user to authenticate again (for example, with MFA) before allowing access to a protected resource."
* Option Ais incomplete. Creating a requirement does nothing unless it is applied.
* Option Bis correct because applying the Authentication Requirement rule to thespecific resource (URL)enforces MFA only for that resource.
* Option Cis incorrect; Web Session Attribute rules are about evaluating existing session attributes, not triggering MFA.
* Option Dis incorrect; HTTP Request Parameter rules are used to evaluate request data, not enforce MFA policies.
Reference:PingAccess Administration Guide -Authentication Requirements
NEW QUESTION # 33
Refer to the following applications:
* hr.company.com
* finance.company.com
* customer.order.company.com
Which action should be taken to allow these applications to share the same web session?
- A. Use Rewrite Cookie Path rule
- B. Set Audience option
- C. Set Cookie Domain option
- D. Use Rewrite Cookie Domain rule
Answer: C
Explanation:
For multiple subdomains to share the same PingAccess session, theCookie Domainmust be configured so that the session cookie is valid across all listed applications.
Exact Extract:
"Set the Cookie Domain in the web session configuration to a parent domain (for example, .company.com) to enable applications in different subdomains to share the same session."
* Option A (Set Audience option)applies to OAuth token validation, not cookie sharing.
* Option B (Set Cookie Domain option)is correct - e.g., setting.company.comallows session cookies to be shared.
* Option C (Rewrite Cookie Domain rule)modifies upstream cookies for back-end applications, not PingAccess session cookies.
* Option D (Rewrite Cookie Path rule)is unrelated; it modifies paths for cookies, not domains.
Reference:PingAccess Administration Guide -Web Session Configuration
NEW QUESTION # 34
Developers report an issue with an application that is protected by PingAccess. Certain requests are not providing claims that are part of the access token.
What should the administrator add for the access token claims?
- A. An identity mapping definition
- B. An OAuth attribute rule
- C. An authentication requirement definition
- D. A web session attribute rule
Answer: B
Explanation:
In PingAccess, when an application relies on claims from an OAuth access token, you must configure PingAccess to evaluate those claims and potentially inject them into headers for the backend application.
* Exact Extract from PingAccess documentation:
"OAuth rules allow you to evaluate claims in OAuth access tokens. You can configure PingAccess to look at specific claims and enforce policies or pass them to target applications."
"To extract attributes from an access token, configure anOAuth Attribute Rule." This clearly matches optionD.
Analysis of each option:
* A. An authentication requirement definition
* Incorrect. Authentication requirements determine how users authenticate to applications (OIDC provider, etc.), but do not manage access token claims.
* B. A web session attribute rule
* Incorrect. Web session attribute rules map attributes from the authenticated user's web session (SSO session), not from OAuth access tokens.
* C. An identity mapping definition
* Incorrect. Identity mappings transform user attributes (from IdP to app), but they don't directly pull claims from OAuth tokens.
* D. An OAuth attribute rule
* Correct. This rule is specifically designed to extract and enforce policies onclaims from OAuth access tokens.
Therefore, the correct answer isD. An OAuth attribute rule.
Reference:PingAccess Administration Guide-Rules # OAuth Attribute Rules.
NEW QUESTION # 35
An administrator needs to support SLO (Single Logout) for a protected web application. What must be configured in a PingAccess Web Session in this situation?
- A. Validate Session
- B. SLO scope
- C. Refresh User Attributes
- D. Idle timeout
Answer: B
Explanation:
To enableSingle Logout (SLO), theSLO scopemust be defined in the PingAccess Web Session configuration. This determines which sessions are ended when a logout request occurs.
Exact Extract:
"The SLO scope option in a web session specifies which applications are included in a logout event when Single Logout is triggered."
* Option A (SLO scope)is correct; it explicitly enables SLO support by linking session termination across apps.
* Option B (Idle timeout)is unrelated; this controls session expiration, not SLO.
* Option C (Validate Session)ensures session state is synchronized but does not configure SLO.
* Option D (Refresh User Attributes)is unrelated; it only controls whether attributes are reloaded.
Reference:PingAccess Administration Guide -Configuring Web Sessions
NEW QUESTION # 36
What is the purpose of the Mutual TLS Site Authenticator?
- A. Allows the backend server to authenticate to PingAccess
- B. Allows PingAccess to authenticate to the backend server
- C. Allows the user to authenticate to the backend server
- D. Allows PingAccess to authenticate to the token provider
Answer: B
Explanation:
Mutual TLS (mTLS) is used to establishtwo-way authenticationwhere both the client and the server present certificates to prove their identity. In the case of PingAccess, aMutual TLS Site Authenticatoris configured when PingAccess acts as a reverse proxy making requests to a backend (target) server.
* Exact Extract from PingAccess documentation:
"Mutual TLS site authenticators provide client certificate authentication when PingAccess connects to a backend site. This allows PingAccess to present its certificate to the target server during the TLS handshake." This means the purpose is forPingAccess (client) to authenticate itself to the backend server (target resource)when establishing a secure connection.
Why other options are wrong:
* A. Allows the backend server to authenticate to PingAccess
* Incorrect. That's normal server-side TLS authentication (the server presents a cert to the client), not mutual TLS initiated by PingAccess.
* B. Allows the user to authenticate to the backend server
* Incorrect. End users do not directly use this setting; this is between PingAccess and the backend application server.
* C. Allows PingAccess to authenticate to the backend server
* Correct. This is exactly the definition of a Mutual TLS Site Authenticator in PingAccess.
* D. Allows PingAccess to authenticate to the token provider
* Incorrect. That would involve OIDC/OAuth token exchange and possibly TLS trust, but it's not the role of the Site Authenticator.
Thus, the correct answer isC. Allows PingAccess to authenticate to the backend server.
Reference:PingAccess Administration Guide-Configuring Site Authenticators (Mutual TLS).
NEW QUESTION # 37
An administrator is integrating a new PingAccess Proxied Application for which the target site uses a certificate issued by a publicly trusted Certificate Authority.
How should the administrator configure PingAccess to trust the target site?
- A. Import the certificate chain into Key Pairs
- B. Drop the certificate chain into a Trusted Certificate Group
- C. Configure the PingAccess Site to use the Java Trust Store Certificate Group
- D. Import the certificate chain into Key Pairs and add it to a Trusted Certificate Group
Answer: C
Explanation:
Publicly trusted Certificate Authorities are already included in theJava Trust Store Certificate Group, which PingAccess can use directly. This avoids importing the certificate manually.
Exact Extract:
"If the target site uses a certificate from a well-known public CA, configure the site to use the Java Trust Store Certificate Group."
* Option Ais incorrect - Key Pairs store private keys for SSL termination, not public CA trust anchors.
* Option Bis correct - Java Trust Store already contains trusted public CAs.
* Option Cis incorrect - again, Key Pairs are not used for trust validation.
* Option Dis unnecessary for public CAs - only internal/self-signed certs must be imported.
Reference:PingAccess Administration Guide -Trusted Certificate Groups
NEW QUESTION # 38
During a business review of an application, the administrator needs to change the Resource Authentication to anonymous. What are the two effects of making this change to the resource? (Choose 2 answers.)
- A. The resource requires no further authentication, and Processing rules still apply.
- B. The resource requires no further authentication, and Identity Mappings still apply.
- C. Requests to this resource are not logged, and Identity Mappings are applied.
- D. The resource requires no further authentication, and all Access Control rules still apply.
- E. The resource requires no further authentication, and no rules will apply.
Answer: A,B
Explanation:
When a resource is configured asanonymous, PingAccess does not challenge the user for authentication.
However, certain processing and identity propagation still occur.
Exact Extract:
"Anonymous resources do not require authentication. Identity mappings and request/response processing rules still apply."
* Option Ais incorrect because rules such as identity mappings and processing still apply.
* Option Bis correct - Identity Mappings can still forward attributes, even for anonymous access.
* Option Cis correct - Processing rules (e.g., request/response modifications) still apply.
* Option Dis incorrect - requestsarelogged; anonymous does not disable logging.
* Option Eis incorrect - access control rules (authorization) are not evaluated for anonymous resources.
Reference:PingAccess Administration Guide -Resource Authentication
NEW QUESTION # 39
Which of the following is a processing rule?
- A. Web Session Attribute
- B. HTTP Request Parameter
- C. Cross-Origin Request
- D. HTTP Request Header
Answer: C
Explanation:
PingAccess rules are categorized intoAccess Control RulesandProcessing Rules.
* Processing Rulesmodify or add to HTTP requests and responses.
* Cross-Origin Request (CORS)is specifically listed as aProcessing Rule, because it modifies response headers to support cross-origin requests.
Exact Extract:
"Processing rules apply to HTTP traffic, such as Cross-Origin Resource Sharing (CORS), header injection, or response modification."
* Option A (Web Session Attribute)is an access control rule.
* Option B (Cross-Origin Request)is correct - this is a processing rule.
* Option C (HTTP Request Parameter)is an access control rule.
* Option D (HTTP Request Header)is an access control rule.
Reference:PingAccess Administration Guide -Rules Overview
NEW QUESTION # 40
An administrator configures the following:
* HTTP Request Parameter Rule for"can_read=yes"
* Web Session Attribute Rule forOpt-in = yes
* Web Session Attribute Rule forgroup = customerService
* Rule SetA(ALL) # includes (HTTP Request Parameter Rule)
* Rule SetB(ANY) # includes (Opt-in yes, group customerService)
* Rule Set GroupC(ALL) # includes (Rule Set A, Rule Set B)Assigned to the web application.
Which set of conditions must be met to be able to access the application?
- A. The request requires a parameter called can_read with a value of yes. The authenticated usermust be either in customer service or have the opt-in attribute set to yes.
- B. The request requires a parameter called can_read with a value of yes unless the authenticated user is in either customer service or has the opt-in attribute set to yes.
- C. The request requires a parameter called can_read with a value of yes. Additionally, the authenticated user must be in customer service and have the opt-in attribute set to yes.
- D. The request requires a parameter called can_read with a value of yes unless the authenticated user is in customer service and the opt-in attribute set to yes.
Answer: A
Explanation:
The Rule Set GroupC(ALL) requiresboth Rule Set A and Rule Set Bto evaluate to true.
* Rule Set A (ALL)requirescan_read=yes.
* Rule Set B (ANY)requireseitherOpt-in=yesORgroup=customerService.
* Together in Rule Set Group C (ALL), both conditions must hold:
* can_read=yesmust be present in the request.
* User must have eitheropt-in=yesor be in thecustomerServicegroup.
This matchesOption Dexactly.
* Option Ais incorrect; it requires both attributes in Rule Set B, but B is ANY (either is sufficient).
* Option Bis incorrect; the "unless" wording is misleading - the parameter is always required because Rule Set A uses ALL.
* Option Cis incorrect; same reasoning as above, B is ANY not AND.
* Option Dis correct -can_read=yesAND(opt-in=yesORgroup=customerService).
Reference:PingAccess Administration Guide -Rules, Rule Sets, and Rule Set Groups
NEW QUESTION # 41
An application owner would like customized errors for rule violations within an application. Where is this configured?
- A. When assigning a Rule to a Resource
- B. When combining Rules into Rule Sets
- C. Within the Root Resource of the Application
- D. Within the Rule definition
Answer: C
Explanation:
PingAccess allows administrators to configurecustom error pages or messagesat theRoot Resource levelof an application. This ensures that when rule violations (e.g., authorization failures) occur, the application can display tailored error responses.
Exact Extract:
"Custom error handling for rule violations is configured within the Root Resource of an application."
* Option Ais incorrect - assigning a rule to a resource does not allow defining custom errors.
* Option Bis correct - the Root Resource is where administrators define custom error handling for the entire application.
* Option Cis incorrect - Rule Sets only combine rules; they do not handle error responses.
* Option Dis incorrect - individual rule definitions do not contain custom error configurations.
Reference:PingAccess Administration Guide -Configuring Application Resources and Error Handling
NEW QUESTION # 42
A protected web application requires that additional attributes be provided once the user is authenticated.
Which two steps must the administrator perform to meet this requirement? (Choose 2 answers.)
- A. Update the Web Session.
- B. Update the Identity Mapping.
- C. Request that the token provider update the ID token with the additional attributes.
- D. Request that the token provider update the access token with the additional attributes.
- E. Update the Site Authenticator.
Answer: A,B
Explanation:
When applications require additional attributes:
* TheWeb Sessionmust be configured to retrieve those attributes from the token provider (OIDC or PingFederate).
* TheIdentity Mappingmust be updated to forward those attributes to the application (e.g., as headers).
Exact Extract:
"Web sessions define how user attributes are retrieved from the token provider. Identity mappings determine how those attributes are inserted into requests to applications."
* Option Ais not necessarily required; attributes can be retrieved via userinfo endpoint or access token, not only ID tokens.
* Option Bis correct - Identity Mappings must be updated to pass attributes to the app.
* Option Cis incorrect - Site Authenticators define how PingAccess authenticates to apps, not attribute handling.
* Option Dis incorrect unless the architecture specifically requires access token updates; PingAccess often uses the Web Session to fetch attributes.
* Option Eis correct - Web Session must be updated to retrieve additional attributes.
Reference:PingAccess Administration Guide -Web Sessions and Identity Mapping
NEW QUESTION # 43
An organization has a highly available PingAccess cluster with four runtime nodes. The administrator wants to provide the same availability to administrative users. What should the administrator do?
- A. Configure one active and three replica administrative nodes with engine cluster pointed to all administrative nodes
- B. Configure one active and one replica administrative node with engine cluster pointed to both administrative nodes
- C. Configure two active administrative nodes with engine cluster pointed to both administrative nodes for configuration
- D. Configure four active administrative nodes with engine cluster pointed to all administrative nodes for configuration
Answer: A
Explanation:
PingAccess supportsone primary administrative console (active)and any number ofreplica administrative consoles. Engines must be configured to connect to theactive console, with replicas available for failover.
Exact Extract:
"In a clustered environment, PingAccess supports one clustered console (active) and replica consoles. Engines can connect to any console node for high availability."
* Option Ais incomplete - only one replica limits redundancy.
* Option Bis incorrect - multiple active consoles are not supported.
* Option Cis incorrect - cannot run two active consoles.
* Option Dis correct - one active admin console with multiple replicas ensures HA.
Reference:PingAccess Administration Guide -Clustered Console and Replica Configuration
NEW QUESTION # 44
An administrator is integrating a new PingAccess Proxied Application. The target site uses a certificate issued by an internal Certificate Authority hosted by the customer. Prior to assigning the certificate group in the Site configuration, which action should the administrator take to configure PingAccess to trust the certificate?
- A. Configure the PingAccess Site to use the Java Trust Store Certificate Group.
- B. Import the certificate chain into Key Pairs and assign it to a new engine listener.
- C. Import the certificate chain and add it to the Trusted Certificate Group.
- D. Import the certificate chain into Key Pairs and add it to the Trusted Certificate Group.
Answer: C
Explanation:
PingAccess must trust the back-end site's certificate to establish TLS. For internally issued certificates, the administrator imports thecertificate chaininto aTrusted Certificate Group.
Exact Extract:
"When a target site uses an internal CA, import the certificate or chain into a Trusted Certificate Group and assign that group to the site."
* Option Ais incorrect - the Java trust store does not contain the internal CA by default.
* Option Bis incorrect - Key Pairs store private keys for SSL termination, not trusted CA certs.
* Option Cis incorrect - engine listeners use key pairs for inbound SSL, not site trust.
* Option Dis correct - the certificate must be imported into Trusted Certificate Groups.
Reference:PingAccess Administration Guide -Trusted Certificate Groups
NEW QUESTION # 45
An administrator is setting up PingAccess to terminate SSL for a proxied application. What action must the administrator take to configure an existing certificate for that application?
- A. Set the secure flag to Yes in the Site configuration
- B. Assign the Key Pair to the Virtual Host
- C. Assign the Key Pair to the Agent Listener
- D. Enable Require HTTPS in the Application configuration
Answer: B
Explanation:
PingAccess terminates SSL at theVirtual Hostlevel. To configure an existing certificate, the administrator must assign the appropriateKey Pair(which contains the certificate and private key) to the Virtual Host.
Exact Extract:
"SSL termination occurs on the engine listener through virtual hosts. Assign the certificate's key pair to the virtual host to secure proxied applications."
* Option Ais correct - assign the key pair to the Virtual Host for SSL termination.
* Option Bis incorrect - Require HTTPS enforces secure access but does not configure SSL termination.
* Option Cis incorrect - Agent Listener is for PingAccess Agents, not proxied apps.
* Option Dis incorrect - secure flag affects cookie settings, not SSL certificates.
Reference:PingAccess Administration Guide -Virtual Hosts and Key Pairs
NEW QUESTION # 46
How many administrators are supported using HTTP Basic Authentication in the Administrative Console?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: B
Explanation:
When usingHTTP Basic Authentication(admin.auth=native), PingAccess only supports asingle administrative account(the default admin user). For multiple administrators, SSO integration (e.g., OIDC) is required.
Exact Extract:
"When admin authentication is set to native (HTTP Basic), only one administrative user is supported. For multiple admins, configure UI authentication with an OIDC provider."
* Option A (1000)is incorrect.
* Option B (1)is correct - only one basic auth admin account.
* Option C (10)andOption D (100)are incorrect.
Reference:PingAccess Administration Guide -Admin Authentication
NEW QUESTION # 47
What is the purpose of thepa.operational.modeconfiguration setting?
- A. To determine if a server should participate in cluster replication
- B. To determine the role the server performs in a cluster
- C. To determine whether a server is a development or production server
- D. To determine if a cluster node is enabled or disabled
Answer: B
Explanation:
Thepa.operational.modeproperty inrun.propertiesdefines therole of the nodein a PingAccess deployment (e.
g.,STANDALONE,CLUSTERED_CONSOLE,CLUSTERED_CONSOLE_REPLICA,ENGINE).
Exact Extract:
"Thepa.operational.modeproperty determines the role of the server in the cluster, such as standalone, console, console replica, or engine."
* Option Ais incorrect - replication is implicit in certain roles, not controlled directly.
* Option Bis correct - the setting specifies whether the node is admin console, replica, or engine.
* Option Cis incorrect - development vs production is not a function of this setting.
* Option Dis incorrect - it does not enable/disable nodes.
Reference:PingAccess Administration Guide -run.properties
NEW QUESTION # 48
An administrator needs to configure a protected web application using theAuthorization Codelogin flow.
Which two configuration parameters must be set? (Choose 2 answers.)
- A. OAuth Client ID
- B. OpenID Connect Issuer
- C. OAuth Token Introspection Endpoint
- D. Virtual Host
- E. OpenID Connect Login Type
Answer: A,E
Explanation:
When using theAuthorization Code Flowfor authentication, PingAccess must be configured with:
* AnOAuth Client IDthat identifies the application to the IdP.
* TheOpenID Connect Login Typeset to Authorization Code.
Exact Extract:
"When configuring an OIDC web session, specify the OAuth client ID and select the OpenID Connect login type (Authorization Code, Hybrid, or Implicit)."
* Option A (OAuth Token Introspection Endpoint)is not required for Authorization Code flow - token introspection is used in other cases.
* Option B (OAuth Client ID)is correct - required for OIDC authorization requests.
* Option C (OpenID Connect Issuer)is discovered automatically via metadata when you configure the token provider.
* Option D (Virtual Host)is required for application exposure but not specific to OIDC flow.
* Option E (OpenID Connect Login Type)is correct - must be set to "Authorization Code." Reference:PingAccess Administration Guide -Configuring OIDC Web Sessions
NEW QUESTION # 49
An organization wants to take advantage of a new product feature that requires upgrading the PingAccess cluster from 7.3 to the current version. The administrator downloads the required files and places the files on the PingAccess servers. What should the administrator do next?
- A. Disable cluster communication.
- B. Upgrade the Replica Admin.
- C. Upgrade the Admin Console.
- D. Disable Key Rolling.
Answer: C
NEW QUESTION # 50
......
Pass Ping Identity PAP-001 Exam Info and Free Practice Test: https://prep4sure.dumpexams.com/PAP-001-vce-torrent.html