Refer to the exhibit.

Application-Aware Routing (AAR) in Cisco SD-WAN tracks network performance (latency, jitter, and loss) in real-time to make intelligent path selection decisions. To achieve the requirements stated in the question, two main components are required:

Centralized Policy: This is where the SLA Class is defined (setting the 100ms latency, 85ms jitter, and 5% loss thresholds) and where the App-Route Policy is created to map specific traffic (video/voice) to those SLA classes and preferred colors (public-internet vs. MPLS).

BFD (Bidirectional Forwarding Detection) Template: While the centralized policy defines the logic, the actual measurement of the path statistics is performed by BFD. BFD runs on all IPsec tunnels between WAN Edge devices. The BFD feature template is where you configure the "app-route multiplier" and "poll-interval." These settings determine how frequently BFD probes the path and how it calculates the average latency, loss, and jitter used by the AAR policy to trigger a switchover.

Why not A (OMP): OMP handles the control plane (routing updates, TLOCs, and crypto keys), not the data plane performance measurement.

Why not B (VPN interface ethernet): This template is used to configure physical/logical interface properties (IP addresses, NAT, etc.), but it does not define the performance monitoring parameters for AAR.

Why not D (VPN): The VPN template defines the service or transport VPN instance but does not manage the path quality monitoring logic.

Here is the verified answer and technical breakdown based on the Implementing Cisco SD-WAN Solutions (ENSDWI) objectives.