A tax assessor tunes Application-Aware Routing so path switches follow underlay quality. Which telemetry inputs typically drive those AAR decisions on transport colors?
Select an answer to reveal the explanation.
Short Explanation
AAR is picky about the road, not the dashboard CPU gauge. It watches loss, latency, and jitter on each color and steers apps when a path gets bumpy. Communities and syslog are different toolkits.
Full Explanation
Application-Aware Routing steers matching application traffic based on underlay path quality rather than static primary-only assumptions. Active probes measure loss, latency, and jitter on transport colors so a tax assessor’s Edge can prefer or switch paths when a color degrades relative to configured thresholds. Those measurements are the telemetry inputs that make AAR decisions meaningful for civic interactive and batch applications.
BGP community tags learned from a PE-CE eBGP session do not replace path-quality probes as AAR’s primary decision inputs. Controller CPU utilization on vManage alone is not underlay path telemetry for color switchover. Syslog severity from the Edge without active probing does not quantify loss, latency, or jitter on transports.
Exam caveat: AAR is about measured transport quality on colors—do not confuse it with routing-attribute tricks, controller health gauges, or log severity alone.
Operational check: enable path probing on the relevant colors, set AAR policy and thresholds for the civic application class, degrade or fail a path in a controlled test window, confirm traffic moves as intended, and restore while watching counters and user experience.