Match each Salesforce security requirement on the left with the correct administration configuration mechanism on the right.
- Completely restrict visibility and edit access for a sensitive 'Salary__c' custom field across all views and API access for standard employees while granting access to HR Managers.Field-Level Security (FLS) restriction on Profiles combined with a targeted Permission Set.
- Allow Sales Representatives to create, view, and modify Account records, but strictly prevent them from deleting any Account records.Object Permissions (Create, Read, Edit enabled; Delete disabled) on the user Profile.
- Hide a custom field on a Lightning Record Page conditionally depending on the record's Stage value, without removing underlying field access.Component Visibility Rules configured using Dynamic Forms in Lightning App Builder.
- Specify exact time windows during which users assigned to the Customer Support team are permitted to log into Salesforce.Login Hours settings configured directly on the user Profile.
Cevap
1. Field access restriction across all interfaces maps to Field-Level Security on Profiles/Permission Sets. 2. Record deletion restriction maps to Profile Object Permissions. 3. Conditional page field hiding maps to Dynamic Forms Component Visibility. 4. Time-restricted login access maps to Profile Login Hours.
Each security requirement correctly aligns with its architectural layer in Salesforce: Field-Level Security (FLS) enforces data visibility at the API/database layer; Profile Object Permissions control object-level CRUD actions; Dynamic Forms manage conditional layout rendering; and Profile Login Hours govern user authentication timing windows.
Adım Adım Çözüm
Anahtar Kavram
Salesforce Security Architecture: Profile Object Permissions, Field-Level Security, Login Hours, and Dynamic Forms Visibility