Examkin

Question

Difficulty: HardLightning App Builder Pages (App, Home, Record Pages)

An administrator is configuring a Lightning Record Page for a custom object named Vendor_Contract__c. The business requires a specialized executive summary component on the page to be visible only to users with the 'Procurement Manager' job role. Additionally, the administrator must ensure that sensitive financial fields on the page are completely inaccessible via API and reports to users without proper data access. Which set of actions meets these requirements while following Salesforce security best practices?

  1. Configure component visibility rules on the Lightning Record Page using the User > Role field for the executive summary component, and enforce Field-Level Security (FLS) settings on the profile or permission set for the financial fields.Answer
  2. B
    Use Dynamic Forms component visibility filters on individual field components to hide the sensitive financial fields from unauthorized users, eliminating the need to set Field-Level Security.
  3. C
    Create a custom Record Type for vendor contracts and remove the sensitive financial picklist fields from the Record Type picklist assignment settings.
  4. D
    Create separate profile-specific Lightning Record Pages and assign them via Org Default activation to restrict access to both the executive summary component and financial fields.

Answer

Configure component visibility rules on the Lightning Record Page using the User > Role field for the executive summary component, and enforce Field-Level Security (FLS) settings on the profile or permission set for the financial fields.
The correct response properly distinguishes between UI display logic and underlying data security. Component visibility rules in Lightning App Builder allow administrators to dynamically filter which components appear based on user record attributes (such as User > Role). Meanwhile, Field-Level Security (FLS) is mandatory for securing sensitive fields against unauthorized access across all access points, including reports, SOQL queries, and API endpoints.

Step-by-Step Solution

1
Analyze UI component restriction requirements
Dynamic component visibility filter criteria on the Lightning App Builder page can conditionally show/hide components based on user attributes such as User > Role.
This selectively displays UI elements without creating redundant record pages.
2
Analyze data access and security requirements for sensitive fields
Field-Level Security (FLS) must be configured at the profile or permission set level to restrict Read/Edit access.
FLS ensures comprehensive data protection across the UI, reports, dashboards, search, and API integrations.
3
Evaluate combined architecture for compliance
Combining Lightning App Builder component visibility with Field-Level Security satisfies both UI customization and data privacy standards.
UI component visibility is for user experience control, while FLS is for true security enforcement.

Key Concept

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

Topics

Lightning App Builder Pages (App, Home, Record Pages)

More questions from this topic