Juniper Updated JN0-281 Exam Questions and Answers by renzo

Link aggregation groups, implemented on Junos as aggregated Ethernet interfaces, allow multiple physical Ethernet links to operate as one logical Layer 2 interface. This increases available bandwidth and provides link level resiliency because member links can fail without taking down the logical interface, as long as at least one member remains operational. In data center leaf spine designs, link aggregation is commonly used for server dual homing, uplinks to appliances, or inter switch connectivity where parallel links are desired with a single logical adjacency.

From a forwarding perspective, the device distributes traffic across member links using a hashing algorithm based on packet header fields so that individual flows remain in order while the aggregate uses multiple links. Control plane operation can be static or negotiated with LACP. With LACP, both sides exchange protocol information to ensure consistent bundling and to remove failed or miswired members automatically. This makes link aggregation a core high availability building block at the link layer, independent of Routing Engine redundancy features.

Graceful Routing Engine switchover, nonstop bridging, and nonstop active routing are control plane redundancy features. They are designed to minimize disruption during Routing Engine failover or preserve protocol state, but they do not combine multiple physical Ethernet interfaces into one logical link layer interface.

Verification sources from Juniper documentation

https://www.juniper.net/documentation/us/en/software/junos/interfaces-ethernet/topics/topic-map/understanding-lacp.html

https://www.juniper.net/documentation/us/en/software/junos/interfaces-ethernet/topics/topic-map/aggregated-ethernet-interfaces-overview.html

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.

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.

On Junos-based Ethernet switching platforms used in data centers, Layer 2 forwarding is handled primarily in the forwarding plane. When a switch receives a frame, it first performs source MAC learning. If the source MAC address is not already present in the Ethernet switching table for that VLAN or bridge domain, the switch creates a new entry that maps the source MAC to the ingress interface and the associated VLAN context. This learning step is fundamental to building the MAC table dynamically and enables efficient forwarding for subsequent frames destined back to that source.

Next, the switch attempts to forward the frame based on the destination MAC lookup in the same VLAN or bridge domain. Because the destination MAC is also not in the Ethernet switching table, the frame is treated as an unknown unicast. The default behavior for unknown unicast in a Layer 2 broadcast domain is to flood the frame out all other interfaces that belong to that VLAN or bridge domain, excluding the ingress interface. Flooding ensures the frame has the best chance of reaching the correct destination host. When the destination responds, the switch then learns that MAC address as a source on the return traffic, allowing future traffic to be forwarded as known unicast instead of flooded.

The switch does not drop the frame by default, and it does not forward the frame to the Routing Engine because this is normal Layer 2 bridging behavior, not a control-plane routing decision.