Free Data Center Associate (JNCIA-DC) Practice Questions

In Junos routing and security contexts, martian addresses are IP prefixes that should not appear as valid, routable sources or destinations on normal interfaces because they are reserved, special-purpose, or otherwise not usable for general unicast forwarding. Treating these as invalid helps protect the control plane and prevents leakage of nonsensical routes into the fabric. This is especially relevant in data center underlays where strict routing hygiene is expected and where improper advertisements can cause blackholing or policy confusion.

The multicast range 224.0.0.0/4 is a classic martian example for unicast routing. These addresses are reserved for multicast and should not be accepted as ordinary unicast sources or carried as typical unicast reachability in an IP fabric. The loopback range 127.0.0.0/8 is also martian on physical networks because it is reserved for host self-reference and must never be forwarded by routers. Seeing it on an interface implies misconfiguration or spoofing.

The prefix 192.0.0.0/24 is reserved for special protocol and IETF assignments and is not intended for general use on public or private networks. As a result, it is commonly treated as martian in routing policy and input validation. By contrast, 172.36.0.0/24 and 198.60.0.0/16 are ordinary globally routable unicast space, so they are not martian by definition.

In a spine-leaf fabric architecture, which is commonly used in data center designs, each device has a distinct role to ensure efficient and scalable network traffic flow.

Step-by-Step Breakdown:

Spine Nodes:

The spine nodes form the backbone of the fabric and are responsible for transit traffic between leaf nodes. They connect to every leaf switch and provide multiple paths for traffic between leaf nodes, ensuring redundancy and load balancing.

Leaf Nodes:

The leaf nodes are used for host connectivity. These switches connect to servers, storage, or edge routers. They also connect to the spine switches to reach other leaf switches.

Juniper Reference:

Spine-Leaf Architecture: In Juniper's IP fabric designs, spine switches handle inter-leaf communication, while leaf switches manage host and endpoint connectivity.

In legacy hierarchical network design, three key layers are used to create a scalable and structured network:

Step-by-Step Breakdown:

Access Layer:

The access layer is where end devices, such as computers and IP phones, connect to the network. It typically involves switches that provide connectivity for devices at the edge of the network.

Aggregation Layer (Distribution Layer):

The aggregation layer (also called the distribution layer) aggregates traffic from multiple access layer devices and applies policies such as filtering and QoS. It also provides redundancy and load balancing.

Core Layer:

The core layer provides high-speed connectivity between aggregation layer devices and facilitates traffic within the data center or between different network segments.

Juniper Reference:

Legacy Hierarchical Design: Juniper networks often follow the traditional three-layer design (Access, Aggregation, and Core) to ensure scalability and high performance.

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.