DVA-C02 Deployment Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  200: OK

  Why this is correct

  200 OK is the standard success response in HTTP, indicating that the server fully processed the request and is returning the expected content in the response body. It is used for successful requests such as GET, where the resource is retrieved, and it can also accompany responses to POST or PUT that include the result of an action. Unlike 201 Created, 200 does not imply that a new resource was created; it simply confirms that the request completed without error.

• ✓

  404: Not Found

  Why this is correct

  404 Not Found is a client-error status returned when the server cannot find a resource matching the request URI, commonly caused by a typo in the URL, a deleted resource, or an undefined route. This status tells the client that the request itself is well-formed but the target resource is absent. It is distinct from 403 Forbidden, because the server is not making an authorization decision; it simply has nothing to serve.

• ✓

  500: Internal Server Error

  Why this is correct

  500 Internal Server Error is a generic server-error response, raised when an unexpected condition prevents the server from fulfilling the request. It typically signals an unhandled exception, a configuration problem, or a failure in a downstream backend service, and the server does not expose specific details about the root cause. Unlike 4xx errors, which implicate the client, 500 makes it clear that the fault lies with the server infrastructure.

• ✗

  200: Created

  Why it's wrong here

  Treating 200 as an indication of a newly created resource is incorrect because 200 OK does not carry any semantic meaning about resource creation. The proper status for a successful creation is 201 Created, which explicitly informs the client that a new resource has been created and typically includes a Location header pointing to that resource. Using 200 in place of 201 loses this important signal, which can break clients that rely on the status code to trigger subsequent actions.

• ✗

  404: Forbidden

  Why it's wrong here

  Matching 404 with 'Forbidden' is a semantic error because the two codes address entirely different problems. 403 Forbidden is the correct response when the server understands the request but refuses to authorize it, meaning the resource exists but the client lacks permission. 404 Not Found, on the other hand, means the resource cannot be located regardless of permissions. Using 404 to indicate forbidden not only misrepresents the state but can also inadvertently conceal whether a resource exists, creating confusion for clients and potential security leaks.

Go deeper

Related to this question