Question 710
A global brand updates its community domain but legacy customers still use old OAuth callbacks. Most decisive verification?
Explanation
Correct Answer
“Verify login/registration settings, callback registration, site membership and successful deep links” distinguishes sign-in from entitlement administration in a global brand updates its community domain but legacy customers still use old OAuth callbacks It checks whether configure site-specific authentication URLs, provider assignments and domain-change migration procedures.
Incorrect Answers
“Review privacy notice version, permission to process, retention and data field minimization” needs to be evaluated against A global brand updates its community domain but legacy customers still use old OAuth callbacks. The relevant check is Verify login/registration settings, callback registration, site membership and successful deep links; Changing Experience Cloud domains can invalidate federation URLs and redirect targets.
“Inspect origin allowlist, redirect, consent, client registration and session lifecycle” needs to be evaluated against A global brand updates its community domain but legacy customers still use old OAuth callbacks. The relevant check is Verify login/registration settings, callback registration, site membership and successful deep links; Changing Experience Cloud domains can invalidate federation URLs and redirect targets.
“Test login discovery, site settings, reset flow, error messaging and accessibility” needs to be evaluated against A global brand updates its community domain but legacy customers still use old OAuth callbacks. The relevant check is Verify login/registration settings, callback registration, site membership and successful deep links; Changing Experience Cloud domains can invalidate federation URLs and redirect targets.