Cost-Effective One-Time Data Join Across Heterogeneous AWS Sources
Short answer
C Use Amazon Athena Federated Query to join the data from all data sources.
Question
Which solution will meet this requirement MOST cost-effectively?
Key Takeaways
The main trap is choosing data movement (S3 copy) or heavy compute (EMR); the insight is that serverless federated queries eliminate ETL overhead and infrastructure costs for ad-hoc analysis.
Learn why Amazon Athena Federated Query is the most cost-effective solution for joining data from DynamoDB, RDS, Redshift, and S3 in a one-time analysis job.
Common mistake: Candidates often choose B (copy to S3) because S3 storage is cheap, forgetting that the ETL process and schema management overhead make it less cost-effective for a single one-time job compared to direct federated access.
Expert Analysis
The scenario presents a classic AWS exam trap: selecting the most feature-rich tool versus the most cost-effective solution for a specific workload type. The key constraints are one-time analysis and multiple heterogeneous data sources (DynamoDB, RDS, Redshift, S3).
Amazon Athena Federated Query is designed specifically to query data across multiple sources without moving it. However, it incurs costs for querying each source (e.g., per-request costs for DynamoDB, I/O for RDS/Redshift) plus the Athena query processing cost. For a one-time job, the overhead of establishing federated connections and paying for external data retrieval can be significant, especially if large datasets are involved.
Option B involves copying data into Amazon S3 and running Athena queries directly on the files. While copying data has an initial ETL cost, S3 storage is extremely cheap, and Athena queries on S3 are highly optimized and predictable in cost. More importantly, for a one-time job, the simplicity and low marginal cost of querying flat files in S3 often outweighs the complexity and potential high latency/cost of federated queries against transactional databases like RDS or NoSQL stores like DynamoDB. The community comments highlight this trade-off, with some arguing for C due to 'no movement,' but others correctly note that S3-centric approaches are often cheaper for ad-hoc analytics.
However, looking closer at AWS best practices for cost-effectiveness in one-time scenarios involving diverse sources, Athena Federated Query (C) allows you to join data without provisioning clusters (unlike EMR) or moving massive volumes of data into S3 first (which might take time and incur transfer costs if not done efficiently). But wait—the question asks for MOST cost-effective.
Let's re-evaluate. Option A (EMR) requires provisioning, which is expensive for one-time jobs. Option D (Redshift Spectrum) is good but limited by Redshift's compute limits and doesn't natively support DynamoDB as easily as Athena Federated Query does without additional setup. Between B and C: Copying data (B) involves ETL labor and time. Federated Query (C) allows immediate analysis. For a one-time job, avoiding the ETL step and the need to manage data duplication in S3 makes C the intended answer in many AWS contexts because it eliminates infrastructure management and data movement costs, focusing purely on query execution. The 'trick' is that while S3 is cheap, the process of getting data there and managing schemas can be more complex/costly than a direct federated join for a single run.
Actually, reviewing official AWS guidance and common exam patterns: For a one-time analysis across heterogeneous sources, Athena Federated Query is the designated solution to avoid data silos and ETL pipelines. It is serverless (pay-per-query), supports all listed sources natively, and avoids the cost/effort of building an ETL pipeline to S3. Therefore, C is correct.
Official Reference
https://docs.aws.amazon.com/athena/latest/ug/federated-query.html
This link opens the official vendor documentation in a new tab.
Exam Strategy
When asked for 'cost-effective' solutions for 'one-time' or 'ad-hoc' tasks, always prioritize serverless services over provisioned ones (like EMR or Redshift clusters). If the task involves joining multiple disparate sources without needing persistent data warehousing, look for 'Federated Query' options as they avoid ETL costs and infrastructure management.
Frequently Asked Questions
Why is Athena Federated Query better than copying data to S3 for a one-time job?
Can Athena Federated Query handle DynamoDB and RDS simultaneously?
What is the primary cost driver for Athena Federated Query?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 6 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 6
-
lucas_rfsb 👍 7 Answered CI would go for C because Federated Query is typical for this porpouse. Besides, we don't need to add/duplicate resources in S3. But I see that, becasuse Athena is more optimized for S3, it can be considered a tricky question, since there can be more trade-offs to consider, such as data governance that are easier if data is centralized in S3 in my opinion.
-
pypelyncar 👍 4 Answered CServerless Processing: Athena is a serverless query service, meaning you only pay for the queries you run. This eliminates the need to provision and manage compute resources like in EMR clusters, making it ideal for one-time jobs. Federated Query Capability: Athena Federated Query allows you to directly query data from various sources like DynamoDB, RDS, Redshift, and S3 without physically moving the data. This eliminates data movement costs and simplifies the analysis process. Reduced Cost for Large Datasets: Compared to copying data to S3, which can be expensive for large datasets, Athena Federated Query avoids unnecessary data movement, reducing overall costs.
-
certplan 👍 2Amazon Athena Federated Query allows you to query data from multiple federated data sources including relational databases, NoSQL databases, and object stores directly from Athena. While this might seem like an efficient way to join data from different sources without the need for copying data into Amazon S3, it's essential to consider the cost implications. AWS documentation on Amazon Athena Federated Query [1] explains that while Federated Query enables you to query data from external data sources without data movement, it does not eliminate data transfer costs. Depending on the data sources involved (such as Amazon RDS, DynamoDB, etc.), there might be data transfer costs associated with querying data directly from these sources. [1] Amazon Athena Federated Query Documentation: https://docs.aws.amazon.com/athena/latest/ug/federated-data-sources.html
-
certplan 👍 11. Data Storage Costs: Storing data in Amazon S3 is generally cheaper compared to the other AWS storage options like Amazon Redshift or Amazon RDS. 2. Compute Costs: Amazon: Athena is a serverless query service that allows you to query data directly from S3 without the need for provisioning or managing infrastructure. You only pay for the queries you run, which can be more cost-effective compared to provisioning an EMR cluster (option A) or using Redshift Spectrum (option D), both of which involve compute resources that you might not fully utilize. 3. Data Transfer Costs: Option B involves copying the data once into S3, and then there are no additional data transfer costs for querying the data using Athena. In contrast, options A and D would involve data transfer costs as data is moved between different services. Amazon Athena Pricing: https://aws.amazon.com/athena/pricing/ Amazon S3 Pricing: https://aws.amazon.com/s3/pricing/
-
certplan 👍 1Point: "perform a one-time analysis job" Option C (Amazon Athena Federated Query) might seem appealing, but it's generally more suited for querying data from external sources without copying the data into S3. However, since the data is already within AWS services, copying it to S3 and using Athena directly would likely be more cost-effective.
Show 1 more comment
-
Deno_Dennis 👍 1 Answered CThe answer is C. Amazon Athena Federated Query allows you to directly query data from multiple data sources such as Amazon DynamoDB, Amazon RDS, Amazon Redshift, and Amazon S3.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All DEA-C01 Questions
Access 100 questions with complete answers and detailed explanations.
View Full DEA-C01 Practice Test →