nerdexam
Cisco

300-370 · Question #14

An engineer has received an alarm on a wireless LAN controller and is unsure of its meaning. The engineer attempted to ping the wireless LAN controller interfaces. Which troubleshooting methodology…

The correct answer is E. divide and conquer. An engineer facing an unknown wireless LAN controller alarm and attempting to ping WLC interfaces is employing the 'divide and conquer' troubleshooting methodology. This approach involves systematically narrowing down the problem area by testing components.

WLAN Troubleshooting Methods

Question

An engineer has received an alarm on a wireless LAN controller and is unsure of its meaning. The engineer attempted to ping the wireless LAN controller interfaces. Which troubleshooting methodology does this action demonstrate?

Options

  • Abottom-up
  • Bfollow the path
  • Cshoot from the hip
  • Dtop-down
  • Edivide and conquer

How the community answered

(40 responses)
  • C
    5% (2)
  • D
    3% (1)
  • E
    93% (37)

Why each option

An engineer facing an unknown wireless LAN controller alarm and attempting to ping WLC interfaces is employing the 'divide and conquer' troubleshooting methodology. This approach involves systematically narrowing down the problem area by testing components.

Abottom-up

Bottom-up troubleshooting starts from the physical layer (Layer 1) and moves upward, meticulously verifying each layer; while pinging is a lower-layer test, the context suggests a broader strategy to localize a fault, not strictly a layer-by-layer progression from the very bottom.

Bfollow the path

'Follow the path' typically refers to tracing the exact network traffic flow from source to destination, which is more specific than simply testing reachability to interfaces.

Cshoot from the hip

'Shoot from the hip' describes an impulsive or unmethodical approach to troubleshooting, which is contrary to the systematic testing involved in pinging interfaces to gather information.

Dtop-down

Top-down troubleshooting starts from the application layer (Layer 7) and works downwards; pinging WLC interfaces is a Layer 3 (network layer) test, so it is not a top-down approach.

Edivide and conquerCorrect

The 'divide and conquer' troubleshooting methodology involves breaking a complex problem into smaller, testable segments to isolate the fault. By pinging the WLC interfaces, the engineer is testing basic network connectivity to determine if the issue is a connectivity problem or internal to the controller, thereby dividing the potential problem space.

Concept tested: Troubleshooting methodologies - Divide and Conquer

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/netmgmt/configuration/15-mt/nm-15-mt-book/nm-config-trouble.html

Topics

#Troubleshooting methodologies#Divide and conquer#Network alarms

Community Discussion

No community discussion yet for this question.

Full 300-370 Practice