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.

EVPN uses a route distinguisher (RD) value to identify which remote leaf device advertised the EVPN route. An RD is a 64-bit value that is prepended to the EVPN NLRI to create a unique VPNv4 or VPNv6 prefix. The RD value is usually derived from the IP address of the PE that originates the EVPN route. By comparing the RD values of different EVPN routes, a PE can determine which remote PE advertised the route and which VRF the route belongs to.

EVPN route Type-3 is used to advertise the IP address of the VTEP and the VNIs that it supports.
This allows the VTEPs to discover each other and form VXLAN tunnels for the VNIs that they have in common. EVPN route Type-2 is used to advertise the MAC and IP addresses of the hosts connected to the VTEPs. This allows the VTEPs to learn the MAC-to-IP bindings and the MAC-to- VTEP mappings for the hosts in the same VNI. Therefore, these two types of VXLAN tunnels will be automatically created by the EVPN control plane when using Juniper Apstra with the ERB design blueprint and two virtual networks in a common routing zone.

In the Juniper Apstra UI, you can create VNI pools for virtual networks that use VXLAN encapsulation in the overlay network. A VNI pool is a resource pool that contains a range of VNIs that can be assigned to the virtual networks. The valid VNI range for a VNI pool is 4096 through
16777214, according to the VXLAN standard. Therefore, the statement B is correct in this scenario. The following three statements are incorrect in this scenario:
Any range is acceptable for the VNI pool. This is not true, because the VNI range has a lower and upper limit defined by the VXLAN standard. The lower limit is 4096, and the upper limit is
16777214. Any VNI outside this range is invalid and cannot be used for VXLAN encapsulation.
The valid VNI range is 2 through 4096. This is not true, because the VNI range does not start from 2, but from 4096. The VNIs from 2 to 4095 are reserved and cannot be used for VXLAN encapsulation. The valid VNI range is 1 through 10000. This is not true, because the VNI range does not include 1, which is also reserved and cannot be used for VXLAN encapsulation. The VNI range also does not end at 10000, but at 16777214, which is the maximum possible value for a 24-bit VNI field.