Question 720
A public help center displays restricted case fields because its guest profile is overly permissive. Best complete IAM decision record?
Explanation
Correct Answer
“Action: Apply restrictive guest access defaults and authorized authenticated-user record sharing tests. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: A public site must never infer data permission merely because a page is accessible without login” addresses the access-design responsibilities in a public help center displays restricted case fields because its guest profile is overly permissive Test against inspect guest profile, object permissions, sharing rules and anonymous negative access checks; a public site must never infer data permission merely because a page is accessible without login.
Incorrect Answers
“Action: Apply restrictive guest access defaults and authorized authenticated-user record sharing tests. Verification: Test identity provider assurance, Salesforce session needs, recovery verification and failed challenge handling. Boundary: A secure sign-in does not replace record-level authorization and field visibility controls” may apply to a related identity task, but it does not establish inspect guest profile, object permissions, sharing rules and anonymous negative access checks for a public help center displays restricted case fields because its guest profile is overly permissive The controlling boundary is: A public site must never infer data permission merely because a page is accessible without login.
“Action: Plan scalable user provisioning, license selection, stable identity matching and dormant-account governance. Verification: Test login discovery, site settings, reset flow, error messaging and accessibility. 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 inspect guest profile, object permissions, sharing rules and anonymous negative access checks for a public help center displays restricted case fields because its guest profile is overly permissive The controlling boundary is: A public site must never infer data permission merely because a page is accessible without login.
“Action: Design external user, contact and account relationships before enabling authorized Experience Cloud access. Verification: Inspect guest profile, object permissions, sharing rules and anonymous negative access checks. Boundary: Creating a login user without the correct contact and account model can break partner access boundaries” may apply to a related identity task, but it does not establish inspect guest profile, object permissions, sharing rules and anonymous negative access checks for a public help center displays restricted case fields because its guest profile is overly permissive The controlling boundary is: A public site must never infer data permission merely because a page is accessible without login.