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 78

Question 770

A partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active. Most decisive verification?

  1. Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test
  2. Inspect guest profile, object permissions, sharing rules and anonymous negative access checks
  3. Inspect account hierarchy, sharing assignments, membership changes and negative access tests
  4. Test login discovery, site settings, reset flow, error messaging and accessibility

Explanation

Correct Answer

A:

“Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test” distinguishes sign-in from entitlement administration in a partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active It checks whether design sign-out behavior and communicate supported single logout versus local session termination.

Incorrect Answers

B:

“Inspect guest profile, object permissions, sharing rules and anonymous negative access checks” needs to be evaluated against A partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

C:

“Inspect account hierarchy, sharing assignments, membership changes and negative access tests” needs to be evaluated against A partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

D:

“Test login discovery, site settings, reset flow, error messaging and accessibility” needs to be evaluated against A partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

Question 771

A partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active. Key caution for this case?

  1. Social login alone must not create broad or duplicate Salesforce account entitlements
  2. A public site must never infer data permission merely because a page is accessible without login
  3. Clearing one application's session does not necessarily terminate every federated identity-provider session
  4. Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site

Explanation

Correct Answer

C:

“Clearing one application's session does not necessarily terminate every federated identity-provider session” needs to be evaluated against A partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

Incorrect Answers

A:

“Social login alone must not create broad or duplicate Salesforce account entitlements” needs to be evaluated against A partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

B:

“A public site must never infer data permission merely because a page is accessible without login” needs to be evaluated against A partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

D:

“Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site” needs to be evaluated against A partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

Question 772

A partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active. Best complete IAM decision record?

  1. Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Test login discovery, site settings, reset flow, error messaging and accessibility. Boundary: Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site.
  2. Action: Configure supported authentication providers and a controlled registration handler for verified external identity claims. Verification: Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test. Boundary: A public site must never infer data permission merely because a page is accessible without login.
  3. Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test. Boundary: Clearing one application's session does not necessarily terminate every federated identity-provider session.
  4. Action: Implement documented consent and data-minimization handling separate from authentication success. Verification: Inspect account hierarchy, sharing assignments, membership changes and negative access tests. Boundary: Clearing one application's session does not necessarily terminate every federated identity-provider session.

Explanation

Correct Answer

C:

“Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test. Boundary: Clearing one application's session does not necessarily terminate every federated identity-provider session” addresses the access-design responsibilities in a partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active Test against trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; clearing one application's session does not necessarily terminate every federated identity-provider session.

Incorrect Answers

A:

“Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Test login discovery, site settings, reset flow, error messaging and accessibility. Boundary: Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site” may apply to a related identity task, but it does not establish trace Salesforce session destruction, IdP session status, browser cookies and re-entry test for a partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active The controlling boundary is: Clearing one application's session does not necessarily terminate every federated identity-provider session.

B:

“Action: Configure supported authentication providers and a controlled registration handler for verified external identity claims. Verification: Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test. Boundary: A public site must never infer data permission merely because a page is accessible without login” may apply to a related identity task, but it does not establish trace Salesforce session destruction, IdP session status, browser cookies and re-entry test for a partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active The controlling boundary is: Clearing one application's session does not necessarily terminate every federated identity-provider session.

D:

“Action: Implement documented consent and data-minimization handling separate from authentication success. Verification: Inspect account hierarchy, sharing assignments, membership changes and negative access tests. 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 trace Salesforce session destruction, IdP session status, browser cookies and re-entry test for a partner signs out of Salesforce Experience Cloud but the enterprise IdP session remains active The controlling boundary is: Clearing one application's session does not necessarily terminate every federated identity-provider session.

Question 773

A shared kiosk user logs out of a community but still has browser sessions in another linked application. Best next IAM response?

  1. Configure supported authentication providers and a controlled registration handler for verified external identity claims
  2. Configure the Experience Cloud service-provider federation and subject mapping with approved membership controls
  3. Implement documented consent and data-minimization handling separate from authentication success
  4. Design sign-out behavior and communicate supported single logout versus local session termination

Explanation

Correct Answer

D:

“Design sign-out behavior and communicate supported single logout versus local session termination” addresses the access-design responsibilities in a shared kiosk user logs out of a community but still has browser sessions in another linked application Test against trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; clearing one application's session does not necessarily terminate every federated identity-provider session.

Incorrect Answers

A:

“Configure supported authentication providers and a controlled registration handler for verified external identity claims” may apply to a related identity task, but it does not establish trace Salesforce session destruction, IdP session status, browser cookies and re-entry test for a shared kiosk user logs out of a community but still has browser sessions in another linked application The controlling boundary is: Clearing one application's session does not necessarily terminate every federated identity-provider session.

B:

“Configure the Experience Cloud service-provider federation and subject mapping with approved membership controls” may apply to a related identity task, but it does not establish trace Salesforce session destruction, IdP session status, browser cookies and re-entry test for a shared kiosk user logs out of a community but still has browser sessions in another linked application The controlling boundary is: Clearing one application's session does not necessarily terminate every federated identity-provider session.

C:

“Implement documented consent and data-minimization handling separate from authentication success” may apply to a related identity task, but it does not establish trace Salesforce session destruction, IdP session status, browser cookies and re-entry test for a shared kiosk user logs out of a community but still has browser sessions in another linked application The controlling boundary is: Clearing one application's session does not necessarily terminate every federated identity-provider session.

Question 774

A shared kiosk user logs out of a community but still has browser sessions in another linked application. Most decisive verification?

  1. Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test
  2. Test login discovery, site settings, reset flow, error messaging and accessibility
  3. Inspect guest profile, object permissions, sharing rules and anonymous negative access checks
  4. Inspect account hierarchy, sharing assignments, membership changes and negative access tests

Explanation

Correct Answer

A:

“Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test” distinguishes sign-in from entitlement administration in a shared kiosk user logs out of a community but still has browser sessions in another linked application It checks whether design sign-out behavior and communicate supported single logout versus local session termination.

Incorrect Answers

B:

“Test login discovery, site settings, reset flow, error messaging and accessibility” needs to be evaluated against A shared kiosk user logs out of a community but still has browser sessions in another linked application. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

C:

“Inspect guest profile, object permissions, sharing rules and anonymous negative access checks” needs to be evaluated against A shared kiosk user logs out of a community but still has browser sessions in another linked application. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

D:

“Inspect account hierarchy, sharing assignments, membership changes and negative access tests” needs to be evaluated against A shared kiosk user logs out of a community but still has browser sessions in another linked application. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

Question 775

A shared kiosk user logs out of a community but still has browser sessions in another linked application. Key caution for this case?

  1. Clearing one application's session does not necessarily terminate every federated identity-provider session
  2. Social login alone must not create broad or duplicate Salesforce account entitlements
  3. A public site must never infer data permission merely because a page is accessible without login
  4. Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site

Explanation

Correct Answer

A:

“Clearing one application's session does not necessarily terminate every federated identity-provider session” needs to be evaluated against A shared kiosk user logs out of a community but still has browser sessions in another linked application. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

Incorrect Answers

B:

“Social login alone must not create broad or duplicate Salesforce account entitlements” needs to be evaluated against A shared kiosk user logs out of a community but still has browser sessions in another linked application. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

C:

“A public site must never infer data permission merely because a page is accessible without login” needs to be evaluated against A shared kiosk user logs out of a community but still has browser sessions in another linked application. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

D:

“Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site” needs to be evaluated against A shared kiosk user logs out of a community but still has browser sessions in another linked application. The relevant check is Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; Clearing one application's session does not necessarily terminate every federated identity-provider session.

Question 776

A shared kiosk user logs out of a community but still has browser sessions in another linked application. Best complete IAM decision record?

  1. Action: Implement documented consent and data-minimization handling separate from authentication success. Verification: Inspect account hierarchy, sharing assignments, membership changes and negative access tests. Boundary: Clearing one application's session does not necessarily terminate every federated identity-provider session.
  2. Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Test login discovery, site settings, reset flow, error messaging and accessibility. Boundary: Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site.
  3. Action: Configure supported authentication providers and a controlled registration handler for verified external identity claims. Verification: Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test. Boundary: A public site must never infer data permission merely because a page is accessible without login.
  4. Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test. Boundary: Clearing one application's session does not necessarily terminate every federated identity-provider session.

Explanation

Correct Answer

D:

“Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test. Boundary: Clearing one application's session does not necessarily terminate every federated identity-provider session” addresses the access-design responsibilities in a shared kiosk user logs out of a community but still has browser sessions in another linked application Test against trace Salesforce session destruction, IdP session status, browser cookies and re-entry test; clearing one application's session does not necessarily terminate every federated identity-provider session.

Incorrect Answers

A:

“Action: Implement documented consent and data-minimization handling separate from authentication success. Verification: Inspect account hierarchy, sharing assignments, membership changes and negative access tests. 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 trace Salesforce session destruction, IdP session status, browser cookies and re-entry test for a shared kiosk user logs out of a community but still has browser sessions in another linked application The controlling boundary is: Clearing one application's session does not necessarily terminate every federated identity-provider session.

B:

“Action: Design sign-out behavior and communicate supported single logout versus local session termination. Verification: Test login discovery, site settings, reset flow, error messaging and accessibility. Boundary: Correct SAML authentication does not prove the user belongs to the intended Experience Cloud site” may apply to a related identity task, but it does not establish trace Salesforce session destruction, IdP session status, browser cookies and re-entry test for a shared kiosk user logs out of a community but still has browser sessions in another linked application The controlling boundary is: Clearing one application's session does not necessarily terminate every federated identity-provider session.

C:

“Action: Configure supported authentication providers and a controlled registration handler for verified external identity claims. Verification: Trace Salesforce session destruction, IdP session status, browser cookies and re-entry test. Boundary: A public site must never infer data permission merely because a page is accessible without login” may apply to a related identity task, but it does not establish trace Salesforce session destruction, IdP session status, browser cookies and re-entry test for a shared kiosk user logs out of a community but still has browser sessions in another linked application The controlling boundary is: Clearing one application's session does not necessarily terminate every federated identity-provider session.

Question 777

A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. Best next IAM response?

  1. Implement documented consent and data-minimization handling separate from authentication success
  2. Define an external-user MFA and recovery assurance policy consistent with supported Salesforce and IdP controls
  3. Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout
  4. Coordinate account or contact deactivation with external session, OAuth token and data-retention controls

Explanation

Correct Answer

C:

“Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout” addresses the access-design responsibilities in a mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources Test against check client type, token leakage resistance, callback origins and shared-device cleanup; a client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

Incorrect Answers

A:

“Implement documented consent and data-minimization handling separate from authentication success” may apply to a related identity task, but it does not establish check client type, token leakage resistance, callback origins and shared-device cleanup for a mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources The controlling boundary is: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

B:

“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 check client type, token leakage resistance, callback origins and shared-device cleanup for a mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources The controlling boundary is: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

D:

“Coordinate account or contact deactivation with external session, OAuth token and data-retention controls” may apply to a related identity task, but it does not establish check client type, token leakage resistance, callback origins and shared-device cleanup for a mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources The controlling boundary is: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

Question 778

A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. Most decisive verification?

  1. Test identity provider assurance, Salesforce session needs, recovery verification and failed challenge handling
  2. Simulate peak signup, duplicate identities, inactive records and reactivation handling
  3. Check client type, token leakage resistance, callback origins and shared-device cleanup
  4. Validate contact-account association, external user license, site membership and test record visibility

Explanation

Correct Answer

C:

“Check client type, token leakage resistance, callback origins and shared-device cleanup” distinguishes sign-in from entitlement administration in a mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources It checks whether choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout.

Incorrect Answers

A:

“Test identity provider assurance, Salesforce session needs, recovery verification and failed challenge handling” needs to be evaluated against A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. The relevant check is Check client type, token leakage resistance, callback origins and shared-device cleanup; A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

B:

“Simulate peak signup, duplicate identities, inactive records and reactivation handling” needs to be evaluated against A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. The relevant check is Check client type, token leakage resistance, callback origins and shared-device cleanup; A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

D:

“Validate contact-account association, external user license, site membership and test record visibility” needs to be evaluated against A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. The relevant check is Check client type, token leakage resistance, callback origins and shared-device cleanup; A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

Question 779

A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. Key caution for this case?

  1. Changing Experience Cloud domains can invalidate federation URLs and redirect targets
  2. Social login alone must not create broad or duplicate Salesforce account entitlements
  3. A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app
  4. A self-service signup form must not grant privileged partner access solely from unverified user input

Explanation

Correct Answer

C:

“A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app” needs to be evaluated against A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. The relevant check is Check client type, token leakage resistance, callback origins and shared-device cleanup; A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

Incorrect Answers

A:

“Changing Experience Cloud domains can invalidate federation URLs and redirect targets” needs to be evaluated against A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. The relevant check is Check client type, token leakage resistance, callback origins and shared-device cleanup; A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

B:

“Social login alone must not create broad or duplicate Salesforce account entitlements” needs to be evaluated against A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. The relevant check is Check client type, token leakage resistance, callback origins and shared-device cleanup; A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

D:

“A self-service signup form must not grant privileged partner access solely from unverified user input” needs to be evaluated against A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. The relevant check is Check client type, token leakage resistance, callback origins and shared-device cleanup; A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

Question 780

A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. Best complete IAM decision record?

  1. Action: Coordinate account or contact deactivation with external session, OAuth token and data-retention controls. Verification: Test identity provider assurance, Salesforce session needs, recovery verification and failed challenge handling. Boundary: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.
  2. Action: Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout. Verification: Check client type, token leakage resistance, callback origins and shared-device cleanup. Boundary: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.
  3. Action: Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout. 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: Implement documented consent and data-minimization handling separate from authentication success. Verification: Check client type, token leakage resistance, callback origins and shared-device cleanup. Boundary: Social login alone must not create broad or duplicate Salesforce account entitlements.

Explanation

Correct Answer

B:

“Action: Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout. Verification: Check client type, token leakage resistance, callback origins and shared-device cleanup. Boundary: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app” addresses the access-design responsibilities in a mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources Test against check client type, token leakage resistance, callback origins and shared-device cleanup; a client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

Incorrect Answers

A:

“Action: Coordinate account or contact deactivation with external session, OAuth token and data-retention controls. Verification: Test identity provider assurance, Salesforce session needs, recovery verification and failed challenge handling. Boundary: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app” may apply to a related identity task, but it does not establish check client type, token leakage resistance, callback origins and shared-device cleanup for a mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources The controlling boundary is: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

C:

“Action: Choose safe browser/mobile authorization patterns with PKCE where appropriate, minimal token storage and controlled logout. 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 check client type, token leakage resistance, callback origins and shared-device cleanup for a mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources The controlling boundary is: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

D:

“Action: Implement documented consent and data-minimization handling separate from authentication success. Verification: Check client type, token leakage resistance, callback origins and shared-device cleanup. Boundary: Social login alone must not create broad or duplicate Salesforce account entitlements” may apply to a related identity task, but it does not establish check client type, token leakage resistance, callback origins and shared-device cleanup for a mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources The controlling boundary is: A client-side embedded secret cannot be assumed private just because it is bundled inside a mobile app.

Certified Platform Identity and Access Management Architect Practice Tests