Facilities removed a noisy interferer near a city council chamber. Before closing the ticket, what validation should the wireless team perform?
Select an answer to reveal the explanation.
Short Explanation
Unplugged isn't proven fixed until spectrum says the racket actually dropped — re-check duty cycle and noise floor, then close the ticket. Ethernet pings and building-wide AP resets aren't RF closure criteria.
Full Explanation
After facilities removes a noisy interferer near a city council chamber, the wireless team should re-measure spectrum metrics such as duty cycle and noise floor on the affected channels to confirm improvement before closing the ticket. Email confirmation that a device was unplugged is not RF validation. Expert closure criteria are measured spectrum and user-symptom clearance.
Closing immediately after the facilities email with no RF re-check risks leaving a second interferer or wrong device attribution undocumented. Only pinging the default gateway from Ethernet validates wired IP, not Wi-Fi RF cleanup. Factory-resetting every AP in the building as a required post-remediation step is destructive theater unrelated to proving the interferer is gone.
Exam caveat: municipal change tickets for RF interferers close on before/after spectrum, not on chat messages. Operational check: capture duty cycle and noise floor on the council-chamber channels after removal, compare to the pre-remediation baseline, confirm client stability in session, then close with attached screenshots. Require dual sign-off—wireless spectrum re-check plus facilities removal confirmation—before the council-chamber interference ticket reaches Closed.