AWS Certified Solutions Architect - Professional Practice Mode

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose B1

  Not A: Solution mentions descriptive error message when the scenario asks for errors not to be shown. B: The problem is with PUT calls, which points to a bottleneck in DynamoDB. Throttling the high-use client will keep enough DynamoDB write capacity for all other low-use clients. Also, solution mentions that application handles 429 "without error" (presumably retries, just like A). Not C: PUT calls can't be cached (or at least it doesn't make sense here). Not D: The problem is with DynamoDB write capacity, not with Lambda functions not scaling up quickly enough.

• Chose B1

  Use API Gateway throttling + usage plans to fairly distribute access and protect your system from high request rates by individual clients. Option B provides a targeted and scalable fix that meets both technical and business goals.

• Chose B1

  Why B is the best solution: Problem Summary: Increased errors during PUT requests. Caused by a single client generating a high volume of requests. The API is noncritical, and retries are acceptable. Errors are affecting customer experience and API reputation. Solution Breakdown: API Gateway usage plans allow you to throttle requests by API key, limiting the impact of a noisy or abusive client. Throttling results in HTTP 429 (Too Many Requests) responses. Clients can be coded to recognize 429 responses and retry with backoff, which improves customer experience while maintaining control. This approach protects backend systems like Lambda and DynamoDB from being overloaded.