A city worker process calls a silent Firepower FDM controller and waits forever, pinning the worker while other municipal jobs starve. What should the REST consumer set to avoid that hang?
Select an answer to reveal the explanation.
Short Explanation
Waiting forever on a quiet phone line ties up the clerk and the whole counter. A finite connect/read deadline turns silence into a timeout you can retry or fail cleanly.
Full Explanation
Robust REST consumers (DEVCOR 2.1) bound outbound calls with connect and read deadlines so a silent controller cannot pin a worker forever. Infinite waits starve sibling jobs. Load-balancer HA design and protocol-version myths are not substitutes for client-side request timeouts.