JN0-106 Timed Practice Test 2 — 10 Questions

Question 1

You are troubleshooting an OSPF adjacency issue between two Juniper MX series routers, R1 and R2, both running Junos 18.2. They are directly connected via a Gigabit Ethernet link. R1's interface ge-0/0/0 is configured with IP 192.168.1.1/24, and R2's ge-0/0/0 is configured with IP 192.168.1.2/24. Both interfaces are in OSPF area 0.0.0.0. The physical connectivity is confirmed up, and both interfaces are administratively enabled. You have checked that the hello and dead intervals match (hello 10, dead 40), the area IDs are identical, and the subnet masks are /24. No firewall filters are blocking OSPF. The OSPF configuration on R1 includes 'authentication-type md5' and 'authentication-key juniper123' under the interface. On R2, the configuration also includes 'authentication-type md5' but the key is 'juniper321'. Both routers have loopback addresses as router IDs: 1.1.1.1 for R1 and 2.2.2.2 for R2. No explicit OSPF network type is set, so the default is broadcast. Despite these configurations, the OSPF adjacency state on both routers remains in INIT. What is the most likely cause of this issue?

10 minute time limit — choose an answer to begin.

Accepted Answer

The OSPF authentication keys do not match.. OSPF authentication keys must match exactly for the adjacency to form. R1 uses key 'juniper123' while R2 uses 'juniper321', causing the MD5 digest computed on each Hello packet to differ. Since OSPF authentication is validated per-packet, mismatched keys prevent the routers from moving past the INIT state.

Answer

The interface MTU size is mismatched.

Answer

The OSPF network type is mismatched.

Answer

The router IDs are not properly configured.

Question 2

During a network traffic storm, a Juniper EX switch's CPU utilization spikes to 100%. Which command would best help identify the cause?

Accepted Answer

monitor traffic interface ge-0/0/0. The 'monitor traffic interface' command captures live packet headers on the specified interface, allowing you to see the type and source of traffic causing the CPU spike. During a traffic storm (e.g., broadcast storm), this command reveals excessive broadcast, multicast, or unknown unicast frames, which are typically the root cause of high CPU utilization on Juniper EX switches.

Answer

show spanning-tree bridge

Answer

show ethernet-switching table

Answer

show interfaces extensive ge-0/0/0

Question 3

A network engineer is configuring a Juniper device in a production network. They have applied several changes to the candidate configuration and run 'commit check', which passes. After a brief pause, they run 'commit' but receive the error: 'commit failed: configuration database modified by another user. Please reload the configuration and try again.' The engineer is the only person currently logged into the device, but they know that another engineer was working on the same device earlier and may have left a commit pending. What is the most likely reason for the commit failure?

Accepted Answer

The other engineer committed their changes between the commit check and the commit.. The error message 'configuration database modified by another user' indicates that another user (the earlier engineer) had a pending commit that was not yet applied or discarded. When the current engineer ran 'commit check', it validated the candidate configuration against the current active configuration, but between that check and the actual 'commit', the other engineer's pending commit was applied (or their session was closed, causing their changes to be committed automatically if they had left a commit pending). This changed the configuration database, causing the commit to fail due to a version mismatch.

Answer

The commit check did not validate the syntax of the new changes.

Answer

The candidate configuration has timed out and must be re-entered.

Answer

The device has insufficient storage to write the new configuration.

Question 4

You are responsible for a Juniper MX router that connects two customer sites over a Layer 3 VPN. The router is configured with BGP for VPN routes and uses MPLS to forward traffic. Recently, the customer reported that traffic from Site A (10.0.1.0/24) to Site B (10.0.2.0/24) is intermittently failing. You check the routing table on the router and see that both routes are present with valid next-hops. However, when you ping from the router's loopback to the remote site's loopback, the ping succeeds. MPLS labels are being assigned and the LSP is up. You also notice that when the failure occurs, the router's BGP session to the remote PE is still established. The failure seems random and lasts a few seconds before recovering. Which troubleshooting step is most likely to identify the root cause?

Accepted Answer

Review the forwarding table for the affected prefixes and check for any discrepancies.. The issue is intermittent packet loss with valid routes in the routing table but successful pings from the loopback. This points to a forwarding table (FIB) inconsistency, where the control plane (routing table) has the correct next-hop, but the forwarding plane (PFE) may have a stale or incorrect entry for the specific prefixes. Checking the forwarding table with 'show route forwarding-table' will reveal if the next-hop or label information differs from the routing table, which is a classic symptom of a hardware programming issue or a transient PFE problem.

Answer

Check the interface error counters for CRC errors or drops.

Answer

Verify the BGP session state and check for route flapping.

Answer

Check the MPLS label switching table to ensure labels are correctly assigned.

Question 5

A network engineer needs to view the operational status of all interfaces on a Junos device, including those that are disabled. Which command should be used?

Accepted Answer

show interfaces terse. The 'show interfaces' command displays detailed information for all interfaces, including those that are administratively disabled. However, 'show interfaces terse' provides a concise, one-line-per-interface summary that is more efficient for quickly viewing the operational status of all interfaces, including disabled ones. For the JNCIA exam, 'show interfaces terse' is the recommended command for this purpose because it offers a clear and compact overview of interface status across the device.

Answer

show interfaces

Answer

show configuration interfaces

Answer

monitor interface traffic

Question 6

What is the primary function of the fxp0 interface on a Juniper device?

Accepted Answer

Management interface. The fxp0 interface is a dedicated out-of-band management Ethernet port on Juniper devices, used exclusively for management traffic such as SSH, SNMP, and syslog. It is separate from the data plane and control plane forwarding interfaces, ensuring administrative access remains available even if the routing or forwarding planes are disrupted.

Answer

Internal routing

Answer

Loopback testing

Answer

Data plane forwarding

Question 7

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

Accepted Answer

show log messages. '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.

Answer

monitor start messages | match "error"

Answer

show log file messages | match "error"

Answer

show system syslog messages

Question 8

A network administrator accidentally deleted a vital part of the configuration while in configuration mode. They need to revert to the previous configuration without losing recent changes that are correct. Which action should they take?

Accepted Answer

rollback 0. The 'rollback 0' command reverts the candidate configuration to the most recently committed configuration (the current active configuration), discarding any uncommitted changes. This allows the administrator to undo the accidental deletion without affecting any recently committed correct changes, as those are already part of the active configuration. Option B, 'rollback 1', would revert to the previous commit, which could remove recently committed correct changes if they were made in the most recent commit. Therefore, 'rollback 0' is the safer choice when you want to preserve correct changes that have already been committed.

Answer

deactivate

Answer

rollback 1

Answer

delete

Question 9

A host in VLAN 10 can ping a host in VLAN 20 without a default gateway configured. What feature is likely enabled on the router that interconnects the VLANs?

Accepted Answer

Proxy ARP. Proxy ARP allows a router to respond to ARP requests on behalf of hosts in different subnets. When a host in VLAN 10 sends an ARP request for a host in VLAN 20, the router responds with its own MAC address if it has a route to the destination. This enables the host to send traffic to the router, which then forwards it to the destination VLAN, even without a default gateway configured on the host.

Answer

VLAN translation is configured on the trunk

Answer

IP routing is enabled on the router

Answer

Dynamic ARP Inspection

Question 10

You are a network engineer at a company that operates a pair of Juniper SRX firewalls in an active/passive cluster (Chassis Cluster). The cluster has been running Junos 15.1X49-D100 for over a year. Management has mandated an upgrade to a newer version to address security vulnerabilities. You follow the recommended upgrade procedure and successfully upgrade the primary node (node0) first, then failover to make node0 the backup, and upgrade the new primary (node1). After the upgrade, both nodes have the same version and appear to be in the cluster, but you notice that the backup node (node0) is stuck in 'ineligible' state and does not synchronize configuration changes. What is the most likely cause?

Accepted Answer

The cluster control link is down or misconfigured on the backup node. The backup node being stuck in 'ineligible' state after a chassis cluster upgrade indicates that the cluster control link (control port) is not functioning correctly. In a Juniper SRX active/passive cluster, the control link is used for heartbeat and cluster state synchronization; if it is down or misconfigured on the backup node, the node cannot participate in the cluster election process and remains ineligible. This is a common issue after upgrades if the control link interfaces are not properly re-established or if the cable is faulty.

Answer

The backup node has not been configured with 'commit synchronize'

Answer

The 'set chassis cluster reth-count' statement is missing on the backup node

Answer

The 'monitor interface' configuration is causing a mis-match between nodes