Examkin

Question

Difficulty: MediumDynamic Forms and Dynamic Actions

A Salesforce Administrator is configuring a Lightning record page for a custom Compliance Audit object. The business requires the sensitive field 'Penalty Amount' to appear on the Lightning record page only when the 'Audit Status' picklist field is set to 'Non-Compliant'. Additionally, data security policies require that users without proper authorization cannot access 'Penalty Amount' values through reports, list views, or API exports. Which combination of configurations should the administrator use to fulfill these requirements?

  1. Configure Field-Level Security to restrict field access for unauthorized users, and set up a Dynamic Forms component visibility rule on the Lightning record page based on Audit Status.Answer
  2. B
    Set up a Dynamic Forms component visibility rule on the Lightning record page, which automatically restricts API access and reporting visibility when the field is hidden.
  3. C
    Create separate Profiles for each Audit Status value and assign custom page layouts to control both UI visibility and data access.
  4. D
    Set Organization-Wide Defaults for the Compliance Audit object to Private and rely on Dynamic Dashboard running user settings to enforce field security.

Answer

Configure Field-Level Security to restrict field access for unauthorized users, and set up a Dynamic Forms component visibility rule on the Lightning record page based on Audit Status.
The correct answer combines Field-Level Security (FLS) with Dynamic Forms component visibility. FLS is mandatory for data security across all entry points (reports, list views, API, and record pages). Dynamic Forms component visibility provides the required conditional rendering on the record page based on the 'Audit Status' picklist value.

Step-by-Step Solution

1
Identify the data security requirement
Field-Level Security (FLS) must be configured for the 'Penalty Amount' field so unauthorized users cannot access it via API, reports, list views, or record detail views.
UI visibility rules alone do not prevent data access through alternative interfaces like reports or API.
2
Identify the user interface requirement
A Dynamic Forms component visibility filter is configured on the 'Penalty Amount' field component in Lightning App Builder with the criteria: Audit Status equals 'Non-Compliant'.
Dynamic Forms allows granular component and field visibility based on record field values on Lightning record pages.
3
Combine security and UI visibility controls
Authorized users will see the field on the Lightning page only when Audit Status is 'Non-Compliant', while unauthorized users will remain unable to access the field anywhere in Salesforce.
Combining FLS and Dynamic Forms visibility ensures both data security and optimal user experience.

Key Concept

Dynamic Forms Visibility vs. Field-Level Security
Rate this question

Topics

Dynamic Forms and Dynamic Actions

More questions from this topic