A data engineer is using AWS Glue to run a nightly ETL job that reads from an Amazon DynamoDB table and writes to Amazon S3 in Parquet format. The DynamoDB table is large and has a high read capacity. The engineer wants to minimize the impact on the DynamoDB table's performance and reduce the ETL job's runtime. Which approach should the engineer take?
DynamoDB's native export to S3 does not consume read capacity units and does not affect table performance. The export creates data in DynamoDB JSON format in S3. AWS Glue can then read from S3, transform as needed, and write to Parquet. This approach minimizes impact on the table and can be faster for large tables since it uses a separate export process. It also reduces the ETL job's runtime because Glue reads from S3 instead of DynamoDB.
Why this answer
To minimize impact on DynamoDB performance and reduce ETL runtime, exporting the table to S3 is ideal because it does not consume read capacity. AWS Glue can then process the exported data from S3, which is faster and does not affect the source table. Other methods like parallel scans or increasing workers still consume capacity and can impact performance.
Exam trap
The trap here is assuming that using DAX or parallel scans will avoid impacting DynamoDB when they still consume read capacity or add complexity.