You automate a rollout through SD-WAN Manager: a Python script posts twelve edge routers and their template variables to the attach endpoint of a device template. The API replies immediately with HTTP 200 and a task identifier while the push is still running. Which follow-up step tells the script when every router has finished receiving the configuration?
Select an answer to reveal the explanation.
Short Explanation
A 200 response is like a package being accepted at the post office—it doesn’t mean it’s arrived yet. You’ll need to use the task ID to poll task status until all twelve routers report success.
Full Explanation
Template attachment is asynchronous, so SD-WAN Manager, the product formerly known as vManage, accepts the request, returns a task identifier, and completes the push as a background job after the HTTP call has finished. Poll the task status using that identifier to see per-device results and gate the next stage on every router reporting success. Treating the 200 OK as confirmation confuses request acceptance with job completion. Sleeping for a fixed interval is unreliable because duration can vary with device count, template size, and controller load. Reissuing the attach call does not query progress and may trigger another action rather than confirm completion. The status path differs between releases, so use the task-ID-then-status pattern rather than memorising a URL.