SF-Admin Data and Analytics Management Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Create a validation rule on the Lead object that requires Lead Source to be populated.

  Why it's wrong here

  A validation rule enforces data entry at the UI level and during API loads, but it does not ensure that the value is one of the existing picklist values. The rule would only check that the field is not blank, not that it matches a picklist entry. This does not satisfy the requirement of restricting to existing picklist values.

• ✓

  Use the Data Import Wizard's field mapping to map a column to Lead Source, and ensure the values match the picklist entries.

  Why this is correct

  The Data Import Wizard allows mapping source columns to Lead Source. If the source values exactly match the picklist entries (case-sensitive), the import will succeed. This ensures that only existing picklist values are loaded. The administrator should verify the picklist values and clean the source data before loading.

• ✗

  Set the Lead Source field as required at the field level for all profiles.

  Why it's wrong here

  Making the field required ensures that a value is provided, but it does not restrict the value to existing picklist entries. Users could still enter arbitrary text if the field is a text field, or if it's a picklist, they could only select from the list, but the requirement is about data loading, not UI entry. This does not guarantee compliance during import.

• ✗

  Create a workflow rule that updates the Lead Source to a default value if it is blank.

  Why it's wrong here

  A workflow rule can set a default value when the field is blank, but it does not validate that the provided value is an existing picklist entry. If the imported value is invalid, the workflow might not correct it, and the record could fail validation or store an invalid value. This does not ensure compliance with picklist values.