Which configuration is loaded when a device boots and stored in non-volatile memory?

Which configuration is loaded when a device boots and stored in non-volatile memory?

• A. Running Config
• B. Baseline
• C. Startup Config
• D. Configuration Backup

Answer: (C)

When a device starts up, it reads a stored configuration from non-volatile memory so it can begin with a known, persistent setup. The file kept in non-volatile memory for this purpose is the startup configuration. On boot, the device pulls startup-config from non-volatile memory, loads it into memory, and uses it as the running configuration. This is why startup-config is the best answer: it represents the settings saved to survive reboots. The running configuration, by contrast, sits in RAM as the active, editable state while the device is running and would be lost if the device reboots unless it’s saved back to startup-config. A baseline isn’t a standard term for what’s loaded at boot, and a configuration backup is simply a saved copy, not the file the device automatically loads during startup.

When a device starts up, it reads a stored configuration from non-volatile memory so it can begin with a known, persistent setup. The file kept in non-volatile memory for this purpose is the startup configuration. On boot, the device pulls startup-config from non-volatile memory, loads it into memory, and uses it as the running configuration. This is why startup-config is the best answer: it represents the settings saved to survive reboots. The running configuration, by contrast, sits in RAM as the active, editable state while the device is running and would be lost if the device reboots unless it’s saved back to startup-config. A baseline isn’t a standard term for what’s loaded at boot, and a configuration backup is simply a saved copy, not the file the device automatically loads during startup.