mcAfee Secure Website
exam =5
exam =6

Exam Code: Certified Platform Identity and Access Management Architect

Exam Name: Certified Platform Identity and Access Management Architect

Certification Provider: Salesforce

Salesforce Certified Platform Identity and Access Management Architect Questions & Answers

Reliable & Actual Study Materials for Certified Platform Identity and Access Management Architect Exam Success

58 Questions & Answers with Testing Engine

"Certified Platform Identity and Access Management Architect: Certified Platform Identity and Access Management Architect" Testing Engine covers all the knowledge points of the real Salesforce Certified Platform Identity and Access Management Architect exam.

The latest actual Certified Platform Identity and Access Management Architect Questions & Answers from Pass4sure. Everything you need to prepare and get best score at Certified Platform Identity and Access Management Architect exam easily and quickly.

exam =7
Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Salesforce Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Was: $137.49
Now: $124.99

Salesforce Certified Platform Identity and Access Management Architect Practice Test 49

Question 480

An acquired business has hundreds of user profiles with inconsistent object entitlements. Best complete IAM decision record?

  1. Action: Preserve Setup Audit Trail and relevant configuration-change evidence with approved retention. Verification: Review license prerequisites, profile defaults, permission sets and effective access tests. Boundary: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.
  2. Action: Use a login flow for approved post-authentication business steps without replacing core authentication controls. Verification: Compare new permissions, active sessions, app policies and denied legacy actions. Boundary: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged.
  3. Action: Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties. Verification: Inspect permission activation event, session level, granted rights and expiration. Boundary: A second password or another knowledge-only challenge is not automatically an independent MFA factor.
  4. Action: Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties. Verification: Review license prerequisites, profile defaults, permission sets and effective access tests. Boundary: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged.

Explanation

Correct Answer

D:

“Action: Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties. Verification: Review license prerequisites, profile defaults, permission sets and effective access tests. Boundary: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged” addresses the access-design responsibilities in an acquired business has hundreds of user profiles with inconsistent object entitlements Test against review license prerequisites, profile defaults, permission sets and effective access tests; a successful federation login does not prove that the user's actual Salesforce data rights are least privileged.

Incorrect Answers

A:

“Action: Preserve Setup Audit Trail and relevant configuration-change evidence with approved retention. Verification: Review license prerequisites, profile defaults, permission sets and effective access tests. Boundary: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation” may apply to a related identity task, but it does not establish review license prerequisites, profile defaults, permission sets and effective access tests for an acquired business has hundreds of user profiles with inconsistent object entitlements The controlling boundary is: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged.

B:

“Action: Use a login flow for approved post-authentication business steps without replacing core authentication controls. Verification: Compare new permissions, active sessions, app policies and denied legacy actions. Boundary: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged” may apply to a related identity task, but it does not establish review license prerequisites, profile defaults, permission sets and effective access tests for an acquired business has hundreds of user profiles with inconsistent object entitlements The controlling boundary is: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged.

C:

“Action: Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties. Verification: Inspect permission activation event, session level, granted rights and expiration. Boundary: A second password or another knowledge-only challenge is not automatically an independent MFA factor” may apply to a related identity task, but it does not establish review license prerequisites, profile defaults, permission sets and effective access tests for an acquired business has hundreds of user profiles with inconsistent object entitlements The controlling boundary is: A successful federation login does not prove that the user's actual Salesforce data rights are least privileged.

Question 481

A vendor connected app asks for full API access although it needs only account read operations. Best next IAM response?

  1. Use session-based permission sets or suitable session assurance controls where supported, with clear revocation
  2. Protect OAuth state, PKCE where appropriate, sensitive token storage and registered redirect validation
  3. Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties
  4. Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions

Explanation

Correct Answer

D:

“Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions” addresses the access-design responsibilities in a vendor connected app asks for full API access although it needs only account read operations Test against validate external client app policies, token grants, permission sets and denied requests; narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Incorrect Answers

A:

“Use session-based permission sets or suitable session assurance controls where supported, with clear revocation” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a vendor connected app asks for full API access although it needs only account read operations The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

B:

“Protect OAuth state, PKCE where appropriate, sensitive token storage and registered redirect validation” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a vendor connected app asks for full API access although it needs only account read operations The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

C:

“Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a vendor connected app asks for full API access although it needs only account read operations The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Question 482

A vendor connected app asks for full API access although it needs only account read operations. Most decisive verification?

  1. Inspect permission activation event, session level, granted rights and expiration
  2. Inspect event timestamps, user IDs, error categories, device/session context and audit retention
  3. Validate external client app policies, token grants, permission sets and denied requests
  4. Validate login flow assignment, post-login screen, cancel behavior and emergency access paths

Explanation

Correct Answer

C:

“Validate external client app policies, token grants, permission sets and denied requests” distinguishes sign-in from entitlement administration in a vendor connected app asks for full API access although it needs only account read operations It checks whether enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions.

Incorrect Answers

A:

“Inspect permission activation event, session level, granted rights and expiration” needs to be evaluated against A vendor connected app asks for full API access although it needs only account read operations. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

B:

“Inspect event timestamps, user IDs, error categories, device/session context and audit retention” needs to be evaluated against A vendor connected app asks for full API access although it needs only account read operations. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

D:

“Validate login flow assignment, post-login screen, cancel behavior and emergency access paths” needs to be evaluated against A vendor connected app asks for full API access although it needs only account read operations. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Question 483

A vendor connected app asks for full API access although it needs only account read operations. Key caution for this case?

  1. Global MFA disablement is not a safe default response to one person's lost device
  2. Updating directory membership is not always equivalent to promptly revoking application-side access
  3. Emergency access should be narrow, time-limited and auditable rather than a permanent SSO bypass for all users
  4. Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation

Explanation

Correct Answer

D:

“Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation” needs to be evaluated against A vendor connected app asks for full API access although it needs only account read operations. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Incorrect Answers

A:

“Global MFA disablement is not a safe default response to one person's lost device” needs to be evaluated against A vendor connected app asks for full API access although it needs only account read operations. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

B:

“Updating directory membership is not always equivalent to promptly revoking application-side access” needs to be evaluated against A vendor connected app asks for full API access although it needs only account read operations. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

C:

“Emergency access should be narrow, time-limited and auditable rather than a permanent SSO bypass for all users” needs to be evaluated against A vendor connected app asks for full API access although it needs only account read operations. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Question 484

A vendor connected app asks for full API access although it needs only account read operations. Best complete IAM decision record?

  1. Action: Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions. Verification: Inspect permission activation event, session level, granted rights and expiration. Boundary: Global MFA disablement is not a safe default response to one person's lost device.
  2. Action: Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties. Verification: Validate external client app policies, token grants, permission sets and denied requests. Boundary: Emergency access should be narrow, time-limited and auditable rather than a permanent SSO bypass for all users.
  3. Action: Use session-based permission sets or suitable session assurance controls where supported, with clear revocation. Verification: Inspect event timestamps, user IDs, error categories, device/session context and audit retention. Boundary: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.
  4. Action: Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions. Verification: Validate external client app policies, token grants, permission sets and denied requests. Boundary: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Explanation

Correct Answer

D:

“Action: Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions. Verification: Validate external client app policies, token grants, permission sets and denied requests. Boundary: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation” addresses the access-design responsibilities in a vendor connected app asks for full API access although it needs only account read operations Test against validate external client app policies, token grants, permission sets and denied requests; narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Incorrect Answers

A:

“Action: Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions. Verification: Inspect permission activation event, session level, granted rights and expiration. Boundary: Global MFA disablement is not a safe default response to one person's lost device” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a vendor connected app asks for full API access although it needs only account read operations The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

B:

“Action: Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties. Verification: Validate external client app policies, token grants, permission sets and denied requests. Boundary: Emergency access should be narrow, time-limited and auditable rather than a permanent SSO bypass for all users” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a vendor connected app asks for full API access although it needs only account read operations The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

C:

“Action: Use session-based permission sets or suitable session assurance controls where supported, with clear revocation. Verification: Inspect event timestamps, user IDs, error categories, device/session context and audit retention. Boundary: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a vendor connected app asks for full API access although it needs only account read operations The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Question 485

A marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export. Best next IAM response?

  1. Protect OAuth state, PKCE where appropriate, sensitive token storage and registered redirect validation
  2. Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties
  3. Use session-based permission sets or suitable session assurance controls where supported, with clear revocation
  4. Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions

Explanation

Correct Answer

D:

“Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions” addresses the access-design responsibilities in a marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export Test against validate external client app policies, token grants, permission sets and denied requests; narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Incorrect Answers

A:

“Protect OAuth state, PKCE where appropriate, sensitive token storage and registered redirect validation” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

B:

“Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

C:

“Use session-based permission sets or suitable session assurance controls where supported, with clear revocation” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Question 486

A marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export. Most decisive verification?

  1. Inspect event timestamps, user IDs, error categories, device/session context and audit retention
  2. Validate external client app policies, token grants, permission sets and denied requests
  3. Inspect permission activation event, session level, granted rights and expiration
  4. Validate login flow assignment, post-login screen, cancel behavior and emergency access paths

Explanation

Correct Answer

B:

“Validate external client app policies, token grants, permission sets and denied requests” distinguishes sign-in from entitlement administration in a marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export It checks whether enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions.

Incorrect Answers

A:

“Inspect event timestamps, user IDs, error categories, device/session context and audit retention” needs to be evaluated against A marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

C:

“Inspect permission activation event, session level, granted rights and expiration” needs to be evaluated against A marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

D:

“Validate login flow assignment, post-login screen, cancel behavior and emergency access paths” needs to be evaluated against A marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Question 487

A marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export. Key caution for this case?

  1. Updating directory membership is not always equivalent to promptly revoking application-side access
  2. Global MFA disablement is not a safe default response to one person's lost device
  3. Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation
  4. Emergency access should be narrow, time-limited and auditable rather than a permanent SSO bypass for all users

Explanation

Correct Answer

C:

“Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation” needs to be evaluated against A marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Incorrect Answers

A:

“Updating directory membership is not always equivalent to promptly revoking application-side access” needs to be evaluated against A marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

B:

“Global MFA disablement is not a safe default response to one person's lost device” needs to be evaluated against A marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

D:

“Emergency access should be narrow, time-limited and auditable rather than a permanent SSO bypass for all users” needs to be evaluated against A marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export. The relevant check is Validate external client app policies, token grants, permission sets and denied requests; Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Question 488

A marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export. Best complete IAM decision record?

  1. Action: Use session-based permission sets or suitable session assurance controls where supported, with clear revocation. Verification: Inspect event timestamps, user IDs, error categories, device/session context and audit retention. Boundary: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.
  2. Action: Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions. Verification: Inspect permission activation event, session level, granted rights and expiration. Boundary: Global MFA disablement is not a safe default response to one person's lost device.
  3. Action: Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties. Verification: Validate external client app policies, token grants, permission sets and denied requests. Boundary: Emergency access should be narrow, time-limited and auditable rather than a permanent SSO bypass for all users.
  4. Action: Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions. Verification: Validate external client app policies, token grants, permission sets and denied requests. Boundary: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Explanation

Correct Answer

D:

“Action: Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions. Verification: Validate external client app policies, token grants, permission sets and denied requests. Boundary: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation” addresses the access-design responsibilities in a marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export Test against validate external client app policies, token grants, permission sets and denied requests; narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Incorrect Answers

A:

“Action: Use session-based permission sets or suitable session assurance controls where supported, with clear revocation. Verification: Inspect event timestamps, user IDs, error categories, device/session context and audit retention. Boundary: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

B:

“Action: Enforce app-specific policy and least privilege across client registration, OAuth scopes and underlying user permissions. Verification: Inspect permission activation event, session level, granted rights and expiration. Boundary: Global MFA disablement is not a safe default response to one person's lost device” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

C:

“Action: Favor minimum profiles plus targeted permission sets and permission-set groups for approved duties. Verification: Validate external client app policies, token grants, permission sets and denied requests. Boundary: Emergency access should be narrow, time-limited and auditable rather than a permanent SSO bypass for all users” may apply to a related identity task, but it does not establish validate external client app policies, token grants, permission sets and denied requests for a marketplace partner requests refresh-token access and broad Salesforce user profiles for a scheduled export The controlling boundary is: Narrowing token scopes cannot compensate for unrestricted API execution identities in every situation.

Question 489

An enterprise restricts Salesforce access to corporate ranges but employees use approved mobile networks during emergencies. Best next IAM response?

  1. Distinguish high-assurance session requirements from normal login and use supported step-up authentication controls
  2. Design context-sensitive login and app IP restrictions with approved exceptions and staged testing
  3. Reconcile entitlement changes and verify effective session or token behavior after role removal
  4. Use a verified identity recovery and MFA re-enrollment process for affected users

Explanation

Correct Answer

B:

“Design context-sensitive login and app IP restrictions with approved exceptions and staged testing” addresses the access-design responsibilities in an enterprise restricts Salesforce access to corporate ranges but employees use approved mobile networks during emergencies Test against check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths; broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

Incorrect Answers

A:

“Distinguish high-assurance session requirements from normal login and use supported step-up authentication controls” may apply to a related identity task, but it does not establish check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths for an enterprise restricts Salesforce access to corporate ranges but employees use approved mobile networks during emergencies The controlling boundary is: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

C:

“Reconcile entitlement changes and verify effective session or token behavior after role removal” may apply to a related identity task, but it does not establish check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths for an enterprise restricts Salesforce access to corporate ranges but employees use approved mobile networks during emergencies The controlling boundary is: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

D:

“Use a verified identity recovery and MFA re-enrollment process for affected users” may apply to a related identity task, but it does not establish check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths for an enterprise restricts Salesforce access to corporate ranges but employees use approved mobile networks during emergencies The controlling boundary is: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

Question 490

An enterprise restricts Salesforce access to corporate ranges but employees use approved mobile networks during emergencies. Most decisive verification?

  1. Test state mismatch, invalid verifier, exposed-token handling and safe support logs
  2. Validate login flow assignment, post-login screen, cancel behavior and emergency access paths
  3. Compare actor identity, change history, login events and rollback evidence
  4. Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths

Explanation

Correct Answer

D:

“Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths” distinguishes sign-in from entitlement administration in an enterprise restricts Salesforce access to corporate ranges but employees use approved mobile networks during emergencies It checks whether design context-sensitive login and app IP restrictions with approved exceptions and staged testing.

Incorrect Answers

A:

“Test state mismatch, invalid verifier, exposed-token handling and safe support logs” needs to be evaluated against An enterprise restricts Salesforce access to corporate ranges but employees use approved mobile networks during emergencies. The relevant check is Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths; Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

B:

“Validate login flow assignment, post-login screen, cancel behavior and emergency access paths” needs to be evaluated against An enterprise restricts Salesforce access to corporate ranges but employees use approved mobile networks during emergencies. The relevant check is Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths; Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

C:

“Compare actor identity, change history, login events and rollback evidence” needs to be evaluated against An enterprise restricts Salesforce access to corporate ranges but employees use approved mobile networks during emergencies. The relevant check is Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths; Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

Certified Platform Identity and Access Management Architect Practice Tests