DAS-C01 · Question #100
A company hosts an on-premises PostgreSQL database that contains historical data. An internal legacy application uses the database for read-only activities. The company's business team wants to move t
The correct answer is D. Configure an AWS Glue crawler to use a JDBC connection to catalog the data in the on-premises. The goal is to migrate on-premises PostgreSQL data to S3 for a data lake with the least operational overhead. AWS Glue is a fully managed, serverless ETL service that can connect to on-premises databases via JDBC over the existing AWS Direct Connect link. Option D uses an AWS Glu
Question
A company hosts an on-premises PostgreSQL database that contains historical data. An internal legacy application uses the database for read-only activities. The company's business team wants to move the data to a data lake in Amazon S3 as soon as possible and enrich the data for analytics. The company has set up an AWS Direct Connect connection between its VPC and its on- premises network. A data analytics specialist must design a solution that achieves the business team's goals with the least operational overhead. Which solution meets these requirements?
Options
- AUpload the data from the on-premises PostgreSQL database to Amazon S3 by using a
- BCreate an Amazon RDS for PostgreSQL database and use AWS Database Migration Service
- CConfigure an AWS Glue crawler to use a JDBC connection to catalog the data in the on-premises
- DConfigure an AWS Glue crawler to use a JDBC connection to catalog the data in the on-premises
How the community answered
(19 responses)- A21% (4)
- B5% (1)
- C11% (2)
- D63% (12)
Explanation
The goal is to migrate on-premises PostgreSQL data to S3 for a data lake with the least operational overhead. AWS Glue is a fully managed, serverless ETL service that can connect to on-premises databases via JDBC over the existing AWS Direct Connect link. Option D uses an AWS Glue crawler to catalog the source data and then leverages Glue ETL jobs to extract, transform/enrich, and load the data directly into Amazon S3 - all without provisioning or managing any infrastructure. Option A (manual upload) requires scripting and ongoing maintenance. Option B (RDS + DMS) introduces an unnecessary intermediate database, adding cost and complexity. Option C is similar to D but likely stops at cataloging without performing the actual migration and enrichment via ETL jobs. D is the complete, serverless, low-overhead solution.
Topics
Community Discussion
No community discussion yet for this question.