Universal Container wants to prevent its service team from accessing deal records. While service users are unable to access deal list views, they are able to find the deal records via a search. What…

Question

Options

• ARecord setting and search index
• BPermissions and tab visibility
• CApp permissions and search terms
• DPage layouts and field- level security

• A
  7% (3)
• B
  12% (5)
• C
  23% (10)
• D
  58% (25)

Explanation

Page layouts and field-level security (FLS) work together to control what data a user can actually see on a record. Even when users locate deal records through search, FLS restricts which fields are visible in both search result previews and on the record detail page. Page layouts further control what sections and related lists are rendered when a record is opened. Removing field visibility via FLS effectively makes a record empty and useless to the service user, fully restricting meaningful access to deal data.

Why the distractors are wrong:

• A (Record setting and search index): Not standard Salesforce terminology for access control; no native "search index" admin setting restricts user access to records.
• B (Permissions and tab visibility): Tab visibility was already addressed (users can't see list views), and object-level permissions alone don't explain why search still returns records. This option doesn't target the data visibility layer.
• C (App permissions and search terms): App permissions restrict which apps are visible, not individual record data; "search terms" is not an access control mechanism in Salesforce.

Memory tip: Think of it as a two-layer lock - Page Layout controls the door (what sections appear), and Field-Level Security controls the contents (which fields are visible). If a user somehow gets into a room (finds the record), FLS ensures they see an empty room.

No community discussion yet for this question.