Examkin

Question

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

An administrator is configuring a customized Lightning Record Page for a custom object named Consulting_Project__c to fulfill two key business requirements:
1. The page named 'Consulting_Executive_Page' must be assigned so that all users working inside the Sales App see it as the default page for Consulting_Project__c records, regardless of record type or user profile.
2. A specialized financial component on the page must only be displayed when the project's Status field is 'Active' and the viewing user possesses the 'Executive_User' custom permission.

Which two statements correctly describe how the administrator should configure these requirements and how Salesforce will evaluate them? (Select 2 choices)

  1. Activating the page as an App Default for the Sales App assigns it to all record types and profiles within that app, overriding the Org Default page.Answer
  2. Setting dynamic component visibility criteria based on record fields and user permissions controls component display without granting or restricting underlying Field-Level Security.Answer
  3. C
    Hiding the financial component using component visibility rules automatically revokes API and report access to the underlying fields for non-executive users.
  4. D
    To activate a page as an App Default, the administrator must first create a custom Record Type and assign picklist values for each user profile.
  5. E
    Component visibility rules can be configured to display fields to users who otherwise lack Field-Level Security read access on their assigned profile.

Answer

The administrator should activate the page as an App Default for the Sales App and configure component visibility filters using record fields and user custom permissions. App Default activation applies across all record types and profiles within the specified app. Component visibility controls UI presentation only and does not alter underlying Field-Level Security permissions.
Activating a Lightning Record Page as an App Default configures the page as the default for all users accessing records within that specific app, overriding Org Defaults without requiring explicit record type or profile mapping. Additionally, component visibility filters enable dynamic conditional display of components based on record values and user permissions without modifying platform-level data security rules like Field-Level Security.

Step-by-Step Solution

1
Analyze activation hierarchy for Lightning Record Pages
Org Default is the lowest priority, App Default is medium priority, and App + Record Type + Profile is the highest priority.
Assigning the page as App Default for the Sales App ensures all users in that app see the page regardless of profile or record type without requiring complex combination assignments.
2
Evaluate component visibility filter behavior
Filters can evaluate Record Fields (Status = 'Active') and User > Permission > Custom Permission ('Executive_User').
Component visibility dynamically renders components based on specified criteria on the UI layer.
3
Distinguish UI visibility from Field-Level Security (FLS) security boundaries
UI component visibility filter rules do not grant access to hidden FLS fields, nor do they restrict API/report data access.
FLS and Object-Level Security govern data access layers, whereas Lightning App Builder governs presentation layers.

Key Concept

Lightning Record Page Activation Levels and Component Visibility vs. Field-Level Security
Estimated Time:2m 0s
Rate this question

Topics

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

More questions from this topic