Branch stores at a retailer lose the inventory application, and every path trace from those stores stops responding at the same hop. What should the analyst investigate?
Select an answer to reveal the explanation.
Short Explanation
If every delivery van stalls at the same intersection, you inspect that intersection. You investigate the hop where every trace stops responding, because the inventory application fails there too. A register browser, a DNS-only story, and a wireless ticket at each store don't explain one shared silent hop.
Full Explanation
Every branch trace stops responding at the same hop, and the inventory application fails along with that trace, so the investigation is that hop. A hop that is silent from every store is shared path evidence, not a separate fault inside each register. The browser on the register would explain a page-rendering fault when the path still completed, and these traces do not get past that hop. DNS only would be a name that fails before a path is underway, and a trace that reaches one hop has already moved past name lookup. A wireless ticket for each sales floor would be a different radio at each store, which does not produce the same silent hop from every branch. The register browser, the branch resolver, and the sales-floor radio do not line up across every store at one hop. Exam caveat: a shared hop where the traces die and the application fails is a path finding, and a per-store browser, DNS, or wireless story would look different at each branch. Operational check: compare traces from several branches and confirm they go silent at the same hop when the inventory application fails.