Data Cleansing & Migration Strategy Flashcards
7 cards from real ERP practice questions. Tap to flip, then mark Knew It or Still Learning โ missed cards come back until you master them.
Read the first 7 Data Cleansing & Migration Strategy flashcards as text
Which data migration risk is specifically introduced by running multiple ETL loads in parallel without dependency management?
Answer: Race conditions causing referential integrity violations
Parallel loads can insert child records before parent records exist if load sequence is not enforced, creating foreign key violations.
What is the key difference between a 'data migration strategy' and a 'data migration plan'?
Answer: The strategy defines approach and principles; the plan details tasks, timelines, and responsibilities
The strategy establishes the high-level approach (e.g., big-bang vs. phased, scope decisions), while the plan operationalizes it with specific tasks, owners, and dates.
During ERP migration, 'business rule validation' in the ETL layer is best described as:
Answer: Applying domain-specific logic to reject or flag records that violate ERP business constraints
Business rule validation enforces domain constraints (e.g., a customer cannot have a negative credit limit) and rejects or flags non-compliant records before they reach the ERP target.
Which factor most commonly causes ERP data migration projects to exceed their planned timelines?
Answer: Underestimation of data quality issues discovered during profiling and cleansing
Organizations consistently discover far more dirty, incomplete, or conflicting data than anticipated once formal profiling begins, driving remediation effort well beyond initial estimates.
A 'data migration cutover checklist' should include which critical item immediately before switching users to the new ERP?
Answer: Verification that all reconciliation totals balance between source and target
Confirming that reconciliation totals balance is the last data-quality gate before go-live, ensuring no records were lost or corrupted during the final migration run.
In ERP migration, 'data archiving' differs from 'data migration' in that archiving:
Answer: Preserves historical data in a read-only repository for compliance without loading it into the live ERP
Archiving stores legacy historical data in a separate, accessible repository for audit and compliance purposes, while migration moves operational data into the new ERP for active use.
Which tool capability is most valuable when cleansing large ERP datasets containing address information?
Answer: Address standardization and USPS/postal validation engine
Address standardization tools parse, correct, and validate addresses against postal authority databases, resolving inconsistencies critical for customer and vendor master data.