Match each security and access control scenario for Global Logistics Corp to the appropriate Salesforce profile or field-level security (FLS) configuration setting.
- Completely restrict visibility of the sensitive field 'Executive_Audit_Notes__c' across all standard users regardless of page layout modifications.Set Field-Level Security (FLS) on the custom field by unchecking 'Visible' for all profiles except System Administrator.
- Grant Read-Only visibility of the custom field 'Credit_Limit__c' to the Standard User profile while allowing full edit capability on the Finance profile.Configure Field-Level Security (FLS) on the custom field to 'Visible' (Read-Only) for one profile and 'Visible' (Editable) for the other.
- Prevent users assigned to a specific custom profile from logging into Salesforce entirely when outside corporate network IP ranges.Define Profile Login IP Ranges on the specific user profile to enforce explicit network perimeter authentication controls.
- Allow Sales Representatives to create, view, and modify custom 'Freight_Contract__c' records while explicitly revoking their capability to delete them.Modify Object Permissions on the custom object profile settings by granting Read, Create, and Edit while leaving Delete unchecked.
Cevap
Each scenario maps to its underlying security level in Salesforce: sensitive field access to FLS hiding, profile-specific field editing to FLS visibility/read-only controls, network login enforcement to Profile Login IP Ranges, and record deletion restrictions to Object Permissions (CRUD).
Each business requirement aligns directly with Salesforce security controls: Field-Level Security governs data access at the field level regardless of UI controls, Object Permissions define baseline record CRUD privileges on profiles, and Profile Login IP Ranges enforce absolute network login restrictions.
Adım Adım Çözüm
Anahtar Kavram
Profiles and Object/Field-Level Security
Tahmini Süre:2m 0s