An airport authority must enable platform debugs on a busy Catalyst during an intermittent guest-Wi-Fi incident without hammering production CPU. Which practice best keeps troubleshooting safe?
Select an answer to reveal the explanation.
Short Explanation
Unfiltered debugs on a busy airport switch are like opening every PA speaker at once—ops drown and the platform suffers. Conditional debugs are the selective mic: only the matching passenger (flow/interface) gets logged so CPU stays healthy.
Full Explanation
Conditional debugging (including platform condition filters on many Catalyst/IOS XE platforms) scopes debug output to specific interfaces, MAC/IP matches, or other criteria, reducing CPU and log volume versus debug all. Production civic networks must treat debugs as invasive: leave CEF intact, avoid broadcast syslog storms, and remove conditions when finished. The operational safety lesson is scope first, then debug—especially on platforms serving passengers and airlines.