Free Practice Questions for the Juniper JNCIS-ENT JN0-352 Exam (2026 Updated)

Nonstop active routing's defining architectural feature is that the backup Routing Engine runs a fully live, active instance of the routing protocol daemon (rpd) in parallel with the primary Routing Engine's rpd instance, continuously, from the moment NSR and its prerequisite GRES are established — not merely at the instant a switchover begins. As protocol adjacencies form, routes are learned, and the RIB is updated on the primary Routing Engine, that same protocol and RIB state is mirrored in real time to the backup Routing Engine's rpd process through an internal synchronization mechanism, so the backup's protocol state remains a live, up-to-date replica of the primary's at essentially every moment during normal operation. When a switchover occurs, the backup Routing Engine simply assumes the primary role with protocol adjacencies, routing tables, and forwarding state already fully populated and current, allowing it to continue operating without re-establishing neighbor relationships or re-learning the network topology, which is what makes the switchover genuinely nonstop and invisible to neighboring routers. This is fundamentally different from graceful restart, where the restarting router must rebuild its state by requesting help from cooperating neighbors after the fact. The Packet Forwarding Engine plays no role in synchronizing protocol-layer information such as LSAs or BGP updates; that is strictly an rpd-to-rpd function coordinated through the Routing Engine synchronization infrastructure. Reference topics: Junos Enterprise Routing – High Availability, Nonstop Active Routing Architecture and rpd Synchronization.

The entire purpose of route aggregation is summarization — replacing a set of more-specific contributing routes with a single, broader prefix advertised outward — and this summarization inherently hides internal routing instability from external peers: if one of the underlying contributing /24 blocks within a summarized /16 flaps up and down due to a local link issue, external peers who only see the stable, unchanging /16 aggregate are completely insulated from that churn, since the aggregate itself remains active and advertised as long as at least one contributing route is present, regardless of how much internal fluctuation occurs among the individual contributors. This stability-hiding characteristic is one of the primary operational benefits that motivates using aggregate routes in the first place, confirming that statement as correct. Regarding next-hop behavior, official Juniper documentation is explicit and unambiguous: when an aggregate route is installed in the routing table, Junos assigns it a reject next hop by default, meaning traffic matching only the aggregate (and no more-specific contributor) is dropped and an ICMP unreachable message is returned to the source; a discard next hop is available only as an optional, explicitly configured alternative when silent dropping without ICMP notification is preferred, but it is not the default. Aggregate routes categorically do not advertise their individual contributing routes; suppressing those specific, more-granular prefixes from onward advertisement in favor of the single summary is the aggregate's defining function, directly contradicting the first statement. Reference topics: Junos Enterprise Routing – Protocol Independent Routing, Default Reject Next Hop and Route Summarization Benefits.

RSTP, as defined in IEEE 802.1w, introduces explicit, well-defined port roles that go beyond legacy 802.1D STP's simpler root/designated/blocking model, and the alternate port role is one of RSTP's key refinements. An alternate port is a port that receives BPDUs from a bridge other than the one through which the local switch's actual root port reaches the root bridge — in other words, it represents a second, redundant path toward the root bridge learned from a different upstream bridge than the one currently providing the best (root port) path. Because the existing root port already provides the lowest-cost, actively used path to the root, the alternate port is deliberately held in the discarding (non-forwarding) state during normal, stable operation, functioning purely as a pre-computed, ready-to-use backup; critically, RSTP's major performance advantage over legacy STP is that if the current root port fails, the switch can transition its alternate port directly and almost instantly into the forwarding root port role without needing to pass through the lengthy listening and learning timer-based states that classic STP required, since the alternate port's suitability as a backup was already continuously verified through ongoing BPDU reception. It is not simply 'not receiving BPDUs' (an alternate port receives BPDUs continuously, just inferior ones relative to the current root port), it is not itself the least-cost path (that describes the root port), and it does not forward based on designated-port overload, which is not a concept that exists in RSTP's port-role logic at all. Reference topics: Junos Enterprise Switching – Spanning Tree Protocols, RSTP Port Roles: Alternate and Backup Ports.

The factory-default storm control configuration on EX Series switches operates in a purely rate-limiting mode rather than an interface-shutdown mode. When broadcast, multicast, or unknown-unicast traffic on a port exceeds the configured bandwidth-percentage threshold, the default action is simply to police the offending traffic type and silently drop only the packets that exceed that threshold, while all traffic within the allowed rate continues to be forwarded normally and the interface itself remains administratively and operationally up throughout the event. This explains the observed symptom precisely: during the burst of unknown-unicast frames, the switch dropped the excess volume above the configured limit, producing a brief period of packet loss, but as soon as the burst subsided and traffic fell back under the threshold, storm control simply stopped dropping packets and normal forwarding resumed automatically — no administrative shutdown, recovery timer, or manual intervention was ever involved, because the interface was never taken down in the first place. This default drop-only behavior is distinct from the optional interface-shutdown action, which must be explicitly configured if an administrator wants storm control to disable a port outright on violation (as seen in a related scenario requiring the clear ethernet-switching recovery-timeout command). Storm control by default covers broadcast, multicast, and unknown-unicast traffic types together, not multicast alone, and it has no functional relationship to GRES, which governs Routing Engine redundancy rather than Layer 2 traffic policing. Reference topics: Junos Enterprise Switching – Storm Control, Default Drop Behavior Versus Interface Shutdown Action.

A functioning GRE tunnel interface in Junos requires, at minimum, both a tunnel source address and a tunnel destination address configured together under the tunnel statement of the gr- logical unit, since these two values together define the outer, delivery-layer IP header that will encapsulate every passenger packet sent through the tunnel; the source identifies which of the router's own addresses will originate the encapsulated traffic, and the destination identifies the remote tunnel endpoint the encapsulated traffic must be routed toward across the underlying IP network. The first option correctly supplies both required values in a single, complete statement — source 192.168.1.1 (Router A's own address) and destination 192.168.2.1 (Router B's address) — fully defining the tunnel's endpoints and ensuring the encapsulation and route-resolution process can succeed. The fourth option supplies only the destination and omits the source entirely, which is an incomplete configuration; without an explicit source, Junos cannot always reliably determine which local address to use for encapsulation, particularly on multi-address or multi-interface routers, and the tunnel configuration is left non-deterministic or non-functional as shown. The second option enables the IPv6 protocol family on the tunnel's logical unit, which is irrelevant to a scenario explicitly requiring IPv4 passenger traffic support. The third option attempts to assign a family inet address directly using one of the underlying tunnel endpoint addresses, which conflates the tunnel's own transport addressing with logical-unit protocol addressing and does not by itself establish the required source/destination tunnel definition. Reference topics: Junos Enterprise Routing – Tunneling, Configuring GRE Tunnel Source and Destination.

A link aggregation group bundles multiple physical Ethernet links into a single logical interface (an ae interface) specifically to provide both increased aggregate bandwidth and link-level redundancy. By default, the aeX interface remains operationally up as long as at least one member link within the bundle remains active and passing traffic; the LAG does not require every member link to be functional to continue operating. When one of the four 1-GbE member links in this scenario fails, LACP (if in use) or the underlying link-status monitoring detects the failure, removes that specific link from the active forwarding set, and redistributes traffic hashing across the three remaining healthy member links automatically and without operator intervention. End devices and upper-layer protocols continue to see a single, continuously up ae interface throughout this process, experiencing only a proportional reduction in available aggregate bandwidth rather than any interruption in connectivity. This default behavior is precisely why LAG is a foundational building block for resilient EX Series switch interconnects in enterprise and data center designs, since it allows individual optic, cable, or transceiver failures to be absorbed transparently. None of the distractor behaviors — full administrative shutdown of the bundle, forwarding limited to broadcast traffic only, or a temporary disabling of all member links during renegotiation — reflect actual Junos LAG behavior, which is designed explicitly to avoid any such disruption. Reference topics: Junos Enterprise Switching – Layer 2 Switching, Link Aggregation Group Resiliency.

The BGP finite state machine defined in RFC 4271 progresses through Idle, Connect, Active, OpenSent, OpenConfirm, and finally Established. The Active state is entered either directly after Idle, when the local router begins retrying a TCP connection setup toward the configured peer, or after a previous Connect attempt has failed and the ConnectRetry timer has expired, prompting the router to keep trying to complete the underlying TCP three-way handshake. Seeing a peer parked in Active therefore means the local device has a fully valid neighbor configuration and is persistently attempting to reach the remote address on TCP port 179, but the handshake is not succeeding — common root causes include a firewall or ACL blocking TCP 179 between the two endpoints, an unreachable or incorrect peer IP address, the remote BGP process not running or not listening, or an asymmetric routing path preventing the SYN/ACK from returning. It does not indicate a misconfiguration on the local box in the sense of a missing statement (that would typically leave the session as Idle), nor does it indicate an established, functioning session exchanging UPDATE messages (that state is Established), and it is not a deliberately idle/disabled condition, which Junos reports plainly as Idle. Recognizing Active as 'trying to connect' rather than 'connected' is essential for correct BGP troubleshooting sequencing. Reference topics: Junos Enterprise Routing – BGP Fundamentals, BGP Finite State Machine and Session Verification.

Voice VLAN is the Junos feature specifically designed to allow a single access port to simultaneously handle two distinct traffic streams: untagged data traffic from a PC or workstation using the port's normal access VLAN, and separately tagged voice traffic generated by an IP telephone that is typically daisy-chained between the switch port and the connected PC. When voice VLAN is configured on an access interface, the switch instructs the attached IP phone (commonly via LLDP-MED) which VLAN ID to tag its voice traffic with, and the switch is then able to correctly classify and prioritize that tagged voice traffic into its designated voice VLAN while simultaneously continuing to treat any untagged frames arriving on that same physical port as belonging to the port's regular, untagged access VLAN — precisely satisfying the requirement to accept both tagged and untagged traffic together on one access port. Native VLAN, by contrast, is a trunk-port-only concept that designates which VLAN untagged frames on a trunk should be associated with; it has no applicability to an access port and does not enable simultaneous tagged traffic acceptance there. Default VLAN simply refers to the VLAN an interface belongs to absent other configuration and carries no dual-traffic capability. IRB interfaces provide Layer 3 gateway functionality for a VLAN and are unrelated to how tagged versus untagged frames are accepted at Layer 2 on a given physical port. Reference topics: Junos Enterprise Switching – VLANs, Configuring Voice VLAN on Access Interfaces.

Root bridge election in Spanning Tree Protocol is governed entirely by the Bridge Identifier, an 8-byte value formed by concatenating the configured bridge priority (the higher-order, more significant portion of the comparison) with the switch's MAC address (used strictly as a tiebreaker when priorities are identical). Every participating switch compares Bridge IDs, and the switch advertising the numerically lowest Bridge ID is elected root. In this exhibit, the three switches have distinctly different priority values — EX-1 at the Junos/IEEE default of 32768, EX-2 at 8192, and EX-3 at 16384 — meaning the comparison is decided entirely at the priority stage and never needs to proceed to a MAC address tiebreak at all. Since 8192 is numerically the lowest of the three priority values, EX-2 is elected root bridge purely on the strength of its lower priority, regardless of what its MAC address happens to be. This is precisely why the correct answer cites priority rather than MAC address as the deciding factor: MAC address only becomes relevant as a tiebreaker in the specific case where two or more switches share an identical priority value, which is not the situation presented here. Understanding that priority is evaluated first and is independently sufficient to decide the outcome whenever it differs is a foundational and heavily tested Spanning Tree concept on the JNCIS-ENT exam. Reference topics: Junos Enterprise Switching – Spanning Tree Protocols, Bridge ID and Root Bridge Election.

A GRE tunnel's outer, delivery-layer packets are forwarded using the router's ordinary underlay routing table, meaning the tunnel destination address (192.168.0.1 in this case) must itself be resolvable to a physical, non-tunnel next hop for the encapsulated packets to actually leave the router. Before this configuration change, the default route (or some more specific route) presumably pointed toward a real physical next hop, allowing the router to reach 192.168.0.1 and keep the tunnel operational. When the administrator commits a static default route of 0.0.0.0/0 with a next hop of gr-0/0/0, every destination lookup that previously fell back to the default route — including the lookup for the tunnel's own destination address, 192.168.0.1, since no more specific route exists for it — now recurses through the GRE interface itself. This creates a circular dependency: the router needs to route to 192.168.0.1 to keep the tunnel up, but the only route it has to reach 192.168.0.1 now points back into the tunnel that requires 192.168.0.1 to already be reachable, so the interface's next-hop resolution fails and the tunnel drops. This is an entirely valid and common GRE design pitfall rather than any platform restriction; GRE interfaces can be legitimately used as static route next hops, do not require loopback-sourced encapsulation, and do not require a /32 host route to resolve their destination, provided that route does not recursively point back through the tunnel. Reference topics: Junos Enterprise Routing – Tunneling, Route Recursion and GRE Tunnel Destination Resolution.

The L column in this output identifies which IS-IS levels are active on each interface, using the standard bitmask where 1 represents Level 1 only and 3 represents both Level 1 and Level 2 combined. Interface ge-0/0/2.0 shows an L value of 1 and its Level 2 DR field explicitly reads Disabled, meaning Level 2 has not been enabled on that circuit at all; consequently no Level 2 adjacency can ever form there, regardless of what the neighboring router advertises, which confirms that statement as correct. The lo0.0 loopback interface shows Passive under both the Level 1 DR and Level 2 DR columns. A passive IS-IS interface is deliberately excluded from adjacency formation — no IIH PDUs are sent or expected on it — but its associated prefix is still injected into the router's own LSP and flooded throughout the area, which is precisely why loopbacks are configured as passive: to guarantee the router ID/loopback prefix is reachable network-wide without wasting adjacency overhead on an interface with no real neighbor. This confirms that R3 advertises its loopback address, while ruling out the claim that the loopback is used to form an adjacency. Regarding designated routers, all circuits shown here report 'Point to Point' rather than an actual DR system ID, because DR election in IS-IS is a construct exclusive to broadcast (LAN) circuits; point-to-point circuits never elect a DR, so the first statement is false. Reference topics: Junos Enterprise Routing – IS-IS, Interface Levels and Passive Interfaces.

A native VLAN is a trunk-port concept, not an access-port concept. On an 802.1Q trunk, every frame is normally expected to carry a VLAN tag identifying its membership; the native VLAN is the single exception that Junos permits an administrator to define using the native-vlan-id statement under the trunk interface's family ethernet-switching hierarchy. Any untagged frame arriving on that trunk port is automatically classified into the configured native VLAN, and conversely, outbound frames belonging to the native VLAN are transmitted untagged rather than with an 802.1Q header. This behavior exists chiefly for interoperability with legacy or third-party devices that either cannot generate 802.1Q tags or intentionally send management or default traffic untagged across an otherwise tagged trunk. Access ports, by definition, only ever carry a single VLAN's traffic and never receive tagged frames in normal operation, so the native VLAN mechanism has no relevance there — which eliminates the access-port-oriented answer choices. The native VLAN also does not restrict a trunk to a single VLAN; the trunk continues to carry all configured tagged VLANs simultaneously, with the native VLAN simply being the designated untagged exception. Misconfiguring or mismatching native VLAN IDs between two trunk peers is a classic Layer 2 troubleshooting scenario on the exam. Reference topics: Junos Enterprise Switching – VLANs, Configuring the Native VLAN on a Trunk Interface.

The virtual-router routing-instance type in Junos is a general-purpose instance type intended for creating isolated, independent routing and forwarding contexts within a single physical device for applications that have nothing to do with MPLS-based VPN services — common use cases include multi-tenant network segmentation, filter-based forwarding deployments, and simple traffic isolation between departments or customers on a shared switch or router, all of which are non-VPN-related applications by nature. Layer 2 and Layer 3 VPN services, by contrast, rely on a different, dedicated routing-instance type specifically named vrf, which integrates with MPLS/BGP-based VPN signaling, route distinguishers, route targets, and PE-CE routing exchange; virtual-router instances do not participate in that VPN signaling framework at all, which is why the statement associating virtual-router with VPN use is incorrect. Whenever an administrator creates any user-configured routing instance — regardless of its specific type — Junos automatically allocates and generates a brand-new, dedicated routing table for that instance, named according to the pattern instance-name.inet.0 (or the appropriate address-family suffix), which is entirely separate from and independent of the default master inet.0 table used by the global/default routing context. Because each new routing instance receives its own distinct table rather than sharing or defaulting into the master inet.0 table, the statement claiming instances automatically fall back to using inet.0 unless configured otherwise is factually incorrect; instances are isolated by design from the outset. Reference topics: Junos Enterprise Routing – Protocol Independent Routing, Routing Instance Types and Table Allocation.

Configuring interface-type p2p under an OSPF interface tells Junos to treat that interface as a point-to-point network type regardless of the underlying physical medium, which removes the interface from the standard broadcast-network state machine entirely. On a true broadcast network, two routers must first complete a Designated Router and Backup Designated Router election, wait through the associated timers, and only then proceed through 2-Way, ExStart, Exchange, and Loading before reaching Full — a multi-step process. A point-to-point interface skips DR/BDR election altogether and proceeds directly from 2-Way into ExStart, so adjacencies form measurably faster, which is the first correct benefit. Because there is no DR on a point-to-point interface, Junos also does not generate a Type 2 Network LSA to describe the segment; the connected subnet is instead advertised as a simple stub-network entry inside the Router LSA itself, eliminating an entire LSA type from the area's link-state database and reducing its overall size, which is the second correct benefit. Point-to-point configuration is entirely incompatible with DR election, so a router configured this way cannot 'win' a DR election — there is no DR to win. Advertisement of the connected network happens on any operational OSPF interface irrespective of network type, so that option describes normal OSPF behavior rather than a benefit specific to the point-to-point setting. Reference topics: Junos Enterprise Routing – OSPF Network Types, Configuring OSPF Interface Type.

Junos firewall filters evaluate terms sequentially from top to bottom, and a term is only terminal for a packet if its then clause contains an explicit terminating action such as accept, discard, reject, or next term without a match. The count and log actions used in track-icmp are non-terminating; they update statistics and generate a log entry but do not stop evaluation, so a matching ICMP packet falls through to the next term after being counted. The second term, allow-tcp-established, matches only TCP packets carrying the ACK or RST flags as defined by the tcp-established keyword; an ICMP echo request does not satisfy protocol tcp, so this term is skipped entirely and does not accept the packet. Evaluation therefore reaches the implicit catch-all term block-rest, which has no from conditions and matches every remaining packet, incrementing blocked-counter and discarding it. The net effect for the described ICMP ping is that icmp-counter is incremented by the first term, the packet is neither accepted nor rejected by the second term, and blocked-counter is incremented immediately before the packet is silently discarded by the final term. This layered-term behavior, where counting is independent of the accept/discard decision, is a frequently tested nuance of Junos firewall filter processing logic. Reference topics: Junos Enterprise Switching – Layer 2 Security and Firewall Filters, Filter Term Evaluation Order.

OSPF neighbor state progression, as defined in RFC 2328 and displayed by Junos through show ospf neighbor, moves through a well-defined set of named states: Down, Attempt, Init, 2-Way, ExStart, Exchange, Loading, and Full. Down is the initial state, indicating no Hello packets have been recently received from a potential neighbor on that interface; it is a genuine, valid OSPF state and is correctly included here. Init indicates that a Hello packet has been received from the neighbor, but that neighbor has not yet listed the local router's own router ID within its Hello packet, so bidirectional communication has not yet been confirmed; this too is a standard, valid state. Loading occurs after the Exchange state, during which Database Description packets have been fully exchanged and the router is now actively requesting the specific, more-detailed LSAs it identified as missing or outdated from its neighbor via Link State Request packets; it is likewise a standard, valid OSPF neighbor state. 'Established' is not an OSPF state at all — that terminology belongs to BGP's finite state machine, where Established represents the fully operational session state; the OSPF equivalent concept is instead called Full. 'Reject' is not a recognized OSPF neighbor state under any circumstance and does not appear anywhere in the RFC 2328 state machine, making it an invalid distractor as well. Reference topics: Junos Enterprise Routing – OSPF, The OSPF Neighbor State Machine.