Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon SAA-C03 Exam - Topic 3 Question 56 Discussion

Actual exam question for Amazon's SAA-C03 exam
Question #: 56
Topic #: 3
[All SAA-C03 Questions]

An e-commerce company has an application that uses Amazon DynamoDB tables configured with provisioned capacity. Order data is stored in a table named Orders. The Orders table has a primary key of order-ID and a sort key of product-ID. The company configured an AWS Lambda function to receive DynamoDB streams from the Orders table and update a table named Inventory. The company has noticed that during peak sales periods, updates to the Inventory table take longer than the company can tolerate. Which solutions will resolve the slow table updates? (Select TWO.)

Show Suggested Answer Hide Answer
Suggested Answer: B, C

:

Key Problem:

Delayed Inventory table updates during peak sales.

DynamoDB Streams and Lambda processing require optimization.

Analysis of Options:

Option A: Adding a GSI is unrelated to the issue. It does not address stream processing delays or capacity issues.

Option B: Optimizing batch size reduces latency and allows the Lambda function to process larger chunks of data at once, improving performance during peak load.

Option C: Increasing write capacity for the Inventory table ensures that it can handle the increased volume of updates during peak times.

Option D: Increasing read capacity for the Orders table does not directly resolve the issue since the problem is with updates to the Inventory table.

Option E: Increasing Lambda timeout only addresses longer processing times but does not solve the underlying throughput problem.

AWS Reference:

DynamoDB Streams Best Practices

Provisioned Throughput in DynamoDB


Contribute your Thoughts:

0/2000 characters
Hannah
4 months ago
Batching DynamoDB streams sounds like a good idea too!
upvoted 0 times
...
Linsey
4 months ago
Wait, can increasing the Lambda timeout really fix the issue?
upvoted 0 times
...
Dorthy
4 months ago
Not sure about adding a global secondary index, though.
upvoted 0 times
...
Tamera
4 months ago
Totally agree, that should help with the write bottleneck!
upvoted 0 times
...
Louvenia
5 months ago
Increasing the provisioned capacity by 1,000 WCUs is a solid move.
upvoted 0 times
...
Phillip
5 months ago
I wonder if increasing the Lambda timeout would really help. It seems like a workaround rather than a real solution.
upvoted 0 times
...
Kristeen
5 months ago
I practiced a similar question, and I think increasing the write capacity units is definitely a solid option.
upvoted 0 times
...
Gayla
5 months ago
I'm not entirely sure, but I think adding a global secondary index might not directly solve the update speed issue.
upvoted 0 times
...
Shawn
5 months ago
I remember that increasing the provisioned capacity can help with performance, so maybe option C is a good choice.
upvoted 0 times
...
Ellen
5 months ago
Increasing the Lambda function timeout might help, but that feels like a band-aid solution. I'd want to explore the other options first.
upvoted 0 times
...
Fairy
5 months ago
Increasing the DynamoDB table provisioned capacity seems like a straightforward solution, but I'm not sure if that's the most efficient approach here.
upvoted 0 times
...
Penney
5 months ago
Okay, I think I've got this. Adding a global secondary index to the Orders table should help speed up the lookups for the Inventory table updates.
upvoted 0 times
...
Derick
5 months ago
Hmm, I'm a bit confused about the difference between read and write capacity units. I'll need to review that before deciding on the right approach.
upvoted 0 times
...
Lavonna
6 months ago
This looks like a tricky one. I'll need to think through the different options carefully to figure out the best solutions.
upvoted 0 times
...

Save Cancel