SF-Data-Arch Salesforce Data Management Practice Question
An organization is consolidating multiple legacy systems into Salesforce. They need to track the lineage of data records back to their source systems for audit purposes. What is the recommended strategy for maintaining data lineage?
⚠ Common exam trap
Test-takers often choose standard name fields or formula fields for data lineage, ignoring the need for indexing and unique upsert capabilities provided by External IDs.
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
✓
Create a custom field marked as an External ID to store legacy identifiers.
The recommended approach is to create a dedicated 'External ID' custom field on relevant objects to store the source system's unique identifier. This field should be marked as an External ID and indexed. This allows for easy upsert operations, prevents duplicates during ongoing synchronization, and provides a clear audit trail for compliance teams to trace records back to their original source systems during data lifecycle management.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Store the source system ID in the standard Name field.
Why it's wrong here
The Name field is intended for identifying the record within Salesforce, not for storing technical metadata from legacy systems. Using it for IDs complicates search, reporting, and data integrity, as it does not enforce uniqueness and is not optimized for the indexing requirements of large data volume lookups.
- ✓
Create a custom field marked as an External ID to store legacy identifiers.
Why this is correct
External ID fields are specifically designed for data integration and lineage. Marking them as an index ensures fast queries when upserting records. This satisfies the requirement to maintain a persistent link between Salesforce and legacy systems, which is essential for ongoing data governance and audit reporting requirements.
- ✗
Use the Salesforce ID as the source record identifier in legacy systems.
Why it's wrong here
This approach is dangerous because it assumes the target system is already established and immutable. If the Salesforce environment is refreshed or migrated, existing IDs may become invalid. Furthermore, mapping to Salesforce IDs is difficult during initial data migration before the target records have been created in Salesforce.
- ✗
Append the source system name to the record's description field.
Why it's wrong here
The Description field is a text area intended for descriptive information, not for structured metadata or integration keys. Querying or reporting on this field would be highly inefficient and prone to errors, failing to provide the robust, scalable lineage tracking required for enterprise-level data management and audit compliance.
Visual reference
About these practice questions
Courseiva writes every SF-Data-Arch question from scratch — 222 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.