Examkin

Question

Difficulty: MediumDynamic Forms and Dynamic Actions

An administrator converts a custom Vendor Application object page to Dynamic Forms and sets a component visibility filter to hide the sensitive 'Tax Identification Number' field unless the status is set to 'Approved'. However, a user without authorization to view tax details reports being able to view and export the 'Tax Identification Number' field using a standard Salesforce report. Which statement explains why the field remains visible in reports, and what should the administrator do to secure the field across the entire org?

  1. Dynamic Forms component visibility rules control UI layout presentation on Lightning pages only; Field-Level Security (FLS) must be restricted on the user profile or permission set to block access in reports and APIs.Answer
  2. B
    Dynamic Forms field visibility rules automatically modify Field-Level Security, but reporting tools bypass page layouts unless Organization-Wide Defaults are set to Private.
  3. C
    To restrict field access in reports, the administrator must create a separate profile for the user with Organization-Wide Defaults modified for custom fields.
  4. D
    Dynamic Forms component visibility filters apply exclusively to mobile device views, so desktop record page rules must be configured in classic Page Layouts.

Answer

Dynamic Forms component visibility rules control UI presentation on Lightning Record Pages only. To restrict field data access in reports, list views, and APIs, Field-Level Security (FLS) must be configured on the user profile or assigned via permission sets.
Dynamic Forms visibility rules govern UI component rendering on Lightning Record Pages. They do not restrict backend data access. Field-Level Security (FLS) settings on profiles and permission sets control data visibility globally across reports, list views, and API calls.

Step-by-Step Solution

1
Analyze the difference between presentation layer controls and data security controls.
Dynamic Forms visibility rules only determine whether a field component renders on a specific Lightning Record Page layout.
UI visibility filters do not alter underlying object security or data access permissions.
2
Identify why the field is visible in reports.
Standard and custom reports query the database directly subject to object permissions and Field-Level Security (FLS), bypassing Lightning page layout rules.
Since FLS was not restricted for the user, the field remains accessible in reporting features.
3
Determine the correct administrative remediation.
Update Field-Level Security on the user's profile or permission set to hide or restrict read access to the 'Tax Identification Number' field.
Field-Level Security is the primary mechanism in Salesforce for enforcing field confidentiality across all interfaces, including reports, list views, and APIs.

Key Concept

UI Presentation (Dynamic Forms Visibility) vs. Platform Data Security (Field-Level Security)
Estimated Time:1m 30s
Rate this question

Topics

Dynamic Forms and Dynamic Actions

More questions from this topic