Ping Identity PAP-001 Exam Dumps

PingAccess enforces step-up or multi-factor authentication using Authentication Requirements, which can be applied to specific resources within an application.

Exact Extract:

''Authentication requirements allow administrators to configure additional authentication (for example, MFA) when accessing sensitive application resources.''

Option A (UI Authentication) applies to access to the admin console, not application resources.

Option B (Auth Token Management) relates to OAuth token lifetimes and refresh, not MFA enforcement.

Option C (Authentication Requirements) is correct --- these rules enforce MFA or step-up auth for specific URLs/resources.

Option D (Authentication Challenge Policy) governs how failed auth challenges are presented but does not enforce MFA.

For multiple subdomains to share the same PingAccess session, the Cookie Domain must 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.com allows 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.

PingAccess automatically creates configuration archive backups whenever changes are made. These are stored in the data/archive directory.

Exact Extract:

''PingAccess stores configuration archive files in the PA_HOME/data/archive directory.''

Option A (tools) is incorrect --- contains administrative scripts.

Option B (conf) is incorrect --- holds configuration files like run.properties.

Option C (data) is correct --- archives are stored under data/archive.

Option D (bin) is incorrect --- contains executables and scripts.

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 supports flexible path matching for resources using wildcards. If the requirement is to match any path that contains a folder named 'escalated', the correct format is:

*/escalated/ matches any location of the escalated directory within the path.

Exact Extract:

''The asterisk (*) wildcard matches zero or more characters. Use it in resource paths to match folders at any depth.''

Option A (escalated/) only matches when the resource starts with ''escalated/'' at the root, not at arbitrary depth.

Option B (*/escalated/) is correct --- it matches the escalated folder no matter where it occurs.

Option C (*/escalated/+ ) is incorrect --- + is not a valid PingAccess wildcard operator.

*Option D (/escalated/) matches only when the path starts with ''escalated'' at the first level, not arbitrary positions.