Examkin

Question

Difficulty: EasyProfiles and Object/Field-Level Security

An administrator needs to completely hide a custom field named Hourly_Rate__c on the Consultant__c object for all users assigned to the Standard Support Profile, while preserving existing access for all other profiles. Which configuration change should the administrator make?

  1. Set Field-Level Security for the Hourly_Rate__c field to hidden on the Standard Support Profile.Answer
  2. B
    Hide the Hourly_Rate__c field component using Dynamic Forms visibility rules on the Lightning record page.
  3. C
    Create a separate custom profile for each support user to manage their field access individually.
  4. D
    Restrict Profile Login IP Ranges on the Standard Support Profile to prevent field viewing.

Answer

Set Field-Level Security for the Hourly_Rate__c field to hidden on the Standard Support Profile.
Field-Level Security (FLS) on the profile directly controls field visibility and editability across the entire Salesforce platform, including record pages, reports, search, and API calls.

Step-by-Step Solution

1
Identify the security requirement.
Access to the Hourly_Rate__c field needs to be restricted at the data level for users assigned to the Standard Support Profile.
Security requirements regarding field data visibility require field-level authorization controls rather than UI-only restrictions.
2
Evaluate the appropriate security mechanism.
Field-Level Security (FLS) on the profile restricts access to the field across all interfaces, including reports, list views, and API calls.
FLS is the standard setting in Salesforce for enforcing field privacy per profile or permission set.

Key Concept

Field-Level Security (FLS) enforcement on profiles
Rate this question

Topics

Profiles and Object/Field-Level Security

More questions from this topic