PingAccess retains backup archives of its configuration in thedata/archivedirectory. The number of retained backups is controlled in therun.propertiesfile.
Exact Extract:
"The number of configuration backups retained in thedata/archivedirectory is controlled by thearchive.
maxCountproperty inrun.properties."
* Option A (log4j2.db.properties)is incorrect; this file controls database logging, not archive retention.
* Option B (jvm-memory.options)is incorrect; this file sets JVM heap and memory arguments.
* Option C (run.properties)is correct - it contains system-level settings includingarchive.maxCount.
* Option D (log4j2.xml)is incorrect; this file configures log appenders and levels, not archive backups.
Reference:PingAccess Administration Guide -Configuration Backup Management

When configuring PingAccess to use PingFederate as theStandard Token Providerfor runtime engines, PingAccess must know how to contact PingFederate. The configuration requires theHost(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.
Reference:PingAccess Administration Guide -Configuring PingFederate as a Token Provider

PingAccess supports logging directly to a relational database usingLog4j database appenders. To enable this:
* Configurelog4j2.xmlto use a JDBC Appender.
* Configurelog4j2.db.propertieswith the database connection information.
* Provide the appropriate database driver in thePA_HOME/libdirectory.
Exact Extract:
"To log to a database, configure log4j2.xml and log4j2.db.properties, and place the JDBC driver JAR file in PA_HOME/lib."
* Option Ais correct - both files must be configured.
* Option Bis incorrect - existing logs do not need removal.
* Option Cis incorrect - enabling audit is unrelated to database logging.
* Option Dis correct - the Oracle JDBC driver must be installed in PA_HOME/lib.
* Option Eis incorrect unless TLS is used to connect to the DB, but it is not required for standard DB logging setup.
Reference:PingAccess Administration Guide -Log Configuration

Identity Mapping in PingAccess relies on attributes provided by thetoken provider(e.g., PingFederate, OIDC provider). If the desired attributes are not present in the dropdown, it means they are not being provided in the token or userinfo response.
Exact Extract:
"Attributes available in identity mappings are those provided in the web session by the token provider. If attributes are missing, they must be added to the token by the identity provider."
* Option Ais correct - the token provider administrator must configure the IdP to include the additional attributes.
* Option Bis incorrect - rewrite rules modify content but do not supply new identity attributes.
* Option Cis incorrect - developers cannot directly add identity attributes; they must come from the IdP.
* Option Dis incorrect - Web Session Attribute rules only evaluate available attributes; they don't create new ones.
Reference:PingAccess Administration Guide -Identity Mapping and Attributes