A DEVCOR item asks how to configure a VLAN object on IOS XE with RESTCONF. Which response stays on the scored idea?
Select an answer to reveal the explanation.
Short Explanation
DEVCOR wants the VLAN object edited through RESTCONF—not a CCNP trunking or VTP campus design essay.
Full Explanation
A DEVCOR item on configuring a VLAN object on IOS XE with RESTCONF stays on the scored idea when the answer is to edit the VLAN YANG resource via RESTCONF with the intended vlan-id and leaves. That response works because the task measures whether you can construct the device-config API edit—path under /restconf/data, correct key, and payload leaves—not whether you can redesign campus trunking. Municipal candidates should keep the answer at VLAN-object construction through RESTCONF.
Calculating DTP negotiation and allowed-VLAN trunk lists for every uplink fails because trunk/DTP design is a broader switching topic outside this RESTCONF VLAN-object item. Designing a multi-site VTP domain hierarchy before any API call fails conceptually: VTP architecture is not the scored RESTCONF VLAN edit. Proving why native VLAN mismatch is preferred over creating the VLAN object fails because mismatch is a problem to avoid, not a substitute for creating the VLAN via the API.
Exam caveat: after the VLAN exists, downstream trunk and access-port assignment may still be required for traffic to flow—but those are follow-on tasks, not a reason to skip the YANG VLAN create on the exam item. Operational check: implement and validate the RESTCONF VLAN create/merge first, then separately track port/trunk follow-ups in the civic change plan so scope for the DEVCOR-style check remains clear.