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 50

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.

Question 491

An enterprise restricts Salesforce access to corporate ranges but employees use approved mobile networks during emergencies. Key caution for this case?

  1. Disabling future logins alone may not prove all previously issued sessions and grants are unusable
  2. Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers
  3. Login history alone does not show every administrative settings change
  4. A certificate-renewal failure is not a justification for accepting unsigned identity assertions

Explanation

Correct Answer

B:

“Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers” 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.

Incorrect Answers

A:

“Disabling future logins alone may not prove all previously issued sessions and grants are unusable” 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:

“Login history alone does not show every administrative settings change” 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.

D:

“A certificate-renewal failure is not a justification for accepting unsigned identity assertions” 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.

Question 492

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

  1. Action: Distinguish high-assurance session requirements from normal login and use supported step-up authentication controls. Verification: Compare actor identity, change history, login events and rollback evidence. Boundary: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.
  2. Action: Design context-sensitive login and app IP restrictions with approved exceptions and staged testing. Verification: Test state mismatch, invalid verifier, exposed-token handling and safe support logs. Boundary: Login history alone does not show every administrative settings change.
  3. Action: Reconcile entitlement changes and verify effective session or token behavior after role removal. Verification: Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths. Boundary: Disabling future logins alone may not prove all previously issued sessions and grants are unusable.
  4. Action: Design context-sensitive login and app IP restrictions with approved exceptions and staged testing. Verification: Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths. Boundary: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

Explanation

Correct Answer

D:

“Action: Design context-sensitive login and app IP restrictions with approved exceptions and staged testing. Verification: Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths. Boundary: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers” 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:

“Action: Distinguish high-assurance session requirements from normal login and use supported step-up authentication controls. Verification: Compare actor identity, change history, login events and rollback evidence. Boundary: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers” 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.

B:

“Action: Design context-sensitive login and app IP restrictions with approved exceptions and staged testing. Verification: Test state mismatch, invalid verifier, exposed-token handling and safe support logs. Boundary: Login history alone does not show every administrative settings change” 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:

“Action: Reconcile entitlement changes and verify effective session or token behavior after role removal. Verification: Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths. Boundary: Disabling future logins alone may not prove all previously issued sessions and grants are unusable” 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 493

A financial org needs stronger session controls for privileged API operations from unknown locations. Best next IAM response?

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

Explanation

Correct Answer

D:

“Design context-sensitive login and app IP restrictions with approved exceptions and staged testing” addresses the access-design responsibilities in a financial org needs stronger session controls for privileged API operations from unknown locations 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:

“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 a financial org needs stronger session controls for privileged API operations from unknown locations The controlling boundary is: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

B:

“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 a financial org needs stronger session controls for privileged API operations from unknown locations The controlling boundary is: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

C:

“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 a financial org needs stronger session controls for privileged API operations from unknown locations The controlling boundary is: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

Question 494

A financial org needs stronger session controls for privileged API operations from unknown locations. Most decisive verification?

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

Explanation

Correct Answer

B:

“Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths” distinguishes sign-in from entitlement administration in a financial org needs stronger session controls for privileged API operations from unknown locations It checks whether design context-sensitive login and app IP restrictions with approved exceptions and staged testing.

Incorrect Answers

A:

“Validate login flow assignment, post-login screen, cancel behavior and emergency access paths” needs to be evaluated against A financial org needs stronger session controls for privileged API operations from unknown locations. 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:

“Test state mismatch, invalid verifier, exposed-token handling and safe support logs” needs to be evaluated against A financial org needs stronger session controls for privileged API operations from unknown locations. 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.

D:

“Compare actor identity, change history, login events and rollback evidence” needs to be evaluated against A financial org needs stronger session controls for privileged API operations from unknown locations. 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.

Question 495

A financial org needs stronger session controls for privileged API operations from unknown locations. Key caution for this case?

  1. Login history alone does not show every administrative settings change
  2. A certificate-renewal failure is not a justification for accepting unsigned identity assertions
  3. Disabling future logins alone may not prove all previously issued sessions and grants are unusable
  4. Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers

Explanation

Correct Answer

D:

“Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers” needs to be evaluated against A financial org needs stronger session controls for privileged API operations from unknown locations. 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.

Incorrect Answers

A:

“Login history alone does not show every administrative settings change” needs to be evaluated against A financial org needs stronger session controls for privileged API operations from unknown locations. 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:

“A certificate-renewal failure is not a justification for accepting unsigned identity assertions” needs to be evaluated against A financial org needs stronger session controls for privileged API operations from unknown locations. 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:

“Disabling future logins alone may not prove all previously issued sessions and grants are unusable” needs to be evaluated against A financial org needs stronger session controls for privileged API operations from unknown locations. 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.

Question 496

A financial org needs stronger session controls for privileged API operations from unknown locations. Best complete IAM decision record?

  1. Action: Reconcile entitlement changes and verify effective session or token behavior after role removal. Verification: Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths. Boundary: Disabling future logins alone may not prove all previously issued sessions and grants are unusable.
  2. Action: Design context-sensitive login and app IP restrictions with approved exceptions and staged testing. Verification: Test state mismatch, invalid verifier, exposed-token handling and safe support logs. Boundary: Login history alone does not show every administrative settings change.
  3. Action: Distinguish high-assurance session requirements from normal login and use supported step-up authentication controls. Verification: Compare actor identity, change history, login events and rollback evidence. Boundary: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.
  4. Action: Design context-sensitive login and app IP restrictions with approved exceptions and staged testing. Verification: Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths. Boundary: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

Explanation

Correct Answer

D:

“Action: Design context-sensitive login and app IP restrictions with approved exceptions and staged testing. Verification: Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths. Boundary: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers” addresses the access-design responsibilities in a financial org needs stronger session controls for privileged API operations from unknown locations 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:

“Action: Reconcile entitlement changes and verify effective session or token behavior after role removal. Verification: Check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths. Boundary: Disabling future logins alone may not prove all previously issued sessions and grants are unusable” may apply to a related identity task, but it does not establish check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths for a financial org needs stronger session controls for privileged API operations from unknown locations The controlling boundary is: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

B:

“Action: Design context-sensitive login and app IP restrictions with approved exceptions and staged testing. Verification: Test state mismatch, invalid verifier, exposed-token handling and safe support logs. Boundary: Login history alone does not show every administrative settings change” may apply to a related identity task, but it does not establish check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths for a financial org needs stronger session controls for privileged API operations from unknown locations The controlling boundary is: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

C:

“Action: Distinguish high-assurance session requirements from normal login and use supported step-up authentication controls. Verification: Compare actor identity, change history, login events and rollback evidence. Boundary: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers” may apply to a related identity task, but it does not establish check allowlists, identity challenge outcomes, VPN assumptions and emergency operator paths for a financial org needs stronger session controls for privileged API operations from unknown locations The controlling boundary is: Broad IP whitelists or forced bypasses can undermine access control or lock out legitimate workers.

Question 497

An incident responder needs to invalidate a compromised browser session immediately after a theft report. Best next IAM response?

  1. Preserve Setup Audit Trail and relevant configuration-change evidence with approved retention
  2. Protect OAuth state, PKCE where appropriate, sensitive token storage and registered redirect validation
  3. Combine account state change with supported session/token revocation and audit the resulting access denial
  4. Use a login flow for approved post-authentication business steps without replacing core authentication controls

Explanation

Correct Answer

C:

“Combine account state change with supported session/token revocation and audit the resulting access denial” addresses the access-design responsibilities in an incident responder needs to invalidate a compromised browser session immediately after a theft report Test against test revoked session, refresh-token rejection, user activity records and alternate devices; disabling future logins alone may not prove all previously issued sessions and grants are unusable.

Incorrect Answers

A:

“Preserve Setup Audit Trail and relevant configuration-change evidence with approved retention” may apply to a related identity task, but it does not establish test revoked session, refresh-token rejection, user activity records and alternate devices for an incident responder needs to invalidate a compromised browser session immediately after a theft report The controlling boundary is: Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

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 test revoked session, refresh-token rejection, user activity records and alternate devices for an incident responder needs to invalidate a compromised browser session immediately after a theft report The controlling boundary is: Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

D:

“Use a login flow for approved post-authentication business steps without replacing core authentication controls” may apply to a related identity task, but it does not establish test revoked session, refresh-token rejection, user activity records and alternate devices for an incident responder needs to invalidate a compromised browser session immediately after a theft report The controlling boundary is: Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

Question 498

An incident responder needs to invalidate a compromised browser session immediately after a theft report. Most decisive verification?

  1. Test revoked session, refresh-token rejection, user activity records and alternate devices
  2. Rehearse IdP outage, alternative admin login, credential custody and post-use review
  3. Validate login flow assignment, post-login screen, cancel behavior and emergency access paths
  4. Track issuer metadata, certificate fingerprints, trust change approvals and login test results

Explanation

Correct Answer

A:

“Test revoked session, refresh-token rejection, user activity records and alternate devices” distinguishes sign-in from entitlement administration in an incident responder needs to invalidate a compromised browser session immediately after a theft report It checks whether combine account state change with supported session/token revocation and audit the resulting access denial.

Incorrect Answers

B:

“Rehearse IdP outage, alternative admin login, credential custody and post-use review” needs to be evaluated against An incident responder needs to invalidate a compromised browser session immediately after a theft report. The relevant check is Test revoked session, refresh-token rejection, user activity records and alternate devices; Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

C:

“Validate login flow assignment, post-login screen, cancel behavior and emergency access paths” needs to be evaluated against An incident responder needs to invalidate a compromised browser session immediately after a theft report. The relevant check is Test revoked session, refresh-token rejection, user activity records and alternate devices; Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

D:

“Track issuer metadata, certificate fingerprints, trust change approvals and login test results” needs to be evaluated against An incident responder needs to invalidate a compromised browser session immediately after a theft report. The relevant check is Test revoked session, refresh-token rejection, user activity records and alternate devices; Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

Question 499

An incident responder needs to invalidate a compromised browser session immediately after a theft report. Key caution for this case?

  1. Global MFA disablement is not a safe default response to one person's lost device
  2. Disabling future logins alone may not prove all previously issued sessions and grants are unusable
  3. Emergency access should be narrow, time-limited and auditable rather than a permanent SSO bypass for all users
  4. A certificate-renewal failure is not a justification for accepting unsigned identity assertions

Explanation

Correct Answer

B:

“Disabling future logins alone may not prove all previously issued sessions and grants are unusable” needs to be evaluated against An incident responder needs to invalidate a compromised browser session immediately after a theft report. The relevant check is Test revoked session, refresh-token rejection, user activity records and alternate devices; Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

Incorrect Answers

A:

“Global MFA disablement is not a safe default response to one person's lost device” needs to be evaluated against An incident responder needs to invalidate a compromised browser session immediately after a theft report. The relevant check is Test revoked session, refresh-token rejection, user activity records and alternate devices; Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

C:

“Emergency access should be narrow, time-limited and auditable rather than a permanent SSO bypass for all users” needs to be evaluated against An incident responder needs to invalidate a compromised browser session immediately after a theft report. The relevant check is Test revoked session, refresh-token rejection, user activity records and alternate devices; Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

D:

“A certificate-renewal failure is not a justification for accepting unsigned identity assertions” needs to be evaluated against An incident responder needs to invalidate a compromised browser session immediately after a theft report. The relevant check is Test revoked session, refresh-token rejection, user activity records and alternate devices; Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

Question 500

An incident responder needs to invalidate a compromised browser session immediately after a theft report. Best complete IAM decision record?

  1. Action: Use a login flow for approved post-authentication business steps without replacing core authentication controls. Verification: Test revoked session, refresh-token rejection, user activity records and alternate devices. Boundary: Emergency access should be narrow, time-limited and auditable rather than a permanent SSO bypass for all users.
  2. Action: Combine account state change with supported session/token revocation and audit the resulting access denial. Verification: Validate login flow assignment, post-login screen, cancel behavior and emergency access paths. Boundary: Global MFA disablement is not a safe default response to one person's lost device.
  3. Action: Preserve Setup Audit Trail and relevant configuration-change evidence with approved retention. Verification: Track issuer metadata, certificate fingerprints, trust change approvals and login test results. Boundary: Disabling future logins alone may not prove all previously issued sessions and grants are unusable.
  4. Action: Combine account state change with supported session/token revocation and audit the resulting access denial. Verification: Test revoked session, refresh-token rejection, user activity records and alternate devices. Boundary: Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

Explanation

Correct Answer

D:

“Action: Combine account state change with supported session/token revocation and audit the resulting access denial. Verification: Test revoked session, refresh-token rejection, user activity records and alternate devices. Boundary: Disabling future logins alone may not prove all previously issued sessions and grants are unusable” addresses the access-design responsibilities in an incident responder needs to invalidate a compromised browser session immediately after a theft report Test against test revoked session, refresh-token rejection, user activity records and alternate devices; disabling future logins alone may not prove all previously issued sessions and grants are unusable.

Incorrect Answers

A:

“Action: Use a login flow for approved post-authentication business steps without replacing core authentication controls. Verification: Test revoked session, refresh-token rejection, user activity records and alternate devices. 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 test revoked session, refresh-token rejection, user activity records and alternate devices for an incident responder needs to invalidate a compromised browser session immediately after a theft report The controlling boundary is: Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

B:

“Action: Combine account state change with supported session/token revocation and audit the resulting access denial. Verification: Validate login flow assignment, post-login screen, cancel behavior and emergency access paths. 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 test revoked session, refresh-token rejection, user activity records and alternate devices for an incident responder needs to invalidate a compromised browser session immediately after a theft report The controlling boundary is: Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

C:

“Action: Preserve Setup Audit Trail and relevant configuration-change evidence with approved retention. Verification: Track issuer metadata, certificate fingerprints, trust change approvals and login test results. Boundary: Disabling future logins alone may not prove all previously issued sessions and grants are unusable” may apply to a related identity task, but it does not establish test revoked session, refresh-token rejection, user activity records and alternate devices for an incident responder needs to invalidate a compromised browser session immediately after a theft report The controlling boundary is: Disabling future logins alone may not prove all previously issued sessions and grants are unusable.

Certified Platform Identity and Access Management Architect Practice Tests