You configure an Aruba CX6200 switch to meet your customer's requirement. you want to save all your settings and make sure that your configuration stays during a reboot of the switch. Which two…

Question

Options

• ASwitch # copy startup-config running-config
• BSwitch # save
• CSwitch # copy current-config sftp
• DSwitch # write memory
• ESwitch # copy running-config startup-config

• A
  7% (4)
• B
  4% (2)
• C
  2% (1)
• D
  88% (50)

Explanation

On Aruba CX switches, write memory (D) and copy running-config startup-config (E) are both equivalent commands that save the active (running) configuration to non-volatile flash memory (startup-config), ensuring it persists across reboots - they are simply two syntactic forms of the same operation.

Why the distractors are wrong:

• A (copy startup-config running-config) does the reverse - it overwrites your live config with the saved one, discarding unsaved changes.
• B (save) is not a valid ArubaOS-CX command; this syntax belongs to older or different vendor CLIs.
• C (copy current-config sftp) exports the config to a remote SFTP server - useful for backups, but it does not save to local flash.

Memory tip: Think of it as "running = RAM, startup = flash." You always want to copy from running to startup to lock in your changes - so any command that moves data in that direction (D or E) is your save command.

No community discussion yet for this question.