Courseiva
Data Ingestion and TransformationhardMultiple SelectObjective-mapped

DEA-C01 Data Ingestion and Transformation Practice Question

A company needs to ingest data from a MySQL database into Amazon S3 using AWS DMS. The data changes frequently and the requirement is to capture changes in near real-time. Which THREE configurations are necessary?

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

Create an S3 target endpoint in DMS.

To capture near real-time changes from a MySQL database to S3 using AWS DMS, you need: B) an S3 target endpoint in DMS to write the data; C) binary logging (binlog) enabled on MySQL to capture changes; and D) a DMS replication instance to process and transfer data. Options A and E are unnecessary: a VPC endpoint for S3 is not required (DMS can use public endpoints or VPC peering), and S3 event notifications are not used to trigger DMS—they are typically for post-processing.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Create a VPC endpoint for S3.

    Why it's wrong here

    Not required for DMS to S3.

  • Create an S3 target endpoint in DMS.

    Why this is correct

    Needed to specify the S3 bucket.

  • Enable binary logging (binlog) on the MySQL source database.

    Why this is correct

    DMS uses binlog for CDC.

  • Create an AWS DMS replication instance.

    Why this is correct

    Required for DMS tasks.

  • Configure an S3 event notification to trigger DMS.

    Why it's wrong here

    DMS is pull-based; events not needed.

Quick reference

AWS S3 Storage Class Comparison

Storage ClassMin DurationRetrievalUse Case
S3 StandardNoneImmediateFrequently accessed data
S3 Standard-IA30 daysImmediateInfrequent access, rapid retrieval
S3 One Zone-IA30 daysImmediateNon-critical infrequent data
S3 Intelligent-TieringNoneImmediate–hoursUnknown or changing access patterns
S3 Glacier Instant90 daysMillisecondsArchive with instant retrieval
S3 Glacier Flexible90 daysMinutes–hoursArchive, flexible retrieval
S3 Glacier Deep Archive180 daysHoursLong-term compliance archive

About these practice questions

Courseiva writes every DEA-C01 question from scratch — 1,711 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more way this is tested on DEA-C01

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. A company needs to ingest data from a MySQL database into Amazon S3 in near real-time. The database is running on EC2. The data engineer wants to minimize the impact on the source database. Which service should be used?

easy
  • A.AWS Database Migration Service (DMS) with ongoing replication
  • B.AWS Glue ETL job with a JDBC connection
  • C.Amazon RDS for MySQL with read replica
  • D.AWS Schema Conversion Tool (SCT)

Why A: AWS DMS with ongoing replication (change data capture) is the correct choice because it can continuously replicate changes from a MySQL source database to Amazon S3 with minimal performance impact. DMS uses a transactional log-based approach (MySQL binlog) to capture changes as they occur, avoiding heavy SELECT queries on the source. This enables near real-time ingestion without adding significant load to the production database.

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.