DEA-C01 AWS DMS BatchApplyEnabled Practice Question
A data engineer is using AWS DMS to migrate a 2 TB Oracle database to Amazon Aurora PostgreSQL. The migration is running in full load mode with ongoing replication. After the full load completes, the ongoing replication task shows a 'TargetMetadata' error: 'ERROR: duplicate key value violates unique constraint'. The engineer verifies that the target table already contains the data. What should the engineer do to resolve this issue?
⚠ Common exam trap
A common mistake is to think that truncating the target table is necessary, but that would cause data loss and downtime. Another mistake is to disable constraints, which can lead to data integrity issues.
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
✓
Enable 'BatchApplyEnabled' and set 'TaskRecoveryTableEnabled' to false in the task settings.
Enabling 'BatchApplyEnabled' allows DMS to batch changes and reduces duplicate key errors, while setting 'TaskRecoveryTableEnabled' to false prevents recovery attempts that can reapply already committed transactions. Option B is wrong because disabling constraints compromises data integrity. Option C is wrong because truncating and restarting loses existing data and does not address the ongoing replication issue. Option D is wrong because dropping indexes does not prevent duplicate key violations.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Enable 'BatchApplyEnabled' and set 'TaskRecoveryTableEnabled' to false in the task settings.
Why this is correct
Batch apply minimizes duplicate key errors, and disabling recovery table prevents re-application of already-applied changes.
- ✗
Disable the unique constraint on the target table.
Why it's wrong here
Disabling constraints compromises data integrity.
- ✗
Truncate the target table and restart the full load.
Why it's wrong here
Truncating would lose data and require a full reload, which is disruptive.
- ✗
Drop the indexes on the target table and recreate them after the migration.
Why it's wrong here
Indexes are not the cause of duplicate key violations; constraints are.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 1,711 original DEA-C01 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DEA-C01 practice question is part of Courseiva's free Amazon Web Services 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 DEA-C01 exam.