Ingesting Oracle to S3 Parquet with Least Effort
A company is building a data lake for a new analytics team. The company is using Amazon S3 for storage and Amazon Athena for query analysis. All data that is in Amazon S3 is in Apache Parquet format. The company is running a new Oracle database as a source system in the company’s data center. The company has 70 tables in the Oracle database. All the tables have primary keys. Data can occasionally change in the source system. The company wants to ingest the tables every day into the data lake. Which solution will meet this requirement with the LEAST effort?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests knowledge of AWS DMS capabilities as a managed replication tool versus self-managed solutions like Sqoop or Glue bookmarks.
Determines the optimal AWS service for migrating on-premises Oracle data to Amazon S3 in Parquet format with minimal configuration effort.
Candidates often select AWS Glue (B) assuming bookmarks handle incremental loads, but Glue is primarily for ETL processing, not direct database-to-S3 replication with automatic schema discovery and Parquet conversion out-of-the-box.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
AWS Database Migration Service (DMS) is designed specifically for continuous data replication from source databases to various targets, including Amazon S3. It supports full load and ongoing replication, automatically handles schema mapping, and can write data directly to S3 in Apache Parquet format without requiring custom code or complex job orchestration. This meets the requirement of ingesting tables daily with the least amount of development and maintenance effort.Why the Other Options Are Wrong
Option A requires building and maintaining an EMR cluster and writing/maintaining Sqoop scripts, which is high effort. Option B uses AWS Glue; while it can connect to Oracle, 'bookmarks' are used to track processed files during re-runs, not to detect changes in the source database itself. Implementing incremental ingestion via Glue would require custom logic or additional services. Option D involves migrating the DB to RDS first, then using triggers and Lambda, which adds significant complexity and latency compared to a direct DMS task.Community Comment Notes
The community strongly favored option C, with 90% of votes selecting it. One user noted that DMS allows S3 as a target with Parquet formatting configured directly. Another user dismissed Glue bookmarks as being for file tracking rather than source change detection. The consensus confirms that DMS is the standard managed solution for this scenario.Official Reference
Exam Strategy
When asked for 'least effort' in data migration scenarios, prioritize fully managed services like AWS DMS over self-managed tools like Sqoop or EMR, especially when the target is S3.
Frequently Asked Questions
Why is AWS Glue bookmark incorrect for incremental ingestion?
Bookmarks track processed files to avoid duplicates on re-run, they do not detect changes in the source database like primary key updates.
Can AWS DMS write directly to S3 in Parquet?
Yes, DMS supports S3 as a target and can serialize data into Parquet format automatically.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →