What must be verified about router configurations to meet 1.2.2?

• A. Router configurations are archived on a separate server.
• B. Router configurations should be archived and not changed.
• C. Router configurations must be synchronized so the running (active) config matches the startup config.
• D. Router configurations require no synchronization.

Answer: (C)

Maintaining synchronized router configurations is about configuration management and ensuring a device’s active settings match the approved baseline. The running (active) configuration is what the router uses in real time, while the startup (or startup-config) is the saved version that should be loaded on boot. If these two differ, changes you expect to be in effect may not persist after a reboot, or an unintended configuration could be applied, creating gaps in security and network behavior. Verifying synchronization ensures the live policy on the router is always the same as the documented, intended configuration, which supports consistent enforcement of security controls and easier auditing.

Archiving configurations on a separate server helps with backups but does not guarantee that the device’s current running configuration equals the saved startup configuration, so it doesn’t by itself ensure consistency. Keeping a configuration that is archived and not changed would prevent legitimate updates and undermine security, since configurations must evolve with risks and requirements. No synchronization allows drift between what’s active and what’s documented, explicitly undermining policy enforcement and change control.