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?
Modern browsers enforce stricter cookie handling rules. If cookies are not configured correctly with the SameSite attribute, 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.
The performance testing team finds that an API hosted in a remote datacenter is experiencing higher response times compared to similar APIs hosted onsite. Which option in PingAccess can be used to improve performance in this scenario?
When APIs are remote, latency is introduced by frequent token validation requests. Enabling Cache Token on the OAuth Resource Server reduces repeated validation calls and improves performance.
Exact Extract:
''The OAuth Resource Server configuration includes a Cache Token option that improves performance by reducing round trips for token validation.''
Option A is incorrect --- key rolling affects cryptographic keys, not API latency.
Option B is incorrect --- virtual hosts control external FQDNs, not performance.
Option C is incorrect --- token attribute size does not significantly affect remote latency.
Option D is correct --- caching tokens reduces validation overhead.
An internal audit reveals that an agent has been compromised. What action must be taken to re-secure the agent?
When a PingAccess agent is compromised, the secure approach is to invalidate the existing credentials and issue a new configuration file from the PingAccess Admin Console. This provides a fresh agent.properties file with new secrets, ensuring compromised keys cannot be reused.
Exact Extract:
''If an agent is compromised, revoke and regenerate the agent configuration by downloading a new agent.properties file from the administrative console.''
Option A is incorrect --- manually changing the secret in the file does not propagate it to PingAccess.
Option B is incorrect --- trusted certificates are not tied to agent authentication.
Option C is unnecessary --- reinstalling the agent does not reset credentials.
Option D is correct --- downloading a new agent.properties file re-secures the agent.
What is the purpose of the engine.ssl.protocols in the run.properties file?
The property engine.ssl.protocols in run.properties specifies the TLS protocol versions that PingAccess engines will support for incoming HTTPS traffic.
Exact Extract:
''The engine.ssl.protocols property 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.
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.
Karen Martin
7 days agoEric Green
27 days agoRonald Phillips
1 month agoLaura Ramirez
2 months agoJessica Stewart
2 months agoBetty Perez
3 months agoHeather Harris
3 months agoRobert Phillips
4 months agoAngela Thompson
4 months agoRebecca Thomas
5 months agoRichard Rogers
5 months agoHarold Adams
5 months agoNathan Cooper
5 months agoKenneth Perez
5 months agoChristopher Scott
5 months agoLaura Bell
5 months agoShenika
6 months agoFiliberto
6 months agoIzetta
6 months agoBarrett
7 months agoJaime
7 months agoTammy
7 months agoHelene
7 months agoSherita
8 months agoWillie
8 months agoGracia
8 months agoNelida
8 months agoDiego
9 months agoDorothea
9 months agoCaitlin
9 months agoTemeka
9 months agoBulah
10 months agoRolande
10 months agoPaz
10 months agoSamuel
10 months agoBillye
11 months agoMarquetta
11 months agoTerrilyn
11 months agoRebeca
11 months agoBelen
12 months agoBrianne
12 months agoRhea
12 months agoKristel
1 year agoDaisy
1 year agoKatina
1 year ago