An audit requires the output of 'show version' and 'show ip interface brief' from 40 Catalyst Center managed switches. The engineer has API credentials and a Python script, but the Command Runner endpoint replies with an identifier instead of the command output. Which workflow retrieves the actual results from the Command Runner task identifier?
Select an answer to reveal the explanation.
Short Explanation
Command Runner works like a ticket queue: you submit the commands and get a task ID back, then check the task and retrieve its results. The first response gives you the job handle, not the show output. Writing config instead doesn't run show commands at all.
Full Explanation
Catalyst Center runs Command Runner as an asynchronous job: your POST carries the command list and target device identifiers, and the response returns a task ID rather than the output. Submit devices in batches supported by the API. Then query the task resource to check its status and retrieve the command results through the documented task or result resource for that release. Reading output from the initial response fails because it carries the job handle; the configuration endpoint does not execute show commands; and driving SSH from Python bypasses Command Runner. Endpoint paths and polling intervals can vary between releases, so use the task identifier and the API documentation for the installed release. A practical check is to log the returned ID, check the task status, and retrieve the output when the task is complete.