Question 860
A preventive architecture review covers this situation: An architect labels gRPC and gNMI as identical protocols, making the telemetry integration diagram ambiguous. Which preventive design control MOST DIRECTLY addresses this specific risk?
Explanation
Correct Answer
Document both API semantics and transport prerequisites in management interface specifications. This control targets the underlying design risk. gNMI defines network configuration and telemetry operations using gRPC as its underlying RPC transport. The follow-up acceptance check remains: An authenticated gNMI Capabilities or Get request succeeds over an established gRPC channel.
Incorrect Answers
gNMI Get retrieves selected modeled paths, while Subscribe handles streaming or subscription behavior. The repeat risk here is different: gNMI defines network configuration and telemetry operations using gRPC as its underlying RPC transport. A directly relevant preventive control is: Document both API semantics and transport prerequisites in management interface specifications.
gNMI Subscribe supports modeled telemetry streaming rather than repeated manual Get operations. The repeat risk here is different: gNMI defines network configuration and telemetry operations using gRPC as its underlying RPC transport. A directly relevant preventive control is: Document both API semantics and transport prerequisites in management interface specifications.
Periodic publication delivers time-indexed samples for rate and trend calculations independently of event changes. The repeat risk here is different: gNMI defines network configuration and telemetry operations using gRPC as its underlying RPC transport. A directly relevant preventive control is: Document both API semantics and transport prerequisites in management interface specifications.