A five-stage IP fabric is typically used when a single pod, even with a three-stage design, cannot meet overall scale requirements for port count, bandwidth, or modular growth. In this model, the data center is built from multiple fabric pods, where each pod is commonly a three-stage topology that includes leaf switches and one or more spine layers. The superspine layer provides the interconnect that ties these pods together into a larger fabric. Functionally, superspines create high-capacity, routed connectivity between the spine layers of different pods so that endpoints in any pod can reach endpoints in any other pod using consistent Layer 3 forwarding principles and equal-cost multipath behavior where applicable.

Option D is correct because the superspine layer is the aggregation and inter-pod transit layer. It does not exist to force every leaf to connect to every spine across the entire multi-pod deployment. That full mesh property is preserved within a pod, not across the entire site at extreme scale. The superspine layer also does not create a Layer 2 underlay; modern fabrics use a routed underlay to avoid spanning tree limitations and to enable deterministic multipathing. Finally, the superspine layer is not defined by creating a single common BGP autonomous system; autonomous system design is a policy choice, while the superspine role is a physical and logical interconnection function between pods.

Nonstop active routing is the Junos high availability capability that focuses on preserving routing protocol operation and routing information across a Routing Engine switchover. In platforms with redundant Routing Engines, a failure of the primary Routing Engine can otherwise reset routing protocol processes, tear down adjacencies, and trigger reconvergence. NSR mitigates this by synchronizing routing protocol state so that the backup Routing Engine can continue routing protocol operations with minimal disruption. This includes maintaining protocol session continuity and keeping the routing information base stable, which directly protects traffic that depends on those routes.

In data center environments, this is particularly important for routed fabrics where BGP or OSPF underlay reachability supports overlay services and east west application traffic. By keeping routing information consistent during the control-plane transition, NSR reduces route churn and helps avoid transient blackholing or microbursts caused by reconvergence.

GRES is closely related but addresses a different scope. GRES helps the forwarding plane continue forwarding during a Routing Engine switchover by preserving certain system and interface states. However, GRES alone does not guarantee that routing protocol sessions and routing information remain uninterrupted. BFD and LACP are valuable availability tools, but they are not Routing Engine redundancy features and do not preserve routing state during a Routing Engine failover.

On broadcast network types in OSPF, such as Ethernet segments, forming a full mesh of adjacencies between every pair of routers would create significant control-plane overhead. Every router would need to maintain neighbor state with every other router, exchange database information redundantly, and flood link-state updates across many parallel adjacencies. This becomes inefficient as the number of routers on the segment grows.

To address this, OSPF elects a Designated Router and a Backup Designated Router. The DR acts as the central point for adjacency formation on that broadcast segment. Instead of each router forming full adjacencies with all others, routers form full adjacencies primarily with the DR and BDR. The DR is responsible for generating and flooding network LSAs that represent the broadcast segment and for coordinating reliable LSA flooding on that segment. This significantly reduces the number of adjacencies and the volume of duplicated database exchange and LSA flooding, which is why option A is correct.

The BDR is a standby control-plane role. It monitors the segment and is prepared to take over the DR function if the DR fails, improving stability and convergence. However, the primary purpose of having DR and BDR is the scaling benefit of reduced adjacency and flooding overhead on broadcast networks.

On Junos Ethernet switching, access and trunk ports serve different purposes and therefore treat VLAN tags differently by default. An access port is intended for a single VLAN and is designed to connect to endpoints that do not tag their frames. Because of that, access ports forward traffic as untagged on the wire and internally associate those untagged frames to the configured access VLAN. This makes access ports the standard choice for single-VLAN server NICs, management devices, and any endpoint expecting a plain Ethernet connection.

A trunk port is intended to carry traffic for multiple VLANs over a single link, which is typical for switch-to-switch uplinks, leaf-to-spine connectivity where VLAN services are extended, and hosts or appliances that use VLAN tagging. By default, trunk ports forward tagged traffic and require VLAN tags to identify the VLAN membership of each frame. Untagged behavior on a trunk is not assumed by default and is typically governed by configuring a native VLAN or equivalent untagged VLAN handling, depending on platform and design. Without such configuration, untagged frames are not treated as a normal expected case for a trunk link in data center fabrics.

Therefore, the correct default statements are that access ports forward untagged traffic and trunk ports forward tagged traffic, matching options B and D.

Nonstop active routing is the Junos high availability feature designed to keep routing protocol operation and routing information continuous across a Routing Engine switchover on platforms with redundant Routing Engines. With NSR enabled, the control-plane routing state is replicated so that protocol sessions and routing information can remain stable when the device transitions from the primary to the backup Routing Engine. The goal is a transparent switchover that minimizes or eliminates routing reconvergence caused by a Routing Engine failure.

This is especially important in data center environments where routing stability underpins EVPN VXLAN control-plane operation, underlay BGP or OSPF adjacencies, and service reachability. By maintaining the routing protocol process state across the switchover, NSR helps prevent neighbor resets and reduces churn in the routing table, which directly protects application traffic paths from disruption that would otherwise occur during a control-plane restart.

GRES is closely related but has a different focus: it preserves forwarding and certain kernel and interface states so that packet forwarding can continue, but by itself it does not preserve the full routing protocol control plane. That is why NSR is the best match when the requirement explicitly includes routing information continuity in addition to traffic continuity. LACP and BFD are valuable availability tools, but they address link bundling and fast failure detection, not Routing Engine stateful failover.

Nonstop bridging is a high availability capability focused on maintaining Layer 2 switching continuity during a Routing Engine switchover on platforms that support redundant control planes. The intent is to keep Layer 2 forwarding operational and minimize disruption to bridged traffic when the system transitions from a primary to a backup Routing Engine. Achieving this requires Graceful Routing Engine switchover, because GRES is the mechanism that enables a control plane switchover while keeping forwarding and interface state stable. With GRES in place, the forwarding plane can continue switching frames while the backup Routing Engine assumes control, reducing or eliminating traffic loss for Layer 2 domains.

Nonstop bridging is not the feature that preserves Layer 3 protocol sessions and routing information end-to-end. That function is associated with nonstop routing capabilities, which focus on maintaining routing protocol state across Routing Engine events. Therefore, stating that nonstop bridging preserves Layer 3 information and protocol sessions is incorrect. Likewise, nonstop active routing is not a requirement for nonstop bridging; it is a separate feature aimed at routing stability. The flow-control setting under gigether-options is unrelated to Routing Engine redundancy and does not determine whether nonstop bridging operates.

In data center access and aggregation environments where VLANs must remain stable for servers and appliances, nonstop bridging paired with GRES helps protect Layer 2 service continuity during control plane events.

In Junos Ethernet switching, a trunk interface is intended to carry multiple VLANs using 802.1Q tags. The native VLAN ID feature defines how the trunk handles frames that arrive without an 802.1Q tag and how it can transmit untagged frames when required. When a native VLAN is configured on a trunk, untagged inbound frames are mapped into the native VLAN’s Layer 2 broadcast domain. Likewise, traffic belonging to the native VLAN can be sent untagged on that trunk, depending on how the receiving device expects to process untagged frames. This is commonly used in data center environments to interoperate with devices that require one VLAN to be carried untagged, or for specific control-plane or legacy connectivity requirements.

Option A is incorrect because native VLAN does not restrict the trunk to tagged-only traffic; it explicitly provides a mechanism to accept or emit untagged frames on a trunk. Option B is incorrect because access ports are designed for a single VLAN and normally treat traffic as untagged by default; they do not become “tagged access” by using native VLAN. Option C is incorrect because native VLAN does not change the VLAN ID range; VLAN ID ranges are determined by the 802.1Q standard and platform support, not by the native VLAN feature.

Qualified next hop is the Junos mechanism that lets you configure more than one next hop for the same static route and control which one is preferred. This is most commonly used to build primary and backup forwarding behavior with deterministic selection. You configure a primary next hop and then add one or more qualified next hops with a different preference value. The route installs the best, lowest preference next hop as active, while keeping the alternate next hop available as standby. If the primary next hop becomes unusable, Junos can switch to the qualified next hop so traffic continues to flow.

This approach is widely used in data center edge and services routing, for example toward management networks, service appliances, or external gateways where you want a static default or summary route with predictable failover. It is not the same as resolving a non-directly-connected next hop. That scenario is handled by recursive resolution behavior, not by qualification. Qualified next hop also does not depend on any specific routing protocol, and it is not limited to link-state environments.

Finally, qualified next hop does not rely on sending pings to test reachability. Health tracking can be achieved through other mechanisms such as interface state, next hop resolution changes, or integration with failure detection features, but the qualified next hop feature itself is about preference-ranked redundancy for static routes.

In the exhibit, we see two next-hop addresses for the default static route (0.0.0.0/0):

The first next hop is 172.25.11.254 , with no specified preference.

The second next hop is 172.25.11.200 , with a specified preference of 140 .

Step-by-Step Breakdown:

Default Static Route Preference : If no preference is explicitly set for a next hop in Junos, it defaults to 5 for static routes.

Determining Preference : In this case, the next hop 172.25.11.254 does not have an explicit preference defined, so it will use the default value of 5 . The second next hop has a preference of 140 , which is higher, meaning it will only be used if the primary next hop is unavailable.

Juniper Reference:

Static Route Preference : In Junos, the default preference for static routes is 5 , and this value is applied unless overridden by the preference parameter.

An IP fabric underlay is the routed foundation of a modern leaf-spine data center. Its purpose is to provide scalable, deterministic Layer 3 reachability between all fabric nodes, typically using point-to-point routed links between leaves and spines. In this design, EBGP is commonly used as an underlay routing protocol because it scales well, supports clear policy boundaries, and enables fast convergence and operational simplicity. Each leaf forms EBGP sessions to each spine, advertising loopback addresses and link subnets so that overlay endpoints and control plane services can reach one another reliably.

RSTP is a Layer 2 spanning tree mechanism and is not the standard protocol for a routed underlay. EVPN is an overlay control plane used to distribute tenant reachability and multihoming information; it is not the underlay routing protocol itself. VXLAN is a data plane encapsulation used by the overlay to transport Layer 2 segments across a Layer 3 fabric; it also is not the underlay routing protocol.

In Juniper data center architectures, the underlay is intentionally kept simple and purely routed, while overlays such as EVPN VXLAN deliver multi-tenant Layer 2 and Layer 3 services on top of that underlay. EBGP fits the underlay requirement among the provided options.