A library Wi-Fi automation job sets a 3-second timeout but retries a down DNA Center host without any attempt limit, hanging for many minutes. What belongs in robust timeout handling?
Select an answer to reveal the explanation.
Short Explanation
A short timeout with infinite loops is still an all-day hang. Cap the attempts or the total budget, then take the unrecoverable path instead of another spin.
Full Explanation
Robust 2.1 handling includes a finite retry budget so a down controller cannot turn a brief timeout into a multi-minute hang. After the budget is exhausted, control flow moves to the unrecoverable branch (2.2), not another unbounded loop. Hiding failures as success or removing timeouts worsens the outage.