A permits portal waits for controller A, then controller B, then a local store before painting the page, and the sum of those round-trips blows the latency budget. Which design change best cuts that latency?
Select an answer to reveal the explanation.
Short Explanation
Three bus transfers in a row add up even if each ride is short. Run independent controller hops in parallel or show a fresh-enough cache for the slow one. “Make the WAN faster” alone is not a design evaluation of the latency budget.
Full Explanation
Latency accumulates when a page waits for controller A, then B, then a local store in series. Parallelizing independent hops or serving a recent cache of the slow one is a design evaluation of the latency budget. The primary answer is not HTTP cache-header mechanics (a later API topic) or simply buying a faster WAN.