Before a bank changes policy tags on the production Catalyst 9800, the engineer wants a way back to today's configuration if the change is wrong. Which maintenance action provides that?
Select an answer to reveal the explanation.
Short Explanation
You copy the map before you redraw the roads. A configuration backup is the way back to today's controller if the new policy tags misbehave. Reloading access points does not put the old tags in your pocket.
Full Explanation
A configuration backup stores the controller's current configuration so it can be restored if a policy-tag change breaks client access. Taking that backup before the change is the maintenance action that meets the requirement. The tags live in the controller configuration, so the backup has to include that configuration, not a radio reboot. Reloading access points makes them rejoin and download whatever tags the controller has now. It does not reconstruct deleted tags from DHCP, and DHCP discovery does not carry policy tags. Clearing the country code disables radios. It does not freeze the old configuration in memory, and it adds an outage on top of the change. A controller is not placed in sniffer mode. Sniffer mode is an access-point mode for captures, and it does not preserve tags or give you a restore point. Exam caveat: a backup you cannot retrieve is not a backout. Know where the file is, and confirm it was taken after the last good change and before this one. Operational check: restore the backup on a lab controller or compare it with the running configuration and confirm the current policy tags are present in the file before you edit production.