Examkin

Soru

Zorluk: OrtaProfiles and Object/Field-Level Security

Pinnacle Solar Energy recently added a custom field named Tax_Identification_Number__c to the Vendor custom object. Currently, the Field-Level Security setting for this field is set to hidden on the 'Standard Vendor User' profile assigned to all 50 operations staff members. The business requirement specifies that 8 compliance auditors within this group require read and edit access to Tax_Identification_Number__c, while the remaining 42 staff members must not be able to view or edit the field. What is the optimal security configuration to meet this requirement?

  1. Create a permission set with Read and Edit Field-Level Security enabled for Tax_Identification_Number__c and assign it to the 8 compliance auditors.Cevap
  2. B
    Clone the 'Standard Vendor User' profile, enable Read and Edit Field-Level Security for Tax_Identification_Number__c on the cloned profile, and reassign the 8 compliance auditors to the new profile.
  3. C
    Configure Dynamic Forms component visibility rules on the Vendor Lightning record page to display Tax_Identification_Number__c only to the 8 compliance auditors.
  4. D
    Configure Network Access IP Ranges in Organization-Wide Settings to restrict access to Tax_Identification_Number__c based on user login IP ranges.

Cevap

The optimal solution is to create a permission set that enables Read and Edit Field-Level Security for the Tax_Identification_Number__c field and assign that permission set to the 8 compliance auditors.
Salesforce security follows an additive permission model using Permission Sets. Setting the baseline Field-Level Security to restricted/hidden on the profile and assigning a Permission Set with Read and Edit access to the specific 8 compliance auditors ensures data security across all interfaces (UI, API, reports) while keeping profile administration simple.

Adım Adım Çözüm

1
Analyze baseline access and user scope.
All 50 users share the 'Standard Vendor User' profile where the field is hidden by default.
Profiles set the baseline minimum access for users assigned to them.
2
Evaluate the mechanism for granting access to a subset of users.
Permission sets allow administrators to grant additional permissions (additive model) to targeted individual users.
Using permission sets avoids profile proliferation and maintains clean security management.
3
Select the correct security feature for data privacy.
Field-Level Security (FLS) controls field access across all entry points, including reports, search, API, and page layouts.
FLS guarantees true field-level data privacy across the entire platform.

Anahtar Kavram

Field-Level Security (FLS) and Permission Sets
Tahmini Süre:1m 0s
Bu soruyu puanla

Konular

Profiles and Object/Field-Level Security

Bu konudan daha fazla soru