Free Data Center Associate (JNCIA-DC) Practice Questions

EBGP is the BGP session type formed between different autonomous systems. In Juniper data center IP fabrics, EBGP is frequently used for the underlay because it can provide all required reachability without an additional interior gateway protocol. The fabric can advertise loopbacks and point-to-point link subnets directly in BGP, then use ECMP to install multiple equal-cost next hops. This is why EBGP sessions do not require an IGP as a fundamental dependency. Some designs still add an IGP for other reasons, but EBGP itself can carry the underlay routes needed for full fabric connectivity.

EBGP sessions are also typically established between directly connected peers. In a standard leaf-spine underlay, each leaf peers with each spine over the routed physical links between them, using the interface IP addresses on those point-to-point subnets. This matches EBGP default behavior, including a one-hop TTL expectation and straightforward operational troubleshooting.

Loopback peering is not required for EBGP. It is possible, but it usually needs additional configuration such as multihop and a routing method to ensure reachability to the remote loopback before the BGP session can form. EBGP also supports sessions with non-directly connected peers when multihop is configured, so it is incorrect to claim EBGP does not support that capability.

In modern data center architectures, an overlay network is a logical or virtual network built on top of an underlay, where the underlay is the physical IP fabric that provides basic Layer 3 transport and reachability between fabric nodes. The overlay abstracts the physical topology and delivers tenant connectivity and segmentation services. This makes the statement that an overlay is a virtual network running on top of a physical network correct.

In EVPN VXLAN based data centers, overlays commonly carry both Layer 2 and Layer 3 services. Layer 2 extension is achieved by encapsulating Ethernet frames inside VXLAN so that a VLAN like segment can span multiple leaf switches across a routed underlay. Layer 3 services are delivered either through symmetric routing at the VTEPs or by advertising IP prefixes and host routes through the overlay control plane. As a result, overlays are not limited to Layer 3 traffic only, and statement D is correct.

The overlay is not defined by being public versus private. It can be built for private multi tenant segmentation inside a single data center, across multiple data centers, or to connect to external services, but public network is not a defining attribute.

Verification sources from Juniper documentation

https://www.juniper.net/documentation/us/en/software/junos/evpn-vxlan/topics/topic-map/evpn-vxlan-overview.html

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

BGP uses a small set of well-defined message types to form and maintain peerings and to exchange routing information. The Open message is used during session establishment after the TCP connection is up. It communicates the parameters required to form the BGP session, such as the BGP version, the autonomous system number, the negotiated hold time, the BGP identifier, and optional capabilities. Capabilities are especially important in data center designs because they enable features such as 4 byte ASNs, route refresh, and EVPN signaling when applicable.

The Update message is the core mechanism BGP uses to advertise reachability and to withdraw routes that are no longer valid. In a data center underlay using EBGP, Update messages carry the prefixes that represent loopbacks and point-to-point links, enabling leaf and spine reachability. In an EVPN control plane, Update messages carry EVPN Network Layer Reachability Information to distribute MAC and IP reachability and multihoming information across the fabric.

Hello is not a BGP message type. Hello is commonly associated with protocols like OSPF, IS-IS, and some discovery mechanisms. LSA is not a BGP message type either; Link State Advertisements are specific to OSP

F.  

Aggregate routes and generated routes are used to create summarized routes in Junos, but they behave differently in terms of forwarding.

Step-by-Step Breakdown:

Aggregate Routes:

An aggregate route summarizes a set of more specific routes, but it does not have a direct forwarding next hop. Instead, it points to the more specific routes for actual packet forwarding.

Generated Routes:

A generated route also summarizes specific routes, but it has a forwarding next hop that is determined based on the availability of contributing routes. The generated route can be used to directly forward traffic.

Juniper Reference:

Aggregate and Generated Routes: In Junos, aggregate routes rely on more specific routes for forwarding, while generated routes can forward traffic directly based on their next-hop information.