Salesforce-Platform-Sharing-and-Visibility-Architect Practice Test
Salesforce Spring 25 Release 77 Questions
Universal Containers (UC) has created a custom Invoice object. Standard sales users at
UC can see the records in search layout, but when they click to viewthe detail, only record
name, created date, and last modified date are shown. When the system admin accesses
it, he or she sees the full record detail with many more data fields.
What is the likely cause of this issue?
A. A role-based sharing rule is missing and should be added for the sales user's role to
grant access to the fields.
B. The Sales Users profile does not have access to the remaining fields.
C. The page layout assigned to Sales User profile has only Read-Only access to the fields.
B. The Sales Users profile does not have access to the remaining fields.
Explanation:
When users can see the record header but only a few fields on detail view, it indicates Field-Level Security rather than sharing. Page Layout controls which fields appear, but FLS determines visibility at all levels—even in the API and search. If the Sales Users profile lacks “Visible” permission for certain Invoice fields, those fields never render, and the user only sees the default Name, Created Date, and Last Modified fields, which are always visible.
→ A missing sharing rule (A) wouldn’t let them see the record at all.
→ A page layout omission (C) hides fields on the layout but doesn’t explain why the admin sees more fields; admins can see everything regardless of layout if FLS permits. The differential visibility points squarely to FLS misconfiguration on the Sales Users profile.