Question 260
A Nexus, UCS or MDS operations team encounters this issue: A monitoring Python script assumes a nested JSON metric is always a number and crashes when NX-OS telemetry omits the optional field on one hardware platform. What is the most appropriate remediation for these symptoms?
Explanation
Correct Answer
The root problem is that The parser lacks schema validation and robust handling of absent or differently typed telemetry values. The selected change addresses it directly: Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics. Verify the outcome: The collector processes supported payload variants and flags incomplete metrics without terminating the monitoring job.
Incorrect Answers
This action concerns ai roce lossless class design, where The RDMA transport has not been mapped to an appropriate lossless traffic class with congestion safeguards. The reported failure instead stems from The parser lacks schema validation and robust handling of absent or differently typed telemetry values.
This action concerns ansible inventory variable scoping, where The playbook target inventory and variable precedence do not isolate the intended lab device group. The corrective response here is “Validate expected JSON fields and handle missing data explicitly before calculating fabric health metrics”; this alternative does not provide that response.
This action concerns terraform plan infrastructure drift, where The infrastructure-as-code state and actual network infrastructure have drifted without pre-apply reconciliation. The stem reports a monitoring Python script assumes a nested JSON metric is always a number and crashes when NX-OS telemetry omits the optional field on one hardware platform; this control addresses a different failure condition.