SF-Data-Arch Data Migration Practice Question
You are migrating records that contain multi-select picklist values. What is the key consideration for mapping this data from a legacy system?
⚠ Common exam trap
Test-takers frequently assume multi-select picklists are mapped using comma-separated lists or arrays, ignoring Salesforce's strict requirement for a semi-colon delimiter format.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The values must be formatted as a semi-colon separated string.
Multi-select picklists are stored as semi-colon separated strings in Salesforce. When migrating, the source data must be transformed to match this specific delimiter format. Failure to use the exact semi-colon separator, or including values that are not currently defined in the Salesforce picklist configuration, will result in import errors. It is essential to sanitize and format these values in the ETL layer before the load.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The values must be separated by commas in the source file.
Why it's wrong here
Salesforce uses the semi-colon (;) as the delimiter for multi-select picklists. Using commas will cause the entire string to be treated as a single, invalid value, which will fail if that single string does not match an existing picklist option or if the picklist is restricted.
- ✗
Each value must be imported as a separate child record.
Why it's wrong here
Multi-select picklists are a single field on the object, not a relational structure. Treating them as child records would break the data model and make it impossible to use native picklist features like filtering or reporting. The values must be mapped to the single multi-select picklist field.
- ✓
The values must be formatted as a semi-colon separated string.
Why this is correct
Salesforce requires multi-select picklist values to be provided as a string with each value separated by a semi-colon. This is the only format that the Salesforce API accepts for this field type. Transforming the source data to this specific format is a mandatory step in the data migration process.
- ✗
The picklist must be converted to a custom object before loading.
Why it's wrong here
Converting a multi-select picklist to a custom object is a massive architectural change that is unnecessary for simple data migration. It would require changing the entire data model, updating all related reports, and rewriting all existing logic, which is far beyond the scope of a data migration task.
About these practice questions
This SF-Data-Arch question is part of Courseiva's 222-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Salesforce exam blueprint
This SF-Data-Arch practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SF-Data-Arch exam.