SF-Data-Arch Data Modeling and Database Design Practice Question
A company is migrating legacy data and needs to preserve the CreatedDate and CreatedById. Which feature should they enable?
⚠ Common exam trap
Candidates frequently assume that standard administrative permissions are sufficient, forgetting that 'Set Audit Fields' is a specialized, high-privilege permission that must be explicitly enabled in the org.
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
✓
Set Audit Fields permission
By default, Salesforce sets the CreatedDate and CreatedById to the time and user of the import. To preserve historical audit logs, Salesforce provides the 'Set Audit Fields' permission. This is vital for data migration projects where historical accuracy is required for compliance and reporting. Without this, the audit trail of the legacy system is lost, which can lead to significant regulatory and reporting issues.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Data Loader batch settings
Why it's wrong here
Data Loader settings do not grant the permission to override system-read-only fields. Even with proper batch sizes, the system will ignore any mapping to CreatedDate unless the 'Set Audit Fields' permission is explicitly enabled for the user performing the data import process.
- ✓
Set Audit Fields permission
Why this is correct
The 'Set Audit Fields' permission is the specific security requirement needed to override system-managed fields. When this is enabled for the integration user, the system allows the ingestion of original creation timestamps and user IDs, ensuring that legacy data maintains its historical integrity after the migration.
- ✗
Field History Tracking
Why it's wrong here
Field History Tracking only logs changes made to records *after* they are in the system. It does not allow for the manual import or preservation of historical 'CreatedDate' or 'CreatedById' values from an external legacy system, making it irrelevant for the initial data migration task.
- ✗
Owner migration setting
Why it's wrong here
Owner migration settings allow changing the record owner, but they do not control the system-level audit fields like 'CreatedDate'. This setting is strictly for reassigning record ownership and does not provide the permission needed to write to read-only metadata fields during a bulk load operation.
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.