A RESTCONF static-route create on IOS XE includes only 10.40.0.0/16 in the body and omits how packets leave. What is missing for a complete edit?
Select an answer to reveal the explanation.
Short Explanation
A destination without an exit is a map with no roads—RESTCONF still needs the next-hop or outgoing interface the model asks for.
Full Explanation
A RESTCONF static-route create that includes only 10.40.0.0/16 and omits how packets leave is missing the forwarding next-hop address and/or outgoing interface the YANG model requires. That missing content matters because static-route resources encode both the destination and the forwarding exit; without next-hop or exit interface, the edit is incomplete and typically fails validation or installs a useless/non-forwarding entry. Municipal edge automation must supply the model-required forwarding fields alongside the prefix.
An AppDynamics application name for APM correlation fails as a substitute because application performance monitoring identity is unrelated to YANG static-route forwarding. A Webex room ID so ChatOps can approve the route fails conceptually: collaboration room identifiers do not populate next-hop or outgoing-interface leaves on IOS XE. A DNA Center fabric VN name when the router is not fabric-enabled fails because fabric VN constructs are not the static-route forwarding fields this non-fabric RESTCONF edit needs.
Exam caveat: whether next-hop, interface, or both are required depends on the specific YANG model and route type (including floating or null routes in advanced cases); read the model constraints rather than always sending one field. Operational check: reject payloads that lack forwarding leaves in CI schema checks, then after apply confirm the RIB shows a resolvable next-hop or exit for 10.40.0.0/16 before advertising the change as complete.