Match each Salesforce administrative requirement on the left with the most appropriate security or configuration mechanism on the right.
- Restrict access to a sensitive SSN field on the Contact object globally across UI pages, standard reports, and API integrations.Field-Level Security (FLS) configuration
- Enforce strict IP address restrictions for a user group so that login attempts originating outside specified corporate IP ranges are blocked.Profile Login IP Ranges setting
- Grant Read and Create permissions on a custom Audit object to a single user without altering permissions for other users sharing the same Profile.Permission Set assignment
- Hide a custom Salary field component on a Lightning Record Page for specific users while keeping the underlying field accessible via API integrations.Dynamic Forms Component Visibility rules
Answer
Field-Level Security matches restricting field access globally across UI, API, and reports. Profile Login IP Ranges matches strict login denial outside specified IP ranges. Permission Sets match granting object access to a single user without altering shared Profiles. Dynamic Forms Component Visibility rules match hiding fields on Lightning record pages while maintaining API field accessibility.
Each requirement maps to its optimal Salesforce configuration feature: Field-Level Security enforces universal field protection across UI, API, and reporting; Profile Login IP Ranges strictly block logins outside designated IP ranges; Permission Sets additively grant permissions to single users without profile sprawl; Dynamic Forms component visibility controls UI rendering while keeping field data accessible via API.
Step-by-Step Solution
Key Concept
Profiles, Permission Sets, Field-Level Security, and UI Visibility Controls