nerdexam
Amazon

DAS-C01 · Question #4

A company is building a data lake and needs to ingest data from a relational database that has time-series data. The company wants to use managed services to accomplish this. The process needs to be…

The correct answer is A. Use AWS Glue to connect to the data source using JDBC Drivers. To ingest incremental time-series data daily from a relational database into Amazon S3 using managed services cost-effectively, AWS Glue is the appropriate choice. AWS Glue ETL jobs can connect via JDBC and be configured to process only new data.

Collection

Question

A company is building a data lake and needs to ingest data from a relational database that has time-series data. The company wants to use managed services to accomplish this. The process needs to be scheduled daily and bring incremental data only from the source into Amazon S3. What is the MOST cost-effective approach to meet these requirements?

Options

  • AUse AWS Glue to connect to the data source using JDBC Drivers.
  • BUse AWS Glue to connect to the data source using JDBC Drivers.
  • CUse AWS Glue to connect to the data source using JDBC Drivers and ingest the entire dataset.
  • DUse AWS Glue to connect to the data source using JDBC Drivers and ingest the full data.

How the community answered

(24 responses)
  • A
    75% (18)
  • B
    13% (3)
  • C
    8% (2)
  • D
    4% (1)

Why each option

To ingest incremental time-series data daily from a relational database into Amazon S3 using managed services cost-effectively, AWS Glue is the appropriate choice. AWS Glue ETL jobs can connect via JDBC and be configured to process only new data.

AUse AWS Glue to connect to the data source using JDBC Drivers.Correct

AWS Glue is a fully managed ETL service that can connect to relational databases using JDBC drivers, extract time-series data, and load it into Amazon S3. It supports scheduling and, importantly, provides job bookmarks that enable incremental data processing, ensuring only new or changed data is ingested daily, which is the most cost-effective approach for this scenario.

BUse AWS Glue to connect to the data source using JDBC Drivers.

This option is identical to option A and provides the same correct solution for ingesting incremental data from a relational database into Amazon S3 using AWS Glue's capabilities.

CUse AWS Glue to connect to the data source using JDBC Drivers and ingest the entire dataset.

Ingesting the entire dataset daily contradicts the requirement to 'bring incremental data only.' Processing the full dataset repeatedly is less efficient and more costly than an incremental approach, especially with time-series data that grows continuously.

DUse AWS Glue to connect to the data source using JDBC Drivers and ingest the full data.

Ingesting the full data daily is explicitly against the requirement to load 'incremental data only.' This method would incur higher costs and processing overhead by repeatedly processing unchanged historical data, making it inefficient and not cost-effective.

Concept tested: Incremental data loading with AWS Glue for relational databases

Source: https://docs.aws.amazon.com/glue/latest/dg/monitor-exceptions-jobs.html

Topics

#AWS Glue#Data Ingestion#Incremental Data Loading#Relational Databases

Community Discussion

No community discussion yet for this question.

Full DAS-C01 Practice