Fifty Catalyst controllers need the same WLAN change. An engineer plans to paste it into each one. Catalyst Center already manages those controllers. Where should the change be made?
Select an answer to reveal the explanation.
Short Explanation
Fifty hand edits are fifty chances to miss one. You already have Catalyst Center managing those controllers. Make the change there once, because a beacon does not replicate a WLAN to the other forty-nine.
Full Explanation
Catalyst Center is the management product for a fleet of controllers it already owns. The same WLAN change belongs there, applied once, instead of a paste into each of fifty controllers that will drift the next time someone misses one. A guest portal does not push WLAN configuration to controllers. An RF profile on one controller sets radios for the access points that use it. It does not copy itself to forty-nine other controllers. One access point's beacon does not update the WLAN on every controller. Fifty controllers need the same WLAN change. Hand-editing each one drifts. Catalyst Center is the workflow that already manages them. Check one live client after the change and leave the rest of the floor alone until that client matches the result you expected. Read the live counters after you retest. Exam caveat: a controller that is not in that Catalyst Center inventory will not receive the change. Check the inventory before you assume all fifty are covered. Operational check: apply the change to a lab controller from Catalyst Center and confirm the WLAN matches before you include the rest.