DEA-C01 · Question #160
An ecommerce company operates a complex order fulfilment process that spans several operational systems hosted in AWS. Each of the operational systems has a Java Database Connectivity…
The correct answer is A. Use AWS Glue to build ingestion pipelines from the operational systems into Amazon Redshift. To consolidate data from multiple JDBC-compliant operational databases into a central system for hourly order tracking with minimal development overhead, AWS Glue is an effective solution.
Question
An ecommerce company operates a complex order fulfilment process that spans several operational systems hosted in AWS. Each of the operational systems has a Java Database Connectivity (JDBC)-compliant relational database where the latest processing state is captured. The company needs to give an operations team the ability to track orders on an hourly basis across the entire fulfillment process. Which solution will meet these requirements with the LEAST development overhead?
Options
- AUse AWS Glue to build ingestion pipelines from the operational systems into Amazon Redshift
- BUse AWS Glue to build ingestion pipelines from the operational systems into Amazon
- CUse AWS Database Migration Service (AWS DMS) to capture changed records in the operational
- DUse AWS Database Migration Service (AWS DMS) to capture changed records in the operational
How the community answered
(53 responses)- A79% (42)
- B4% (2)
- C6% (3)
- D11% (6)
Why each option
To consolidate data from multiple JDBC-compliant operational databases into a central system for hourly order tracking with minimal development overhead, AWS Glue is an effective solution.
AWS Glue is a fully managed, serverless ETL service that can connect to multiple JDBC-compliant relational databases, extract data, transform it, and load it into Amazon Redshift. This allows for building efficient, scheduled ingestion pipelines for hourly updates, providing a robust data warehouse for analytical queries with significantly less development effort due to Glue's automated code generation and managed infrastructure.
The option is incomplete ('into Amazon'). Assuming it implies a different target than Redshift, Redshift is specifically optimized for analytical queries across consolidated data for reporting needs, which fits the 'track orders on an hourly basis' requirement better than raw storage in S3 without a dedicated analytical engine.
AWS Database Migration Service (AWS DMS) is primarily designed for database migration and continuous replication (CDC), not for building complex ETL pipelines to consolidate and prepare data from multiple sources for hourly analytical reporting in a data warehouse like AWS Glue does.
AWS Database Migration Service (AWS DMS) is focused on data replication, not the broader ETL capabilities for transformation and consolidation from multiple operational systems into an analytical store for hourly reporting with least development overhead, which is a strength of AWS Glue.
Concept tested: AWS Glue for ETL from JDBC sources to Amazon Redshift
Source: https://docs.aws.amazon.com/glue/latest/dg/aws-glue-programming-etl-connect.html
Topics
Community Discussion
No community discussion yet for this question.