HTTP 200 OK is typically returned for which REST operations?

HTTP 200 OK is typically returned for which REST operations?

• A. Created
• B. OK for GET, DELETE, PATCH, PUT
• C. Not Modified
• D. Bad Request

Answer: (B)

HTTP 200 OK means the request succeeded and the server is returning a representation in the response body. In REST, this status is typically used when an operation completes successfully and content is provided back to the client. For a GET, you fetch a resource and get it back with 200. For PUT and PATCH, which update a resource, the server commonly returns the updated resource in the response body with 200. For DELETE, if the API returns a payload confirming what was deleted or details about the result, 200 is commonly used as well (though some APIs return 204 No Content when there’s no body to return). The other options represent different scenarios: 201 Created is used when a new resource is created, 304 Not Modified relates to caching/conditional requests, and 400 Bad Request indicates a client-side error.

HTTP 200 OK means the request succeeded and the server is returning a representation in the response body. In REST, this status is typically used when an operation completes successfully and content is provided back to the client. For a GET, you fetch a resource and get it back with 200. For PUT and PATCH, which update a resource, the server commonly returns the updated resource in the response body with 200. For DELETE, if the API returns a payload confirming what was deleted or details about the result, 200 is commonly used as well (though some APIs return 204 No Content when there’s no body to return). The other options represent different scenarios: 201 Created is used when a new resource is created, 304 Not Modified relates to caching/conditional requests, and 400 Bad Request indicates a client-side error.