Examkin

Question

Difficulty: EasyProfiles and Object/Field-Level Security

An administrator needs to prevent non-HR users from viewing or editing a sensitive custom field, SSN__c, on the Contact object across all UI pages, reports, search results, and API integrations. Which security mechanism should the administrator use to satisfy this requirement?

  1. Field-Level Security (FLS) on the Contact object settingsAnswer
  2. B
    Dynamic Forms component visibility rules on the record page layout
  3. C
    Distinct profiles for each department with customized page layouts
  4. D
    Profile Login IP Ranges configured for non-HR user profiles

Answer

Field-Level Security (FLS) on the Contact object settings
Field-Level Security (FLS) directly controls whether a field is visible or editable for a profile or permission set across all access points, including page layouts, list views, reports, search results, and API integrations.

Step-by-Step Solution

1
Identify the administrative security requirement
The field must be protected from view and edit access across all channels, including reports and APIs.
Controls that operate strictly on user interface pages (like page layouts or component visibility) are insufficient for comprehensive field security.
2
Select the appropriate data security feature
Configure Field-Level Security (FLS) to set visibility and edit permissions by profile or permission set.
FLS is enforced at the platform layer across all tools, reports, list views, and APIs.

Key Concept

Field-Level Security (FLS) vs. Page Layout & Component Visibility
Estimated Time:45s
Rate this question

Topics

Profiles and Object/Field-Level Security

More questions from this topic