A developer is receiving HTTP 400: ThrottlingException errors intermittently when calling the Amazon CloudWatch API. When a call fails, no data is retrieved. What best practice should first be applied

Question

Options

• AContact AWS Support for a limit increase.
• BUse the AWS CLI to get the metrics.
• CAnalyze the applications and remove the API call.
• DRetry the call with exponential backoff.

• A
  8% (2)
• B
  4% (1)
• C
  8% (2)
• D
  81% (21)

Explanation

Exponential backoff (D) is the AWS-recommended first response to ThrottlingException errors because throttling is transient - it means you've temporarily exceeded the API rate limit, not that something is permanently broken. Retrying with exponential backoff (progressively longer waits between retries) reduces request pressure and gives the service time to recover, eventually succeeding without any infrastructure changes.

Why the distractors fail:

• A (Contact AWS Support) - a limit increase is a valid escalation, but it's not the first step; retrying is simpler, faster, and often sufficient for intermittent errors.
• B (Use the AWS CLI) - the CLI still calls the same CloudWatch API under the hood, so it hits the same throttling limits and solves nothing.
• C (Remove the API call) - eliminating the call removes the functionality entirely; that's a last resort, not a best practice.

Memory tip: Think of throttling like a traffic light - you don't reroute your entire trip (C), call the city (A), or switch vehicles (B). You simply wait, then go. Throttled = wait and retry.

No community discussion yet for this question.