Fill in the blank to complete the URL for an API call to Cisco SD-WAN to display the history of the Bidirectional Forwarding Detection sessions that run on a vEdge router…

This question tests knowledge of Cisco SD-WAN's vManage REST API URL structure, specifically the endpoint path used to retrieve historical BFD (Bidirectional Forwarding Detection) session data from a vEdge router.

Controller-Based Network Automation

Question

Fill in the blank to complete the URL for an API call to Cisco SD-WAN to display the history of the Bidirectional Forwarding Detection sessions that run on a vEdge router. https://<vmanage-ip-address>/dataservice/device/__________ deviceId=<deviceId>

Explanation

Approach. The correct answer to fill in the blank is 'bfd/history?' - making the full URL: https://<vmanage-ip-address>/dataservice/device/bfd/history?deviceId=<deviceId>. The Cisco SD-WAN vManage API organizes device-level telemetry under /dataservice/device/, and BFD-related endpoints follow the pattern /bfd/<resource>. The 'history' sub-resource specifically retrieves historical session records rather than real-time state. The deviceId query parameter scopes the result to a specific vEdge router identified by its system IP or UUID.

Concept tested. Cisco SD-WAN vManage REST API URL structure - specifically the /dataservice/device/bfd/history endpoint used to query historical Bidirectional Forwarding Detection session data for a targeted vEdge device.

Reference. Cisco SD-WAN (Viptela) REST API documentation - Device BFD APIs: GET /dataservice/device/bfd/history

Topics

#Cisco SD-WAN API#vManage#BFD#Network Monitoring

Community Discussion

No community discussion yet for this question.

Full 300-435 Practice