DELETE for removing resources in Rest API - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the HTTP status code returned after a successful DELETE request?

Consider a REST API where a DELETE request is sent to remove a resource. What is the typical HTTP status code returned to indicate success?

A 204 No Content

B 201 Created

C 200 OK

D 404 Not Found

💡 Hint

Think about a response that means the resource was deleted and no content is returned.

A successful DELETE request usually returns 204 No Content, meaning the resource was deleted and there is no content to send back.

❓ Predict Output

intermediate

What happens if you DELETE a resource that does not exist?

If you send a DELETE request to remove a resource that is not found on the server, what is the typical HTTP status code returned?

A 404 Not Found

B 204 No Content

C 200 OK

D 500 Internal Server Error

💡 Hint

Think about what the server returns when the resource is missing.

If the resource does not exist, the server usually returns 404 Not Found to indicate the resource was not found.

🧠 Conceptual

advanced

Why is DELETE considered an idempotent HTTP method?

In REST APIs, DELETE is called an idempotent method. What does this mean in practice?

A DELETE requests cannot be cached

B DELETE requests always return the same status code

C Multiple DELETE requests have the same effect as one DELETE request

D DELETE requests create new resources

💡 Hint

Idempotent means repeating the action does not change the result beyond the initial application.

DELETE is idempotent because sending the same DELETE request multiple times results in the same state as sending it once. After the first successful deletion, further DELETEs do nothing.

🔧 Debug

advanced

Why does this DELETE request return 405 Method Not Allowed?

You send a DELETE request to /api/items/123 but get a 405 error. What is the most likely cause?

Rest API

DELETE /api/items/123 HTTP/1.1
Host: example.com

A The resource 123 does not exist

B The server does not support DELETE on this endpoint

C The request is missing an authentication token

D The request method should be POST instead of DELETE

💡 Hint

405 means the method is not allowed on the URL.

A 405 Method Not Allowed means the server understands the request but does not allow DELETE on that URL. The endpoint likely only supports GET or POST.

🚀 Application

expert

How to safely implement DELETE to avoid accidental data loss?

You want to implement a DELETE endpoint in your API but want to avoid accidental data loss. Which approach is best?

A Return 200 OK even if the resource does not exist

B Allow DELETE requests without any checks to keep it simple

C Delete the resource immediately without logging

D Require a confirmation token in the DELETE request body before deleting

💡 Hint

Think about adding a safety step before deleting.

Requiring a confirmation token or similar check in the DELETE request helps prevent accidental deletions by ensuring the client really intends to delete the resource.