Question 780
A mobile commerce app uses a public OAuth client to let customers access Experience Cloud resources. Best complete IAM decision record?
Explanation
Correct Answer
“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
“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.
“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.
“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.