Question

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

A Salesforce administrator is reviewing Lightning App Builder page activations and assignment options across Home pages and Record pages for a multi-department organization. Which two statements correctly describe the behavior and assignment capabilities of Lightning pages? (Select 2 answers)

  1. A custom Lightning Home page can be assigned as the Org Default or to specific combinations of Apps and Profiles, but it cannot be assigned by Record Type.Answer
  2. B
    Setting component visibility filters on a Lightning Record Page automatically restricts field-level security permissions for users across reports and API calls.
  3. Activating a Lightning Record Page using the App, Record Type, and Profile combination overrides both Org Default and App Default page assignments for those specific contexts.Answer
  4. D
    A custom Home page can be assigned directly to specific Record Types to present dynamic component layouts when users view record details.
  5. E
    Lightning Record Page activations can be assigned directly to individual Permission Set Groups instead of Profiles.

Answer

The correct statements are that custom Lightning Home pages can be assigned as Org Default or to App and Profile combinations (but not by Record Type), and that activating a Record Page by App, Record Type, and Profile overrides Org Default and App Default assignments.
Lightning Home pages support Org Default and App/Profile level assignments, but not Record Type assignments because they are not record-bound. Additionally, in Lightning Record Page activation hierarchy, assigning a page by App, Record Type, and Profile provides the highest specificity, overriding both App Default and Org Default assignments.

Step-by-Step Solution

1
Analyze Home Page Activation Levels
Home pages can be activated as Org Default or assigned to specific Apps and Profiles. Because Home pages are not tied to object records, Record Type assignment is unavailable.
Understanding the activation hierarchy prevents misconfiguration of Home pages.
2
Evaluate Record Page Precedence
Record pages evaluate precedence from most specific to least specific: (1) App + Record Type + Profile, (2) App Default, (3) Org Default.
Granular activations override broader default assignments for targeted user groups.
3
Distinguish UI Visibility from Field-Level Security
Component visibility controls on Lightning App Builder pages only manage user interface rendering and do not enforce backend data security or FLS.
Security permissions must be managed via Profiles, Permission Sets, and Field-Level Security settings.

Key Concept

Lightning App Builder Page Activation Precedence and Scope
Rate this question