A regional MSP manages 180 SD-WAN edges in SD-WAN Manager and needs a nightly Python report showing hostname, device model, reachability and software version for NOC triage. The script must authenticate once and reuse the session for inventory polling. Which Device Inventory API approach retrieves the device list and displays the key fields?
Select an answer to reveal the explanation.
Short Explanation
You’ve got this—nightly triage depends on a clear, complete table. Your session-based inventory call reuses authentication and gives the NOC the requested fields at a glance.
Full Explanation
The approach that authenticates once, passes the session to the device inventory API, and displays hostname, model, reachability and software version matches both the requested data and workflow. Reusing the session avoids repeated authentication during nightly polling, and the inventory report includes the device-level attributes needed for triage. An inventory report that leaves reachability to a separate health check omits an explicitly requested field; that separate check may be useful operationally, but it does not make reachability appear in this report. A report that shows last-seen time instead of software version substitutes a useful monitoring value for the requested release information. An approach that authenticates before each paginated request retrieves the right fields from the right endpoint, but repeats authentication rather than reusing one session, adding unnecessary overhead and violating the requirement. Exam caveat: API names, pagination behavior and session mechanisms can vary by SD-WAN Manager release, so verify the version-specific documentation rather than assuming an endpoint or field name. Practical check: run a small poll and confirm the response includes all four requested fields across pages, using the same authenticated session throughout.