An administrator is designing user interface experiences in Lightning App Builder, configuring a custom Home Page for the Sales application and a custom Record Page for a custom object. Which two considerations must the administrator evaluate regarding page activation capabilities and component visibility rules? (Select 2 choices)
- Home pages can be activated as Org Default, App Default, or assigned to specific App and Profile combinations, but they do not support Record Type assignment.Answer
- Component visibility filters control whether a component is displayed on the page UI, but they do not restrict user access to underlying field data via reports, API, or global search.Answer
- CHiding a component containing record fields using component visibility filters automatically revokes the user's Field-Level Security Read access for those fields.
- DHome pages can be assigned to specific Record Types when paired with custom profile assignments in Lightning App Builder.
- EOrg Default page activations override granular App, Record Type, and Profile activation assignments whenever a conflict occurs.
Answer
The two correct considerations are that Home pages support activation by Org Default, App Default, or App and Profile combinations (but not Record Type), and that component visibility filters only hide UI elements without restricting underlying data access through the API or reporting.
The valid statements highlight two fundamental Lightning App Builder principles: first, Home pages support Org Default, App Default, and App + Profile activation levels but do not use Record Types; second, component visibility filters only change visual display on the page and do not restrict data access via reports or APIs.
Step-by-Step Solution
Key Concept
Lightning Page Activation Granularity and Component Visibility vs Data Security