Examkin

Question

Difficulty: HardDynamic Forms and Dynamic Actions

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?

  1. 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.Answer
  2. B
    Applying a component visibility filter automatically revokes Field-Level Security read access for all profiles excluded by the filter criteria.
  3. C
    Sales Rep users will encounter a page layout runtime error when loading the record because Dynamic Forms visibility rules override Profile permissions.
  4. D
    The administrator must create a separate profile for Sales Reps and assign a legacy page layout to prevent field exposure across the application.

Answer

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.

Step-by-Step Solution

1
Analyze the scope of Dynamic Forms component visibility rules.
Dynamic Forms visibility rules only dictate whether a field or section component appears on a specific Lightning Record Page layout.
UI component visibility is a presentation layer feature, not a data security layer feature.
2
Evaluate data access mechanisms outside the Lightning Record Page.
Field-Level Security (FLS), Object permissions, and Sharing settings dictate true data access across all interfaces (Reports, List Views, SOQL API, Mobile).
If FLS grants read access to a field, hiding the field on a Dynamic Form component does not block users from querying or reporting on that field.
3
Select the correct security evaluation statement.
Identify that component visibility fails to provide data security compliance without FLS enforcement.
Hiding a field using Dynamic Forms visibility filters creates a false sense of security if underlying FLS remains accessible.

Key Concept

Dynamic Forms Component Visibility vs Field-Level Security (FLS)
Estimated Time:2m 0s
Rate this question

Topics

Dynamic Forms and Dynamic Actions

More questions from this topic