A Salesforce Administrator is evaluating security requirements for different administrative requests. Match each security requirement on the left with the most appropriate Salesforce security mechanism on the right.
- Restrict access to a sensitive 'Tax Identification Number' field across all UI views, reports, list views, and API calls for users assigned to a specific profile.Field-Level Security (FLS) on the Profile
- Grant Read and Create permissions on the custom 'Audit Record' object to all users assigned to the Compliance Operations team.Object Permissions (CRUD) on the Profile
- Completely prevent users assigned to the Customer Support profile from logging into Salesforce when they are outside the corporate network.Login IP Ranges configured on the Profile
- Grant access to a restricted field for a single user without modifying the permissions of other users who share the same assigned profile.Permission Set assigned directly to the individual user
Answer
1. Field-Level Security on Profile controls field access across all entry points; 2. Object Permissions on Profile establish baseline object-level CRUD access; 3. Profile Login IP Ranges restrict login access based on network IP address; 4. Permission Sets grant incremental access to individual users.
Each business requirement aligns with a specific Salesforce security feature: Field-Level Security restricts field access everywhere across the platform; Object Permissions grant object CRUD rights for a profile; Profile Login IP Ranges enforce strict network restriction for users on that profile; and Permission Sets extend permissions to individual users without modifying shared profiles.
Step-by-Step Solution
Key Concept
Salesforce Security Architecture: Object Permissions, Field-Level Security, Profile Login Restrictions, and Permission Sets