The leaf device in AS 65000 will receive three routes for the 10.100.0.0/16 prefix, one from each spine device in AS 65001, AS 65002, and AS 65003. Since ECMP load balancing is enabled, the leaf device will install all three routes in its routing table and distribute the traffic among them. The other options are incorrect because:
* B. 1 is wrong because the leaf device will not receive only one route for the prefix. It will receive multiple routes from different spine devices and use ECMP to load balance among them.
* C. 2 is wrong because the leaf device will not receive only two routes for the prefix. It will receive three routes from three spine devices, as explained above.
* D. 4 is wrong because the leaf device will not receive four routes for the prefix. It will receive three routes from three spine devices, as explained above. The fourth spine device in AS 65004 is not directly connected to the leaf device and will not advertise the prefix to it. References:
* IP Fabric Underlay Network Design and Implementation
* BGP Multipath load sharing iBGP and eBGP
* ECMP Load Balancing

BGP is the protocol used to advertise EVPN routes. EVPN routes are a new type of BGP network layer reachability information (NLRI) that carry MAC address and IP prefix information for Ethernet VPNs. EVPN routes are exchanged between PEs using BGP multiprotocol extensions (MP-BGP) over MPLS, VXLAN, SR, or SRv6 tunnels. EVPN routes enable PEs to learn the reachability of MAC addresses and IP prefixes of different sites within the same EVPN instance. EVPN routes also support various features such as fast convergence, redundancy, aliasing, and inter-subnet routing. The other options are incorrect because:
* A. OSPF is wrong because OSPF is an interior gateway protocol (IGP) that is used to advertise IP routes within an autonomous system. OSPF is not used to advertise EVPN routes, which are a type of BGP NLRI that carry MAC address and IP prefix information for Ethernet VPNs.
* C. IS-IS is wrong because IS-IS is an interior gateway protocol (IGP) that is used to advertise IP routes and MPLS labels within an autonomous system. IS-IS is not used to advertise EVPN routes, which are a type of BGP NLRI that carry MAC address and IP prefix information for Ethernet VPNs.
* D. RIP is wrong because RIP is an interior gateway protocol (IGP) that is used to advertise IP routes within an autonomous system. RIP is not used to advertise EVPN routes, which are a type of BGP NLRI that carry MAC address and IP prefix information for Ethernet VPNs. References:
* EVPN Fundamentals
* RFC 9136 - IP Prefix Advertisement in Ethernet VPN (EVPN)
* EVPN Type-5 Routes: IP Prefix Advertisement
* Understanding EVPN Pure Type 5 Routes

According to the Juniper documentation1, an interface map is a configuration template that maps interfaces between logical devices and physical hardware devices (represented with device profiles) while adhering to vendor specifications. An interface map can be either predefined or custom. A predefined interface map is one that ships with Apstra software and supports most qualified Juniper devices. A custom interface map is one that is created by the user to meet specific requirements. An interface map can be stored in either the global catalog or the blueprint catalog. The global catalog contains all the interface maps that are available for use in any blueprint. The blueprint catalog contains the interface maps that are imported from the global catalog and used in a specific blueprint.
When a member of your organization makes changes to a predefined interface map, the following statements are correct:
* Changes to interface maps in the global catalog do not affect interface maps that have already been imported into blueprint catalogs. This means that the existing blueprints that use the original version of the interface map will not be impacted by the changes. However, if you want to use the updated version of the interface map in a new or existing blueprint, you need to import it again from the global catalog.
* Any changes made to predefined interface maps are discarded when Apstra is upgraded. This means that the changes will not be preserved across different versions of Apstra software. If you want to retain a customized interface map through Apstra upgrades, you need to clone the predefined interface map, give it a unique name, and customize it instead of changing the predefined one directly.
Therefore, the correct answer is A and B. Changes to interface maps in the global catalog do not affect interface maps that have already been imported into blueprint catalogs and any changes made to predefined interface maps are discarded when Apstra is upgraded. References: Edit Interface Map | Apstra 4.2 | Juniper Networks

Referring to the exhibit, the image shows a user interface of the Juniper Apstra software application, which is used for network management and configuration. The image shows the Virtual Networks table under the Resources menu, which displays the details of the VLANs and VXLANs in the network. The table has 11 columns, but only 9 are visible in the image. The other two columns are IPv6 Connectivity and IPv6 Subnet, which are hidden by default. To display the IPv6 subnets for all of the listed VXLANs, the user needs to select Columns, then select IPv6 Subnet. This will show the IPv6 Subnet column in the table, which will display the IPv6 addresses assigned to the VXLANs from the IPv6 pools. For more information, see Virtual Networks (Resources). References:
* Virtual Networks (Resources)
* IPv6 Pools (Resources)
* Apstra User Guide

A pristine configuration in Juniper Apstra is the configuration file that is used to onboard a device into the Apstra software application. A pristine configuration contains the minimum settings that are required for the device to communicate with the Apstra server, such as the hostname, management IP address, username, password, and SSH key1. A pristine configuration has the following characteristics:
* It is the configuration file placed on the device when decommissioning the device. This is because when a device is decommissioned from the Apstra software application, it is reverted back to its pristine configuration, which removes all the network configuration and services that were applied by the Apstra software application. This allows the device to be reused or repurposed for another network2.
* It is the configuration file on a device before acknowledgment in Apstra. This is because when a device is onboarded into the Apstra software application, it is initially in the discovery state, which means that
* the device is discovered by the Apstra server, but not yet acknowledged by the user. In the discovery state, thedevice has the pristine configuration, which can be viewed and edited by the user. Once the user acknowledges the device, the device moves to the deployed state, which means that the device is ready to receive the network configuration and services from the Apstra software application3.
The following two statements are incorrect in this scenario:
* It is the device's currently active configuration. This is not true, because the pristine configuration is not the device's currently active configuration, unless the device is in the discovery state or the decommissioned state. In the deployed state, the device's currently active configuration is the network configuration and services that are applied by the Apstra software application, which are based on the blueprint and the intent3.
* It is the device's previously active configuration. This is not true, because the pristine configuration is not the device's previously active configuration, unless the device is in the decommissioned state. In the discovery state, the pristine configuration is the device's initial configuration, which may or may not be the same as the device's previous configuration before being onboarded into the Apstra software application. In the deployed state, the device's previously active configuration is the network configuration and services that were applied by the Apstra software application before the last commit3.
References:
* Pristine Config
* Decommission Device
* Device States