Your Python script attaches a device template to a branch router in SD-WAN Manager, filling in the template's device variables first. The team needs confirmation that the push actually finished on the device before the next site is processed. Which sequence of API steps confirms that the template push completed on that device?
Select an answer to reveal the explanation.
Short Explanation
The attach call queues the work, and the task identifier lets you track it. Polling task status shows when the job reaches a terminal status. Like a tracking number, dispatch is not delivery.
Full Explanation
Attaching a device template in SD-WAN Manager (formerly vManage) is an asynchronous job: the API accepts the attach request and returns a task identifier while the controller builds and pushes the configuration. The response confirms that the request was accepted, not that the push finished. Poll the action status resource using the task identifier and wait for a terminal status for that device. Treating the response code as proof skips monitoring and can hide failures. Pushing raw configuration is a different workflow and does not track the requested template attach. Attaching other sites in bulk and checking an event log afterward does not provide the required per-device confirmation before proceeding. A task status indicates the outcome reported for the job; check the device configuration separately if you also need to verify the resulting configuration.