Free Practice Questions for the Juniper JNCIA-DC JN0-280 Exam (2026 Updated)

When an OSPF (Open Shortest Path First) neighborship is stuck in the ExStart state, it usually points to a mismatch in Maximum Transmission Unit (MTU) settings between two routers trying to establish the adjacency. The ExStart state is where OSPF routers negotiate the master-slave relationship and exchange DBD (Database Description) packets.

Step-by-Step Breakdown:

OSPF Neighbor States : OSPF goes through several states to establish an adjacency with a neighbor:

Down : No hello packets have been received.

Init : Hello packets are received, but bidirectional communication isn't confirmed.

2-Way : Bidirectional communication is established.

ExStart : The routers are negotiating who will be the master and who will be the slave, and begin to exchange DBD packets.

Exchange : The routers start exchanging the database information.

Loading : The routers process the Link-State Advertisements (LSAs).

Full : The adjacency is fully established.

MTU Mismatch Issue : During the ExStart state, both OSPF routers must agree on their MTU values. If there is an MTU mismatch between the two routers, OSPF neighbors will fail to move from the ExStart to the Exchange state. The router with the larger MTU setting will not accept DBD packets from the router with a smaller MTU because the packets may exceed the smaller MTU size.

In Juniper devices, this behavior can be identified by examining the MTU settings using the show interfaces command and ensuring both routers have matching MTU configurations. To resolve this issue, either match the MTU settings on both routers or configure OSPF to ignore MTU mismatches using the command set protocols ospf ignore-mtu.

Juniper Reference:

Junos Command : show ospf neighbor helps diagnose neighbor states.

MTU Adjustment : set interfaces < interface-name > mtu < size > can be used to set the MTU values correctly.

Comprehensive Detailed Step by Step Explanation with all Juniper Data Center References

Layer 2 interfaces on a switch operate in two key modes: Access and Trunk .

Step-by-Step Breakdown:

Access Mode :

Access ports are used to connect end devices, like PCs or servers, and they are assigned to a single VLAN. These interfaces handle untagged traffic and do not pass VLAN tags.

Example: A port assigned to VLAN 10 will only handle traffic for that VLAN.

Trunk Mode :

Trunk ports are used to connect switches or other networking devices that need to handle traffic from multiple VLANs. Trunk interfaces carry tagged traffic, allowing multiple VLANs to traverse the same physical link.

Trunk ports typically use 802.1Q VLAN tagging to differentiate between VLANs.

Juniper Reference:

Access and Trunk Ports : Juniper switches use these modes to manage VLAN traffic at Layer 2, with access ports handling untagged traffic and trunk ports handling tagged traffic from multiple VLANs.

Each port on a modern switch creates a separate collision domain . This allows multiple devices to communicate simultaneously without collisions on different ports.

Step-by-Step Breakdown:

Collision Domain :

A collision domain is a network segment where data packets can collide if two devices send packets simultaneously.

On a switch, each port creates a separate collision domain , so collisions only occur if two devices connected to the same port (through a hub, for instance) try to send data at the same time.

Switches vs Hubs : Unlike hubs, which have one large collision domain, switches isolate collisions to individual ports, improving performance.

Juniper Reference:

Switch Port Behavior : In Juniper switches, each port operates in its own collision domain, enhancing network efficiency by reducing the chances of packet collisions.

IBGP (Internal Border Gateway Protocol) is used to exchange routing information between routers within the same AS (Autonomous System).

Step-by-Step Breakdown:

TTL of 255 :

By default, IBGP sessions are established with a TTL (Time to Live) value of 255 . This allows IBGP neighbors to communicate over multiple hops within the AS without requiring any additional configuration.

Full Mesh Requirement :

IBGP requires a logical full mesh between all IBGP routers to ensure that routing information is fully distributed within the AS. Since IBGP does not propagate routes learned from one IBGP peer to another by default, a full mesh topology is needed unless route reflectors or BGP confederations are used.

Juniper Reference:

IBGP Full Mesh : Juniper recommends using route reflectors in large networks to simplify IBGP full-mesh requirements.

In the exhibit, we see a static route configuration with two possible next hops for the default route (0.0.0.0/0):

next-hop 172.25.20.254 with the default preference of 7.

qualified-next-hop 172.25.20.200 with a preference of 6.

Step-by-Step Breakdown:

Preference Value : In Junos OS, the preference value is used to determine which route should be preferred in the routing table. The lower the preference value, the higher the priority for the route.

Comparison : In this case:

The next hop 172.25.20.254 has a preference of 7 .

The qualified-next-hop 172.25.20.200 has a preference of 6 .

Preferred Next Hop : Since 172.25.20.200 has a lower preference (6) compared to 172.25.20.254 (7), it will be the preferred next hop in the routing table, assuming both next hops are reachable.

Juniper Reference:

Qualified Next Hop : In Junos, static routes with multiple next-hop options are selected based on the preference value , with the lower value being preferred.

In Junos OS, direct routes are the most preferred routes in the routing table, having the highest priority.

Step-by-Step Breakdown:

Direct Routes :

Direct routes represent networks that are directly connected to the router's interfaces. Since these routes are directly accessible, they are assigned the highest priority and always take precedence over other types of routes.

Preference Values :

Direct routes have a preference of 0 , which is the most preferred in Junos. Static routes, OSPF routes, and BGP routes have higher preference values and will only be used if there are no direct routes to the destination.

Juniper Reference:

Direct Route Preference : In Junos, direct routes are always preferred over other routes, ensuring that the router forwards traffic through locally connected networks.

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:

A black text on a white background Description automatically generated

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.

To verify that your router is learning routes from a remote BGP peer at a specific IP address (e.g., 10.10.100.1), the correct command to use is show route receive-protocol bgp.

Step-by-Step Breakdown:

BGP Route Learning : The show route receive-protocol bgp command displays the routes that have been received from a specified BGP peer. This helps in confirming that the remote peer is sending routes correctly and that your router is receiving them.

Command Example :

show route receive-protocol bgp 10.10.100.1

This will show all routes that have been received from the BGP peer with IP address 10.10.100.1.

Juniper Reference:

BGP Route Verification : Use this command to troubleshoot and verify that routes from a specific BGP peer are being received.

When creating a LAG (Link Aggregation Group) in Junos, the duplex settings and link speed must be the same across all member interfaces.

Step-by-Step Breakdown:

LAG Overview : A LAG combines multiple physical interfaces into a single logical interface to increase bandwidth and provide redundancy. All member links must act as a single cohesive unit.

Interface Requirements :

Duplex : All member interfaces must operate in the same duplex mode (either full-duplex or half-duplex). Mismatched duplex settings can cause performance issues, packet drops, or interface errors.

Link Speed : All interfaces in the LAG must have the same link speed (e.g., all interfaces must be 1 Gbps or 10 Gbps). Mismatched speeds would prevent the interfaces from functioning correctly within the LAG.

Configuration and Validation : Ensure that all member interfaces have identical settings before adding them to the LAG. These settings can be checked using the show interfaces command, and the LAG can be configured using:

set interfaces ae0 aggregated-ether-options link-speed 10g

set interfaces ge-0/0/1 ether-options 802.3ad ae0

Juniper Reference:

LAG Configuration : Duplex and link speed must be consistent across member interfaces to ensure proper LAG operation in Juniper devices.

Graceful Restart (GR) is a feature that allows a router to maintain forwarding even when the routing process (e.g., the rpd process in Junos) is restarting, minimizing disruption to the network.

Step-by-Step Breakdown:

Graceful Restart Function : During a GR event , the forwarding plane continues to forward packets based on existing routes, while the control plane (rpd process) is restarting. This prevents traffic loss and maintains routing stability.

Minimizing Disruptions : GR is particularly useful in ensuring continuous packet forwarding during software upgrades or routing protocol process restarts.

Juniper Reference:

Graceful Restart in Junos : GR ensures high availability by maintaining forwarding continuity during control plane restarts, enhancing network reliability.

In IBGP (Internal Border Gateway Protocol) , all routers within the same AS (Autonomous System) must have a logical full-mesh topology. This means that every IBGP router must be able to communicate with every other IBGP router directly or indirectly to ensure proper route propagation.

Step-by-Step Breakdown:

Logical Full Mesh :

In an IBGP setup, routers do not re-advertise routes learned from one IBGP peer to another IBGP peer. This rule is in place to prevent routing loops within the AS.

To ensure full route propagation, a logical full mesh is required, meaning every IBGP router must peer with every other IBGP router in the AS. This can be done either directly or via route reflection or confederation.

Physical Full Mesh Not Required : The physical topology does not need to be a full mesh, but the BGP peering relationships must form a logical full mesh. Techniques like route reflectors or BGP confederations can reduce the need for manual full-mesh peering.

Juniper Reference:

IBGP Configuration : IBGP logical full mesh requirements can be simplified using route reflectors to avoid the complexity of manually configuring many IBGP peers.

OSPF (Open Shortest Path First) calculates the best path based on the cost of the route, which is derived from the bandwidth of the interfaces along the path.

Step-by-Step Breakdown:

OSPF Path Selection :

OSPF assigns a cost to each link, typically based on the link's bandwidth (higher bandwidth equals lower cost).

The OSPF algorithm computes the shortest path to a destination by adding the costs of all links in the path. The path with the numerically lowest total cost is chosen as the best path.

Cost Calculation : The OSPF cost can be manually adjusted or automatically calculated using the default formula:

Cost=Reference BandwidthLink Bandwidth\text{Cost} = \frac{\text{Reference Bandwidth}}{\text{Link Bandwidth}}Cost=Link BandwidthReference Bandwidth​

Juniper Reference:

OSPF Best Path Selection : OSPF selects the path with the lowest cumulative cost, ensuring efficient use of higher-bandwidth links in Junos networks.

In the exhibit, BGP is configured with local AS 65101 and a neighbor at 172.16.1.1 in peer AS 65201 . This setup involves two different Autonomous Systems (AS), indicating an External BGP (EBGP) configuration.

Step-by-Step Breakdown:

EBGP vs. IBGP :

EBGP is used between routers in different ASes. In this case, the local AS is 65101 and the peer AS is 65201 , meaning the BGP session is EBGP .

IBGP is used between routers within the same AS, which is not applicable here as the AS numbers are different.

BGP Group Configuration :

The configuration does not require a type external parameter because Junos OS automatically recognizes the session as EBGP when the local and peer AS numbers are different.

The BGP session will operate as EBGP, and the configuration will commit successfully.

Juniper Reference:

BGP Configuration : In Juniper, EBGP is automatically recognized when the local and peer AS numbers differ, without needing to specify type external.

When configuring an aggregate route , you have options for how to handle traffic that matches the route but does not match any more specific route in the routing table. Two actions can be taken: discard and reject .

Step-by-Step Breakdown:

Discard :

The discard option will silently drop packets that match the aggregate route. No notification is sent to the sender, and the packet is simply dropped.

Reject :

The reject option will drop the packet and also send an ICMP Destination Unreachable message back to the sender. This informs the sender that the packet could not be delivered because there is no specific route available.

Juniper Reference:

Aggregate Routes : The reject and discard next-hop options provide different levels of feedback when packets cannot be routed, and they can be used to control how unreachable destinations are handled.

In the exhibit, the ae0 and ae1 interfaces are in a link down state. This occurs when no physical interfaces (member interfaces) have been added to the LAG (Link Aggregation Group) interfaces, or the member interfaces are not operational.

Step-by-Step Breakdown:

LAG Configuration : A LAG interface (aggregated Ethernet interface) is a logical interface that combines multiple physical interfaces for redundancy and increased bandwidth. The LAG will only be operational if at least one member interface is active and configured correctly.

No Operational Member Interfaces : If no member interfaces are added or if the member interfaces are down, the LAG will remain in a down state, as shown in the exhibit for ae0 and ae1.

Resolution : Verify that physical interfaces have been added to the LAG using commands like:

LAG Interface Status : In Juniper, the link status of the LAG depends on its member interfaces, which must be operational for the LAG to function.

The BGP AS (Autonomous System) path attribute is crucial in path selection and loop prevention. Each BGP router appends its local AS number to the beginning of the AS path when it advertises a route to an external BGP (eBGP) peer.

Step-by-Step Breakdown:

AS Path Attribute : The AS path is a sequence of AS numbers that a route has traversed to reach a destination. Each AS adds its number to the front of the path, allowing BGP to track the route’s history.

Why the Local AS is Added at the Beginning : When advertising a route to an eBGP neighbor, a BGP router adds its own AS number to the beginning of the AS path. This ensures that the AS path reflects the route's journey accurately from the origin to the destination, and prevents loops in BGP. If the route returns to the same AS, the router will detect its AS number in the path and reject the route, preventing routing loops.

Order of the AS Path : The order is significant because BGP uses it to select the best path. A shorter AS path is preferred, as it indicates fewer hops between the source and destination.

Juniper Reference:

AS Path Attribute : Junos devices append the local AS at the start of the AS path before advertising the route to an external peer.