Score Higher on Verified JN0-480 | Data Center Specialist (JNCIS-DC) Exam Questions with Answers

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 standard1. 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 standard1. 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 encapsulation1.
• 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 encapsulation1. The VNI range also does not end at 10000, but at 16777214, which is the maximum possible value for a 24-bit VNI field1.

References:

• VNI Pools (Resources)

The Juniper Apstra Rendered configuration is the configuration that is generated from the staged blueprint and applied to the devices in the network. The Rendered configuration is dynamically rendered at commit time, which means that it is created on the fly based on the latest changes and validations in the blueprint. The Rendered configuration is not stored in any database, but it can be viewed in the Apstra UI or downloaded as a file. The Rendered configuration reflects the desired state of the network as defined by the intent of the blueprint. The other options are incorrect because:

• A. It is built at commit time and stored in a MySQL database is wrong because the Rendered configuration is not stored in any database, let alone a MySQLdatabase. Apstra uses a graph database to store the network topology and configuration data, not a relational database like MySQL.
• B. It is stored in a NoSQL database and incrementally updated is wrong because the Rendered configuration is not stored in any database, let alone a NoSQL database. Apstra uses a graph database to store the network topology and configuration data, not a non-relational database like NoSQL. The Rendered configuration is not incrementally updated, but dynamically rendered at commit time.
• D. It is rendered from the graph database and stored locally is wrong because the Rendered configuration is not rendered from the graph database, but from the staged blueprint. The graph database stores the network topology and configuration data, but the Rendered configuration is generated from the blueprint, which is a logical representation of the network design and intent. The Rendered configuration is not stored locally, but it can be downloaded as a file if needed. References:
• Config Rendering in Juniper Apstra
• AOS Device Configuration Lifecycle
• Configlets (Datacenter Design)

According to the Juniper documentation1, a five-stage Clos architecture allows for large-scale topologies with an additional aggregation layer that interconnects multiple pods into a single fabric. A pod is a group of racks that share the same spine devices. A rack is a group of leaf devices that connect to the same servers. To create a five-stage Clos network using Juniper Apstra, you need to choose the pod-based fabric type in the template creation wizard. This will allow you to specify the number of pods, planes, spines, and leaves for your network design. Therefore, the correct answer is D. pod-based. References: 5-Stage Clos Architecture | Apstra 4.1 | Juniper Networks