CCNP Practice Question: Which three statements about HTTP response status…

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 is used to indicate a successful GET request.

  Why this is correct

  A successful GET returns the requested representation with 200 OK, confirming the resource was retrieved. This is the standard success code for read operations, distinguishing it from 201, which signals resource creation rather than retrieval.

• ✓

  201 Created is returned when a resource is successfully created via POST.

  Why this is correct

  A successful POST that creates a resource returns 201 Created, typically with a Location header pointing to the new resource. This distinguishes creation from 200 OK, which merely confirms a successful request without implying a new resource.

• ✗

  404 Not Found indicates a server-side error.

  Why it's wrong here

  404 is a client error: the request URI does not map to an existing resource, so the client must correct the path. It is tempting because the resource is absent on the server, but the 4xx class assigns fault to the requester; 5xx codes such as 500 denote server-side failures.

• ✓

  400 Bad Request is a client error indicating malformed request syntax.

  Why this is correct

  400 sits in the 4xx client-error class, returned when the server cannot process a request due to malformed syntax, invalid framing or bad parameters. It is not a server fault, so it correctly describes client-side request defects in REST APIs.

• ✗

  500 Internal Server Error is a client error.

  Why it's wrong here

  500 belongs to the 5xx server error class, signalling the server failed while processing an otherwise valid request. It is tempting because the failure surfaces at the server, but classification depends on which party is at fault, not where the error appears; 4xx codes such as 400 denote client errors.