QuestionQ91

Data Ingestion and Transformation

A company is establishing a data pipeline in AWS. The pipeline extracts client data from Amazon S3 buckets, performs quality checks, and transforms the data. The pipeline saves the processed data in a relational database. The company will use the processed data for future queries.

Which solution will satisfy these requirements in the MOST cost-effective way?

  • A Use AWS Glue ETL to extract the data from the S3 buckets and perform the transformations. Use AWS Glue Data Quality to enforce suggested quality rules. Load the data and the quality check results into an Amazon RDS for MySQL instance.
  • B Use AWS Glue Studio to extract the data from the S3 buckets. Use AWS Glue DataBrew to perform the transformations and quality checks. Load the processed data into an Amazon RDS for MySQL instance. Load the quality check results into a new S3 bucket.
  • C Use AWS Glue ETL to extract the data from the S3 buckets and perform the transformations. Use AWS Glue DataBrew to perform quality checks. Load the processed data and the quality check results into a new S3 bucket.
  • D Use AWS Glue Studio to extract the data from the S3 buckets. Use AWS Glue DataBrew to perform the transformations and quality checks. Load the processed data and quality check results into an Amazon RDS for MySQL instance.
Explanation

Amazon RDS for MySQL provides the required relational destination for processed data that will be queried later. AWS Glue Studio supports visual ETL jobs, and AWS Glue DataBrew supports data preparation, including transformations and data-quality checks. Because quality-check results do not need to be relationally queried, storing them in Amazon S3 is more cost-effective than allocating database storage for them.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!