A transit-agency client receives HTTP 403 Forbidden on one Cisco API call and HTTP 429 Too Many Requests on another. How should unrecoverable-error control flow treat them?
Select an answer to reveal the explanation.
Short Explanation
A red light and a traffic cop’s hand are both “stop,” but only the temporary jam clears if you wait. 429 says slow down and retry; 403 says you are not allowed—choose the stop branch for permission, not a blanket “all 4xx” rule.
Full Explanation
Not every 4xx shares the same recovery path. 429 Too Many Requests is typically recoverable with backoff or Retry-After. 403 Forbidden (and similar permission or validation failures) is an unrecoverable branch for that attempt: stop rather than hammer the API. Treating all 4xx as fatal drops recoverable rate limits; treating all 4xx as retryable attacks forbidden calls.