Different switches have different limitations for the number of NAE scripts, monitors, and agents supported is a correct description of Network Analytics Engine (NAE) limitations on ArubaOS-CX switches. NAE is a feature that provides automation and analytics for managing ArubaOS-CX switches. NAE scripts are scripts that run on switches and collect data from various sources. NAE monitors are rules that define conditions and actions for NAE agents. NAE agents are instances of NAE scripts and monitors that run on switches. Different switches have different limitations for the number of NAE scripts, monitors, and agents supported depending on their hardware resources1.

The exhibit shows a network topology where Switch-1 and Switch-2 are part of a Virtual Switching Extension (VSX) fabric, and the router runs OSPF on LAG 100, which is a Layer 3 LAG. The question asks how to control how core-to-access traffic is forwarded, which means how the router chooses between the two links to Switch-1 and Switch-2. To force the router to use both links, ensuring that active gateway is enabled on LAG 100 on both Switch-1 and Switch-2 is not the correct solution. Active gateway is a feature that allows both VSX members to act as the default gateway for downstream devices, using a common virtual MAC address. Active gateway does not affect how upstream devices, such as the router, forward traffic to the VSX members1. To force the router to use both links, the correct solution is to configure equal-cost multi-path (ECMP) in OSPF on the router. ECMP is a feature that allows a router to load balance traffic across multiple paths with the same cost. ECMP can be configured using the maximum-paths command and specifying how many equal-cost paths the router should use2. Therefore, this does not correctly explain how to control how core-to-access traffic is forwarded.

VTEPs that use headend replication forward unicasts with unknown destination MAC addresses as unicast packets to each VTEP in the same VNI is a correct description of how the VTEPs handle VXLAN traffic forwarding. Headend replication is a method of replicating VXLAN packets at the ingress VTEP instead of using multicast routing. The ingress VTEP sends a copy of the VXLAN packet to each egress VTEP that belongs to the same VNI using unicast tunnels1.

Creating a conformance test to check that the firmware matches the desired version is part of the process for using NetEdit to update firmware on ArubaOS-CX switches1. NetEdit is a tool that allows you to manage and monitor multiple switches from a single interface1. It also provides a conformance feature that lets you create tests to verify that the switches comply with your desired configuration and firmware settings1. You can use NetEdit to create a conformance test to check that the firmware matches the desired version and then run it on the switches1.
https://asp.arubanetworks.com/downloads;products=Aruba%20Switches