The standard Lead Rating field has picklist values of Hot, Warm, and Cold. A list of new leads was importance without errors even though several records had the value of Unrated in the Rating field…

Question

Options

• AThe Restricted picklist checkbox was unchecked.
• BField-level security was set to Visible for all profiles.
• CA global picklist value set was used to populate the picklist.
• DThe Add to All Record Types checkbox was selected.

• A
  91% (21)
• B
  4% (1)
• D
  4% (1)

Explanation

Option A is correct because an unrestricted picklist allows any value to be saved to the field - even values not defined in the picklist - during imports, API calls, or data loads. When the "Restricted" checkbox is unchecked, Salesforce will accept "Unrated" without error even though it isn't one of the defined picklist values (Hot, Warm, Cold).

Why the distractors are wrong:

• B (Field-level security): FLS controls whether a field is visible or editable for a profile, but has no effect on which values are accepted during an import.
• C (Global picklist value set): Using a global value set actually enforces restriction more strictly - global picklists are restricted by default and would have prevented the import of "Unrated."
• D (Add to All Record Types): This determines which picklist values are available on each record type, not whether out-of-picklist values can be saved.

Memory tip: Think of the Restricted checkbox as a "bouncer" - when it's checked, the bouncer only lets approved values in; when it's unchecked, anyone (any value) can walk through the door. If records with unknown values sneak in, the bouncer was off duty (unrestricted).

No community discussion yet for this question.