nerdexam
Salesforce

CRT-101 · Question #103

The 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 a…

The correct answer is A. Assign a decision element to direct the user to a second screen to hold specific search engine. Important note: The marked correct answer (A) appears to be incorrect for this question. Based on current Salesforce Flow functionality, C is the correct answer. Why C is correct: Salesforce Screen Flows support Conditional Visibility directly on screen components, allowing a…

Workflow/Process Automation

Question

The 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 a search engine from a picklist. If lead source is not "Search Engine", this picklist should be hidden. How should the administrator complete this requirement?

Options

  • AAssign a decision element to direct the user to a second screen to hold specific search engine
  • BUse an assignment element, one for when lead source is "Search Engine" and one for everything
  • CCreate a picklist for specific search engine, and set conditional visibility so that is only shown
  • DConfigure a picklist for specific search engine, and use a validation rule to conditionally show only

How the community answered

(26 responses)
  • A
    77% (20)
  • B
    12% (3)
  • C
    4% (1)
  • D
    8% (2)

Explanation

Important note: The marked correct answer (A) appears to be incorrect for this question. Based on current Salesforce Flow functionality, C is the correct answer.

Why C is correct: Salesforce Screen Flows support Conditional Visibility directly on screen components, allowing a picklist to be shown only when a specific condition is met (e.g., Lead Source = "Search Engine") - all on the same screen. This is precisely the feature designed for this scenario: dynamically hiding or revealing fields without navigating to a new screen.

Why the other options are wrong:

  • A (Decision element → second screen): A Decision element routes flow execution to different paths, which would require building two separate screens. This works technically but is unnecessarily complex and not the intended approach when both fields belong on the same screen.
  • B (Assignment element): Assignment elements set variable values - they have no ability to control UI visibility. Wrong tool entirely.
  • D (Validation rule): Validation rules fire at the record-save level in Salesforce, not within a Flow screen. They validate data; they do not show or hide flow components.

Memory tip: Think of it this way - if you need a field to disappear based on another field's value on the same screen, reach for Conditional Visibility. If you need to send the user down a completely different path in the flow, use a Decision element. The word "hidden" in the question is your clue.

If this came from a study guide, double-check the source - C is the answer aligned with current Salesforce documentation and exam objectives.

Topics

#Screen Flows#Conditional Logic#Decision Elements#Lead Management

Community Discussion

No community discussion yet for this question.

Full CRT-101 Practice