DATA-ARCHITECT practice question 20 of 35

Universal Containers (UC) is in the process of selling half of its company. As part of this split, UC's main Salesforce org will be divided into two…

Full set: 257 questions
Universal Containers (UC) is in the process of selling half of its company. As part of this split, UC's main Salesforce org will be divided into two org:org A and org B, UC has delivered these requirements to its data architect 1. The data model for Org B will drastically change with different objects, fields, and picklist values. 2. Three million records will need to be migrated from org A to org B for compliance reasons. 3. The migrate will need occur within the next two month, prior to be split. Which migrate strategy should a data architect use to successfully migrate the date?
Answer options
A: use as ETL tool to orchestrate the migration. Correct answer
B: Use Data Loader for export and Data Import Wizard for import
C: Write a script to use the Bulk API
D: Use the Salesforces CLI to query, export, and import
Correct Answer:
A. use as ETL tool to orchestrate the migration.
Explanation

An ETL (Extract, Transform, Load) tool is the most appropriate solution for this scenario. The key requirements are the large data volume (3 million records) and, most importantly, a drastically different data model in the target org. ETL tools are specifically designed to handle complex data transformations, such as mapping fields, changing data types, and translating picklist values between disparate systems. They provide robust orchestration, error handling, and performance management capabilities necessary for a large-scale, complex migration, making them superior to basic data loading tools or custom scripts for this use case.

Why Incorrect

B. Use Data Loader for export and Data Import Wizard for import The Data Import Wizard is limited to 50,000 records and cannot handle this volume. Data Loader lacks the advanced transformation capabilities needed for a drastically different data model.
C. Write a script to use the Bulk API While technically feasible, writing a custom script for complex transformations is time-consuming, error-prone, and requires significant development and testing effort, making an off-the-shelf ETL tool a more efficient choice.
D. Use the Salesforces CLI to query, export, and import The Salesforce CLI is primarily for metadata deployment and simple data operations. It is not designed as a comprehensive tool for large-scale, complex data transformation and migration projects.

References

1. Salesforce Architects, Architect's Guide to Data Migration. This guide details migration strategies, stating, "For complex migrations, especially those that require data from multiple sources or significant data transformation, an ETL tool is often the best choice."

2. Salesforce Developer Documentation, Which Data Loading Tool Should I Use?. The comparison table indicates that for complex logic and transformations, ETL tools are recommended over Data Loader or the Data Import Wizard.

3. Kimball, R., & Ross, M. (2013). The Data Warehouse Toolkit: The Definitive Guide to Dimensional Modeling (3rd ed.). Wiley. Chapter 1 discusses the critical role of the ETL system in extracting, cleaning, conforming, and delivering data to a new target schema, which aligns with the scenario's requirements.

Scroll to Top