Courseiva

CCNA Operational Monitoring and Maintenance Questions

54 questions · Operational Monitoring and Maintenance · All types, answers revealed

1
MCQeasy

Refer to the exhibit. Which interface has a physical layer connectivity problem?

A.ge-0/0/2
B.ge-0/0/0
C.ge-0/0/3
D.ge-0/0/1
AnswerD

ge-0/0/1 is administratively up (configuration enables the interface) but the link is down, meaning the physical layer is not establishing connectivity. This mismatch—admin up, link down—points to a Layer 1 problem such as a disconnected cable, faulty optics, or an unpowered peer. Unlike an administratively down interface, this is not expected; further troubleshooting like checking the SFP and cable is needed.

Why this answer

Interface ge-0/0/1 shows 'Physical link is Down' in the output, which directly indicates a physical layer connectivity problem. The 'Device present' field is also 'No', confirming that no transceiver or cable is detected, which is a Layer 1 issue.

Exam trap

The trap here is that candidates may focus on the 'Admin' status (up/down) rather than the 'Physical link' status, mistakenly assuming an administratively down interface is a physical layer problem, when in fact the physical layer issue is indicated by the link state being down regardless of administrative configuration.

How to eliminate wrong answers

Option A is wrong because ge-0/0/2 shows 'Physical link is Up' and 'Device present' is 'Yes', indicating no physical layer problem. Option B is wrong because ge-0/0/0 shows 'Physical link is Up' and 'Device present' is 'Yes', so the physical layer is functioning correctly. Option C is wrong because ge-0/0/3 shows 'Physical link is Up' and 'Device present' is 'Yes', meaning there is no physical layer connectivity issue.

2
MCQhard

A network operator needs to upgrade the Junos OS on the backup RE (re1) of a dual-RE system. Which procedure ensures that only the backup RE is upgraded and rebooted without affecting the forwarding plane?

A.Use 'request system software add <image> re1' and then 'request system reboot re1'
B.Use 'request system software add <image> both' and then 'request system reboot both'
C.Use 'request system software add <image> re0' and then 'request system reboot re0'
D.Copy the image to both REs and reboot the backup RE with 'request system reboot slice 1'
AnswerA

Targeting re1 with the 're1' keyword ensures the image is installed only on the backup Routing Engine, leaving the active primary RE untouched. Rebooting re1 restarts only that RE; the primary continues handling forwarding and control traffic, so there is no service interruption. After re1 returns online as standby, it is ready to assume primary role in a later switchover, which is the correct maintenance procedure.

Why this answer

The 'request system software add <image> re1' command installs the Junos OS image only on the backup Routing Engine (RE1), and the subsequent 'request system reboot re1' reboots only that RE. In a dual-RE system, this procedure isolates the upgrade to the backup RE, ensuring the forwarding plane remains active on the primary RE (RE0) and no traffic disruption occurs.

Exam trap

The trap here is that candidates may confuse the 'both' option with a safe upgrade method, not realizing it reboots both REs simultaneously and disrupts traffic, or they may incorrectly assume that copying the image manually and using a non-existent 'slice' command is a valid procedure.

How to eliminate wrong answers

Option B is wrong because 'request system software add <image> both' and 'request system reboot both' upgrade and reboot both REs simultaneously, which would disrupt the forwarding plane by causing a full system outage. Option C is wrong because 'request system software add <image> re0' and 'request system reboot re0' target the primary RE, which would interrupt the forwarding plane and potentially cause a traffic loss. Option D is wrong because 'request system reboot slice 1' is not a valid Junos command for rebooting a specific RE; the correct syntax uses 're0' or 're1' to specify the Routing Engine, and copying the image to both REs without using the proper 'request system software add' command does not ensure a controlled upgrade.

3
MCQeasy

A network administrator is troubleshooting high latency on a link. Which command provides real-time interface statistics?

A.show interfaces extensive
B.monitor interface traffic
C.show interfaces terse
D.show log messages
AnswerB

This is the correct choice because it provides a continuously updating, real-time display of bandwidth utilization (in bps) and packet counts (in pps) for the selected interface, refreshing at a configurable interval (typically every second). High latency is often caused by transient congestion or traffic spikes, which only a live view can reveal effectively. The command samples the interface's current rate and presents it in a dynamic table, enabling the administrator to correlate latency symptoms with immediate traffic patterns.

Why this answer

The 'monitor interface traffic' command provides real-time, continuously updating statistics for interface traffic, including packet counts and error rates, which is essential for diagnosing high latency as it allows the administrator to observe changes in real time. Unlike static commands, this dynamic output refreshes automatically, making it ideal for troubleshooting transient issues.

Exam trap

The trap here is that candidates often choose 'show interfaces extensive' because it provides detailed statistics, but they overlook that it is a static snapshot rather than a real-time monitoring tool, which is explicitly required by the question.

How to eliminate wrong answers

Option A is wrong because 'show interfaces extensive' displays detailed but static interface information, including counters and errors, but does not provide real-time updates; it requires manual re-entry to see changes. Option C is wrong because 'show interfaces terse' shows a brief, one-line summary of interface status and configuration, lacking traffic statistics or real-time monitoring capability. Option D is wrong because 'show log messages' displays system log messages, which are event-driven and not focused on real-time interface statistics; it may show link flaps or errors but not continuous traffic data.

4
MCQeasy

A network administrator wants to see the current CPU load average over the last 1, 5, and 15 minutes on a Juniper device. Which command displays this information?

A.show chassis routing-engine
B.show system uptime
C.show system processes
D.show system statistics
AnswerB

The `show system uptime` command is the correct way to view CPU load averages on Junos because its output begins with a `Load averages:` line that shows the 1-, 5-, and 15-minute averages. These three numbers indicate how many threads are runnable or waiting for I/O, providing a historical trend that a simple percentage cannot capture. The command also shows system uptime, time, and active users, but the load average is the key field for this question.

Why this answer

The 'show system uptime' command displays the system's uptime along with the load averages for the last 1, 5, and 15 minutes. This is the standard Junos command for viewing CPU load averages, which are calculated based on the number of processes in the run queue over those time intervals.

Exam trap

The trap here is that candidates often confuse 'show chassis routing-engine' (which shows current CPU utilization) with the load average command, not realizing that load averages are a separate time-weighted metric displayed by 'show system uptime'.

How to eliminate wrong answers

Option A is wrong because 'show chassis routing-engine' displays the status and resource utilization of the Routing Engine (including CPU and memory), but it does not show the load average over 1, 5, and 15 minutes; it shows current CPU utilization percentage. Option C is wrong because 'show system processes' lists all running processes with their PID, memory, and CPU usage, but it does not aggregate the load average over time intervals. Option D is wrong because 'show system statistics' displays various system-wide counters and statistics (e.g., packet counts, memory usage), but it does not include CPU load averages.

5
MCQeasy

A network engineer notices that a device is not sending SNMP traps to the NMS. Which operational command should be used to verify SNMP configuration?

A.show system uptime
B.show route
C.show snmp
D.show interfaces terse
AnswerC

The 'show snmp' command is the correct diagnostic tool on Junos devices for verifying SNMP configuration and operation. It displays whether the SNMP agent is enabled, configured trap groups, target addresses, community strings, and various SNMP statistics. This command directly shows why a device might not send traps, such as missing trap-group definitions, incorrect targets, or an explicitly disabled SNMP service.

Why this answer

The 'show snmp' command in Junos displays the current SNMP configuration, including community strings, trap destinations, and enabled trap groups. Since the issue is that the device is not sending SNMP traps, this command allows the engineer to verify that trap destinations are correctly configured and that the appropriate trap groups are enabled. Other commands like 'show system uptime' or 'show route' do not provide any SNMP-specific configuration details.

Exam trap

The trap here is that candidates often confuse 'show snmp' with 'show snmp statistics' or 'show snmp mib walk', but the question specifically asks for verifying configuration, not statistics or MIB data, making 'show snmp' the correct operational command.

How to eliminate wrong answers

Option A is wrong because 'show system uptime' displays the system uptime and load averages, not SNMP configuration or trap settings. Option B is wrong because 'show route' displays the routing table and is used for verifying network reachability, not SNMP trap configuration. Option D is wrong because 'show interfaces terse' shows a summary of interface status and configuration, which is unrelated to SNMP trap settings.

6
MCQeasy

A Juniper device is running out of disk space on the /var partition. Which command can be used to check disk usage?

A.show system storage
B.show system disk-space
C.show system memory
D.show system resource
AnswerA

This is the correct command. It provides a detailed view of every mounted filesystem on the device, including the /var partition, with columns for total space, used space, available space, and mount points. The output is analogous to the UNIX 'df -k' utility, making it the standard operational command to diagnose disk-full conditions in Junos.

Why this answer

The correct command to check disk usage on a Juniper device is 'show system storage'. This command displays detailed information about disk partitions, including total, used, and available space, as well as the percentage of usage for each mounted filesystem, such as /var. It is the standard operational mode command for monitoring storage utilization in Junos OS.

Exam trap

The trap here is that candidates familiar with other operating systems might expect a command like 'show system disk-space' or confuse memory with storage, but Junos uses the specific phrase 'storage' for disk usage monitoring.

How to eliminate wrong answers

Option B is wrong because 'show system disk-space' is not a valid Junos command; the correct command uses 'storage' not 'disk-space'. Option C is wrong because 'show system memory' displays RAM and memory utilization, not disk storage. Option D is wrong because 'show system resource' shows system resource usage like CPU and memory, but does not provide disk partition or filesystem usage details.

7
MCQhard

Refer to the exhibit. Based on the log output, what is the most likely issue with interface ge-0/0/1?

A.Interface is experiencing flapping
B.Interface is up and stable
C.Interface is administratively down
D.Interface is configured incorrectly
AnswerA

The log output shows repeated interface state transitions between up and down within a short time window, which is the classic signature of interface flapping. Such behavior is typically caused by physical-layer issues, such as a faulty transceiver, damaged cable, or a remote peer that is itself unstable. An interface that is flapping never reaches a sustained operational state, so the up/down cycles evident in the log directly support this conclusion.

Why this answer

The log output shows repeated 'link UP' and 'link DOWN' events for interface ge-0/0/1 within a short time window, which is the classic symptom of interface flapping. Flapping typically occurs due to physical layer issues such as faulty cables, damaged transceivers, or marginal signal integrity, causing the interface to continuously transition between up and down states.

Exam trap

The trap here is that candidates may assume any interface issue is configuration-related (Option D) or that a single 'link UP' message means the interface is stable (Option B), but the repeated pattern of alternating UP/DOWN events is the definitive indicator of flapping.

How to eliminate wrong answers

Option B is wrong because the log clearly shows the interface is not stable; it is oscillating between up and down states, which contradicts the definition of a stable interface. Option C is wrong because an administratively down interface would show a 'administratively down' status in the log, not repeated link transitions; the interface is actively trying to come up. Option D is wrong because while configuration errors can cause operational issues, the specific pattern of rapid link state changes points to a physical or Layer 1 problem, not a configuration mistake like incorrect VLAN or IP settings.

8
MCQhard

An administrator observes that the router's CPU utilization is consistently high. Which command helps identify which process is consuming the most CPU?

A.show log messages
B.show system resource
C.show chassis routing-engine
D.show system processes extensive
AnswerD

This command displays detailed information about every running process, including its process ID, parent, and the amount of CPU and memory it is consuming. The "extensive" variant adds per-thread and per-process statistics, allowing an administrator to identify exactly which process is causing high CPU utilization. It is the equivalent of "top" on Unix and is the appropriate tool for this diagnostic.

Why this answer

'show system processes extensive', is correct because it displays detailed CPU utilization statistics for each running process on a Junos device, including the percentage of CPU time consumed. This allows the administrator to identify which specific process (e.g., routing protocol daemon, SNMP, or management process) is causing the high CPU load, enabling targeted troubleshooting.

Exam trap

The trap here is that candidates often confuse 'show chassis routing-engine' (which shows aggregate CPU load) with process-level CPU breakdown, leading them to choose option C, but only 'show system processes extensive' provides the per-process detail needed to pinpoint the culprit.

How to eliminate wrong answers

Option A is wrong because 'show log messages' displays system log entries (syslog messages) and does not provide real-time CPU utilization per process; it is used for reviewing events and errors, not for process-level CPU monitoring. Option B is wrong because 'show system resource' shows overall system resource usage (memory, CPU, and storage) but does not break down CPU usage by individual process; it gives a high-level summary, not per-process granularity. Option C is wrong because 'show chassis routing-engine' displays the status and resource utilization of the Routing Engine (RE), including CPU load average, but it does not list individual processes; it shows aggregate RE health, not process-specific CPU consumption.

9
MCQeasy

An engineer needs to check the current system uptime on a Juniper device running Junos OS. Which command should they use?

A.show system status
B.show system health
C.show system resources
D.show system uptime
AnswerD

The correct term for checking uptime on Junos is 'show system uptime'. This operational command presents the current time, how long the system has been running, and load average figures. It also shows the number of users logged in, making it the standard tool for verifying system availability in Junos troubleshooting and monitoring workflows.

Why this answer

The correct command to check current system uptime on a Juniper device running Junos OS is 'show system uptime'. This command displays the time since the system was last booted, as well as the current time and the time since the routing protocol process (rpd) started. It is the standard operational command for this specific metric.

Exam trap

The trap here is that candidates may confuse 'show system uptime' with similar-sounding commands from other vendors (like Cisco's 'show version' or 'show system status'), leading them to select a non-existent or incorrect Junos command.

How to eliminate wrong answers

Option A is wrong because 'show system status' is not a valid Junos command; the correct command for general system status information is 'show system information'. Option B is wrong because 'show system health' is not a valid Junos command; the correct command for hardware health monitoring is 'show chassis hardware' or 'show system health-monitor' (in newer releases). Option C is wrong because 'show system resources' displays CPU, memory, and filesystem utilization, not system uptime.

10
MCQmedium

An administrator wants to verify that BGP neighbors are established. Which command provides a summary of all BGP peer sessions?

A.show bgp neighbor
B.show bgp summary
C.show interfaces terse
D.show route protocol bgp
AnswerB

The 'show bgp summary' command is the standard tool for verifying BGP peer status at a glance. Its tabular output lists each neighbor's address, AS number, session state (e.g., Active, Idle, or Established), and uptime, along with the number of prefixes received and advertised. Because it condenses all peers into a single screen, an administrator can immediately confirm that each peer is in the Established state, which is exactly what this task requires.

Why this answer

The 'show bgp summary' command is correct because it provides a concise, one-line-per-peer overview of all BGP sessions, including the peer IP address, AS number, state (e.g., Established), and counters for prefixes received. This is the standard command in Junos for quickly verifying that all BGP neighbors are in the Established state without the detailed per-neighbor output.

Exam trap

The trap here is that candidates familiar with Cisco IOS might expect 'show ip bgp summary' but mistakenly choose 'show bgp neighbor' because they confuse the detailed neighbor output with a summary view, or they overlook that Junos uses 'show bgp summary' for the aggregated peer list.

How to eliminate wrong answers

Option A is wrong because 'show bgp neighbor' displays detailed per-neighbor information (including timers, capabilities, and NLRI details) for each BGP peer, not a summary table. Option C is wrong because 'show interfaces terse' lists interface status and configuration, not BGP peer session information. Option D is wrong because 'show route protocol bgp' displays the routing table entries learned via BGP, not the status of BGP peer sessions.

11
MCQmedium

After a configuration change, a router is not behaving as expected. The administrator wants to rollback to the previous configuration. Which command accomplishes this?

A.rollback 0
B.commit check
C.rollback 1
D.load override current
AnswerC

Rollback 1 is the automatic configuration snapshot saved at the commit immediately before the most recent one, i.e., the last known-good state prior to your change. Issuing `rollback 1` replaces the candidate configuration with that snapshot, and once you commit, the router reverts to its previous behavior. This is the standard way to undo the most recent commit in Junos because it precisely targets the prior committed configuration rather than a file or the current state.

Why this answer

The 'rollback 1' command reverts the active configuration to the most recent committed configuration (the one before the latest commit). In JUNOS, the rollback command uses a numeric index where 0 is the current active configuration, 1 is the previous committed configuration, and higher numbers go further back. This allows the administrator to undo an unwanted configuration change without manually editing the configuration.

Exam trap

The trap here is that candidates familiar with Cisco IOS might think 'rollback 0' undoes the last change, but in JUNOS, rollback 0 refers to the current active configuration, not the previous one.

How to eliminate wrong answers

Option A is wrong because 'rollback 0' reverts to the current active configuration, which is effectively a no-op and does not undo any changes. Option B is wrong because 'commit check' only validates the syntax and semantics of the candidate configuration without committing it; it does not roll back to a previous configuration. Option D is wrong because 'load override current' is not a valid JUNOS command; the correct command to replace the candidate configuration with the current active configuration is 'load override terminal' or 'load override <filename>', but this does not roll back to a previous committed configuration.

12
MCQeasy

You are managing a Juniper MX240 router at a small ISP. The router has been operating normally for months. This morning, a customer reports intermittent packet loss on their connection, which is served by interface ge-0/0/2. You SSH into the router and run 'show interfaces ge-0/0/2 extensive'. The output shows input errors increasing rapidly, including CRC errors and frame errors. The interface is up/up. You also notice that the interface statistics show a high number of carrier transitions. The cable connecting the router to the customer's CPE was recently replaced by the customer's technician. What is the most likely cause of the errors and the correct action to resolve the issue?

A.Clear the MAC address table on the router to fix possible MAC flapping issues.
B.Administer a 'shutdown' and 'no shutdown' on the interface to reset the line protocol.
C.Replace the cable with a known good one because CRC and frame errors indicate a physical layer problem such as a damaged cable or loose connector.
D.Change the interface speed and duplex settings to auto-negotiate because the errors are due to a mismatch between the router and CPE.
AnswerC

CRC and frame errors indicate that frames are receiving an invalid FCS, which is a classic symptom of a physical-layer issue such as a damaged cable, loose connector, or excessive signal attenuation. The problem appeared after a recent cable change, which strongly implicates the new cable or its seating. Replacing that cable with a known-good one is the correct first step because it directly tests the most likely failure point, and a clean interface afterward confirms the diagnosis.

Why this answer

CRC and frame errors increasing rapidly, combined with a high number of carrier transitions, are classic symptoms of a physical-layer issue. Since the cable was recently replaced by the customer's technician, the most likely cause is a faulty cable or a loose connector. Replacing the cable with a known good one directly addresses the physical layer problem, which is the root cause of these errors.

Exam trap

The trap here is that candidates may confuse CRC/frame errors with a speed/duplex mismatch (Option D) or think a simple interface reset (Option B) will fix the problem, when the rapid increase in carrier transitions and the recent cable replacement clearly indicate a physical cabling fault.

How to eliminate wrong answers

Option A is wrong because MAC address table clearing addresses MAC flapping, which is a Layer 2 issue unrelated to CRC/frame errors or carrier transitions. Option B is wrong because administratively resetting the interface (shutdown/no shutdown) would only temporarily clear counters and restart the line protocol, but it would not fix the underlying physical-layer problem causing the errors. Option D is wrong because while speed/duplex mismatch can cause errors, the presence of carrier transitions and the recent cable replacement strongly point to a physical cabling issue, not a negotiation mismatch; auto-negotiation is already the default on modern Juniper interfaces and would not resolve a faulty cable.

13
MCQeasy

To monitor interface traffic in real-time, which operational command is most appropriate?

A.show interface traffic
B.request system reboot
C.show log
D.monitor interface
AnswerD

"monitor interface" is the correct Junos operational command for real-time interface monitoring. It repeatedly samples the specified interface's counters — showing input/output packets per second, bytes per second, and error counts — and refreshes the output at a configurable interval using the "interval" option, making it ideal for watching live traffic patterns, congestion, or interface flaps.

Why this answer

The 'monitor interface' command in Junos provides real-time, continuous display of interface statistics and traffic counters, updating every second by default. This is the correct operational command for live traffic monitoring, as it refreshes the output dynamically without requiring manual re-entry.

Exam trap

The trap here is that candidates familiar with Cisco IOS may mistakenly expect a 'show interface traffic' command (similar to 'show interfaces' with counters) and overlook the Junos-specific 'monitor interface' command for real-time updates.

How to eliminate wrong answers

Option A is wrong because 'show interface traffic' is not a valid Junos command; the correct static display command is 'show interfaces traffic' which shows a snapshot, not real-time updates. Option B is wrong because 'request system reboot' is used to reboot the device, not to monitor traffic, and would disrupt operations. Option C is wrong because 'show log' displays system log messages from files like messages or interactive-commands, which are not designed for real-time interface traffic monitoring and lack live counter updates.

14
MCQhard

A network administrator is troubleshooting a routing issue and wants to view the routing table for a specific routing instance called 'VPN-A'. Which command should they use?

A.show routing-table VPN-A
B.show route table VPN-A
C.show route instance VPN-A
D.show routing instance VPN-A route
AnswerB

The 'show route table' command with the routing-instance name is the correct way to view all routes in that instance. In Junos, each routing instance has its own set of routing tables (e.g., VPN-A.inet.0), and specifying the instance name as the table argument displays all of its tables. This command shows the full routing table, including protocol preference, next-hop, and route flags.

Why this answer

The correct command to view the routing table for a specific routing instance in Junos is 'show route table VPN-A'. This command displays the routes associated with the routing instance named 'VPN-A', which is essential for troubleshooting routing issues within that instance. The 'show route' command is the standard way to view routing tables, and specifying the 'table' keyword followed by the instance name targets the correct routing table.

Exam trap

The trap here is that candidates familiar with Cisco IOS might expect 'show ip route vrf VPN-A' and incorrectly apply similar syntax like 'show routing-table VPN-A' or 'show route instance VPN-A', not realizing Junos uses 'show route table <instance-name>' for the same purpose.

How to eliminate wrong answers

Option A is wrong because 'show routing-table VPN-A' is not a valid Junos command; the correct syntax uses 'show route table' not 'show routing-table'. Option C is wrong because 'show route instance VPN-A' is not a valid command; 'show route instance' does not exist, and the correct command to view routing instance details is 'show routing instance VPN-A', which shows configuration and status but not the routing table. Option D is wrong because 'show routing instance VPN-A route' is syntactically incorrect; the proper command to view the routing table for an instance is 'show route table VPN-A', not a combination of 'routing instance' and 'route'.

15
Multi-Selecteasy

Which two commands can be used to display real-time interface information? (Choose two.)

Select 2 answers
A.monitor interface
B.monitor traffic
C.show log
D.request system reboot
E.show system storage
AnswersA, B

monitor interface is a Junos operational command that provides continuously updated, real-time statistics for a specified interface, including current input/output rates, packet counts, and error counters. It refreshes at a fixed interval, allowing you to observe dynamic changes in interface utilization and detect transient issues like CRC errors or drops that a one-time show command might miss. This makes it the first choice for live health checks of physical or logical interfaces.

Why this answer

Option A, `monitor interface`, is correct because it provides a real-time, continuously updating view of interface statistics such as traffic counters, errors, and link state on Juniper devices. Option B, `monitor traffic`, is correct because it captures and displays live packet-level traffic on an interface, showing real-time data as packets traverse the interface. Option C, `show log`, is incorrect because it displays stored log file contents rather than live interface information.

Option D, `request system reboot`, is incorrect because it reboots the device and does not display interface data. Option E, `show system storage`, is incorrect because it reports disk and filesystem usage, not real-time interface information.

Exam trap

The trap here is confusing static `show` commands (like `show interfaces`) with real-time `monitor` commands, or assuming that any command displaying data is real-time, when only `monitor` commands provide live, updating output.

16
MCQeasy

A network engineer needs to check the system's disk space usage. Which command should be used?

A.show system storage
B.show configuration
C.show version
D.show system uptime
AnswerA

The 'show system storage' operational command is the correct Junos CLI command for checking disk space usage. It displays each mounted file system (e.g., /var, /tmp, /config) with total, used, and available space in both kilobytes and percentage, along with mount points. This command is the standard way to monitor disk capacity on Junos devices, particularly for critical partitions like /var that can fill with logs or crash dumps.

Why this answer

The 'show system storage' command displays disk space usage on Junos devices, including total, used, and available space for each mounted filesystem. This is the correct command for monitoring storage utilization, as it directly reports on the /, /config, and /var partitions critical for system operation.

Exam trap

The trap here is that candidates might confuse 'show system storage' with 'show system uptime' or 'show version' because they all start with 'show system', but only 'show system storage' provides disk space information.

How to eliminate wrong answers

Option B is wrong because 'show configuration' displays the active configuration, not disk space usage. Option C is wrong because 'show version' shows software version and hardware model information, not storage details. Option D is wrong because 'show system uptime' displays how long the device has been running and load averages, not disk space.

17
MCQeasy

An administrator notices that the routing table is not updating as expected. Which command should be used to verify the routing table contents?

A.show log
B.show route
C.show system storage
D.show interfaces
AnswerB

show route: This is the correct command to display the routing table on Junos, showing all active routes, their next hops, and protocol attributes. It allows an administrator to verify if the routing table is updating correctly by checking for presence or absence of specific prefixes. Additionally, options like 'show route protocol ospf' or 'show route prefix' provide granular views for troubleshooting.

Why this answer

The 'show route' command displays the routing table, which contains all active routes learned via static configuration, direct interfaces, or dynamic routing protocols such as OSPF, IS-IS, BGP, and RIP. If the routing table is not updating as expected, this command allows the administrator to verify the current routes, their next hops, and protocol sources to identify missing or incorrect entries.

Exam trap

The trap here is that candidates may confuse 'show route' with 'show interfaces' or 'show log', thinking that interface status or log messages would directly reveal routing table updates, when in fact only 'show route' provides the definitive view of the routing table contents.

How to eliminate wrong answers

Option A is wrong because 'show log' displays system log messages (e.g., from syslog or traceoptions), not the routing table contents; it is used for troubleshooting events, not for viewing route entries. Option C is wrong because 'show system storage' reports disk usage and file system space, which is unrelated to routing table updates. Option D is wrong because 'show interfaces' displays interface status, statistics, and configuration, but does not show the routing table; it is used for verifying link-level connectivity, not route propagation.

18
MCQmedium

A network administrator is troubleshooting high CPU usage on a Juniper router. Which command helps identify which process is consuming the most CPU?

A.show log messages
B.show system memory
C.show system processes extensive
D.show interfaces
AnswerC

The `show system processes extensive` command is the correct diagnostic tool because it provides a detailed snapshot of every running process on the Junos device, including their IDs, CPU utilization percentages, and the cumulative time spent in user and system mode. The `extensive` keyword adds thread-level details and memory usage, enabling an administrator to pinpoint exactly which process is driving the high CPU load, such as rpd or mgd. This directly addresses the troubleshooting scenario.

Why this answer

The 'show system processes extensive' command displays detailed information about all running processes, including CPU utilization, memory usage, and process IDs. This allows the administrator to identify which process (e.g., routing protocol daemon, management daemon) is consuming the most CPU cycles, directly addressing the troubleshooting need.

Exam trap

The trap here is that candidates often confuse 'show system processes extensive' with 'show system memory' or 'show log messages', mistakenly thinking memory or log analysis will reveal CPU hogs, when only the process list provides per-process CPU metrics.

How to eliminate wrong answers

Option A is wrong because 'show log messages' displays system log entries (syslog), which may indicate errors or events but does not provide real-time per-process CPU usage. Option B is wrong because 'show system memory' reports memory utilization statistics, not CPU consumption by individual processes. Option D is wrong because 'show interfaces' shows interface status and traffic counters, which are unrelated to identifying CPU-intensive processes.

19
MCQeasy

An administrator is asked to check the system log files for any error messages related to interface failures. Which command would be most efficient?

A.monitor start messages | match "error"
B.show log file messages | match "error"
C.show log messages
D.show system syslog messages
AnswerC

show log messages — This is the correct operational command to display the contents of the default system log file /var/log/messages. It shows all messages stored in that file, providing the administrator with the historical log data needed. While it outputs everything without a match filter, it is the only valid command among the options that actually works for viewing existing log entries. Additional filtering could be applied with a pipe, e.g., 'show log messages | match error', but the base command is sufficient.

Why this answer

'show log messages' is the standard JUNOS command to display the contents of the /var/log/messages file. While it does not include a filter, it is the only valid command among the options that allows the administrator to view existing system log messages. The other options are either invalid commands (B and D) or used for real-time monitoring (A), which is not efficient for checking historical log files.

Exam trap

The trap here is that candidates may confuse 'monitor start messages' with 'show log messages', thinking the real-time monitor is more efficient for checking logs, but the question asks for checking existing log files, not monitoring live events.

How to eliminate wrong answers

Option A is wrong because 'monitor start messages' is a real-time monitoring command that continuously streams new log entries to the terminal, not a static search of existing log files; it would require the administrator to wait for errors to occur and does not efficiently check historical logs. Option C is wrong because 'show log messages' displays the entire contents of the messages log file without any filtering, which is inefficient for finding specific error messages related to interface failures, especially on a busy system with many log entries. Option D is wrong because 'show system syslog messages' is not a valid JUNOS command; the correct command to view syslog configuration is 'show configuration system syslog', but this does not display log file contents or error messages.

20
MCQmedium

You are troubleshooting an OSPF issue on a Juniper router. The router has a single interface ge-0/0/1 with IP 10.1.1.1/30 connected to a neighbor with IP 10.1.1.2/30. OSPF is configured area 0. The 'show ospf neighbor' command shows no neighbors. 'show interfaces ge-0/0/1 terse' shows the interface is up. 'show configuration protocols ospf' shows: area 0.0.0.0 { interface ge-0/0/1.0 { passive; } } What is the problem?

A.The OSPF interface is configured as passive
B.The hello timer is too slow
C.Authentication is missing
D.The interface is administratively down
AnswerA

Setting an OSPF interface to passive in Junos disables hello packet transmission entirely on that interface. Without hellos, the router cannot discover neighbors or form an adjacency, so the OSPF neighbor state remains Down. The interface stays administratively and protocol up, but OSPF treats it as a stub network, advertising the subnet while never establishing a neighbor relationship. This directly matches a terse output showing the interface up and no OSPF neighbors.

Why this answer

The 'passive' statement under the OSPF interface configuration prevents the router from sending or processing OSPF Hello packets on that interface. Without Hello packets, the router cannot discover neighbors or form adjacencies, which is why 'show ospf neighbor' returns no neighbors even though the interface is operationally up.

Exam trap

The trap here is that candidates often assume 'passive' only prevents the interface from sending routing updates (like in RIP or EIGRP), but in OSPF it blocks all Hello packets, preventing neighbor discovery entirely.

How to eliminate wrong answers

Option B is wrong because the hello timer being too slow would still allow neighbor discovery and adjacency formation, just with longer intervals; it would not result in zero neighbors. Option C is wrong because authentication is not configured in the given output, and its absence does not prevent neighbor discovery unless authentication is required on the neighbor side. Option D is wrong because 'show interfaces ge-0/0/1 terse' shows the interface is up, not administratively down.

21
MCQhard

Your company runs a Juniper MX480 router as the core gateway. The router has been experiencing intermittent connectivity issues with a remote site over a point-to-point OC3 link. Users report that the link goes down for a few seconds several times a day. You suspect that the issue might be related to physical layer errors or framing. You need to determine the cause and collect relevant data to present to the service provider. Which course of action should you take first?

A.Run 'monitor interface so-0/0/0' and observe for any CRC errors or alarms over a period of time.
B.Perform a loopback test on the interface using 'test interface so-0/0/0'.
C.Review the system syslog file using 'show log messages' and search for interface down messages.
D.Immediately replace the serial interface card to rule out hardware failure.
AnswerA

This command provides a continuous real-time view of interface statistics and alarms, allowing you to observe transient physical-layer errors such as CRC errors, framing errors, or loss of signal that might occur intermittently. By watching the output over time, you can correlate error bursts with specific conditions (e.g., nearby equipment, cable movement) without disrupting traffic. It directly confirms the health of the physical layer before moving to more invasive testing or hardware replacement.

Why this answer

'monitor interface so-0/0/0' provides real-time, continuous display of interface counters and alarms, allowing you to observe CRC errors, framing errors, or alarms (e.g., LOS, LOF) as they occur. This is the most direct way to capture transient physical-layer issues on a SONET/SDH OC3 link without disrupting service, making it the appropriate first step before escalating to the service provider.

Exam trap

The trap here is that candidates may choose the loopback test (Option B) because it is a classic troubleshooting tool, but they overlook that it is an intrusive, out-of-service test that should follow passive monitoring to avoid unnecessary downtime.

How to eliminate wrong answers

Option B is wrong because performing a loopback test ('test interface so-0/0/0') would disrupt live traffic and is typically used for out-of-service troubleshooting after initial data collection, not as a first step. Option C is wrong because reviewing the system syslog ('show log messages') may show interface down messages but lacks the granularity to capture brief, intermittent physical-layer errors like CRC or framing alarms that occur over seconds. Option D is wrong because immediately replacing the serial interface card is a premature and invasive action that should only be taken after diagnostic data (e.g., from monitoring or loopback tests) confirms a hardware fault.

22
Multi-Selectmedium

Which two commands can be used to monitor real-time interface statistics and errors on a Junos device?

Select 2 answers
A.show interfaces terse
B.show interfaces ge-0/0/0
C.show interfaces extensive ge-0/0/0 | refresh 1
D.monitor interface ge-0/0/0
E.monitor security log
AnswersC, D

The `| refresh 1` pipe re-runs the command every second, giving continuous real-time interface statistics and error counters for ge-0/0/0, which satisfies the monitoring requirement. The `extensive` keyword adds detailed error and counter data beyond the default summary output.

Why this answer

Option C, 'show interfaces extensive ge-0/0/0 | refresh 1', is correct because the 'extensive' keyword displays detailed statistics including error counters, and the '| refresh 1' pipe re-runs the command every second, giving real-time monitoring of a specific interface. Option D, 'monitor interface ge-0/0/0', is correct because the 'monitor interface' command is Junos's dedicated real-time interface statistics viewer, continuously updating counters such as packets, bytes, and errors for the named interface. Option A, 'show interfaces terse', only gives a one-time summary of interface status and addresses without error detail or refresh, so it is not real-time monitoring.

Option B, 'show interfaces ge-0/0/0', provides a single snapshot of standard statistics and does not refresh or emphasize error counters. Option E, 'monitor security log', streams security log messages rather than interface statistics and errors, so it does not meet the requirement.

Exam trap

The trap here is that candidates often confuse static 'show interfaces' commands (which provide a point-in-time snapshot) with real-time monitoring commands, leading them to select option B instead of the correct real-time options C and D.

23
MCQmedium

After a software upgrade, a router fails to boot with the new image. The engineer suspects the image is corrupted. What is the recommended method to recover?

A.Insert the rescue media and boot from it, then reinstall the image
B.Delete the current configuration and reboot
C.Reboot the router multiple times
D.Use the request system software add command with the force option
AnswerA

This is the standard recovery procedure for a corrupted or incomplete Junos image. The rescue media (e.g., a USB install drive) contains a minimal bootable environment that bypasses the damaged primary storage, allowing you to boot the router into a limited operational state. From there, you can reinstall the image onto internal media, overwriting the corrupt installation and restoring full functionality. This directly addresses the root cause—image corruption—rather than side effects like configuration or transient boot issues.

Why this answer

When a Junos OS image is corrupted and the router fails to boot, the recommended recovery method is to boot from rescue media (such as a USB flash drive or a pre-configured rescue partition) and then reinstall the correct image. This bypasses the corrupted software on the internal storage and provides a clean environment for recovery, ensuring the router can be restored to a functional state.

Exam trap

The trap here is that candidates may think the 'request system software add' command with the 'force' option can recover a corrupted image while the router is still booting, but this command requires a running Junos OS, which is unavailable when the image is corrupted.

How to eliminate wrong answers

Option B is wrong because deleting the current configuration does not address a corrupted image; the router cannot boot without a valid OS, and configuration is irrelevant at this stage. Option C is wrong because rebooting multiple times will not repair a corrupted image; it only repeats the same boot failure. Option D is wrong because the 'request system software add' command requires the router to be booted and operational, which is impossible if the image is corrupted and the router cannot boot; the 'force' option does not bypass the need for a running system.

24
MCQmedium

A network engineer wants to schedule a reboot of a Juniper device at 3:00 AM. Which command should be used?

A.request system configuration rescue save
B.request system reboot
C.request system reboot at 03:00
D.load override /config/juniper.conf.gz
AnswerC

The `request system reboot at 03:00` command schedules the reboot to occur at 03:00 in the device's local time zone. Junos validates the time argument and queues the reboot, allowing the engineer to finish maintenance tasks before the device restarts. This is the exact operational command designed for a scheduled reboot at a specific time.

Why this answer

The 'request system reboot at 03:00' command schedules a one-time reboot of the Juniper device at the specified time (3:00 AM). The 'at' parameter allows the engineer to set an absolute time for the reboot, which is the exact requirement for scheduling a reboot at a specific future time.

Exam trap

The trap here is that candidates often confuse 'request system reboot' (immediate reboot) with 'request system reboot at' (scheduled reboot), or they mistakenly think that loading a configuration file will trigger a reboot.

How to eliminate wrong answers

Option A is wrong because 'request system configuration rescue save' is used to save the current active configuration as a rescue configuration, which can be used to recover the device if the configuration becomes corrupted; it does not schedule or perform a reboot. Option B is wrong because 'request system reboot' without any time parameter triggers an immediate reboot of the device, not a scheduled reboot at 3:00 AM. Option D is wrong because 'load override /config/juniper.conf.gz' is a configuration mode command used to replace the current candidate configuration with the configuration stored in the specified file; it does not schedule or initiate a reboot.

25
MCQhard

A network engineer needs to analyze NTP synchronization status and offset. Which command provides detailed NTP peer information including delay, offset, and jitter?

A.show ntp statistics
B.show ntp associations
C.show ntp status
D.show ntp peer
AnswerB

'show ntp associations' is the correct command because it displays a row for each configured NTP peer, including its address, stratum, delay, offset, and jitter. Junos also marks the currently synchronized peer with an asterisk (*) and the local clock with 'o', giving the engineer an immediate, per-peer snapshot of the NTP synchronization status.

Why this answer

The 'show ntp associations' command displays detailed NTP peer information, including delay, offset, and jitter, which are essential for analyzing synchronization status. This command lists all configured NTP peers and their current state, providing the specific metrics needed to assess clock accuracy and stability.

Exam trap

The trap here is that candidates familiar with Cisco IOS may expect 'show ntp peer' to work, but Junos uses 'show ntp associations' for the same detailed peer information, while 'show ntp peer' is not a valid command.

How to eliminate wrong answers

Option A is wrong because 'show ntp statistics' displays NTP packet statistics (e.g., packets sent/received, dropped) rather than per-peer delay, offset, and jitter. Option C is wrong because 'show ntp status' shows the local NTP daemon status (e.g., clock stratum, reference ID) but not detailed peer-level metrics. Option D is wrong because 'show ntp peer' is not a valid Junos command; the correct command for peer details is 'show ntp associations'.

26
MCQeasy

A junior engineer needs to collect a snapshot of the current system state, including routing tables, interfaces, and configuration, for a support ticket. Which command achieves this?

A.show configuration
B.show interfaces
C.request support information
D.show route
AnswerC

This is a Junos operational command that automatically collects a comprehensive set of system data, including configurations, interface statistics, routing tables, logs, system processes, and other diagnostic information into a single archive. It is designed specifically for troubleshooting and for providing a complete snapshot to Juniper support or for offline analysis. This one command aggregates far more data than any individual show command, making it the correct choice for a full system snapshot.

Why this answer

The 'request support information' command is the correct choice because it collects a comprehensive snapshot of the current system state, including routing tables, interface details, configuration, logs, and other operational data into a single archive file. This is specifically designed for support tickets, as it bundles all relevant diagnostic information in one step, unlike individual show commands that only capture partial data.

Exam trap

The trap here is that candidates often confuse individual show commands (like 'show route' or 'show interfaces') with the all-in-one 'request support information' command, failing to recognize that only the latter captures the full system state required for a support ticket.

How to eliminate wrong answers

Option A is wrong because 'show configuration' only displays the current active configuration, not the dynamic operational state like routing tables or interface statistics. Option B is wrong because 'show interfaces' only shows interface status and counters, missing routing tables and configuration. Option D is wrong because 'show route' only displays the routing table, omitting interfaces and configuration data.

27
MCQmedium

Which command is used to verify that the current active configuration is the same as the candidate configuration?

A.commit check
B.show configuration
C.show system configuration
D.show | compare
AnswerD

The 'show | compare' command displays the differences between the candidate configuration and the active configuration. It outputs only the lines that would change, in a unified diff format, and if there are no differences, it returns no output. This makes it the ideal command to verify that the candidate exactly matches the active configuration.

Why this answer

The command `show | compare` displays the differences between the candidate configuration and the active (committed) configuration. If there are no differences, the candidate configuration is identical to the active configuration. This is the correct way to verify whether the candidate configuration matches the active configuration in Junos.

Exam trap

The trap here is that candidates often confuse `commit check` (which only validates syntax) with a comparison command, leading them to select Option A, but `commit check` does not compare the candidate to the active configuration.

How to eliminate wrong answers

Option A is wrong because `commit check` validates the syntax and semantics of the candidate configuration but does not compare it to the active configuration; it only ensures the candidate can be committed without errors. Option B is wrong because `show configuration` displays the candidate configuration (or the active if no candidate changes exist), but it does not perform a comparison with the active configuration. Option C is wrong because `show system configuration` is not a valid Junos command; the correct command to view system configuration is `show configuration` or `show system` with specific filters.

28
MCQeasy

A network administrator wants to view the current configuration that is actively running on a Juniper device. Which operational mode command should be used?

A.show configuration
B.show running-config
C.show active-config
D.show current-config
AnswerA

In Junos, the operational mode command "show configuration" (or its alias "show config") displays the current active configuration that is committed and in use on the device. This command reads from the candidate configuration, which becomes the active configuration after a commit, and reflects the exact hierarchy of the Junos configuration database. It is the standard way to view the running configuration in Junos.

Why this answer

In Junos OS, the operational mode command 'show configuration' displays the active, committed configuration currently running on the device. Unlike Cisco IOS, Junos does not use a separate 'running-config'; instead, the configuration is stored as a single candidate configuration that becomes active only after a 'commit' operation. Thus, 'show configuration' is the correct command to view the active configuration.

Exam trap

The trap here is that candidates familiar with Cisco IOS may instinctively choose 'show running-config', but Junos uses a different paradigm with 'show configuration' to display the active committed configuration.

How to eliminate wrong answers

Option B is wrong because 'show running-config' is a Cisco IOS command, not a valid Junos operational mode command; Junos uses 'show configuration' to display the active configuration. Option C is wrong because 'show active-config' is not a valid Junos command; Junos does not have an 'active-config' keyword in its operational mode. Option D is wrong because 'show current-config' is not a valid Junos command; Junos uses 'show configuration' as the standard command to view the current active configuration.

29
MCQeasy

Refer to the exhibit. An administrator notices the /var partition is nearly full. Which command can be used to safely reclaim disk space?

A.request system reboot
B.request system storage cleanup
C.delete /var/log/messages
D.request system software delete
AnswerB

The 'request system storage cleanup' command is the correct procedure because it safely identifies and removes files that are no longer needed, including old log backups, temporary files, and core dumps that have exceeded retention thresholds. It is designed to avoid deleting active or critical files, and it releases space on /var and other partitions in a controlled manner, making it the recommended first step when disk space is low.

Why this answer

The 'request system storage cleanup' command safely removes old log files, core dumps, and other temporary files that are no longer needed, freeing up space on the /var partition without risking system stability. This is the recommended Junos method for reclaiming disk space because it targets only files that can be safely deleted.

Exam trap

The trap here is that candidates may think manually deleting log files (option C) is safe and effective, but Junos relies on its own cleanup mechanisms to avoid breaking log rotation or losing important diagnostic data.

How to eliminate wrong answers

Option A is wrong because 'request system reboot' only restarts the system and does not delete any files, so it will not reclaim disk space. Option C is wrong because manually deleting '/var/log/messages' can cause loss of critical logging data and may not be safe if the file is still being written to; Junos manages log rotation automatically, and direct deletion can disrupt that. Option D is wrong because 'request system software delete' is used to remove installed software packages, not to clean up temporary or log files, and it could inadvertently remove needed software.

30
MCQmedium

A technician needs to monitor routing table updates in real time. Which command provides continuous output of routing changes?

A.monitor route
B.show log messages | match route
C.show route
D.show route protocol bgp
AnswerA

The `monitor route` command is a real-time operational command that subscribes to the routing table event stream, displaying incremental updates as routes are added, withdrawn, or modified. Unlike a one-time snapshot, it continuously refreshes with each RIB change until you interrupt it with Ctrl+C. This makes it the correct tool for observing routing changes as they happen.

Why this answer

The 'monitor route' command in Junos provides a real-time, continuously updating view of routing table changes as they occur. Unlike static commands that show a snapshot, this command actively tracks route additions, removals, and modifications, making it the correct choice for monitoring routing updates in real time.

Exam trap

The trap here is that candidates often confuse 'monitor route' with 'show route' or filtered log commands, assuming any command with 'route' or 'log' can provide real-time output, but only 'monitor route' offers continuous, live updates in Junos.

How to eliminate wrong answers

Option B is wrong because 'show log messages | match route' displays historical log entries filtered for the word 'route', not a continuous real-time stream of routing changes. Option C is wrong because 'show route' outputs a static snapshot of the current routing table, not a live update feed. Option D is wrong because 'show route protocol bgp' shows only BGP-learned routes in a static format, lacking the continuous monitoring capability required.

31
Multi-Selecthard

Which TWO commands can be used to view the current routing table entries for IPv4 unicast routes?

Select 2 answers
A.show route protocol static
B.show route table inet.0
C.show forwarding-table
D.show route
E.show route table inet6.0
AnswersB, D

The command 'show route table inet.0' explicitly selects the IPv4 unicast routing table (inet.0) for display. In Junos, inet.0 is the default routing table for IPv4 unicast routes, holding both active and inactive routes from all protocols. This command is functionally equivalent to a plain 'show route' but makes the table selection explicit, ensuring the administrator is viewing the complete IPv4 unicast routing table rather than another table or protocol-specific subset.

Why this answer

`show route table inet.0` explicitly displays the IPv4 unicast routing table (inet.0) in Junos. Option D is correct because `show route` without any filter defaults to showing all routes in the inet.0 table, which is the primary IPv4 unicast routing table.

Exam trap

The trap here is that candidates confuse the routing table (`show route`) with the forwarding table (`show forwarding-table`), or assume a specific protocol filter like `protocol static` shows all routes, when in fact it only shows routes learned via that protocol.

32
MCQmedium

Refer to the exhibit. An engineer notices that input drops are increasing. What is the most likely cause?

A.Speed mismatch
B.Buffer overflow
C.Cable fault
D.CRC errors
AnswerB

Input drops are specifically the counter that increments when the ingress packet buffer or the shared memory on the forwarding engine is full, forcing new packets to be discarded before they can be processed. This occurs when traffic bursts (often micro-bursts) exceed the interface's buffering capacity or when congestion causes tail-drop at the input queue. Unlike physical-layer errors, this is a congestion-related drop, and it is the correct explanation for the observed input drops in the exhibit.

Why this answer

Input drops occur when the ingress interface's receive buffer is full and cannot accept more packets, typically due to the ingress rate exceeding the interface's ability to process or forward packets to the internal switch fabric. In Junos, this is often caused by microbursts or sustained oversubscription, not by a speed mismatch (which would show as errors or link flaps) or cable faults (which cause physical-layer errors). Buffer overflow is the correct answer because input drops directly indicate that the packet buffer has been exhausted.

Exam trap

The trap here is that candidates often confuse input drops with CRC errors or assume a speed mismatch is the cause, but Junos explicitly separates input drops (buffer overflow) from physical-layer errors, and the question's exhibit would show no CRC errors or link flaps, isolating the issue to buffer exhaustion.

How to eliminate wrong answers

Option A is wrong because a speed mismatch between two connected interfaces would typically cause the link to not come up or generate extensive CRC/alignment errors, not specifically input drops. Option C is wrong because a cable fault usually manifests as CRC errors, frame errors, or link flaps, not as a steady increase in input drops. Option D is wrong because CRC errors are a separate counter indicating data corruption at the physical layer, often due to signal integrity issues, and are not the direct cause of input drops.

33
MCQeasy

A technician needs to view the last 50 log messages from the system log file. Which command accomplishes this?

A.show system log messages
B.monitor start messages
C.show system syslog
D.show log messages | last 50
AnswerD

show log messages | last 50 is the correct operational command to view the most recent 50 entries from the default /var/log/messages file. The pipe to 'last' is a Junos CLI filter that displays only the final 50 lines of the output, similar to 'tail -50' in a Unix shell. This is both efficient and reliable because it avoids printing the entire log and directly shows the newest events.

Why this answer

The 'show log messages | last 50' command displays the last 50 lines from the /var/log/messages file on a Junos device. The pipe to 'last' is a Junos CLI filter that outputs only the final N lines of the command output, which is exactly what is needed to view the most recent log entries.

Exam trap

The trap here is that candidates confuse the 'show log' command with 'show system syslog' or 'show system log messages', misremembering the exact syntax for viewing log file contents versus configuration.

How to eliminate wrong answers

Option A is wrong because 'show system log messages' is not a valid Junos command; the correct command to view the system log file is 'show log messages'. Option B is wrong because 'monitor start messages' is used to tail the log file in real time, not to view a static set of the last 50 messages. Option C is wrong because 'show system syslog' displays the syslog configuration, not the actual log file contents.

34
MCQeasy

A network administrator needs to check the current software version and hardware model of a Juniper device. Which command should the administrator use?

A.show version
B.show system information
C.show configuration version
D.show chassis hardware
AnswerA

The show version command displays the Junos OS software version, hardware model, and other system information such as uptime and build date. It is the standard command to quickly obtain the device's software and hardware details, making it ideal for inventory and compatibility checks.

Why this answer

The show version command is specifically designed to display the Junos OS software version and hardware model. It provides a concise summary that includes the hostname, model, Junos version, and uptime. The other commands either focus on hardware details or are invalid, making show version the correct choice for this scenario.

Exam trap

The trap here is confusing hardware inventory commands like show chassis hardware with the command that provides both software version and hardware model.

35
MCQmedium

An administrator is troubleshooting a Junos device that is dropping packets. The administrator wants to see the real-time traffic statistics for interface ge-0/0/0, including packets per second and errors, updated every second. Which command should the administrator use?

A.show interfaces ge-0/0/0 extensive
B.show interfaces ge-0/0/0 terse
C.monitor interface ge-0/0/0
D.show interfaces ge-0/0/0 statistics
AnswerC

The monitor interface command provides a continuously updating, real-time display of interface statistics, including packets per second, errors, and utilization. It refreshes every second by default and is ideal for observing traffic patterns and troubleshooting packet drops as they occur. This command is part of the operational mode and does not require configuration changes.

Why this answer

The monitor interface command is designed for real-time monitoring, refreshing statistics every second. It shows packets per second, errors, and other counters, allowing the administrator to observe traffic fluctuations and identify issues as they occur. The other commands provide static snapshots or limited information, which are not suitable for continuous observation of interface behavior.

Exam trap

The trap here is confusing static show commands that display detailed statistics with the monitor interface command that provides continuous real-time updates.

36
MCQmedium

A technician notices that the /var partition is filling up on a Juniper device. Which action would be most appropriate to free up space while preserving critical logs?

A.Delete core files manually
B.Run 'request system storage cleanup'
C.Reboot the device
D.Delete all files in /var/log
AnswerB

The 'request system storage cleanup' command is the correct method because it systematically scans well-known system directories and removes only files that are safe to delete, such as stale core files, old log files, and unused software images, while preserving the current system's operational logs and active configuration. It reports how much space was reclaimed and is designed by Juniper to be the standard, nondestructive way to free the /var partition. This avoids the pitfalls of ad-hoc deletion and ensures essential diagnostic data remains intact.

Why this answer

The 'request system storage cleanup' command is the correct action because it safely removes non-essential files such as old log files, core dumps, and temporary files that are no longer needed, while preserving critical logs and configuration files. This command performs a controlled cleanup without risking the deletion of important operational data, making it the most appropriate method for freeing up space on the /var partition.

Exam trap

The trap here is that candidates often assume manual deletion (Option A) or a reboot (Option C) are quick fixes, but they overlook the Junos-specific safe cleanup command that automates the process while preserving essential data.

How to eliminate wrong answers

Option A is wrong because manually deleting core files is risky and inefficient; core files may be needed for debugging, and manual deletion could accidentally remove files that are still in use or miss other space-consuming temporary files. Option C is wrong because rebooting the device does not free up disk space; it only clears temporary memory and may cause unnecessary downtime without addressing the underlying storage issue. Option D is wrong because deleting all files in /var/log would remove critical logs needed for troubleshooting and compliance, and it could also delete active log files that are still being written to, potentially causing system instability or loss of forensic data.

37
Multi-Selecthard

Which three steps are part of a typical software upgrade process on a Juniper device? (Choose three.)

Select 3 answers
A.Issue the request system software add command
B.Download the image to /var/tmp
C.Shut down all interfaces
D.Delete the old image before adding the new one
E.Reboot the device
AnswersA, B, E

The `request system software add` command is the central Junos CLI operation that ingests the software package, typically specified as a local file path or an HTTP/FTP URL. It performs integrity and version checks, then unpacks the image onto the alternate boot partition so it becomes the next active image on the next reboot. It can also include the `reboot` option to automate the restart sequence, but the command itself is what officially 'adds' the package.

Why this answer

Option A is correct because the request system software add command is the standard Junos CLI command used to install a new software image onto the device, validating and unpacking it into the alternate partition. Option B is correct because the software image must first be downloaded to the device, and /var/tmp is the conventional directory used for staging the Junos package before installation. Option E is correct because after the new image is added, the device must be rebooted so it boots from the newly installed software on the alternate partition.

Option C is not part of the process because interfaces do not need to be manually shut down; the reboot handles the transition. Option D is not required because Junos installs the new image to the alternate partition and the old image can remain, so deleting it beforehand is unnecessary and not a standard step.

Exam trap

The trap here is that candidates may mistakenly think interfaces must be shut down before an upgrade (option C), confusing Junos' non-disruptive upgrade process with Cisco IOS procedures where manual interface shutdown is often recommended to prevent routing flaps during the reload.

38
MCQeasy

Which command displays the status of all configured interfaces, including administrative and operational status?

A.show interfaces terse
B.show configuration interfaces
C.show chassis hardware
D.show interface statistics
AnswerA

The 'show interfaces terse' command renders each interface on the device—including all configured interfaces—as a single line in a table with columns for Interface, Admin, Link, Proto, and Local address. Admin reflects the administrative state (up when not administratively disabled, regardless of the physical condition), Link reflects the actual operational state (up only when a valid carrier or signal is detected), and Proto indicates whether a protocol such as inet/IPv4 is active on the interface. Because it combines both the configured administrative state and the real-time operational state in one compact, easy-to-scan output, it is the standard quick check for interface health.

Why this answer

The 'show interfaces terse' command displays a concise summary of all interfaces, including their administrative status (up or down) and operational status (up or down), along with protocol states. This makes it the correct choice for quickly viewing the status of all configured interfaces in a single output.

Exam trap

The trap here is that candidates often confuse 'show interfaces terse' with 'show interface statistics' or 'show configuration interfaces', mistakenly thinking statistics or configuration output will show operational status, but only 'show interfaces terse' provides the concise admin and link status in a single view.

How to eliminate wrong answers

Option B is wrong because 'show configuration interfaces' displays the current configuration of interfaces, not their real-time operational or administrative status. Option C is wrong because 'show chassis hardware' shows physical hardware components (like FPCs, PICs, and power supplies), not interface status. Option D is wrong because 'show interface statistics' shows traffic counters and error statistics for interfaces, but does not explicitly display administrative or operational status in a summary format.

39
MCQmedium

A network engineer suspects a hardware issue on an interface. Which command provides the most detailed hardware error counters, including CRC errors, framing errors, and runts?

A.show interfaces diagnostics optics
B.show interfaces detail
C.show interfaces extensive
D.show log messages
AnswerC

'show interfaces extensive' is the definitive operational command for hardware error analysis on Junos. It outputs each interface's input breakdown, including CRC errors, frame errors, runts, giants, and resource exhaustion, plus output error subcategories like carrier transitions and errors. It also reveals physical-layer state and multiple logical unit statistics, making it possible to correlate errors with transmit/receive activity. When you suspect a hardware fault, this command gives the most complete and structured view of interface health.

Why this answer

The 'show interfaces extensive' command provides the most detailed hardware error counters for a Junos interface, including CRC errors, framing errors, and runts. This command displays per-interface statistics at the physical layer, such as input errors, output errors, and specific error types like frame, runts, giants, and CRC errors, which are essential for diagnosing hardware issues.

Exam trap

The trap here is that candidates often confuse 'show interfaces detail' with 'show interfaces extensive', assuming 'detail' provides the most granular error counters, but only 'extensive' includes the full hardware error breakdown required for hardware fault diagnosis.

How to eliminate wrong answers

Option A is wrong because 'show interfaces diagnostics optics' is used to display optical transceiver diagnostics (e.g., temperature, voltage, laser bias) and does not show interface error counters like CRC or framing errors. Option B is wrong because 'show interfaces detail' provides more information than the basic output but does not include the extensive hardware error counters; it omits the per-error-type breakdown found in the extensive output. Option D is wrong because 'show log messages' displays system log messages, not real-time interface hardware error counters; it is used for troubleshooting events and errors logged by the system, not for granular interface statistics.

40
Multi-Selectmedium

Which two commands display the IPv4 unicast routing table? (Choose two.)

Select 2 answers
A.show ip route
B.show route protocol ospf
C.show route
D.show route table inet.0
E.show routing
AnswersC, D

In Junos, the command 'show route' with no arguments displays the contents of the default routing table, inet.0, which is the primary IPv4 unicast routing table. This is the standard way to view active IPv4 routes on a Junos device. Because it shows the entire inet.0 table, it correctly satisfies the requirement to display the IPv4 unicast routing table.

Why this answer

Option C, `show route`, is correct because on Junos devices this command displays the complete routing table, which by default is the IPv4 unicast table (inet.0), listing all learned and direct routes. Option D, `show route table inet.0`, is also correct because inet.0 is the specific routing table name for IPv4 unicast routes, so this command explicitly displays exactly that table. Option A, `show ip route`, is not a valid Junos command (it is Cisco IOS syntax), so it does not belong.

Option B, `show route protocol ospf`, only filters and displays OSPF-learned routes rather than the entire IPv4 unicast routing table. Option E, `show routing`, is not a valid command and therefore cannot display the routing table.

Exam trap

The trap here is that candidates familiar with Cisco IOS may incorrectly choose 'show ip route' (Option A) or 'show routing' (Option E), not realizing Junos uses the 'show route' command and organizes routing information into named tables like inet.0.

41
MCQmedium

A junior administrator wants to view only the operational state of interface ge-0/0/1, including its link status and protocol state. Which command should they use?

A.show interface ge-0/0/1
B.show interfaces ge-0/0/1 terse
C.show configuration interfaces ge-0/0/1
D.show interfaces ge-0/0/1 extensive
AnswerB

The command 'show interfaces ge-0/0/1 terse' is correct because 'terse' is a display level that shows one summary line per interface or logical unit, including admin status, link status, protocol status, and the configured IP addresses. This is exactly what the junior administrator needs to quickly view operational status without cluttering the output with counters or configuration details. The 'terse' keyword is the standard Junos way to get a concise operational snapshot.

Why this answer

The 'show interfaces ge-0/0/1 terse' command displays a concise operational state of the interface, including link status (up/down) and protocol state (up/down) without configuration details. This is the standard Junos command for quickly verifying the operational status of a specific interface.

Exam trap

The trap here is that candidates familiar with Cisco IOS might type 'show interface' (singular) instead of the Junos plural 'show interfaces', or they might choose 'extensive' thinking more detail is better, when 'terse' is the precise tool for a quick operational state check.

How to eliminate wrong answers

Option A is wrong because 'show interface ge-0/0/1' is an invalid command in Junos; the correct syntax uses the plural 'interfaces'. Option C is wrong because 'show configuration interfaces ge-0/0/1' displays the configuration stanza for the interface, not its operational state. Option D is wrong because 'show interfaces ge-0/0/1 extensive' provides detailed operational and statistical data, which is more than the junior administrator needs for just link and protocol state.

42
MCQhard

An operator wants to monitor the temperature and voltage sensors on a Juniper chassis. Which command displays current sensor readings?

A.show chassis environment
B.show chassis hardware
C.show system health
D.show log messages | match temperature
AnswerA

The `show chassis environment` operational command in Junos is the standard tool for environmental monitoring: it reads live temperature sensors, voltage rails, and fan speeds across the Routing Engine, line cards, and power supplies. Without any filters it returns current values for all monitored components, and with `detail` it also shows acceptable operating ranges and alarm thresholds. This is the only option that delivers a structured, real-time view of the exact sensors the operator asked about.

Why this answer

The 'show chassis environment' command displays real-time sensor readings for temperature, voltage, and fan status on Juniper devices. It is the standard operational command for monitoring chassis environmental health, directly matching the operator's requirement to check temperature and voltage sensors.

Exam trap

The trap here is that candidates may confuse 'show chassis hardware' (static inventory) with 'show chassis environment' (dynamic sensor data), or assume 'show system health' is a valid Junos command when it is not.

How to eliminate wrong answers

Option B is wrong because 'show chassis hardware' lists installed components (like FRUs, serial numbers, and part numbers) but does not display dynamic sensor readings such as temperature or voltage. Option C is wrong because 'show system health' is not a valid Junos command; the correct command for system health checks is 'request system health' or 'show chassis environment'. Option D is wrong because 'show log messages | match temperature' filters system log messages for temperature-related entries, but it does not show current sensor readings—it only displays historical log events that may be outdated or incomplete.

43
MCQeasy

A network administrator notices that the CPU utilization on an MX240 router has been consistently above 90% for the past hour. Users are reporting intermittent connectivity issues. The administrator logs in and runs 'show system processes extensive' which shows the Routing Protocol Daemon (rpd) consuming 70% of the CPU. Further investigation reveals that the router has over 5000 BGP prefixes from multiple peers. The administrator suspects that the high CPU is due to continuous route processing. What should the administrator do to immediately reduce CPU load while maintaining network stability?

A.Perform a 'show log messages' to check for errors before taking action
B.Apply a prefix-limit on each BGP session to restrict the number of prefixes received
C.Bounce all BGP sessions by clearing them with 'clear bgp neighbor *'
D.Disable BGP multipath to reduce route processing
AnswerB

Applying a prefix-limit on each BGP session directly caps the number of routes that rpd must read, parse, and install in the RIB and BGP table. By rejecting excess updates (or tearing down the session when a threshold is exceeded), you stop route churn and table bloat at the source, which is the most effective way to lower CPU utilization. It also protects the router from a peer that advertises an abnormally large table due to misconfiguration or a route leak.

Why this answer

Applying a prefix-limit on each BGP session immediately restricts the number of prefixes the router will accept from peers. This prevents the Routing Protocol Daemon (rpd) from processing excessive BGP updates, reducing CPU load while maintaining network stability by keeping existing sessions and routes intact. The prefix-limit action (e.g., with a teardown threshold) ensures the router does not accept more prefixes than it can handle, directly addressing the root cause of high CPU usage.

Exam trap

The trap here is that candidates may confuse diagnostic actions (like checking logs) or disruptive resets (like clearing all BGP sessions) with immediate corrective measures, overlooking the targeted, non-disruptive solution of applying prefix limits to control route processing load.

How to eliminate wrong answers

Option A is wrong because checking logs ('show log messages') is a diagnostic step that does not reduce CPU load; it only gathers information, which is not an immediate action to alleviate the high CPU caused by continuous route processing. Option C is wrong because bouncing all BGP sessions with 'clear bgp neighbor *' would temporarily drop all BGP peers, causing a complete loss of routing information and network instability, and the CPU spike would likely recur when sessions re-establish and process the same 5000+ prefixes again. Option D is wrong because disabling BGP multipath does not reduce the number of prefixes being processed; it only affects how multiple equal-cost paths are used for forwarding, not the volume of route processing by rpd.

44
MCQmedium

A technician is troubleshooting a connectivity issue and needs to see the path packets take to a remote host. Which Junos command is appropriate?

A.traceroute
B.monitor interface
C.ping
D.show route
AnswerA

traceroute is the correct tool because it actively discovers the Layer 3 path by sending packets with incrementally increasing TTL (or hop limit in IPv6) values. Each router that decrements the TTL to zero discards the packet and returns an ICMP Time Exceeded message, revealing its interface address. This builds a sequential list of hops from source to destination, precisely what the technician needs to locate a connectivity break.

Why this answer

The `traceroute` command in Junos is the correct tool for tracing the path packets take to a remote host. It sends UDP probes with increasing TTL values and listens for ICMP Time Exceeded messages from intermediate routers, revealing each hop along the route. This directly matches the technician's need to see the path packets take.

Exam trap

The trap here is that candidates often confuse `ping` (which tests reachability) with `traceroute` (which shows the path), leading them to select ping when the question explicitly asks for the path packets take.

How to eliminate wrong answers

Option B is wrong because `monitor interface` is used to display real-time interface statistics and traffic counters, not to trace the path packets take to a remote host. Option C is wrong because `ping` only tests reachability and measures round-trip time to a destination, but it does not reveal the specific hops or path taken. Option D is wrong because `show route` displays the local routing table entries on the Junos device, not the actual path packets traverse through the network to a remote host.

45
MCQhard

A router is experiencing intermittent packet loss. The engineer runs 'show interfaces ge-0/0/0 extensive' and notices a high number of input errors but no output errors. What is the most likely cause?

A.The cable is too long
B.A faulty transceiver
C.MTU mismatch
D.The interface is oversubscribed
AnswerB

A faulty transceiver (SFP/SFP+/QSFP) is a classic source of receive-side errors: imperfect optical transmission or receiver degradation creates bit errors, FCS/CRC failures, and symbol errors that increment the input error counter. On Junos, an optics failure can appear intermittently as temperature or wavelength drifts, making it a prime suspect for sporadic packet loss with input errors. Swapping the optic is the standard first step to confirm.

Why this answer

A high number of input errors with no output errors on a Juniper interface typically indicates a Layer 1 issue at the receiving end. A faulty transceiver can cause signal degradation, leading to CRC errors, framing errors, or alignment errors, all of which are counted as input errors. Since output errors are absent, the problem is not with the router's transmission but with the incoming signal quality.

Exam trap

The trap here is that candidates often confuse input errors with output drops or oversubscription, but input errors are strictly Layer 1 physical-layer issues, not congestion or configuration mismatches.

How to eliminate wrong answers

Option A is wrong because a cable that is too long would likely cause both input and output errors due to signal attenuation and timing issues, not exclusively input errors. Option C is wrong because an MTU mismatch typically causes packet drops at the IP layer (often seen as 'giants' or 'fragmentation needed' counters) and would not manifest as a high number of input errors on the physical interface; it would more likely cause output errors or discards. Option D is wrong because an oversubscribed interface would show output drops or congestion-related discards, not input errors; input errors are physical-layer issues, not capacity-related.

46
Multi-Selectmedium

Which TWO methods can be used to restore a previous configuration on a Juniper device? (Select two.)

Select 2 answers
A.load override /config/rescue.conf
B.commit confirmed
C.rollback 1
D.load replace previous
E.rollback 0
AnswersA, C

The rescue configuration is a dedicated backup file stored at /config/rescue.conf. The 'load override' command replaces the entire candidate configuration with the contents of this file, which can then be committed to restore the device to a known-good state. This is a valid and reliable method for recovering a previous configuration, especially in disaster recovery scenarios.

Why this answer

Option A, `load override /config/rescue.conf`, is correct because the rescue configuration is a saved, known-good configuration file that can be loaded with the `load override` command to replace the entire current candidate configuration, after which a `commit` restores the device to that prior state. Option C, `rollback 1`, is correct because Junos retains the last 49 committed configurations, and `rollback 1` loads the immediately previous committed configuration into the candidate, which can then be committed to restore the earlier configuration. Option B, `commit confirmed`, is not a restore method; it activates a configuration temporarily and auto-rolls back unless confirmed, so it is used for safe changes, not for restoring a previous config.

Option D, `load replace previous`, is invalid syntax—`load replace` requires a specific file or terminal input, and there is no `previous` keyword for it. Option E, `rollback 0`, loads the currently active (most recent) committed configuration, so it does not restore an earlier configuration.

Exam trap

The trap here is that candidates often confuse 'rollback 0' with restoring a previous configuration, not realizing that rollback 0 refers to the current active configuration, while rollback 1 or higher is needed to access a prior committed configuration.

47
Multi-Selectmedium

Which THREE operational commands are used to monitor interface statistics and status? (Select three.)

Select 3 answers
A.show interfaces terse
B.monitor interface
C.show interfaces
D.show log interfaces
E.show interfaces diagnostics
AnswersA, B, C

The 'show interfaces terse' command is a compact operational mode command that lists every interface on a single line, displaying the administrative and link status, protocol status, and configured IP addresses. It is ideal for quickly determining which interfaces are up or down, and is often used in scripts to capture a high-level snapshot of interface state.

Why this answer

Option A, "show interfaces terse," is correct because it provides a compact, one-line-per-interface summary of operational status (up/down), protocol state, and basic counters, making it ideal for quickly monitoring interface status. Option B, "monitor interface," is correct because it displays real-time, continuously updating interface statistics and status, which is specifically designed for live monitoring of interface traffic and errors. Option C, "show interfaces," is correct because it gives detailed operational output including status, protocol state, error counters, and statistics for each interface, serving as a primary monitoring command.

Option D, "show log interfaces," is not a valid operational command for monitoring interface statistics and status; logs are viewed with commands like "show log messages." Option E, "show interfaces diagnostics," is not a standard command for monitoring interface statistics and status; diagnostics commands typically display optics or hardware diagnostic information rather than general interface status and counters.

Exam trap

The trap here is that candidates may confuse 'show log interfaces' with the valid 'show log' command or mistakenly think 'show interfaces diagnostics' is a catch-all command, when in reality Junos requires specific sub-commands like 'show interfaces diagnostics optics' for optics monitoring.

48
MCQmedium

A network engineer notices that traffic to a critical server is being dropped intermittently. The server is reachable via a static route on the Juniper router. The engineer checks the routing table and sees the route is present. Which operational command should the engineer use next to isolate the issue?

A.show interfaces terse
B.show route 10.0.0.1
C.show arp
D.show route forwarding-table destination 10.0.0.1
AnswerD

show route forwarding-table destination 10.0.0.1 is the correct command because it queries the Packet Forwarding Engine's forwarding table (FIB) for the specific destination. While show route only shows the RIB in the Routing Engine, this command reveals the actual entry the PFE uses to forward packets, including the resolved next hop and output interface. If the route exists in the RIB but traffic is dropped, this command can expose a missing or stale forwarding entry, an incorrect next hop, or a drop caused by a firewall filter applied in the forwarding path.

Why this answer

The `show route forwarding-table destination 10.0.0.1` command displays the actual forwarding entry in the kernel's forwarding table (FIB). Even if the route is present in the routing table (RIB), a mismatch between the RIB and FIB can cause traffic drops. This command directly verifies whether the route has been installed into the forwarding table, isolating the issue to a possible hardware or kernel programming failure.

Exam trap

The trap here is that candidates assume a route present in the routing table guarantees it is being used for forwarding, but Junos separates control plane (RIB) from forwarding plane (FIB), so the FIB must be checked separately to identify programming failures.

How to eliminate wrong answers

Option A is wrong because `show interfaces terse` only displays interface status and configuration, not the routing or forwarding state for a specific destination. Option B is wrong because `show route 10.0.0.1` shows the route in the routing table (RIB), which the engineer already confirmed is present; it does not reveal whether the route is correctly programmed into the forwarding table (FIB). Option C is wrong because `show arp` displays the ARP cache for resolving next-hop MAC addresses, but the issue is about traffic being dropped despite a valid route, not about Layer 2 resolution failures.

49
MCQmedium

A BGP session is flapping. The engineer runs 'show log messages' and sees 'BGP recv Notification' with error code 'Cease'. What does this indicate?

A.The BGP table is full
B.The hold timer expired
C.The remote peer closed the connection
D.The interface went down
AnswerC

A BGP Cease notification indicates that the remote peer explicitly sent a NOTIFICATION message to terminate the BGP session. The Cease error code (6) covers several subcodes, such as administrative shutdown, peer de-configured, or local system restart, but all mean the remote peer closed the connection at the BGP protocol level. Because the log specifically records a Cease, the most direct inference is that the remote peer closed the connection, thereby causing the session to flap. This is why this is the correct answer.

Why this answer

A BGP Cease notification indicates that the remote peer has closed the BGP session, often due to an administrative shutdown, configuration change, or error condition on the peer. The 'BGP recv Notification' message means the local router received this notification from the peer, so the remote peer initiated the closure.

Exam trap

The trap here is that candidates often confuse 'Cease' with a hold timer expiration, but 'Cease' is a clean notification sent by the peer, while hold timer expiration is a local detection of a missed keepalive.

How to eliminate wrong answers

Option A is wrong because a full BGP table would typically cause a 'BGP recv Notification' with error code 'Resource' or 'Maximum Prefixes', not 'Cease'. Option B is wrong because a hold timer expiration results in a 'Hold Timer Expired' error code, not 'Cease'. Option D is wrong because an interface going down would cause a BGP session reset due to a TCP connection failure, not a clean 'Cease' notification.

50
MCQhard

An administrator suspects that an interface is flapping but the router is remote and the connection is intermittent. The administrator wants to monitor the interface status without maintaining an SSH session. Which approach should be used?

A.Configure event-options to trigger on interface down and send syslog
B.Use 'monitor interface ge-0/0/0' and rely on terminal persistence
C.Use 'monitor start' to capture logs
D.Schedule a cron job to run 'show interfaces ge-0/0/0' every minute and log output
AnswerA

Junos event-options provide a policy-based framework that monitors for interface down (and up) events in real time, and when triggered, can send a syslog message to a remote server. This is fully automatic and requires no active SSH session on the device, because the Junos device itself evaluates the event and forwards the syslog to a collector. By capturing the event at the moment it occurs, even brief flaps are recorded reliably, making this the preferred method for logging interface state changes in a network environment.

Why this answer

Junos event-options allows you to define an event policy that triggers on a specific event, such as an interface down transition, and then executes an action like sending a syslog message. This enables asynchronous monitoring without requiring an active SSH session, making it ideal for intermittent connectivity scenarios.

Exam trap

The trap here is that candidates confuse real-time monitoring commands like 'monitor interface' with persistent event-driven monitoring, assuming that terminal persistence or log capture can substitute for an event-based solution that works without an active session.

How to eliminate wrong answers

Option B is wrong because 'monitor interface' is a real-time CLI command that requires an active SSH session to display continuous output; it does not persist after the session ends. Option C is wrong because 'monitor start' is used to capture log file output in real time, but it also requires an active SSH session and does not trigger on specific events like interface flapping. Option D is wrong because scheduling a cron job on a remote router is not a native Junos feature; Junos does not support cron, and the approach would require an external management server, not a solution directly on the device.

51
MCQhard

A network engineer needs to verify the checksum of a downloaded Junos image before installation. Which command is used?

A.file checksum sha256 <filename>
B.compare <filename> original
C.request system software validate <filename>
D.show system software
AnswerA

The Junos CLI command 'file checksum sha256 <filename>' computes the SHA-256 cryptographic hash of the specified file, producing a deterministic digest that can be compared against the vendor-published checksum to confirm the download's integrity and detect corruption or tampering. This is the standard, purpose-built method on Junos for verifying a downloaded image or file, and it directly addresses the engineer's task.

Why this answer

The `file checksum sha256 <filename>` command computes the SHA-256 hash of the specified file, allowing the engineer to compare it against the published checksum from Juniper Networks to verify integrity and authenticity before installation. This ensures the image has not been corrupted or tampered with during download.

Exam trap

The trap here is that candidates confuse the `request system software validate` command, which performs a package validation, with a checksum verification, but it does not compute or display a cryptographic hash for external comparison.

How to eliminate wrong answers

Option B is wrong because `compare <filename> original` is not a valid Junos command; it is likely confused with the `file compare` command used to diff two files, not to verify checksums. Option C is wrong because `request system software validate <filename>` validates the software package's internal integrity and compatibility with the current system, but it does not compute or display a checksum for external verification against a published hash. Option D is wrong because `show system software` displays installed software packages and their versions, not a checksum verification function for a downloaded image.

52
MCQeasy

An engineer needs to check the last time the configuration was changed. Which command provides this information?

A.show system commit
B.show configuration | display set
C.show system alarms
D.show system uptime
AnswerA

show system commit is correct because it directly displays the commit log, which records every configuration commit along with the timestamp, user, and commit comment. By listing each commit event, it provides the exact last time the configuration was changed and saved as an active operational state. This command is the standard way to audit configuration change history on Junos devices.

Why this answer

The 'show system commit' command displays the commit history, including the date, time, and user for each configuration change. This allows the engineer to see exactly when the last configuration was committed, which is the definitive way to determine the last time the configuration was changed.

Exam trap

The trap here is that candidates often confuse 'show configuration' (which shows the current config) with a command that shows when the config was last changed, but only 'show system commit' provides the timestamp of the last commit.

How to eliminate wrong answers

Option B is wrong because 'show configuration | display set' shows the current active configuration in set format, but it does not include any timestamp or commit history to indicate when the configuration was last changed. Option C is wrong because 'show system alarms' displays active system alarms (such as hardware or software issues), not configuration change timestamps. Option D is wrong because 'show system uptime' shows how long the device has been running and the time since the last reboot, but it does not provide any information about configuration commit times.

53
Multi-Selectmedium

Which two events typically trigger a change to the routing table? (Choose two.)

Select 2 answers
A.Interface state change
B.System uptime
C.Log file rotation
D.BGP neighbor reset
E.Configuration commit
AnswersA, D

An interface state change (up or down) is a primary trigger for routing table updates. When an interface transitions, the kernel notifies rpd, which immediately adds or removes the directly connected route for that subnet; this change in turn causes the routing table to recalculate and, if necessary, sends updated route information to dynamic routing protocols like OSPF or IS-IS.

Why this answer

An interface state change (up/down) directly affects the reachability of directly connected networks. When an interface goes up, Junos adds the corresponding directly connected route to the routing table; when it goes down, the route is removed. Similarly, a BGP neighbor reset causes the BGP session to be torn down and re-established, which triggers the withdrawal and re-advertisement of all BGP routes, thereby modifying the routing table.

Exam trap

The trap here is that candidates often confuse a configuration commit (option E) with an automatic routing table change. A commit only activates the configuration; it does not directly modify the routing table unless the configuration itself triggers a protocol event or interface change.

54
MCQeasy

You are a junior network engineer tasked with upgrading the Junos OS on a pair of EX3400 switches that are in a Virtual Chassis. You have downloaded the new software image to the primary switch. Before performing the upgrade, you must verify the image's integrity and check the current version. Which sequence of commands should you use?

A.Run 'show system uptime' and then 'request system software add /var/tmp/junos-new.tgz'.
B.Run 'show system software' and then 'request system software add validate'.
C.Run 'show version' and then 'request system software validate /var/tmp/junos-new.tgz'.
D.Run 'show configuration system software' and then 'file checksum sha256 /var/tmp/junos-new.tgz'.
AnswerC

This is the correct approach because 'show version' first confirms the currently running Junos image and software version, which is essential for comparing against the new package and verifying upgrade path compatibility. Then 'request system software validate /var/tmp/junos-new.tgz' performs a dry-run validation of the image file, checking its integrity, checksum, and compatibility with the current system without actually installing it. Together, these two commands give the engineer a clear picture of the current state and a verified upgrade package before installation.

Why this answer

'show version' displays the current Junos OS version running on the switch, which is necessary to confirm the starting point before an upgrade. Then 'request system software validate /var/tmp/junos-new.tgz' performs a checksum verification and package integrity check on the image file without installing it, ensuring the image is not corrupted. This sequence directly addresses the two tasks: verifying the image's integrity and checking the current version.

Exam trap

The trap here is that candidates confuse 'show system software' (a non-existent command) with 'show version', or think that 'file checksum sha256' alone is sufficient for integrity verification, missing the fact that Junos requires the full 'request system software validate' command to perform a comprehensive package check before installation.

How to eliminate wrong answers

Option A is wrong because 'show system uptime' shows how long the switch has been running, not the current software version, and 'request system software add /var/tmp/junos-new.tgz' immediately installs the image without any integrity validation. Option B is wrong because 'show system software' is not a valid Junos command (the correct command is 'show version' or 'show system software information'), and 'request system software add validate' is syntactically incorrect—the correct syntax is 'request system software validate <filename>'. Option D is wrong because 'show configuration system software' displays the software-related configuration (e.g., licenses), not the current running version, and while 'file checksum sha256' does verify integrity, it only checks the hash and does not perform the full package validation that 'request system software validate' does, nor does it check the current version.

Ready to test yourself?

Try a timed practice session using only Operational Monitoring and Maintenance questions.