Plat-Admn-201 practice question 9 of 25

A Platform Administrator at Universal Containers has a screen flow that helps users create new leads. When Lead Source is "Search Engine", the administrator needs to require the user to choose a specific search engine from a picklist. If Lead Source is not "Search Engine", this picklist should be hidden. What is the most efficient way for the administrator to complete this requirement?

Full set: 148 questions
Answer options
A: Use a conditional filter in the screen element to only show the Specific Search Engine field only when Lead Source is "Search Engine".
B: Use Assignment elements; one for when Lead Source is "Search Engine" and one for everything else.
C: Create a picklist for Specific Search Engine, and set conditional visibility so that it is only shown when Lead Source is "Search Engine". Correct answer
D: Configure a picklist for Specific Search Engine, and use a validation rule to conditionally show only when Lead Source is "Search Engine".
Correct Answer:
C. Create a picklist for Specific Search Engine, and set conditional visibility so that it is only shown when Lead Source is "Search Engine".
Explanation

The most efficient method to dynamically show or hide a component on a flow screen is by using the built-in Component Visibility feature. The administrator can add the "Specific Search Engine" picklist to the screen and then configure its visibility properties. The condition would be set to render the component only when the "Lead Source" component on the same screen has a value of "Search Engine". This is a declarative feature that handles the logic on a single screen without requiring extra elements or complex branching, making it the most direct and efficient solution.

Why Incorrect

A. "Conditional filter" is not the correct terminology for this feature. Component Visibility is the specific name for controlling the display of screen components based on other values.
B. Using Assignment and Decision elements to route to different screens is inefficient. It creates unnecessary complexity and maintenance overhead compared to handling the logic on one screen.
D. Validation rules enforce data integrity when a record is saved. They cannot control the visibility of components on a user interface screen during data entry.

References

1. Salesforce Help. (2024). Flow Screen Input Component, Set Component Visibility. "You can declare that a component appears on a screen only when certain conditions are met. This feature is supported for all standard and custom screen components... For example, specify that a text box for providing a reason appears only when a checkbox is selected."

2. Salesforce Trailhead. (2024). Screen Flows Module, Control Flow Navigation Unit. "Use conditional visibility to show a component only when it’s needed. For example, on a contact screen, show a mailing address section only when a checkbox is selected."

Scroll to Top