JN0-352 Exam Dumps - Juniper JNCIS-ENT Questions and Answers

In this configuration, R1's physical interface address (10.10.10.1) is different from the VRRP virtual IP address (10.100.100.1), meaning R1 is operating as a non-owner VRRP master — it did not originate the virtual address as one of its own real interface addresses. By default, Junos VRRP masters that do not own the virtual address will forward transit traffic destined through that address but will not process or respond to traffic addressed directly to the VIP itself, such as ICMP echo requests, Telnet, or SSH sessions aimed at 10.100.100.1. This is deliberate default behavior intended to prevent ambiguity about which physical device is answering on behalf of a shared virtual identity. To allow the master to accept and respond to packets whose destination is the virtual address itself, the accept-data statement must be explicitly configured under the vrrp-group hierarchy. Once enabled, the elected master will process locally destined traffic sent to the VIP, resolving exactly the symptom described. The track option is used for interface or route-based priority adjustment to influence mastership, advertise-interval tunes the frequency of VRRP hello advertisements, and no-preempt prevents a higher-priority router from reclaiming mastership once a lower-priority router has taken over — none of these affect whether the master processes traffic destined to the VIP. Reference topics: Junos Enterprise Routing – High Availability, VRRP accept-data Behavior.

Root bridge election is based on comparing each switch's full Bridge Identifier, which combines the bridge priority value with the switch's MAC address, with priority always evaluated first and MAC address serving strictly as a tiebreaker when two or more switches present identical priority values. In this scenario, the network has been left entirely at the default spanning-tree configuration, meaning every switch is operating at the standard IEEE and Junos default bridge priority of 32768; since all three switches share the exact same priority value, the comparison necessarily falls through to the MAC address tiebreak, where the switch with the numerically lowest MAC address wins the election. Comparing the three addresses shown — 00:1a:2b:3c:4d:01, 00:1a:2b:3c:4d:02, and 00:1a:2b:3c:4d:03 — Switch A's address is the lowest, since only the final octet differs and 01 is less than both 02 and 03, making Switch A the elected root bridge. RSTP uses the identical Bridge ID comparison mechanism as legacy STP for root election, so there is no special 'median MAC address' rule that applies uniquely under RSTP, making that distractor factually invalid regardless of protocol version. The election process also does not require any manual bridge priority configuration to complete; the default priority value is entirely sufficient on its own to allow a deterministic election to occur, since default priorities are still numerically comparable Bridge IDs. Reference topics: Junos Enterprise Switching – Spanning Tree Protocols, Default Priority and MAC Address Tiebreaking.

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.

The show spanning-tree bridge command is specifically designed to surface exactly the two pieces of information required in this scenario within a single output. Its Root ID field reports the full Bridge Identifier (priority and MAC address) of whichever switch has been elected root bridge for the spanning-tree instance in question, immediately answering which switch in the campus network is currently acting as root, regardless of whether that happens to be the local device or a remote one. In the same output, the command's Root port field explicitly names the specific local interface (for example, ge-0/0/1.0) that the local switch has selected as its path toward that root bridge, directly answering the second part of the requirement without needing to cross-reference a separate command. Together, these two fields give a complete, immediate picture of both root bridge identity and local root port selection from one operational command. show spanning-tree interface instead presents a per-interface breakdown of STP role (root, designated, alternate, backup) and state across all local ports, which can indirectly reveal the root port by looking for the 'Root' role, but it does not directly report the Root ID/root bridge identity in the same structured way that show spanning-tree bridge does. show ethernet-switching table and show ethernet-switching interface pertain entirely to MAC address learning and switching-specific interface configuration respectively, and neither surfaces any spanning-tree topology or root bridge information at all. Reference topics: Junos Enterprise Switching – Spanning Tree Protocols, Verifying Root Bridge and Root Port with show spanning-tree bridge.

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.

This scenario describes end hosts — virtualization hosts running software switches or virtual bridging stacks — unexpectedly generating and transmitting BPDUs on ports that are supposed to be pure edge (host-facing) ports where no BPDUs should ever legitimately be received. BPDU protection (BPDU guard) is the Junos feature purpose-built for exactly this situation: when applied to an edge-designated interface, it continuously monitors that port for any incoming BPDU, and the moment one is detected, it immediately and automatically disables the port, preventing the unexpected BPDU source from ever participating in or influencing the spanning-tree topology calculation, thereby protecting the stable, intended topology from disruption caused by unauthorized or accidental BPDU generation at the access edge. This directly and precisely resolves the described problem at its source, since the root cause is illegitimate BPDUs arriving on ports that were never meant to see them. Increasing the max-age timer only adjusts how long stale topology information is retained before being aged out and has no effect on preventing rogue BPDUs from being processed in the first place. Disabling RSTP outright on access interfaces would eliminate spanning tree's loop-prevention protection on those ports entirely, introducing a much more severe risk of undetected Layer 2 loops. Root protection (root guard) defends specifically against a port attempting to become the root port by receiving a superior BPDU claiming a better path to root; it addresses a different threat model than blocking any BPDU outright on a true edge port. Reference topics: Junos Enterprise Switching – Spanning Tree Protocols, BPDU Protection on Edge Interfaces.

The destination address 172.16.200.5 falls within the 172.16.0.0/16 aggregate's summarized range but does not fall within either of the two active, more-specific contributing routes actually present in the table — 172.16.10.0/24 and 172.16.99.0/24 — meaning no route more specific than the /16 itself exists to cover it. Under Junos's longest-match forwarding logic, the lookup for 172.16.200.5 therefore resolves to the aggregate route itself, and since aggregate routes are installed by default with a reject next hop rather than any real forwarding path, the router drops the packet and simultaneously generates an ICMP destination-unreachable message back to the originating source, explicitly signaling that no valid path exists for that specific destination even though a covering summary is being advertised. This reject behavior is precisely why aggregate routes are valuable for reducing the number of routes advertised upstream while still providing clear, immediate feedback for traffic aimed at address space within the summary that has no genuine underlying route, rather than silently black-holing it or misdirecting it toward an unrelated contributing route's next hop. The aggregate route itself remains active and installed throughout this process — a gap in contributing coverage does not deactivate the aggregate, since the aggregate's activation depends only on at least one contributing route being active, which is satisfied here by both existing /24 blocks. There is also no default route present in this scenario to fall back upon. Reference topics: Junos Enterprise Routing – Protocol Independent Routing, Aggregate Route Reject Behavior for Uncovered Address Space.

IS-IS (Intermediate System to Intermediate System) was designed by ISO as a link-state Interior Gateway Protocol for routing within a single autonomous system, functioning on a hierarchical two-level model conceptually similar to OSPF's areas, which makes the first statement unambiguously correct. Within that hierarchy, Level 1 routers maintain detailed topology information only for their own local area and use a default route toward the nearest Level 2 or Level 1/Level 2 router to reach destinations outside the area; they explicitly do not carry inter-area topology information and therefore cannot route traffic between areas on their own. Routers that participate in both levels simultaneously — Level 1/Level 2 (L1/L2) routers — sit at the area boundary, maintaining a Level 1 database for their local area and a Level 2 database for the backbone, and it is specifically these dual-level routers that stitch inter-area traffic together, forwarding packets from the local area into the Level 2 backbone and vice versa, which confirms the second correct statement. Regarding route preference, Junos assigns distinct default preference (administrative distance) values of 15 for IS-IS Level 1 routes and 18 for IS-IS Level 2 routes — neither of which is 20 — so the preference-value statement is factually incorrect and included as a distractor testing precise knowledge of Junos default protocol preferences. Reference topics: Junos Enterprise Routing – IS-IS, Level 1, Level 2, and L1/L2 Router Roles; Default Route Preference Values.

BGP employs two distinct loop-prevention mechanisms depending on whether peers are external or internal to the same autonomous system. Between external peers (EBGP), loop prevention relies on the AS path attribute: every time a route crosses an AS boundary, the local AS number is prepended to the path, and a router rejects any incoming route whose AS path already contains its own AS number, since that would indicate the route has looped back around. Between internal peers (IBGP) within the same AS, however, the AS path attribute never changes, because IBGP does not add AS numbers as routes are readvertised internally — meaning AS path alone cannot detect an internal loop. Instead, IBGP enforces a strict split-horizon-style rule: a router that learns a route via IBGP must never readvertise that route to another IBGP peer. This rule guarantees that every IBGP speaker within the AS must be directly peered with every other IBGP speaker (a logical full mesh) in order for all routers to receive all routes, since no IBGP router will relay IBGP-learned routes onward on another router's behalf. This full-mesh requirement is precisely why techniques such as route reflection and confederations were later developed — they preserve the same loop-prevention guarantee while relaxing the physical full-mesh peering burden. VRRP and BFD serve entirely unrelated purposes (gateway redundancy and fast failure detection, respectively) and play no role in BGP loop prevention. Reference topics: Junos Enterprise Routing – BGP, IBGP Split-Horizon and the Full-Mesh Requirement.