HTTPS management to a parks AP is unreachable after a bad VLAN change, but the AP still has power. What should the technician bring to regain local management?
Select an answer to reveal the explanation.
Short Explanation
When the IP door jams, use the serial hatch. A console adapter gets you back into the CLI without needing the broken VLAN path. It beats panic-resetting and losing the whole config.
Full Explanation
When HTTPS management to a parks AP is unreachable after a bad VLAN change but the AP still has power, the technician should bring a console or serial adapter and cable to access the AP CLI out-of-band. Serial management does not depend on the broken IP/VLAN path and allows correction of addressing or VLAN settings without an immediate factory reset. Out-of-band console recovery is a core municipal field skill for autonomous and many controller-based APs.
A wireless packet injector rewriting config over the air without credentials is not an approved recovery method. A second cloud controller license unrelated to this autonomous AP does not restore local management. Factory reset is not the only allowed recovery option and unnecessarily destroys configuration when console access can fix the VLAN mistake.
Exam caveat: when IP management fails but power remains, think console/serial before reset. Operational check: connect serial, authenticate locally, correct the management VLAN/IP settings, restore HTTPS reachability on the proper VLAN, and save configuration before disconnecting from the parks AP. Carry a known-good serial adapter in the parks go-bag; VLAN mistakes are common enough that out-of-band access saves hours.