City planning digital-twin traffic needs Spectrum-X adaptive routing plus visible telemetry. Which combination meets that observability goal?
Select an answer to reveal the explanation.
Short Explanation
Adaptive routing with telemetry going only to chargeback accounting views is a detour system with no traffic cameras—city planning digital twins need dashboards, not just billing data. Turn on Spectrum-X adaptive routing and keep telemetry visible so operators can see how AI paths shift under load.
Full Explanation
City planning digital-twin traffic that needs Spectrum-X adaptive routing plus visible telemetry is satisfied by enabling adaptive routing together with Spectrum-X telemetry dashboards for AI fabric observability. Adaptive routing steers around congestion for digital-twin and related AI flows, while dashboards expose link health, path changes, and queue/congestion signals so planners and operators trust what the fabric is doing. Both pieces are required for the stated observability goal.
Adaptive routing enabled with Spectrum-X flow counters streamed to chargeback accounting views leaves detours unexplained and unverifiable because accounting views don't expose link health, path changes, or congestion signals for AI fabric observability.
Static ECMP routing paired with Spectrum-X telemetry dashboards for AI fabric utilization history observes a fabric that cannot adapt because ECMP does not steer around congestion.
Adaptive routing enabled with Spectrum-X telemetry collected via hourly SNMP polling for offline capacity analysis fails both performance response and real-time visibility because hourly polling is not live dashboard observability.
Exam caveat: “adaptive routing plus observability” means both features on—not one without the other, and not hourly SNMP polling for offline capacity analysis instead of live dashboards. Operational check: turn on Spectrum-X adaptive routing for the city planning digital-twin rails, connect telemetry dashboards to the same fabric, induce or wait for congestion, and confirm dashboards show path adaptation; do not stream telemetry only to chargeback accounting views, use static ECMP instead of adaptive routing, or rely on hourly SNMP polling for offline capacity analysis as the operating model.