Examkin

Soru

Zorluk: OrtaProfiles and Object/Field-Level Security

Starlight Solar Solutions uses a custom object named Customer_Audit__c to track quality assurance reviews. The System Administrator needs to restrict access to a sensitive custom field, Risk_Assessment_Notes__c, so that only three risk analysts out of forty employees assigned to the Support Specialist profile can view it. Access must be restricted across all interfaces, reports, and API calls for the remaining thirty-seven users. Which configuration approach should the administrator implement to meet this requirement following Salesforce best practices?

  1. Set Field-Level Security for Risk_Assessment_Notes__c to hidden on the Support Specialist profile, create a permission set granting Read access to the field, and assign the permission set to the three risk analysts.Cevap
  2. B
    Clone the Support Specialist profile to create a Risk Analyst profile, enable Read access for Risk_Assessment_Notes__c on the cloned profile, and assign it to the three risk analysts.
  3. C
    Grant Read access to Risk_Assessment_Notes__c on the Support Specialist profile, then configure Dynamic Forms component visibility filters on the record page to hide the field from users who are not risk analysts.
  4. D
    Add the IP addresses of the three risk analysts to the profile's Login IP Ranges to automatically grant them elevated field-level access to Risk_Assessment_Notes__c.

Cevap

Set Field-Level Security for Risk_Assessment_Notes__c to hidden on the Support Specialist profile, create a permission set granting Read access to the field, and assign the permission set to the three risk analysts.
The standard Salesforce best practice for granting field access to a subset of users on a shared profile is to restrict the Field-Level Security on the profile level and use a Permission Set to grant additive Read or Edit access to the specific users who require it. FLS enforces security universally across the UI, API, reports, and list views.

Adım Adım Çözüm

1
Evaluate baseline Field-Level Security (FLS) on the common profile
Remove visibility for Risk_Assessment_Notes__c on the Support Specialist profile so that the default baseline access for all forty users is restricted.
Profiles should define the minimum baseline access required by all users sharing that profile role.
2
Create an additive Permission Set
Build a permission set that enables Read access for the Risk_Assessment_Notes__c field.
Permission sets allow administrators to grant additional field permissions to specific users without modifying their assigned profile.
3
Assign the Permission Set to targeted users
Assign the new permission set directly to the three risk analysts.
This grants field visibility to only the required individuals across all UI surfaces, reports, and APIs while keeping the field secured for all other profile members.

Anahtar Kavram

Profiles establish baseline access restrictions, while Permission Sets grant additive Field-Level Security (FLS) access for user exceptions.
Tahmini Süre:1m 30s
Bu soruyu puanla

Konular

Profiles and Object/Field-Level Security

Bu konudan daha fazla soru