Question 670
A retailer adds a social sign-in button to its Experience Cloud site and must map return identities to customer contacts. Most decisive verification?
Explanation
Correct Answer
“Test issuer trust, provider subject, duplicate contact matching and re-login outcomes” distinguishes sign-in from entitlement administration in a retailer adds a social sign-in button to its Experience Cloud site and must map return identities to customer contacts It checks whether configure supported authentication providers and a controlled registration handler for verified external identity claims.
Incorrect Answers
“Review privacy notice version, permission to process, retention and data field minimization” needs to be evaluated against A retailer adds a social sign-in button to its Experience Cloud site and must map return identities to customer contacts. The relevant check is Test issuer trust, provider subject, duplicate contact matching and re-login outcomes; Social login alone must not create broad or duplicate Salesforce account entitlements.
“Test unauthenticated registration path, invite token, profile selection and elevation denial” needs to be evaluated against A retailer adds a social sign-in button to its Experience Cloud site and must map return identities to customer contacts. The relevant check is Test issuer trust, provider subject, duplicate contact matching and re-login outcomes; Social login alone must not create broad or duplicate Salesforce account entitlements.
“Check client type, token leakage resistance, callback origins and shared-device cleanup” needs to be evaluated against A retailer adds a social sign-in button to its Experience Cloud site and must map return identities to customer contacts. The relevant check is Test issuer trust, provider subject, duplicate contact matching and re-login outcomes; Social login alone must not create broad or duplicate Salesforce account entitlements.