300-435 · Question #56
Which two API calls are used to trigger a device configuration sync in Cisco DNA Center? (Choose two.)
The correct answer is C. PUT /dna/intent/api/v1/network-device/{networkDeviceID}/sync. To trigger a configuration sync for a specific device in Cisco DNA Center, the API call targets that device's unique ID with a PUT request to the /sync endpoint.
Question
Options
- APUT /dna/intent/api/v1/network-device
- BPUT /dna/intent/api/v1/network-device/sync-all
- CPUT /dna/intent/api/v1/network-device/{networkDeviceID}/sync
- DPUT /dna/intent/api/v1/network-device-device/{networkDeviceID}/sync
How the community answered
(29 responses)- A3% (1)
- B3% (1)
- C93% (27)
Why each option
To trigger a configuration sync for a specific device in Cisco DNA Center, the API call targets that device's unique ID with a PUT request to the /sync endpoint.
PUT /dna/intent/api/v1/network-device is generally used for creating or updating the entire network device object itself, not specifically triggering a configuration sync for an existing device.
PUT /dna/intent/api/v1/network-device/sync-all implies a bulk operation to sync all network devices, which is different from syncing a specific device.
The PUT /dna/intent/api/v1/network-device/{{networkDeviceID}}/sync API call is used to initiate a configuration synchronization process for a specific network device identified by its unique ID. This endpoint allows administrators to force a device to pull or reapply its intended configuration from Cisco DNA Center.
PUT /dna/intent/api/v1/network-device-device/{{networkDeviceID}}/sync contains a typo ('network-device-device') in the path, making it an incorrect or non-existent API endpoint.
Concept tested: Cisco DNA Center device configuration sync API
Source: https://developer.cisco.com/docs/dna-center/#!device-provisioning-api-device-provisioning
Topics
Community Discussion
No community discussion yet for this question.