A city’s network team ships a portal that enables guest SSIDs through a wireless controller API. When an enable fails at 09:14, support must match the same failure on the portal error screen, the portal back-end log, and the outbound controller request log. Which design choice best enables that cross-hop match?
Select an answer to reveal the explanation.
Short Explanation
Picture a baggage tag that stays on the suitcase from curb to carousel—every hop uses the same ID. A correlation or request identifier does the same for your portal UI, back-end, and controller call. When the ticket cites 09:14, that one ID stitches the three views together.
Full Explanation
Distributed municipal integrations fail across hops; timestamps alone are brittle when clocks drift. A correlation (trace) ID designed into the request path lets operators join the UI error, application log, and outbound controller log without guessing. Product-specific SIEM rule names or logging only the last status do not replace that shared identifier as a first-class design artifact.