Drag and Drop Question Refer to the exhibit. Drag and drop the code from the bottom onto the blanks in the code to construct a cURL command using the Cisco DNA Center API. which will provide the detai

Question

Exhibits

Answer Area

Explanation

The question tests the ability to construct a Cisco DNA Center API call using cURL to retrieve wireless LAN controller details by correctly identifying and ordering the API endpoint path segments.

Approach. To construct the correct cURL command for retrieving wireless LAN controller details by ID, the API endpoint path needs to be correctly identified. The base URL is https://dna/intent/api/v1/.

1. The first segment of the path typically specifies the primary resource type. 'network-device' is the most appropriate choice from the options for devices managed by DNA Center. Therefore, 'network-device' should be dragged to the first blank.
2. The question specifies retrieving details for a controller 'with Id af397748444'. In RESTful APIs, retrieving a specific instance of a resource usually involves specifying its ID. Thus, 'id' serves as a placeholder for the actual controller ID in the API path. Therefore, 'id' should be dragged to the second blank.
3. The final segment of the path should specify the sub-resource or specific information being requested about the identified device. The JSON exhibit clearly states 'Returns the wireless lan controller info'. Among the remaining options ('wireless', 'wireless-info', 'controller', 'details'), 'wireless-info' is the most precise and descriptive term for retrieving the wireless LAN controller's information. Therefore, 'wireless-info' should be dragged to the third blank. This results in the complete API path: /network-device/{id}/wireless-info, making the full cURL command: curl -L --request GET --url 'https://dna/intent/api/v1/network-device/id/wireless-info' --header 'Content-Type: application/json' --header 'Accept: application/json'.

Common mistakes.

• common_mistake. Common mistakes include incorrectly ordering the path segments, choosing less specific terms, or omitting necessary segments. For instance, directly using 'wireless' or 'controller' as the primary resource is incorrect because DNA Center APIs typically start with a broader resource like 'network-device'. Placing 'wireless-info' before 'id' or 'network-device' would violate the logical RESTful API structure of 'resource-type/specific-instance-id/sub-resource'. Using 'details' instead of 'wireless-info' is less precise, as 'wireless-info' directly corresponds to the data described in the exhibit's JSON. Omitting 'id' would imply requesting a list of all wireless controllers, not the details of a specific one, which contradicts the question's premise of retrieving information 'with Id af397748444'.

Concept tested. Understanding Cisco DNA Center REST API endpoint structures, identifying appropriate resource paths for specific data retrieval, and constructing basic cURL commands for GET requests. It also tests familiarity with common API design patterns (resource/ID/sub-resource) and how they apply to a specific vendor's API.

No community discussion yet for this question.