From which device should you start PerfStack analysis when a hub site is experiencing slow performance?

• A. From the affected hub site's edge router
• B. From the hub site's core switch
• C. From the remote office router
• D. From the data center firewall

Answer: (A)

Starting PerfStack at the hub site’s edge router puts you at the first point where traffic from the WAN enters the hub. If the hub is slow, the bottleneck is most often at this border—high WAN latency, interface queueing, dropped packets, or CPU issues on the device that handles all incoming and outgoing traffic. By beginning with the edge router, you quickly see whether the problem originates at the border or if border performance is healthy and the issue lies deeper inside the hub. Once you confirm the edge router’s status, you can add the hub’s core switch, the remote office router, and the data center firewall to the same PerfStack view to correlate metrics over the same time window and trace where delays accumulate. Starting at downstream devices like the core switch or firewall can miss border symptoms, and starting at remote sites can mislead you about where traffic is actually stalling.