Soru

Zorluk: KolayProfiles and Object/Field-Level Security

A Salesforce administrator needs to ensure that users assigned to the Support Specialist profile can view the Social_Security_Number__c field on the Contact object, but are strictly prevented from editing it across all user interfaces, reports, and API integrations. Which security mechanism should the administrator configure to satisfy this requirement?

  1. Configure Field-Level Security (FLS) on the Social_Security_Number__c field to Read-Only for the Support Specialist profile.Cevap
  2. B
    Set component visibility on the Lightning Record Page using Dynamic Forms to hide the field when in edit mode.
  3. C
    Clone the profile and assign a new profile for each individual Support Specialist user requiring restricted edit permissions.
  4. D
    Add designated network IP addresses to the Profile Login IP Ranges to block edit capabilities.

Cevap

Configure Field-Level Security (FLS) on the Social_Security_Number__c field to Read-Only for the Support Specialist profile.
Field-Level Security (FLS) is the authoritative standard in Salesforce for restricting access to individual fields. Setting a field to Read-Only for a profile ensures users assigned to that profile can view the field value but cannot create or update values in that field regardless of where they interact with Salesforce (UI, API, reports, or tools).

Adım Adım Çözüm

1
Identify the level of security required.
The requirement specifies preventing edits across all interfaces, reports, and API integrations.
UI-only settings like page layouts or Dynamic Forms do not secure data at the API or report level.
2
Select the appropriate security control feature.
Field-Level Security (FLS) overrides page layout settings and enforces field access across the entire platform.
Setting FLS to Read-Only on the target profile guarantees users can read the field data but cannot modify it anywhere in Salesforce.

Anahtar Kavram

Field-Level Security (FLS) vs. UI Layout Controls
Bu soruyu puanla