Q: 16
DRAG DROP Drag and drop the code from the bottom onto the box where the code is missing to configure a router that runs Cisco IOS XE by using RESTCONF. The API call is made to the management URL of the IOS XE device and on a registered port number. Errors that are caught during HTTP operation are registered. Not all options are used. 
Drag & Drop
Discussion
ios-xe-mgmt, 9443, requests.patch, 201
That's the order I remember from a similar question on a practice set. The patch method lines up with making config changes via RESTCONF and port 9443 is standard for IOS XE mgmt. Pretty sure this matches what Cisco expects.
That's the order I remember from a similar question on a practice set. The patch method lines up with making config changes via RESTCONF and port 9443 is standard for IOS XE mgmt. Pretty sure this matches what Cisco expects.
ios-xe-mgmt, 9443, requests.patch, 201. Had something like this in a mock, this ordering fits RESTCONF with IOS XE.
Yeah, this order makes sense for RESTCONF on IOS XE: ios-xe-mgmt, 9443, requests.patch, 201. Port 9443 is the default for mgmt traffic, and PATCH is what's used for updating config. I think that's right but open to correction.
Hmm, respectfully disagree with some of the earlier posts. It should be ios-xe-mgmt, 9443, requests.patch, 201. Port 9443 is typical for RESTCONF on IOS XE and PATCH matches partial config updates. Some might pick requests.post here but that would be for new resources, not updates. Correct me if I'm off but this is what I've seen in exam reports.
ios-xe-mgmt, 401, requests.post, 201. I put 401 since that's the HTTP Unauthorized code and figured it might show up if there's an authentication issue during RESTCONF access. Used post instead of patch thinking it's needed for sending data. Not fully sure on the status code though, someone else maybe confirm?
Be respectful. No spam.
