Amazon Web Services Data-Engineer-Associate Exam With Confidence Using Practice Dumps

Option B is most cost-effective because it combines a serverless ETL service for overnight processing with a serverless warehouse for partner SQL access during business hours. The material describes AWS Glue as a “fully managed, serverless, scalable ETL service” that can extract, transform, and load data with minimal operational overhead, which fits the requirement for multiple transformations and data cleaning.

For the SQL access layer, the study material highlights the cost advantage of Amazon Redshift Serverless: it automatically provisions and scales capacity and you pay only for the compute capacity provisioned, with no compute costs when no workloads are running. That directly supports “multiple business partners” querying during business hours while avoiding the always-on cost of a provisioned cluster.

Options C and D use a provisioned Redshift cluster, which is less cost-effective because capacity must be paid for even when partners are not querying. Option A adds EMR cluster management cost and operational overhead compared to using Glue for ETL.

Aurora zero-ETL integration with Amazon Redshift Serverless is specifically designed to provide near real-time analytics on Aurora transactional data without the need to build or manage data pipelines. This integration continuously replicates data changes from Aurora MySQL into Redshift Serverless automatically.

The solution is fully serverless, requires no infrastructure provisioning, and eliminates the need for schema conversion, replication tasks, or streaming frameworks. Data is kept in sync with low latency, making it immediately available for analytical queries in Redshift Serverless.

AWS DMS-based solutions require task configuration, monitoring, and maintenance. Amazon MSK with Debezium introduces significant operational complexity and is not serverless. Kinesis-based replication pipelines require additional services and ongoing operational management.

Aurora zero-ETL integration is the lowest-maintenance, highest-efficiency solution and is explicitly recommended by AWS for this use case.

Problem Analysis:

The company must log all user activities and connection activities in Amazon Redshift for security compliance.

Key Considerations:

Redshift supports audit logging, which can be configured to write logs to an S3 bucket.

S3 provides durable, scalable, and cost-effective storage for logs.

Solution Analysis:

Option A: S3 for Logging

Standard approach for storing Redshift logs.

Easy to set up and manage with minimal cost.

Option B: Amazon EFS

EFS is unnecessary for this use case and less cost-efficient than S3.

Option C: Aurora MySQL

Using a database to store logs increases complexity and cost.

Option D: EBS Volume

EBS is not a scalable option for log storage compared to S3.

Final Recommendation:

Enable Redshift audit logging and specify an S3 bucket as the destination.

Amazon Redshift Audit Logging

Storing Logs in Amazon S3