A managed service provider with 400 WAN Edge devices needs nightly inventory, tunnel health, and alarm summaries for customer reports without manual clicks in the GUI. Which REST API monitoring approach should you use for device inventory, statistics and bulk monitoring?
Select an answer to reveal the explanation.
Short Explanation
You want reports that run themselves while you sleep. Paged API pulls pull inventory and stats in bulk reliably, like scanning barcodes instead of counting boxes by hand.
Full Explanation
SD-WAN Manager, formerly vManage, exposes REST APIs with token or session authentication that return JSON for devices, interface and tunnel statistics, and alarms, supporting pagination and filtering for large-scale bulk monitoring and automation. That mechanism makes authenticated paged REST calls to SD-WAN Manager correct because it provides complete inventory, health, and alarm data for scheduled reports without GUI interaction. NETCONF to SD-WAN Controller for OMP routes fails by concept because NETCONF streams configuration and operational state per device and OMP routes describe control state, not Manager-aggregated alarms and statistics. Validator REST polling fails by concept because SD-WAN Validator, formerly vBond, orchestrates onboarding and control connectivity, not device inventory and performance statistics. GUI scraping with shared admin fails by concept because it is manual, fragile, and insecure compared with structured API pagination and service accounts. Exam caveat is to associate REST monitoring with SD-WAN Manager, not Validator or Controller. Practical check is to test authentication, page size, and time filters, then validate counts against Manager dashboard totals.