A Salesforce Administrator configures a custom object record page using Dynamic Forms in Lightning App Builder. To comply with internal privacy guidelines, the administrator sets a component visibility filter on a custom field component named Executive_Comments__c so that it only renders on the Lightning page when the current user's profile is System Administrator. Users with the Sales Rep profile can no longer see the field section on this Lightning record page. Which statement accurately describes the security impact of this configuration?
- Sales Rep users can still access the Executive_Comments__c field data via reports, API queries, or list views because Dynamic Forms visibility filters do not restrict Field-Level Security.Cevap
- BApplying a component visibility filter automatically revokes Field-Level Security read access for all profiles excluded by the filter criteria.
- CSales Rep users will encounter a page layout runtime error when loading the record because Dynamic Forms visibility rules override Profile permissions.
- DThe administrator must create a separate profile for Sales Reps and assign a legacy page layout to prevent field exposure across the application.
Cevap
Sales Rep users can still access the Executive_Comments__c field data via reports, API queries, or list views because Dynamic Forms visibility filters do not restrict Field-Level Security.
Dynamic Forms component visibility filters control only whether a field component is rendered on the specified Lightning Record Page. They do not enforce data security. Because Field-Level Security (FLS) was not restricted, users with the Sales Rep profile can still access the field via reports, API calls, global search, and list views.
Adım Adım Çözüm
Anahtar Kavram
Dynamic Forms Component Visibility vs Field-Level Security (FLS)
Tahmini Süre:2m 0s