Emergency-management on-call must isolate PFC-related discards on Spectrum. How should WJH be used?
Select an answer to reveal the explanation.
Short Explanation
PFC discards hide in the noise if you stare at every event the same way. Filter WJH categories so emergency-management on-call can isolate Spectrum PFC-related discards fast.
Full Explanation
Emergency-management on-call isolating PFC-related discards on Spectrum must narrow WJH to the event types and categories that map to Priority Flow Control behavior. Filtering WJH event types lets responders analyze PFC-related Spectrum discard categories without wading through unrelated link, authentication, or administrative noise, which shortens mean time to isolate during a civic incident.
Why the other options fail by concept: streaming WJH buffer occupancy baselines to profile Spectrum ECN marking behavior looks at the wrong congestion mechanism—ECN marking behavior is a separate signal from PFC pause-driven discards, so baselining it does not isolate the PFC-related events the on-call team actually needs. Aggregating WJH L3 routing drop counters to review Spectrum PFC pause handling mismatches the data source to the mechanism—L3 routing drops reflect forwarding decisions, not the link-level pause-frame behavior that PFC discards are built from, so this view will not isolate PFC activity. Polling WJH port state events to validate Spectrum LLDP PFC negotiation status looks at link-neighbor discovery rather than the discard events themselves; LLDP negotiation state does not tell responders whether PFC pause frames are actually causing discards right now.
Exam caveat: PFC discards indicate pause-frame dynamics and buffer pressure; they are not automatically “bad Ethernet.” Misconfigured PFC or mismatched priorities can create head-of-line blocking. Confirm that the filtered categories actually correspond to PFC on the municipal Spectrum image in use, because naming can vary by NOS version.
Operational check: during a Spectrum discard spike affecting emergency-management AI traffic, apply WJH filters for PFC-related categories, count events per leaf/port in the incident window, correlate with pause counters or QoS maps, and only then decide whether to tune buffers, priorities, or upstream senders—without disabling PFC as a first step.