What types of telemetry and monitoring are typically collected in MEF SD-WAN?

• A. Link status, tunnel health, throughput, latency, jitter, packet loss, application performance, utilization, device health (CPU/memory), and security events; accessible via APIs and dashboards.
• B. Only CPU and memory usage.
• C. Traffic shaping policies and QoS settings for applications.
• D. Cloud provider performance metrics only.

Answer: (A)

The thing being tested is what telemetry and monitoring data MEF SD-WAN provides to give operators end-to-end visibility and quick, proactive management. In a true SD-WAN deployment, you don’t just want to know how busy a router is; you need a full picture of both the network and application performance across all paths. This includes link status and tunnel health to confirm paths are up and viable, throughput and latency metrics to measure how fast data moves, jitter and packet loss to detect quality degradation, and application performance metrics that show how specific applications behave over the WAN. Utilization helps you see how much capacity remains on each link, while device health (CPU/memory) helps spot hardware bottlenecks. Security events alert you to potential threats or policy violations. All of this is typically accessible through APIs and dashboards so operators can monitor in real time and automate responses when thresholds are crossed.

The other options are too narrow or misaligned with telemetry. Focusing only on CPU and memory misses essential network and application performance data. Focusing on policies or QoS settings is about configuration, not the telemetry itself. Limiting metrics to cloud provider performance ignores the broader WAN, including on-prem/off‑net links and security monitoring.