Q: 8
What do 2xx HTTP response codes indicate for REST APIs?
Options
Discussion
Hard to say, C. 2xx responses handle protocol-level info, like 201 for resource created or 204 for no content. Not totally sure though, maybe I'm missing something simple here.
D imo, had something like this in a mock and it was successful request for REST APIs.
Yeah, D tbh. 2xx status codes show success for HTTP requests, so with REST APIs it means the operation worked as expected. Haven't seen any real exceptions to this. Let me know if there's a catch I'm missing.
I kind of see why C might seem right since HTTP status codes are part of the protocol, but for REST APIs, 2xx usually signals the request was handled successfully. Not totally convinced though-depends how strict they want to be with wording here. Agree?
Option D that's what the official Cisco study guide and REST API docs both say. Check practice exams for similar questions.
D tbh, 2xx always means a successful request was received and processed. That’s how REST APIs signal things went fine, no extra steps needed from the client. Only caveat is if async or batch, but not mentioned here.
D official guide and API docs say 2xx is success. Anyone else got a different resource?
D imo, 2xx HTTP codes always mean the client’s request was successful. Seen this in API docs a lot, so pretty confident here.
Be respectful. No spam.
