PLAT-ADMN-202 practice question 31 of 35

Cloud Kicks (CK) tracks the support level of its customers on the account record page. CK wants to show a text notification on a case record page when the related account is a platinum-level customer. How could an app builder meet this requirement?

Full set: 311 questions

Domain Workflow/Process Automation

Answer options
A: Add a rich text area to the Case Lighting page > Set the component visibility of the rich text area to show when the account support level is platinum. Correct answer
B: Create a text-only Visualforce page > Drag the Visualforce component into the Case page layout > Set its visibility to show when the account support level is platinum.
C: Create a text-only Visualforce page > Clone the case page layout > Drag the Visualforce component into the page, and assign the layout to platinum cases.
D: Clone the Case Lightning page > Add a rich text area to the new page, and assign this page to platinum accounts.
Correct Answer:
A. Add a rich text area to the Case Lighting page > Set the component visibility of the rich text area to show when the account support level is platinum.
Explanation

The most efficient and modern declarative solution is to use the Lightning App Builder to configure dynamic component visibility. An app builder can add a Rich Text component to the Case Lightning record page and enter the desired notification text. Then, by setting a component visibility filter, the component can be configured to display only when the Support Level field on the related Account record has a value of 'Platinum'. This approach directly addresses the requirement using standard, point-and-click functionality without needing code or multiple page layouts.

Why Incorrect

B: This is incorrect because dynamic visibility based on field values is a feature of Lightning Record Pages (managed in the Lightning App Builder), not traditional page layouts. Using Visualforce for a simple text notification is also unnecessarily complex compared to the native Rich Text component. C: Page layouts are assigned based on a user's profile and the record's type, not on the value of a specific field. It is not possible to assign a page layout dynamically when a field value changes to 'platinum'. D: Lightning Record Pages are assigned based on a combination of App, Record Type, and Profile. They cannot be dynamically assigned based on a field value from a related record, such as the support level on the parent account.

References

1. Salesforce Help - Dynamic Lightning Pages: "You can make your Lightning record pages more dynamic by configuring component visibility filters... For example, you can create a rule for a component to appear only when a case is escalated." This document establishes the core principle of using component visibility filters.

2. Salesforce Help - Component Visibility Filters for Lightning Record Pages: This document explicitly states how to filter based on related objects. "On a contact record page, you can use fields on the contact object and fields on the account object that it’s related to." This directly supports using the related Account's field from the Case record page, confirming the viability of option A. The filter syntax would traverse the lookup relationship (e.g., Record > Account > Support Level).

3. Salesforce Help - Assign Lightning Record Pages to Profiles: This document details the assignment criteria for Lightning Pages. "After you activate a Lightning record page, you can assign it to a combination of apps, record types, and profiles." This confirms that assignment cannot be based on a specific field's value, invalidating option D.

Scroll to Top