Your customer’s network experiencing a severe broadcast storm, which you suspect is caused by a loop somewhere at the network edge. You start by disconnecting all the switch downlinks from the aggregation switch, checking CPU utilization, and then reconnecting the downlinks one at a time. Which troubleshooting methodology does this exemplify?
Select an option, then click Submit answer.
Reference / correct answer:
Most accepted answer: D. Divide and conquer
Community votes: A=1, B=1, D=1
Selected Answer: D Could also be argued as Divide and Conquer approach. Given it specifies you start with dicconnecting downstream of the Aggregate Switch, I.e. the middle of the LAN: Divide and conquer is a powerful, systematic troubleshooting method where you isolate faults by testing the middle of a system. By checking if the problem exists before or after the midpoint, you eliminate half the potential causes with every step, rapidly pinpointing the root cause. upvoted 1 times
Selected Answer: A Answer feels like A to me - but specifically the Bottom-Up Approach per below: This method starts at the lowest level of a system (the Physical Layer, such as cables, power, and physical hardware) and systematically moves upward. •How it works: You first verify the most basic elements—checking if cables are plugged in, lights are blinking, and servers have power. Once a layer is confirmed to be working, you test the next layer up until the issue is isolated. •Best used for: Hardware failures, complete network outages, or when troubleshooting a localized physical environment upvoted 1 times
Selected Answer: B I checked the official docs on this topic, and B is the correct implementation. upvoted 1 times