Question

Difficulty: MediumProfiles and Object/Field-Level Security

Cloud Solar Solutions manages utility-scale installations using a custom object named Project Site. All members of the Operations department are assigned to a custom profile named 'Operations Specialist'. Management requires that only three specific Operations team members have Read and Edit access to a sensitive custom field, Environmental_Impact_Score__c, while all other Operations users must not see or edit this field. Furthermore, all users assigned to the Operations Specialist profile must be strictly restricted from logging in outside the corporate network IP range, while users on other profiles should not be affected.

Which TWO configuration actions should the Salesforce Administrator take to fulfill these requirements? (Choose 2 answers)

  1. Set Field-Level Security for Environmental_Impact_Score__c to hidden on the Operations Specialist profile, create a Permission Set with Read and Edit access for the field, and assign it to the three specific users.Answer
  2. Define the allowed IP boundaries under Login IP Ranges directly on the Operations Specialist profile settings.Answer
  3. C
    Add the corporate network IP ranges under Network Access in Organization-Wide Setup to restrict login access exclusively for Operations Specialist profile users.
  4. D
    Hide Environmental_Impact_Score__c using Dynamic Forms component visibility rules on the Lightning Record Page layout instead of modifying Field-Level Security.

Answer

The correct actions are: setting Field-Level Security for the field to hidden on the profile and assigning a Permission Set with Read and Edit access to the three designated users, and defining the allowed IP address ranges under Login IP Ranges directly on the profile.
Field-Level Security at the profile level sets the most restrictive baseline. Applying FLS (hidden) on the Operations Specialist profile prevents unauthorized viewing. A Permission Set is then used to grant additive Read and Edit access to the target subset of users. Simultaneously, configuring Login IP Ranges on the Operations Specialist profile strictly restricts login access to designated IP ranges for users assigned to that profile.

Step-by-Step Solution

1
Evaluate field accessibility requirements for specific users on a shared profile.
Identify that profiles set baseline access, and permission sets add permissions for specific users.
Restricting FLS on the profile ensures non-authorized users cannot view the field, while a Permission Set grants additive Read/Edit access to the three specific team members.
2
Evaluate profile-specific login IP restriction requirements.
Determine that profile-level Login IP Ranges enforce strict login boundaries per profile.
Configuring Login IP Ranges on the profile denies login access outside specified ranges for users on that profile without impacting other profiles.

Key Concept

Profiles establish baseline access restrictions (such as Profile Login IP Ranges and default FLS), while Permission Sets extend object and field access to specific users additively.
Rate this question