A Salesforce administrator is configuring Lightning App Builder pages for a custom object named Asset_Inspection__c. The requirements state that specific fields must only display when an inspection fails, and custom record layouts must be deployed selectively to different teams. Which two statements accurately describe the functionality of Lightning App Builder page activations and Dynamic Forms component visibility? (Select 2 choices.)
- Setting a conditional component visibility filter on a field in Dynamic Forms hides the field from the Lightning user interface but does not prevent access through APIs or standard reports.Answer
- BConfiguring component visibility on a Dynamic Forms field automatically revokes Field-Level Security read permissions for users who fail the visibility criteria.
- CA customized Lightning Home page can be activated and assigned by combining App, Record Type, and Profile settings.
- Activating a Lightning Record Page by App, Record Type, and Profile takes precedence over both App Default and Org Default activations for matching users.Answer
- EField picklist values can be filtered dynamically using page layout component visibility rules without assigning them to specific Record Types.
Answer
Dynamic Forms component visibility controls UI display without altering API or reporting access, and activating a Lightning Record Page by App, Record Type, and Profile overrides App Default and Org Default assignments.
Dynamic Forms visibility filters are designed for user interface display control and do not modify underlying Field-Level Security or reporting access. Furthermore, Lightning Record Page activation follows a strict hierarchy where the combination of App, Record Type, and Profile assignment takes precedence over broader App Default and Org Default settings.
Step-by-Step Solution
Key Concept
Lightning App Builder Activation Precedence and Dynamic Forms UI Visibility