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 80

Question 790

A seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy. Most decisive verification?

  1. Inspect account hierarchy, sharing assignments, membership changes and negative access tests
  2. Test issuer trust, provider subject, duplicate contact matching and re-login outcomes
  3. Simulate peak signup, duplicate identities, inactive records and reactivation handling
  4. Test unauthenticated registration path, invite token, profile selection and elevation denial

Explanation

Correct Answer

C:

“Simulate peak signup, duplicate identities, inactive records and reactivation handling” distinguishes sign-in from entitlement administration in a seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy It checks whether plan scalable user provisioning, license selection, stable identity matching and dormant-account governance.

Incorrect Answers

A:

“Inspect account hierarchy, sharing assignments, membership changes and negative access tests” needs to be evaluated against A seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy. The relevant check is Simulate peak signup, duplicate identities, inactive records and reactivation handling; A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.

B:

“Test issuer trust, provider subject, duplicate contact matching and re-login outcomes” needs to be evaluated against A seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy. The relevant check is Simulate peak signup, duplicate identities, inactive records and reactivation handling; A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.

D:

“Test unauthenticated registration path, invite token, profile selection and elevation denial” needs to be evaluated against A seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy. The relevant check is Simulate peak signup, duplicate identities, inactive records and reactivation handling; A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.

Question 791

A seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy. Key caution for this case?

  1. Authentication to an Experience Cloud site does not automatically establish consent for every data use
  2. Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site
  3. A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse
  4. Changing Experience Cloud domains can invalidate federation URLs and redirect targets

Explanation

Correct Answer

C:

“A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse” needs to be evaluated against A seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy. The relevant check is Simulate peak signup, duplicate identities, inactive records and reactivation handling; A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.

Incorrect Answers

A:

“Authentication to an Experience Cloud site does not automatically establish consent for every data use” needs to be evaluated against A seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy. The relevant check is Simulate peak signup, duplicate identities, inactive records and reactivation handling; A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.

B:

“Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site” needs to be evaluated against A seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy. The relevant check is Simulate peak signup, duplicate identities, inactive records and reactivation handling; A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.

D:

“Changing Experience Cloud domains can invalidate federation URLs and redirect targets” needs to be evaluated against A seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy. The relevant check is Simulate peak signup, duplicate identities, inactive records and reactivation handling; A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.

Question 792

A seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy. Best complete IAM decision record?

  1. Action: Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout. Verification: Inspect account hierarchy, sharing assignments, membership changes and negative access tests. Boundary: A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.
  2. Action: Plan scalable user provisioning, license selection, stable identity matching and dormant-account governance. Verification: Simulate peak signup, duplicate identities, inactive records and reactivation handling. Boundary: A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.
  3. Action: Bind partner permissions and sharing to validated account/contact relationships and reconcile changes. Verification: Simulate peak signup, duplicate identities, inactive records and reactivation handling. Boundary: Changing Experience Cloud domains can invalidate federation URLs and redirect targets.
  4. Action: Plan scalable user provisioning, license selection, stable identity matching and dormant-account governance. Verification: Test unauthenticated registration path, invite token, profile selection and elevation denial. Boundary: Authentication to an Experience Cloud site does not automatically establish consent for every data use.

Explanation

Correct Answer

B:

“Action: Plan scalable user provisioning, license selection, stable identity matching and dormant-account governance. Verification: Simulate peak signup, duplicate identities, inactive records and reactivation handling. Boundary: A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse” addresses the access-design responsibilities in a seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy Test against simulate peak signup, duplicate identities, inactive records and reactivation handling; a design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.

Incorrect Answers

A:

“Action: Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout. Verification: Inspect account hierarchy, sharing assignments, membership changes and negative access tests. Boundary: A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse” may apply to a related identity task, but it does not establish simulate peak signup, duplicate identities, inactive records and reactivation handling for a seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy The controlling boundary is: A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.

C:

“Action: Bind partner permissions and sharing to validated account/contact relationships and reconcile changes. Verification: Simulate peak signup, duplicate identities, inactive records and reactivation handling. Boundary: Changing Experience Cloud domains can invalidate federation URLs and redirect targets” may apply to a related identity task, but it does not establish simulate peak signup, duplicate identities, inactive records and reactivation handling for a seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy The controlling boundary is: A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.

D:

“Action: Plan scalable user provisioning, license selection, stable identity matching and dormant-account governance. Verification: Test unauthenticated registration path, invite token, profile selection and elevation denial. Boundary: Authentication to an Experience Cloud site does not automatically establish consent for every data use” may apply to a related identity task, but it does not establish simulate peak signup, duplicate identities, inactive records and reactivation handling for a seasonal marketplace sees spikes of customer self-registration and repeated federated login after months of dormancy The controlling boundary is: A design that works for a handful of test users may fail under B2C scale or long-dormant identity reuse.

Question 793

A franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions. Best next IAM response?

  1. Define an external-user MFA and recovery assurance policy consistent with supported Salesforce and IdP controls
  2. Design sign-out behavior and communicate supported single logout versus local session termination
  3. Coordinate account or contact deactivation with external session, OAuth token and data-retention controls
  4. Plan scalable user provisioning, license selection, stable identity matching and dormant-account governance

Explanation

Correct Answer

C:

“Coordinate account or contact deactivation with external session, OAuth token and data-retention controls” addresses the access-design responsibilities in a franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions Test against verify site membership removal, token revocation, contact status and legitimate retention requirements; deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Incorrect Answers

A:

“Define an external-user MFA and recovery assurance policy consistent with supported Salesforce and IdP controls” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

B:

“Design sign-out behavior and communicate supported single logout versus local session termination” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

D:

“Plan scalable user provisioning, license selection, stable identity matching and dormant-account governance” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Question 794

A franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions. Most decisive verification?

  1. Validate profile and permission set, account role model, sharing criteria and row-level tests
  2. Inspect guest profile, object permissions, sharing rules and anonymous negative access checks
  3. Verify site membership removal, token revocation, contact status and legitimate retention requirements
  4. Review privacy notice version, permission to process, retention and data field minimization

Explanation

Correct Answer

C:

“Verify site membership removal, token revocation, contact status and legitimate retention requirements” distinguishes sign-in from entitlement administration in a franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions It checks whether coordinate account or contact deactivation with external session, OAuth token and data-retention controls.

Incorrect Answers

A:

“Validate profile and permission set, account role model, sharing criteria and row-level tests” needs to be evaluated against A franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

B:

“Inspect guest profile, object permissions, sharing rules and anonymous negative access checks” needs to be evaluated against A franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

D:

“Review privacy notice version, permission to process, retention and data field minimization” needs to be evaluated against A franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Question 795

A franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions. Key caution for this case?

  1. Custom login pages must preserve anti-phishing signals and should not expose user enumeration details
  2. Clearing one application's session does not necessarily terminate every federated identity-provider session
  3. Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion
  4. Authentication to an Experience Cloud site does not automatically establish consent for every data use

Explanation

Correct Answer

C:

“Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion” needs to be evaluated against A franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Incorrect Answers

A:

“Custom login pages must preserve anti-phishing signals and should not expose user enumeration details” needs to be evaluated against A franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

B:

“Clearing one application's session does not necessarily terminate every federated identity-provider session” needs to be evaluated against A franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

D:

“Authentication to an Experience Cloud site does not automatically establish consent for every data use” needs to be evaluated against A franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Question 796

A franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions. Best complete IAM decision record?

  1. Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Verify site membership removal, token revocation, contact status and legitimate retention requirements. Boundary: Custom login pages must preserve anti-phishing signals and should not expose user enumeration details.
  2. Action: Coordinate account or contact deactivation with external session, OAuth token and data-retention controls. Verification: Verify site membership removal, token revocation, contact status and legitimate retention requirements. Boundary: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.
  3. Action: Coordinate account or contact deactivation with external session, OAuth token and data-retention controls. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: Clearing one application's session does not necessarily terminate every federated identity-provider session.
  4. Action: Define an external-user MFA and recovery assurance policy consistent with supported Salesforce and IdP controls. Verification: Validate profile and permission set, account role model, sharing criteria and row-level tests. Boundary: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Explanation

Correct Answer

B:

“Action: Coordinate account or contact deactivation with external session, OAuth token and data-retention controls. Verification: Verify site membership removal, token revocation, contact status and legitimate retention requirements. Boundary: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion” addresses the access-design responsibilities in a franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions Test against verify site membership removal, token revocation, contact status and legitimate retention requirements; deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Incorrect Answers

A:

“Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Verify site membership removal, token revocation, contact status and legitimate retention requirements. Boundary: Custom login pages must preserve anti-phishing signals and should not expose user enumeration details” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

C:

“Action: Coordinate account or contact deactivation with external session, OAuth token and data-retention controls. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: Clearing one application's session does not necessarily terminate every federated identity-provider session” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

D:

“Action: Define an external-user MFA and recovery assurance policy consistent with supported Salesforce and IdP controls. Verification: Validate profile and permission set, account role model, sharing criteria and row-level tests. Boundary: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a franchise terminates a partner relationship but several associated Experience Cloud users still have active sessions The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Question 797

A customer requests account closure while external app refresh tokens and portal contact references persist. Best next IAM response?

  1. Plan scalable user provisioning, license selection, stable identity matching and dormant-account governance
  2. Design sign-out behavior and communicate supported single logout versus local session termination
  3. Coordinate account or contact deactivation with external session, OAuth token and data-retention controls
  4. Define an external-user MFA and recovery assurance policy consistent with supported Salesforce and IdP controls

Explanation

Correct Answer

C:

“Coordinate account or contact deactivation with external session, OAuth token and data-retention controls” addresses the access-design responsibilities in a customer requests account closure while external app refresh tokens and portal contact references persist Test against verify site membership removal, token revocation, contact status and legitimate retention requirements; deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Incorrect Answers

A:

“Plan scalable user provisioning, license selection, stable identity matching and dormant-account governance” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a customer requests account closure while external app refresh tokens and portal contact references persist The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

B:

“Design sign-out behavior and communicate supported single logout versus local session termination” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a customer requests account closure while external app refresh tokens and portal contact references persist The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

D:

“Define an external-user MFA and recovery assurance policy consistent with supported Salesforce and IdP controls” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a customer requests account closure while external app refresh tokens and portal contact references persist The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Question 798

A customer requests account closure while external app refresh tokens and portal contact references persist. Most decisive verification?

  1. Review privacy notice version, permission to process, retention and data field minimization
  2. Inspect guest profile, object permissions, sharing rules and anonymous negative access checks
  3. Verify site membership removal, token revocation, contact status and legitimate retention requirements
  4. Validate profile and permission set, account role model, sharing criteria and row-level tests

Explanation

Correct Answer

C:

“Verify site membership removal, token revocation, contact status and legitimate retention requirements” distinguishes sign-in from entitlement administration in a customer requests account closure while external app refresh tokens and portal contact references persist It checks whether coordinate account or contact deactivation with external session, OAuth token and data-retention controls.

Incorrect Answers

A:

“Review privacy notice version, permission to process, retention and data field minimization” needs to be evaluated against A customer requests account closure while external app refresh tokens and portal contact references persist. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

B:

“Inspect guest profile, object permissions, sharing rules and anonymous negative access checks” needs to be evaluated against A customer requests account closure while external app refresh tokens and portal contact references persist. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

D:

“Validate profile and permission set, account role model, sharing criteria and row-level tests” needs to be evaluated against A customer requests account closure while external app refresh tokens and portal contact references persist. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Question 799

A customer requests account closure while external app refresh tokens and portal contact references persist. Key caution for this case?

  1. Authentication to an Experience Cloud site does not automatically establish consent for every data use
  2. Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion
  3. Clearing one application's session does not necessarily terminate every federated identity-provider session
  4. Custom login pages must preserve anti-phishing signals and should not expose user enumeration details

Explanation

Correct Answer

B:

“Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion” needs to be evaluated against A customer requests account closure while external app refresh tokens and portal contact references persist. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Incorrect Answers

A:

“Authentication to an Experience Cloud site does not automatically establish consent for every data use” needs to be evaluated against A customer requests account closure while external app refresh tokens and portal contact references persist. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

C:

“Clearing one application's session does not necessarily terminate every federated identity-provider session” needs to be evaluated against A customer requests account closure while external app refresh tokens and portal contact references persist. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

D:

“Custom login pages must preserve anti-phishing signals and should not expose user enumeration details” needs to be evaluated against A customer requests account closure while external app refresh tokens and portal contact references persist. The relevant check is Verify site membership removal, token revocation, contact status and legitimate retention requirements; Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Question 800

A customer requests account closure while external app refresh tokens and portal contact references persist. Best complete IAM decision record?

  1. Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Verify site membership removal, token revocation, contact status and legitimate retention requirements. Boundary: Custom login pages must preserve anti-phishing signals and should not expose user enumeration details.
  2. Action: Define an external-user MFA and recovery assurance policy consistent with supported Salesforce and IdP controls. Verification: Validate profile and permission set, account role model, sharing criteria and row-level tests. Boundary: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.
  3. Action: Coordinate account or contact deactivation with external session, OAuth token and data-retention controls. Verification: Verify site membership removal, token revocation, contact status and legitimate retention requirements. Boundary: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.
  4. Action: Coordinate account or contact deactivation with external session, OAuth token and data-retention controls. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: Clearing one application's session does not necessarily terminate every federated identity-provider session.

Explanation

Correct Answer

C:

“Action: Coordinate account or contact deactivation with external session, OAuth token and data-retention controls. Verification: Verify site membership removal, token revocation, contact status and legitimate retention requirements. Boundary: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion” addresses the access-design responsibilities in a customer requests account closure while external app refresh tokens and portal contact references persist Test against verify site membership removal, token revocation, contact status and legitimate retention requirements; deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Incorrect Answers

A:

“Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Verify site membership removal, token revocation, contact status and legitimate retention requirements. Boundary: Custom login pages must preserve anti-phishing signals and should not expose user enumeration details” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a customer requests account closure while external app refresh tokens and portal contact references persist The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

B:

“Action: Define an external-user MFA and recovery assurance policy consistent with supported Salesforce and IdP controls. Verification: Validate profile and permission set, account role model, sharing criteria and row-level tests. Boundary: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a customer requests account closure while external app refresh tokens and portal contact references persist The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

D:

“Action: Coordinate account or contact deactivation with external session, OAuth token and data-retention controls. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: Clearing one application's session does not necessarily terminate every federated identity-provider session” may apply to a related identity task, but it does not establish verify site membership removal, token revocation, contact status and legitimate retention requirements for a customer requests account closure while external app refresh tokens and portal contact references persist The controlling boundary is: Deleting a front-end login option alone cannot guarantee complete deprovisioning or lawful data deletion.

Certified Platform Identity and Access Management Architect Practice Tests