Question 600
During a production change postcheck at fictional Marble Bay Software, the change record states: A gNMI telemetry collector cannot process bursty device messages and drops interface counters without reporting any gaps. Which targeted correction best addresses the network automation failure?
Explanation
Correct Answer
Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting. This addresses the problem because streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Confirm success using: Load tests show telemetry consumers keeping up with target throughput or explicitly signaling lost samples without presenting false continuity. Applied here, the relevant facts are: A gNMI telemetry collector cannot process bursty device messages and drops interface counters without reporting any gaps. The question asks which targeted correction best addresses the network automation failure.
Incorrect Answers
The offered action targets: authentication proves identity but each network resource action requires separate policy-based authorization controls. The case facts point instead to: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. Implement “Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting” to address that specific condition.
This alternative is a response to another technical cause: cA-signed certificates are public trust assertions but the associated private key must remain confidential for endpoint authentication. The reported case instead depends on: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. The action that directly addresses it is “Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting”.
The proposed action belongs to the mechanism: downstream error messages can reflect cascaded failures; causality is established by correlating the earlier specific event and affected resource. Here the stated fault follows a different mechanism: streaming telemetry pipelines have collectors, transports, ingestion queues and storage capacity that can fail independently of device subscriptions. The corrective choice is “Introduce bounded buffering, backpressure monitoring and horizontal ingestion capacity with visible gap or loss reporting”.