CRT-101 practice question 3 of 30

User at Cloud Kicks want to see information more useful for their role on the Case page. How should an administrator make the pages more dynamic and easier to use?

Full set: 248 questions
Answer options
A: Add Component visibility filters to the Components. Correct answer
B: Remove fields from the record details component.
C: Delete the extra component from the page.
D: Include more tab components with filters.
Correct Answer:
A. Add Component visibility filters to the Components.
Explanation

Component visibility filters in the Lightning App Builder are the designated feature for creating dynamic user experiences. Administrators can configure a component to appear or disappear based on specific criteria, including fields on the user's record, such as their Role or Profile. This allows the Case page to dynamically display components and information relevant only to certain users, making the page more useful and less cluttered for each specific role. This directly addresses the requirement to make the page dynamic and tailored to the user's context.

Why Incorrect

B. Remove fields from the record details component. This is a static change affecting all users assigned to the page layout, not a dynamic adjustment based on user role.
C. Delete the extra component from the page. This permanently removes the component for all users, rather than dynamically showing or hiding it based on specific criteria like user role.
D. Include more tab components with filters. While tabs organize content, the fundamental mechanism to make tabs or components appear dynamically based on user role is component visibility, not filters within the tabs.

References

1. Salesforce Help Documentation: Dynamic Lightning Pages.

Reference: Under the "Set Component Visibility Filters" section, it states, "You can make your Lightning pages more dynamic by configuring component visibility filters in the Lightning App Builder... A component on a Lightning page can be visible or hidden based on criteria you define." It explicitly lists "User > Role" as a filterable field.

2. Salesforce Trailhead: Lightning App Builder Module, Build a Dynamic Lightning Page Unit.

Reference: This unit provides a step-by-step guide on creating dynamic pages. It explains, "With dynamic Lightning pages, you can control when a component appears on a record page by adding filter conditions and logic to its properties... You can filter on the viewing user’s device, or on fields associated with the record, the user, their permissions, or their role."

3. Salesforce Help Documentation: Component Visibility Filter Considerations.

Reference: This document details the fields available for visibility rules. In the "User" section, it confirms that fields on the User object, such as Profile.Name and Role.Name, can be used to control component visibility, directly supporting the solution for a role-based dynamic page.

Scroll to Top