A municipal change-ticket worker receives HTTP 422 Unprocessable Entity from a Cisco configuration API. How should the consumer map that result?
Select an answer to reveal the explanation.
Short Explanation
When the building inspector stamps “rejected,” the permit desk does not file it as “approved.” Map a 422 into a known app outcome—reject the job, mark failed, notify—rather than fake success or leave only a raw stack.
Full Explanation
Professional consumers convert unrecoverable HTTP failures into outcomes the application already understands: reject the job, mark the item failed, or notify an operator. That mapping preserves honest state. Pretending the write succeeded or exposing only an unstructured stack as the contract leaves automation and humans without a controlled path forward.