A city’s asset-tagging service POSTs a new switch hostname to a Cisco inventory API and receives HTTP 409 Conflict because that name already exists. How should the consumer handle the response?
Select an answer to reveal the explanation.
Short Explanation
Think of a reserved parking spot that already has a car in it—you do not keep circling hoping the space magically empties. A 409 means the server refused the write because state already conflicts, so the app must read what is there and choose merge or abort.
Full Explanation
HTTP 409 Conflict signals that the request cannot be completed given the current resource state, such as a duplicate name or a stale version. Robust REST consumers treat that as a permanent-for-this-attempt conflict path, not as retryable unavailability like 503. The correct control flow is to fetch the current representation, reconcile or abort, and surface the outcome—not to spin retries that will keep failing.