Which of the following is a processing rule?
Answer(s): B
PingAccess rules are categorized into Access Control Rules and Processing Rules. Processing Rules modify or add to HTTP requests and responses.Cross-Origin Request (CORS) is specifically listed as a Processing 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.
PingAccess Administration Guide Rules Overview
What information must be provided when setting the PingFederate Standard Token Provider for the Runtime engines?
Answer(s): C
When configuring PingAccess to use PingFederate as the Standard Token Provider for runtime engines, PingAccess must know how to contact PingFederate. The configuration requires the Host (PingFederate base URL).Exact Extract:"When configuring the Standard Token Provider, specify the PingFederate host to which PingAccess engines will connect for token validation."Option A (Issuer) is part of OIDC metadata but not required explicitly in this configuration. Option B (Client ID) is needed for OAuth clients but not when defining the token provider connection itself.Option C (Host) is correct -- this is required to connect to PingFederate. Option D (Port) may be included within the host definition (host:port) but is not the required field.
PingAccess Administration Guide Configuring PingFederate as a Token Provider
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?
Answer(s): A
To enforce step-up authentication for selected resources, PingAccess uses Authentication 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 B is incorrect; the reserved resource base path is unrelated to authentication. Option C is incorrect; changing the context root just changes the URL path prefix. Option D is incorrect; manual ordering of resources is unrelated to enforcing MFA.
PingAccess Administration Guide Authentication Challenge Policies
An application is hosted on a server that requires clients to authenticate using a username:password pair. This application is behind PingAccess, which is acting as a gateway. What action should the administrator take to allow PingAccess to access the application?
When a back-end site requires HTTP Basic Authentication, PingAccess supports this via a Basic Authentication Site Authenticator. The authenticator is configured with credentials so that PingAccess can successfully authenticate to the target site.Exact Extract:"PingAccess can authenticate to target sites using a Site Authenticator. Use the Basic Authentication Site Authenticator when the site requires a username and password." Option A is incorrect -- identity mappings are used to forward user attributes, not for site-to-site authentication.Option B is incorrect -- web sessions represent end-user sessions, not back-end credentials. Option C is correct -- the Basic Authentication Site Authenticator should be configured on the Site. Option D is incorrect -- mTLS authenticates with certificates, not username/password.
PingAccess Administration Guide Site Authenticators
What is the default port for the administrative console?
When PingAccess is first installed, the Administrative Console (the web-based UI for managing configuration) is bound to a default port of 9000. This is documented in the installation and configuration guides:Exact Extract from documentation:"By default, the administrative console is available at https://<host>:9000." (PingAccess Installation Guide Default Ports)This means that unless the administrator has explicitly changed the port in run.properties or during installation, the console will always be available on port 9000.Option Analysis:A . 9000Correct. Default administrative console port.B . 3000Incorrect. This is not a PingAccess default port.C . 9090Incorrect. Sometimes used by other Ping products for APIs, but not the PingAccess admin console.D . 3030Incorrect. Not a default PingAccess port.
PingAccess Installation Guide Default Administrative Console Port (9000).
Post your Comments and Discuss Ping Identity PAP-001 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the PAP-001 content, but please register or login to continue.