Question 820
A post-incident design review discusses the following: A network engineer assumes all IETF YANG models are Cisco proprietary because a Cisco device exposes them. Which preventive design control MOST DIRECTLY addresses this specific risk?
Explanation
Correct Answer
Store module names, namespaces and revisions alongside each automation dependency. This control targets the underlying design risk. IETF YANG models standardize common semantics independently of a vendor’s native extension models. The follow-up acceptance check remains: The module namespace and revision identify the applicable standards-based schema correctly.
Incorrect Answers
Native models expose device-specific data that may not map exactly to a standards-based OpenConfig schema. The repeat risk here is different: IETF YANG models standardize common semantics independently of a vendor’s native extension models. A directly relevant preventive control is: Store module names, namespaces and revisions alongside each automation dependency.
OpenConfig publishes vendor-neutral network models, while support and deviations vary by device implementation. The repeat risk here is different: IETF YANG models standardize common semantics independently of a vendor’s native extension models. A directly relevant preventive control is: Store module names, namespaces and revisions alongside each automation dependency.
Cloud on-ramp designs can reduce unnecessary backhaul but must preserve security inspection and policy controls. The repeat risk here is different: IETF YANG models standardize common semantics independently of a vendor’s native extension models. A directly relevant preventive control is: Store module names, namespaces and revisions alongside each automation dependency.