After N consecutive timeouts to the same FDM host, the city automation keeps issuing immediate new attempts and burning its timeout budget. What robust timeout handling should it apply next?
Select an answer to reveal the explanation.
Short Explanation
If the same door never opens, stop ringing it every second. Cool down, fail fast for a bit, then probe once—saving the timeout budget for when the host might actually answer.
Full Explanation
After a streak of timeouts, continuing immediate attempts wastes budget and piles errors. A short cool-down with fail-fast behavior and a later probe is robust 2.1 timeout handling. AppDynamics instrumentation and geographic HA placement are different concerns and not substitutes for this client control flow.