When consuming APIs with security constraints like rate limits and timeouts, which combination of techniques must a security team implement to ensure API requests are processed efficiently without…

Question

Options

• ADisable authentication checks for high-volume API calls to increase request throughput without delays.
• BIncrease API call frequency to ensure all requests are handled promptly, process errors separately, and rely on firewall logs for monitoring.
• CImplement request throttling, retry logic for failed requests, and monitor API usage rates to avoid breaching rate limits.
• DReduce API call frequency to prevent exceeding rate limits, but avoid implementing retry logic to not breach the limits.

• A
  4% (2)
• B
  7% (4)
• C
  76% (41)
• D
  13% (7)

Explanation

Option C is correct because request throttling controls the pace of outgoing calls to stay within provider-defined limits, retry logic (ideally with exponential backoff) handles transient failures like timeouts without manual intervention, and monitoring API usage rates gives the team visibility to catch and correct limit breaches before they cause errors. Together, these three form the standard, defense-in-depth approach to resilient API consumption.

Why the distractors fail:

• A removes authentication, which introduces a critical security vulnerability and has nothing to do with rate limiting.
• B increases call frequency, which is the opposite of what rate limits require, and relying solely on firewall logs provides no proactive throttle management.
• D gets the first part right (reduce frequency) but discards retry logic - retries are essential for handling the transient errors that will still occur even at reduced volumes.

Memory tip: Think of the three pillars as "Slow, Recover, Watch" - throttle to slow down, retry to recover from failures, monitor to watch the limits. If an answer removes any one of these three, it's incomplete and wrong.

No community discussion yet for this question.