Question 290
While checking a production data center change, the team finds: A fabric experiences transient packet drops but operations relies on a once-per-day manual counter snapshot and misses short-lived congestion spikes. Which implementation action should the engineer take first?
Explanation
Correct Answer
The root problem is that The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events. The selected change addresses it directly: Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics. Verify the outcome: The time-series reports expose the loss interval and correlate it with the affected interfaces and fabric paths.
Incorrect Answers
This action concerns span source and destination isolation, where The SPAN session source and dedicated monitor destination roles were assigned incorrectly. The reported failure instead stems from The monitoring design lacks continuous streaming telemetry and historical assurance correlation for transient events.
This action concerns netflow exporter reachability, where Flow-export destination reachability or the configured source and monitoring VRF are incorrect. The corrective response here is “Enable approved supported streaming telemetry and Nexus Dashboard assurance views for relevant fabric health metrics”; this alternative does not provide that response.
This action concerns vpc peer link consistency, where The vPC peer-link VLAN membership is inconsistent with downstream vPC service VLAN requirements. The stem reports a fabric experiences transient packet drops but operations relies on a once-per-day manual counter snapshot and misses short-lived congestion spikes; this control addresses a different failure condition.