An application requires MFA for URLs that are considered high risk. Which action should the administrator take to meet this requirement?
PingAccess allows fine-grained authentication enforcement by applying Authentication Requirement rules at the resource level. These rules can invoke MFA flows based on request context or policy.
Exact Extract:
''Authentication requirement rules determine whether PingAccess challenges a user to authenticate again (for example, with MFA) before allowing access to a protected resource.''
Option A is incomplete. Creating a requirement does nothing unless it is applied.
Option B is correct because applying the Authentication Requirement rule to the specific resource (URL) enforces MFA only for that resource.
Option C is incorrect; Web Session Attribute rules are about evaluating existing session attributes, not triggering MFA.
Option D is incorrect; HTTP Request Parameter rules are used to evaluate request data, not enforce MFA policies.
A business application must be accessible via two FQDNs. Which PingAccess functionality should an administrator use to meet this requirement?
Virtual Hosts in PingAccess define the external FQDNs (and ports) through which applications are accessed. An application can be bound to multiple virtual hosts to allow access via multiple FQDNs.
Exact Extract:
''A virtual host specifies the fully qualified domain name and port number through which an application is accessed.''
Option A (Virtual Hosts) is correct --- multiple FQDNs can be supported by assigning multiple virtual hosts.
Option B (Applications) define resource protection but do not manage FQDN binding.
Option C (Sites) define back-end targets, not the public-facing FQDN.
Option D (Web Sessions) handle authentication state, unrelated to hostnames.
Developers report an issue with an application that is protected by PingAccess. Certain requests are not providing claims that are part of the access token.
What should the administrator add for the access token claims?
In PingAccess, when an application relies on claims from an OAuth access token, you must configure PingAccess to evaluate those claims and potentially inject them into headers for the backend application.
Exact Extract from PingAccess documentation:
''OAuth rules allow you to evaluate claims in OAuth access tokens. You can configure PingAccess to look at specific claims and enforce policies or pass them to target applications.''
''To extract attributes from an access token, configure an OAuth Attribute Rule.''
This clearly matches option D.
Analysis of each option:
A . An authentication requirement definition
Incorrect. Authentication requirements determine how users authenticate to applications (OIDC provider, etc.), but do not manage access token claims.
B . A web session attribute rule
Incorrect. Web session attribute rules map attributes from the authenticated user's web session (SSO session), not from OAuth access tokens.
C . An identity mapping definition
Incorrect. Identity mappings transform user attributes (from IdP to app), but they don't directly pull claims from OAuth tokens.
D . An OAuth attribute rule
Correct. This rule is specifically designed to extract and enforce policies on claims from OAuth access tokens.
Therefore, the correct answer is D. An OAuth attribute rule.
An administrator must protect an application on multiple domains or hosts. What should the administrator configure to complete this action?
Applications in PingAccess can be associated with multiple Virtual Hosts. Each virtual host defines an FQDN and port combination through which the application is exposed, allowing protection across multiple domains or hostnames.
Exact Extract:
''Virtual hosts specify the fully qualified domain names (FQDNs) and ports that PingAccess uses to expose applications.''
Option A (Sites) represent the target back-end servers, not the external FQDN.
Option B (Virtual Hosts) is correct --- use multiple virtual hosts for multiple domains.
Option C (Redirects) are unrelated to multi-domain application protection.
Option D (Rules) define access policies, not hostnames.
An administrator must onboard a new application from the application team. The application has multiple paths that will need different rules. What would be the first step in this process?
All onboarding in PingAccess begins with defining an Application. Once the application exists, the administrator can define Resources within it and assign different rules to those resources.
Exact Extract:
''Before you can configure resources and rules, you must first create an application in PingAccess.''
Option A (Identity Mapping) may be required later but not the first step.
Option B (Web Session) can be shared but is not the first onboarding step.
Option C (Application) is correct --- the starting point for onboarding.
Option D (Resource) comes after creating the application.
Tammy
13 hours agoHelene
10 days agoSherita
17 days agoWillie
25 days agoGracia
1 month agoNelida
1 month agoDiego
2 months agoDorothea
2 months agoCaitlin
2 months agoTemeka
2 months agoBulah
3 months agoRolande
3 months agoPaz
3 months agoSamuel
3 months agoBillye
4 months agoMarquetta
4 months agoTerrilyn
4 months agoRebeca
4 months agoBelen
5 months agoBrianne
5 months agoRhea
5 months agoKristel
5 months agoDaisy
5 months agoKatina
6 months ago