200-901 · Question #606
Refer to the exhibit. A network engineer makes a RESTCONF API call to Cisco IOS XE to retrieve information. Which HTTP method and URL does the engineer use to make the API call?
The correct answer is C. GET https://devnetlab.local/restconf/api/running/native/interface/GigabitEthernet/2/. RESTCONF uses GET to retrieve data (read-only operation), so GET is correct across all options. The path structure for Cisco IOS XE RESTCONF follows: /restconf/api/running/native/interface/{interface-type}/{interface-number}/. Option A is wrong because it omits 'interface' from…
Question
Refer to the exhibit. A network engineer makes a RESTCONF API call to Cisco IOS XE to retrieve information. Which HTTP method and URL does the engineer use to make the API call?
Exhibit
Options
- AGET https://devnetlab.local/restconf/api/running/native/GigabitEthernet
- BGET https://devnetlab.local/restconf/api/running/native/interface/GigabitEthernet
- CGET https://devnetlab.local/restconf/api/running/native/interface/GigabitEthernet/2/
- DGET https://devnetlab.local/restconf/api/running/ios/native/interface/GigabitEthernet/1/
How the community answered
(24 responses)- A17% (4)
- B8% (2)
- C71% (17)
- D4% (1)
Explanation
RESTCONF uses GET to retrieve data (read-only operation), so GET is correct across all options. The path structure for Cisco IOS XE RESTCONF follows: /restconf/api/running/native/interface/{interface-type}/{interface-number}/. Option A is wrong because it omits 'interface' from the path hierarchy, making it an invalid resource path. Option B is wrong because it addresses all GigabitEthernet interfaces rather than a specific one (no instance key). Option D uses an incorrect path segment ('ios') and targets interface 1 rather than the interface shown in the exhibit (interface 2). Option C correctly identifies GigabitEthernet interface 2 with the proper RESTCONF path structure for IOS XE.
Topics
Community Discussion
No community discussion yet for this question.
