N10-009 Question 201
Single answerConfiguration management: Production configuration, Backup configuration, Baseline/golden configurationA network administrator is preparing to replace a failed access switch at a remote branch office. The original switch was configured with the company's standard VLANs, trunk settings, management IP scheme, SSH settings, and port security policies. The administrator wants the replacement to be deployed quickly while minimizing configuration drift from company standards. Which action is the BEST way to accomplish this?
- A
Restore the most recent backup of the failed switch's running configuration to the new switch and verify hardware-specific settings before putting it into production
- B
Apply the current baseline/golden configuration template to the new switch without reviewing site-specific settings
- C
Use the new switch's factory default configuration, then allow users to report connectivity issues so settings can be adjusted as needed
- D
Copy only the production VLAN database from another branch switch because VLAN information is sufficient for most access-layer deployments
Show answer and explanation
Correct answer: A
Explanation
The best answer is to restore the most recent backup of the failed switch's production configuration, because this most accurately returns the branch to its previous operational state with minimal downtime. In configuration management, a production configuration is the active configuration currently used by a device in the live environment. A backup configuration is a saved copy used for recovery after failure or misconfiguration. A baseline or golden configuration is the organization's approved standard template used to ensure consistency and compliance across deployments. Best practice is to maintain current configuration backups, use golden configurations to define standards, and validate any restored configuration against hardware differences before moving the device into production. Vendor documentation from major switch manufacturers commonly recommends backing up startup/running configurations regularly and reviewing restored configurations when replacing hardware, especially if model, software version, or interface layout differs.
- A. Correct.
Correct. Restoring the most recent backup configuration from the failed production switch is the best choice when replacing a like-for-like device at a specific site. It preserves the production configuration actually in use, including local interface assignments, management addressing, trunk settings, and security controls. The administrator should still verify hardware-specific items such as interface numbering, licensing differences, stacking members, or model-dependent commands before deployment. This approach is faster than rebuilding from scratch and reduces the risk of missing site-specific settings.
- B. Incorrect.
Incorrect. A baseline or golden configuration is intended as a standardized starting point for compliant deployments, not necessarily a complete replacement for a site's production configuration. Using it without reviewing site-specific requirements could omit branch-specific management IP addresses, uplink port assignments, voice VLANs, or local security policies. A golden configuration is useful for standardization, but in a replacement scenario, the backed-up production configuration is usually more appropriate.
- C. Incorrect.
Incorrect. Deploying a switch with factory defaults and troubleshooting reactively is poor operational practice. It increases downtime, introduces inconsistent settings, and can leave management access and security features unconfigured. This option reflects a common misconception that access switches can be safely configured after users begin reporting problems, but production devices should be restored in a controlled manner.
- D. Incorrect.
Incorrect. VLAN information alone is not enough to restore an access switch to service. The switch also needs interface mode settings, trunk allowed VLANs, management configuration, remote access settings, STP-related settings, port security, and possibly QoS or authentication settings. Copying only VLAN data from another branch also risks introducing incorrect site-specific values.