Question

Difficulty: HardProfiles and Object/Field-Level Security

A Salesforce Administrator at Quantum Energy must configure security controls for five HR Compliance Officers who currently share the standard Operations profile with thirty other employees. The business requirements state:
1. The five HR Compliance Officers require Read access to the sensitive `National_ID__c` field on the Contact object, but all other Operations users must be prevented from accessing or viewing this field across all interfaces, reports, and API calls.
2. The five HR Compliance Officers must be strictly blocked from logging into Salesforce when working outside the corporate network IP range of 198.51.100.0/24198.51.100.0/24, while other Operations users may continue logging in from any location.

Which configuration strategy should the administrator implement to satisfy these security requirements with minimal impact on other users?

  1. Clone the Operations profile to create a custom HR Compliance profile, configure the Login IP Ranges on the new profile, and assign a Permission Set with Read access for National_ID__c via Field-Level Security to the five officers.Answer
  2. B
    Add the corporate network range to Network Access under Org-Wide Security Controls in Setup, and assign a Permission Set granting Field-Level Security Read access on National_ID__c to the five officers.
  3. C
    Set Component Visibility on the Contact Lightning Record Page using Dynamic Forms to render the National_ID__c field only for HR Compliance Officers, and add the Login IP Ranges to their existing Operations profile.
  4. D
    Keep all users on the existing Operations profile and assign a new Permission Set to the five HR Compliance Officers that configures both the Login IP Ranges restriction and Field-Level Security Read access.

Answer

Create a custom profile for the HR Compliance Officers with Login IP Ranges configured to enforce the IP restriction, and assign a Permission Set granting Field-Level Security Read access for the field.
Configuring a custom profile for the HR Compliance Officers allows the administrator to define strict Profile Login IP Ranges that block login attempts outside the designated IP network without impacting non-HR Operations users. Combining this with a Permission Set that grants Read access to the sensitive field via Field-Level Security (FLS) ensures secure, complete protection across all access channels (UI, API, and reporting) in alignment with Salesforce security best practices.

Step-by-Step Solution

1
Analyze login IP restrictions requirement
Login IP Ranges must be configured at the Profile level because Login IP Ranges cannot be set in Permission Sets or Network Access settings.
Profile Login IP Ranges actively deny login outside specified ranges, whereas Network Access only waives multi-factor/activation challenges.
2
Evaluate user separation for profile settings
Create a dedicated custom profile for the five HR Compliance Officers cloned from the Operations profile.
Modifying IP ranges on the shared Operations profile would inadvertently restrict the remaining thirty employees.
3
Configure Field-Level Security (FLS) access
Keep the field hidden on the profile and grant Read access to the field using a Permission Set assigned to the five officers.
Field-Level Security (FLS) ensures total field privacy across UI, API, and reports, and using a Permission Set follows Salesforce best practices for additive field permissions.

Key Concept

Profiles control restrictive security boundary settings like Login IP Ranges, whereas Permission Sets grant additive data and field access like Field-Level Security (FLS).
Estimated Time:2m 0s
Rate this question