Juniper Data Center Associate (JNCIA-DC) JN0-281 Exam Dumps: Updated Questions & Answers (March 2026)

To advertise OSPF-learned routes to BGP neighbors on Junos, you must explicitly control route redistribution using policy. Junos does not automatically redistribute routes between routing protocols simply because both protocols are enabled. Instead, you create a routing policy that matches the routes you intend to export, in this case routes whose protocol origin is OSPF. The policy must accept those matched routes so they become eligible for advertisement.

After the policy is created, you must apply it as an export policy under the relevant BGP group or under the BGP protocol hierarchy, depending on your design. Export policy controls what your router sends to BGP peers. When the export policy accepts OSPF routes, Junos advertises those routes to the BGP neighbors in that group, subject to any additional BGP constraints such as next-hop handling, route families, and any peer-specific policy terms.

Creating a policy to match and accept BGP routes is not required for this goal because that would influence what routes are imported into your routing table from BGP, not what you export. Likewise, applying a policy as a BGP import policy affects received routes, not OSPF-to-BGP redistribution. In data center fabrics, this policy-driven approach prevents unintended route leakage and keeps redistribution tightly scoped to the prefixes that must be carried between domains.

The diagram shows multiple autonomous systems, with each device labeled with a different AS number. Because the peers are in different autonomous systems, the correct BGP session type is external BGP. In a typical Juniper data center IP fabric underlay, this design is intentional: EBGP is used between leaf and spine devices to simplify policy boundaries, improve operational clarity, and avoid the additional mechanisms commonly required in large internal BGP designs.

In an EBGP-based underlay, neighbors are most commonly formed over the directly connected point-to-point links between leaf and spine. That means the BGP peering is established using the IP addresses configured on those physical routed interfaces, not loopback addresses. Using physically connected addresses aligns with the default EBGP behavior where the TTL is one hop, and it reduces configuration complexity because no multihop settings or additional reachability dependencies are required to bring up the session.

Peering using loopbacks is possible, but it typically requires EBGP multihop and a routing method to ensure reachability to the remote loopback before BGP can establish. That approach is more common for overlay control-plane sessions or for specific design requirements, rather than for the simplest and most common underlay implementation. Therefore, the two true statements are that the exhibit uses EBGP and that devices should peer using physically connected IP addresses.

Traditional data center networks are often built using a layered three-tier design with access, aggregation, and core. These designs frequently rely on Layer 2 domains and spanning tree to prevent loops. One major drawback is inefficient resource usage. Spanning tree typically blocks redundant links, which means installed bandwidth and expensive uplinks can sit idle during normal operation. To compensate, organizations overbuild capacity or use complex workarounds, raising cost and operational burden. In addition, scaling tends to be vertical, adding bigger chassis or more complex aggregation, which can concentrate risk and reduce flexibility.

Another common challenge is increased latency. In a three-tier model, traffic between servers in different access blocks often traverses multiple tiers, adding hops and delay. Even when traffic stays within the same facility, the path is not consistently short, and application performance can suffer, especially for east-west workloads such as distributed databases and microservices where frequent server-to-server communication is normal. Modern leaf spine IP fabrics reduce these issues by using a routed underlay with predictable one-spine-hop paths between leaves and by keeping all links active with multipath routing.

While traditional architectures can also experience suboptimal path behavior, the most consistently cited challenges are idle capacity due to blocked links and additional hop count that increases latency.

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.

When creating an IP fabric underlay using OSPF as the routing protocol, consistent interface speeds are important to ensure optimal traffic distribution and utilization of all links.

Step-by-Step Breakdown:

OSPF and Interface Speeds:OSPF calculates the cost of a link based on its bandwidth. The default cost calculation in OSPF is:

If interface speeds vary significantly, OSPF may choose paths with lower cost (higher bandwidth), resulting in some links being underutilized.

Equal Utilization:To ensure that all links are equally utilized in an IP fabric, it is recommended to maintain uniform interface speeds across the fabric. This ensures balanced load sharing across all available paths.

Juniper Reference:

IP Fabric with OSPF: Juniper recommends consistent interface speeds to maintain even traffic distribution and optimal link utilization in IP fabric underlay designs.

Nonstop active routing relies on control-plane state synchronization between the primary and backup Routing Engines so that routing protocol operation can continue across a switchover. To verify whether that synchronization is occurring and to see which protocol processes are participating, Junos provides visibility into the underlying replication framework. The command show task replication displays replication status and synchronization details for replicated tasks, which commonly include routing-related processes when NSR is enabled. This output helps confirm whether the backup Routing Engine is receiving the necessary state updates and whether replication is in sync, catching up, or experiencing issues.

This is the most direct operational validation because NSR effectiveness depends on ongoing state replication. Simply checking general switchover readiness does not prove protocol state is synchronized. Likewise, listing system services does not confirm replication or identify which routing protocols are actively supported for nonstop behavior. High availability statistics under services are oriented toward service-specific HA functions and do not provide the routing protocol replication view that NSR troubleshooting typically requires.

In data center fabrics where underlay routing stability is critical, routinely checking task replication status is a practical way to verify that NSR is actually providing the intended resilience before you perform maintenance or experience an unplanned Routing Engine event.

Verification sources from Juniper documentation

https://www.juniper.net/documentation/us/en/software/junos/high-availability/topics/topic-map/nonstop-active-routing-understanding.html

https://www.juniper.net/documentation/us/en/software/junos/high-availability/topics/reference/command/show-task-replication.html

The configuration shown is under protocols bgp and defines a BGP group named service-pod with the statement type internal. In Junos, the BGP group type determines whether the sessions formed by neighbors in that group are treated as internal BGP or external BGP. When the group is set to type internal, the router establishes an iBGP session to the configured neighbor address. That means both peers are expected to be in the same autonomous system, and the session is used to exchange routes within that single AS.

The local-address statement sets the source address that the router will use when initiating the TCP connection for BGP. In data center designs, this is commonly a loopback address so the session can be resilient and independent of any single physical interface. The neighbor statement identifies the remote peer address. With type internal, the session is iBGP even if the neighbor is directly connected, because the relationship is defined by AS scope rather than topology.

OSPF and IS-IS are different routing protocols entirely and are not established through BGP configuration. EBGP would require type external and typically involves different AS numbers across the peering. Therefore, the only correct answer is IBGP.

The exhibit shows BFD liveness detection configured under a BGP group with minimum-interval set to 1000 milliseconds. In Junos, BFD provides rapid failure detection by sending periodic BFD control packets between neighbors. The minimum-interval value is the negotiated minimum transmit and receive interval used for BFD control packets for that session. A neighbor is declared down when the local system fails to receive a certain number of consecutive BFD packets within the expected time window.

That time window is determined by the BFD detection time, which is calculated as the minimum-interval multiplied by the BFD multiplier. The multiplier represents how many BFD control packets can be missed before the session is considered failed. If the multiplier is not explicitly configured, Junos uses the default multiplier value of 3. Therefore, with minimum-interval set to 1000 ms and the default multiplier of 3, the detection time becomes 3000 ms. After approximately 3 seconds without receiving the expected BFD control packets, the BFD session transitions to down and BGP can react by treating the associated peer as unreachable for fast convergence.

This behavior is commonly used in data center underlays and EVPN fabrics to reduce convergence time compared to relying only on BGP hold timers.

To intentionally drop traffic to a specific destination while also informing the sender that the destination is unreachable, Junos provides a routing action specifically meant for this behavior: a static route with a next hop of reject. A reject route installs a forwarding entry that causes matching packets to be dropped, and it also triggers generation of an ICMP unreachable message back to the traffic source. This is useful in data center routing for controlled blackholing with feedback, for example when you want to signal misrouted traffic, invalid destinations, or to enforce policy with explicit notification.

A discard route also drops packets, but it does so silently without sending ICMP unreachable messages. That makes discard appropriate for traffic-sink use cases such as safe summarization or DDoS mitigation where you do not want to generate return traffic. Adding addresses to martians is intended to block invalid special-use prefixes from being treated as routable, not to create a targeted unreachable response for an arbitrary destination. Using inet.3 is related to MPLS label-switched forwarding and does not address the requirement. A firewall filter that discards traffic will typically drop silently unless explicitly configured to send rejects in a security context, and it is not the standard routing-table-based method when the requirement is an ICMP unreachable response for a destination prefix.

Therefore, a reject static route is the correct solution.

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.