You recently made a configuration change on a switch, and shortly afterward, you noticed a...

Comprehensive Detailed Explanation:

When a recent configuration change causes a spike in CPU utilization that negatively impacts users, the fastest way to restore normal operation is to revert the change. This rollback immediately removes the offending configuration, potentially stabilizing the CPU and restoring service.

Rebooting the switch (Option A) is disruptive and takes more time.

Disabling debug logging (Option C) may help if debug is causing high CPU, but it doesn't undo config changes.

Pausing NAE monitoring (Option D) only suspends monitoring and doesn’t address the root cause.

Hence, reverting the recent config change is the best immediate action.