Examkin

Question

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

An administrator at Northern Trail Outfitters needs to configure user interface experience settings for a custom object, `Equipment_Maintenance__c`. The requirement states that when viewing records in the 'Field Operations' Lightning App, users with the 'Maintenance Technician' profile must see a tailored Lightning Record Page assigned specifically to their record type. However, for all other Lightning Apps, these same users should see the standard default page assigned for that record type. Which TWO activation and visibility configurations should the administrator implement to fulfill these requirements? (Select 2 choices)

  1. Activate the tailored Lightning Record Page by assigning it as App, Record Type, and Profile default for the 'Field Operations' app and 'Maintenance Technician' profile.Answer
  2. B
    Set the tailored Lightning Record Page as the Org Default to override all existing record page assignments across all applications.
  3. Ensure the standard record page remains assigned as the App Default or Org Default for other Lightning Apps so non-target apps retain their baseline layout.Answer
  4. D
    Configure component visibility rules on the tailored page to check the user's active Lightning App context via a custom Field-Level Security setting.
  5. E
    Assign the tailored page as an App Default for the 'Field Operations' app without specifying Record Types or Profiles.

Answer

The administrator must activate the custom page using the App, Record Type, and Profile combination for the 'Field Operations' app and target profile, while relying on lower-precedence App or Org defaults for other apps.
In Salesforce Lightning App Builder, page activation follows a strict precedence hierarchy: 1) App, Record Type, and Profile, 2) App Default, and 3) Org Default. Activating the tailored page specifically for the 'Field Operations' app combined with the target Record Type and 'Maintenance Technician' profile satisfies the requirement for the target app. For all other apps, because no specific 3-tier assignment exists, Salesforce falls back to the lower-level App Default or Org Default, maintaining the standard layout seamlessly.

Step-by-Step Solution

1
Analyze activation hierarchy precedence in Lightning App Builder.
App + Record Type + Profile activation has the highest precedence, overriding App Default and Org Default only when those three criteria match.
To restrict a custom Lightning Record Page to a specific app, record type, and profile, the explicit 3-tier activation method must be used.
2
Verify fallback behavior for other apps.
When users navigate to the record in any other app, Salesforce checks for matching activation rules; if none exist for that app, it falls back to the App Default or Org Default.
Maintaining the standard page as Org/App default guarantees that non-target apps display the standard layout without further custom configuration.

Key Concept

Lightning Record Page Activation Precedence (Org Default vs App Default vs App + Record Type + Profile)
Rate this question

Topics

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

More questions from this topic