PAP-001 Exam Dumps and Practice Questions

PingAccess terminates SSL at the Virtual Host level. To configure an existing certificate, the administrator must assign the appropriate Key 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 A is correct --- assign the key pair to the Virtual Host for SSL termination.

Option B is incorrect --- Require HTTPS enforces secure access but does not configure SSL termination.

Option C is incorrect --- Agent Listener is for PingAccess Agents, not proxied apps.

Option D is incorrect --- secure flag affects cookie settings, not SSL certificates.

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.

PingAccess allows administrators to configure custom error pages or messages at the Root Resource level of 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 A is incorrect --- assigning a rule to a resource does not allow defining custom errors.

Option B is correct --- the Root Resource is where administrators define custom error handling for the entire application.

Option C is incorrect --- Rule Sets only combine rules; they do not handle error responses.

Option D is incorrect --- individual rule definitions do not contain custom error configurations.

All administrative API calls that change PingAccess configuration are logged in pingaccess_api_audit.log. This allows administrators to track who made configuration changes.

Exact Extract:

''The pingaccess_api_audit.log file contains entries for all administrative API calls and is used to audit configuration changes.''

Option A (pingaccess.log) contains runtime system messages but not detailed API audit entries.

Option B (pingaccess_engine_audit.log) is specific to engine request/response audit logging.

Option C (pingaccess_agent_audit.log) is used for PingAccess Agent traffic auditing, not administrative changes.

Option D (pingaccess_api_audit.log) is correct --- it tracks admin API modifications.

PingAccess officially supports Google Chrome and Microsoft Edge for the administrative console. Other browsers (Safari, Opera, Brave) may work but are not officially supported.

Exact Extract:

''The PingAccess administrative console is supported on current versions of Google Chrome and Microsoft Edge.''

Option A (Safari) is not officially supported.

Option B (Opera) is not supported.

Option C (Google Chrome) is correct.

Option D (Microsoft Edge) is correct.

Option E (Brave) is not officially supported.