The municipal Intersight consumer receives HTTP 503 with a Retry-After header during a maintenance blip. Which 2.1 branch should the client take inside its retry budget?
Select an answer to reveal the explanation.
Short Explanation
503 with Retry-After is 'the counter is closed for a short cleanup—come back then.' Wait and retry inside the budget. It is not a forever locked door like a hard permission deny.
Full Explanation
HTTP 503 plus Retry-After signals temporary unavailability and is a recoverable wait-and-retry path under 2.1. Treating it as 403-style permission failure or aborting every 5xx without waiting skips the robust recoverable branch. Permanent 4xx handling belongs to 2.2, not this case.