Exam AWS Certified Solutions Architect - Associate SAA-C03 topic 1 question 962 discussion

DynamoDB export connector literally "exports" table snapshot to s3 as dynamoDB-json object, then process on it. So it does not affect on read / write capacity on dynamoDB itself. But Athena query directly on dynamoDB so affects on read / write capacity

The trick here is to avoid, by any means, interact with the original DynamoDB table because doing so would affect the provisioned capacity. Option "B" is the only one that interacts with an EXPORTED COPY of the table. So, the question is: would provisioned capacity be affected by the DynamoDB export process? The answer is: NO! (https://docs.aws.amazon.com/glue/latest/dg/aws-glue-programming-etl-connect-dynamodb-home.html): "DynamoDB export to S3 allows you to export both full and incremental data from your DynamoDB table. Exports do not consume any read capacity units (RCUs) and have no impact on table performance and availability"

A - Athena allows you to use standard SQL, but it doesn't guarantee minimal impact on the table. B - It minimizes direct read/write operations on the table because the exported data can be processed separately (for example, export to S3 then do the processing). C - Cool but there's no native connector to directly pull data from DynamoDB. You must export the data to S3 or another source first, adding complexity. D - EMR impacts throughput significantly.

The correct answer is B. Use an AWS Glue job with the AWS Glue DynamoDB export connector to calculate performance metrics on a recurring schedule. Explanation: Option B: Correct. AWS Glue offers an efficient method to extract, transform, and load (ETL) data from DynamoDB to Amazon S3, without affecting the table’s provisioned throughput as significantly. Once data is in S3, it can be further processed or queried using AWS Glue or other analytics services, without impacting DynamoDB's immediate R/W provisioning.

Explanation: Amazon Athena with DynamoDB Connector: Athena is a serverless interactive query service that allows you to run SQL queries directly on data in various storage systems, including DynamoDB, through the Athena DynamoDB connector. This setup minimizes the impact on the provisioned read and write capacity of the DynamoDB table because the connector reads data efficiently without directly querying the table. Performance Metrics Calculation: Athena provides SQL capabilities to compute performance metrics on the data fetched via the DynamoDB connector. The queries can be scheduled using Amazon EventBridge or other automation tools to run daily. Minimal Operational Overhead: Athena requires no infrastructure to manage, making it a low-maintenance solution. It is cost-effective since you pay only for the queries you run.

I think A is correct. We can query the data from DynamoDB by Amazon Athena DynamoDB connector directly, not via S3 Bucket.

https://aws.amazon.com/blogs/big-data/accelerate-amazon-dynamodb-data-access-in-aws-glue-jobs-using-the-new-aws-glue-dynamodb-elt-connector/

The DynamoDB export connector allows you to export data from DynamoDB to other storage solutions like Amazon S3 without consuming the table's provisioned read capacity, ensuring minimal impact on the performance of the table.

B. Instead, the new AWS Glue DynamoDB export connector reads DynamoDB data from the snapshot, which is exported from DynamoDB tables. This approach has following benefits: It doesn’t consume read capacity units of the source DynamoDB tables

To calculate performance metrics for customer device data on a daily basis with minimal effect on the table’s provisioned read and write capacity, the best solution would be: A. Use an Amazon Athena SQL query with the Amazon Athena DynamoDB connector to calculate performance metrics on a recurring schedule. This approach allows you to run SQL queries directly on the data stored in DynamoDB without impacting the provisioned throughput, as Athena queries are serverless and do not consume DynamoDB read or write capacity1.

The right answer is B

VOTE B

why is B wrong.. Glue DynamoDB export connector will read data from PITR instead of DynamoDB directly..

I go with A