Which two methods are supported by the Junos OS to automatically archive your configuration upon commit? (Choose two.)

In Junos OS, two methods are commonly used to automatically archive the configuration upon commit: SCP (Secure Copy Protocol) and FTP (File Transfer Protocol). These methods facilitate the secure transfer of configuration files to a designated remote server for backup purposes.

SCP is particularly important because it provides a secure way to transfer files over the network using SSH (Secure Shell) for encryption, ensuring that sensitive configuration data is protected during transfer. This method is widely preferred for its security features.

FTP, on the other hand, is a more traditional method for file transfer but is less secure compared to SCP as it does not encrypt the data being transferred. However, it is still relevant in contexts where security is not a primary concern or where legacy systems are in use.

In contrast, HTTP and Telnet are not suitable for this purpose. HTTP is primarily used for web traffic and does not support the necessary file transfer functionalities that SCP and FTP provide for configuration backups. Telnet is an insecure protocol used for command-line access, which lacks the encryption features needed for safely transmitting sensitive configuration data.

Therefore, understanding these supported methods for configuration archiving helps network professionals ensure that their network configurations can be safely backed up and restored as needed.