A bad ACL push on a city wireless controller blocks all EAP authentication for staff. How does configuration management help most in recovery?
Select an answer to reveal the explanation.
Short Explanation
Bad ACL, no EAP—hit the undo button that config management gave you. Roll back to the last good config and breathe. Factory-resetting the whole city is not a surgical recovery.
Full Explanation
Configuration management is essential in municipal WLAN operations for quickly recovering from misconfigurations such as a bad ACL push that blocks all EAP authentication for staff. The most effective recovery method is to roll back to the last known-good configuration saved by configuration management tools. This restores proper EAP authentication settings swiftly, minimizing downtime and user impact. Rebuilding every access point from factory defaults without leveraging saved configurations is inefficient and increases recovery time, as it requires manual reconfiguration and risks introducing new errors. Leaving the faulty ACL in place and issuing a new pre-shared key (PSK) bypasses the root cause, resulting in continued authentication failures and potential security gaps. Waiting several days for a full redesign delays restoration unnecessarily and ignores the immediate need to restore secure access. A key caveat is that configuration backups must be current and verified to ensure rollback effectiveness. Operationally, municipal WLAN teams should maintain automated configuration backups and test rollback procedures regularly to enable rapid recovery from configuration errors affecting critical authentication mechanisms.