DEA-C01 Data Operations and Support Practice Question
A company uses AWS DMS to replicate data from an on-premises Oracle database to Amazon RDS for MySQL. The full load completes successfully, but ongoing replication (CDC) is failing with a 'Failed to add supplemental logging' error. What should the data engineer do to resolve this issue?
⚠ Common exam trap
DEA-C01 often tests the specific prerequisite that AWS DMS requires supplemental logging on Oracle sources for CDC, and candidates may incorrectly assume DMS can always enable it automatically or that the error relates to endpoint or network configuration.
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 supplemental logging on the source Oracle database manually.
AWS DMS requires supplemental logging to be enabled on the source Oracle database to capture change data for CDC replication. The 'Failed to add supplemental logging' error occurs because DMS cannot automatically enable this at the database level when the user lacks the necessary privileges (e.g., ALTER DATABASE). The data engineer must manually enable supplemental logging on the source Oracle database, typically by executing ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; and ensuring table-level supplemental logging is also configured.
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 supplemental logging on the source Oracle database manually.
Why this is correct
Oracle requires supplemental logging to supply the primary key and before-image data DMS needs for change capture. Enabling it manually on the source tables or database lets CDC read redo logs and clear the error.
- ✗
Recreate the DMS endpoint for the source database with a new connection.
Why it's wrong here
The error arises because Oracle supplemental logging is not enabled at database or table level on the source; recreating the endpoint changes nothing about that database setting. Endpoint recreation suits connectivity or credential faults, such as an unreachable host or invalid password, not a missing Oracle logging configuration.
- ✗
Modify the target MySQL database to use a different engine version.
Why it's wrong here
The failure stems from Oracle source-side supplemental logging being absent, which the MySQL target engine version cannot influence; CDC reads redo/archive logs on the source. Changing the target engine version addresses target-side incompatibilities, such as unsupported data types or DDL replication limits, not source log configuration.
- ✗
Increase the task log interval in the DMS task settings.
Why it's wrong here
Raising the log interval only changes how often DMS writes task diagnostics; it cannot grant the Oracle source the supplemental logging CDC requires. It is tempting because verbose logging aids troubleshooting, and it would be the right response when diagnosing task failures rather than fixing a missing database-level prerequisite.
Visual reference
Go deeper
Related to this question
About these practice questions
One of 1,321 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Amazon Web Services exam blueprint
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.