A retailer with branch stores wants the SD-WAN controller included in the assurance picture instead of left as a separate inventory. What should be integrated?
Select an answer to reveal the explanation.
Short Explanation
A traffic director missing from the incident board forces you to rebuild the story from memory. Integrate Catalyst SD-WAN Manager so the controller sits in the same assurance picture as the rest of the path. A spreadsheet of tunnel status, turning that controller off, or a collector that does not share the view leaves the SD-WAN story in a side room.
Full Explanation
The request is to bring the SD-WAN controller into the assurance picture rather than keep it as a side inventory. Integrating Catalyst SD-WAN Manager so its view joins that picture is the handoff that matches the controller they already run. A standalone spreadsheet of tunnel status updated by the network team is a manual side list, and it stays outside the shared assurance view. Turning Catalyst SD-WAN Manager off so only ThousandEyes remains removes the controller from the picture instead of including it. A second collector that does not share a view with the SD-WAN controller adds another isolated data set and does not put the controller into the assurance picture. Exam caveat: the current controller name is Catalyst SD-WAN Manager, and the task is to include it, not to retire it or to export it to a private sheet. Operational check: during a branch path issue, confirm the assurance view shows Catalyst SD-WAN Manager information with the other path evidence, and that tunnel status is not trapped in a spreadsheet or in a collector that does not share the view.