A GET of UCS inventory for the city's data-center audit dies on a read timeout. Which consumer behavior is the robust next step for that idempotent read?
Select an answer to reveal the explanation.
Short Explanation
A timed-out inventory GET is like asking the clerk again after they catch their breath—not shouting the question fifty times at once. Delayed retry fits a safe, idempotent read.
Full Explanation
Task 2.1 expects robust handling of timeouts on safe, idempotent reads: retry after a delay rather than never retrying or spinning tightly. Immediate storms amplify load. Changing the verb to a non-idempotent POST is the wrong recovery and risks duplicate creates.