Examkin

Question

Difficulty: Very hardLightning App Builder Pages (App, Home, Record Pages)

A Salesforce administrator is tasked with updating the Case object user interface to support complex compliance requirements. Tier 2 Support Agents using the Service Console app require a dedicated Lightning Record Page layout when working on 'Escalated' cases, while Tier 1 agents must retain their existing layout. Additionally, a specialized SLA Compliance component on the new record page must only be visible to users assigned a custom permission named 'View Escalations', regardless of whether users have Field-Level Security (FLS) access to the SLA fields. Which two configuration actions must the administrator execute within Lightning App Builder to satisfy these requirements? (Select 2 choices)

  1. Activate the custom Lightning Record Page as App, Record Type, and Profile default for the Service Console app, Escalated record type, and Tier 2 Support profile.Answer
  2. Add a conditional component visibility filter to the SLA Compliance component evaluating User > Permissions > Custom Permission > View Escalations equals True.Answer
  3. C
    Modify Field-Level Security (FLS) settings on the SLA fields to Restricted for Tier 1 agents to force the component to hide dynamically.
  4. D
    Activate the custom page at the Org Default level and configure page layout assignment rules within Object Manager for the Escalated Record Type.
  5. E
    Remove the Escalated Record Type picklist assignment from the Tier 1 Support profile to prevent unauthorized page views.

Answer

To meet the requirements, the administrator must activate the page using the App, Record Type, and Profile assignment combination and apply a component visibility filter based on the user's assigned custom permission.
The combination of activating the page at the App, Record Type, and Profile level and setting a component visibility filter based on user custom permissions fully addresses both requirements. App, Record Type, and Profile is the most specific activation scope in Lightning App Builder, ensuring Tier 2 agents see the customized page while Tier 1 agents continue using their current page assignment. Furthermore, Lightning App Builder allows component visibility filters to check assigned Custom Permissions directly on the user context.

Step-by-Step Solution

1
Determine the required activation precedence level in Lightning App Builder.
Recognize that conflicting target requirements for different profiles (Tier 1 vs Tier 2) within the same app and record type require the highest assignment specificity.
App, Record Type, and Profile assignment overrides Org Default and App Default settings, isolating the new page to Tier 2 agents in the Service Console on Escalated cases.
2
Configure component visibility for the SLA Compliance component.
Add a filter criterion using User > Permissions > Custom Permission > View Escalations set to True.
Lightning App Builder supports dynamic component visibility based on Client Device, Record Fields, or User attributes (including Custom Permissions).

Key Concept

Lightning Record Page Activation Precedence and Dynamic Component Visibility Filters
Estimated Time:2m 0s
Rate this question

Topics

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

More questions from this topic