An on-premises Oracle database supports a live ordering system. A data engineer must copy the existing order rows into an Amazon S3 data lake and then keep S3 current with every insert, update and delete, while placing minimal load on the source. Which approach should the engineer use?
Choose one.
AWS DMS tasks come in three types: full load (one-time copy), CDC only (changes from a start point) and full load plus CDC (copy, then continuous changes read from the transaction log).
The requirement has two halves: the existing rows and every later change, including deletes. Full load and ongoing replication covers both and reads changes from the redo log rather than by querying tables. Full load alone misses continuity and hammers the source, CDC only misses history, and a Glue JDBC bookmark sees only newly inserted keys.
- Split the requirement: historical rows plus continuous inserts, updates and deletes.
- Note that deletes and updates require log-based change capture, not key-based incremental reads.
- Match both halves to one DMS task type: full load plus CDC.
Exam tip: Existing data plus every later change from a relational source means an AWS DMS full-load-and-CDC task.
Data Ingestion on AWS: Kinesis, MSK, DMS, Glue, and Batch Patterns — the lesson that teaches this.