A Salesforce Administrator at a global logistics firm must configure security controls for various departmental requirements. Match each business requirement on the left with the appropriate security feature or configuration on the right.
- Completely prevent all users assigned to the Sales Rep profile from viewing a sensitive custom field across all page layouts, reports, and API integrations.Configure Field-Level Security (FLS) on the Profile to set the field as Hidden.
- Remove a field from the record detail view for general users while still allowing them to report on and edit the field value.Remove the field component from the Page Layout customization.
- Prevent users assigned to a custom Support profile from viewing or creating any records of a new custom object.Set Object Permissions on the Profile to remove Read and Create access.
- Grant view access to a restricted financial field for only two specific users who share a standard profile with non-authorized users.Assign a Permission Set granting Read access for the field to the designated users.
Answer
Each security requirement maps directly to its corresponding feature based on Salesforce's security hierarchy: Profile FLS restricts field access platform-wide; Page Layouts control UI display only; Object Permissions control object-level access; Permission Sets grant selective incremental permissions to specific users.
Each requirement correctly pairs with the appropriate Salesforce mechanism: Profile FLS for global field restriction, Page Layouts for UI display adjustments, Object Permissions on Profiles for object access, and Permission Sets for targeted access extensions to specific individuals.
Step-by-Step Solution
Key Concept
Profiles, Permission Sets, Field-Level Security (FLS), and Page Layouts
Estimated Time:1m 30s