Which two actions would you perform when you are in the operational mode of the...

The Junos Command Line Interface (CLI) is strictly partitioned into operational and configuration modes to maintain a clear boundary between monitoring and administrative changes. Operational mode, identified by the > prompt, is designed for executing commands that monitor device status, troubleshoot network connectivity, and manage the physical system state. One typical administrative task performed here is clearing log files (using the clear log command) to free up storage space or reset diagnostic data during troubleshooting.

Additionally, high-level system requests that do not alter the persistent configuration database, such as rebooting the hardware, are executed in operational mode. The request system reboot command allows the administrator to gracefully restart the device after a software update or as part of a maintenance cycle. In contrast, actions such as configuring routing protocols or committing changes require transitioning to configuration mode (the # prompt). Committing a configuration is the specific act of moving changes from the candidate database to the active database, which is a logic-altering event strictly reserved for configuration mode. Therefore, operational mode remains the dedicated environment for real-time observation and system-level requests that ensure the device operates correctly within its existing parameters. Reference: User Interfaces, CLI Modes, Operational Mode Commands.

==========