HTTP method routing (GET, POST, PUT, DELETE) in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output when accessing a Laravel route defined with GET method?

Consider this Laravel route definition:

Route::get('/welcome', function () {
    return 'Hello GET!';
});

What will be the response when a browser sends a GET request to /welcome?

Laravel

Route::get('/welcome', function () {
    return 'Hello GET!';
});

A The browser receives a 404 Not Found error.

B The browser receives 'Hello GET!' as the response body.

C The browser receives a 405 Method Not Allowed error.

D The browser receives an empty response with status 200.

💡 Hint

Think about what the GET method means in HTTP and how Laravel matches routes.

Laravel matches the GET request to the route and executes the closure, returning the string 'Hello GET!'.

📝 Syntax

intermediate

Which Laravel route definition correctly handles a POST request?

Which of the following route definitions correctly handles POST requests to /submit?

A Route::post('/submit', function () { return 'Posted!'; });

B Route::delete('/submit', function () { return 'Posted!'; });

C Route::put('/submit', function () { return 'Posted!'; });

D Route::get('/submit', function () { return 'Posted!'; });

💡 Hint

POST requests are used to send data to the server. Which method matches POST?

Only Route::post matches POST HTTP requests. Others match different methods.

🔧 Debug

advanced

Why does this Laravel route return a 405 Method Not Allowed error?

Given these routes:

Route::get('/item', function () {
    return 'GET item';
});

Route::post('/item', function () {
    return 'POST item';
});

What happens if a client sends a PUT request to /item?

Laravel

Route::get('/item', function () {
    return 'GET item';
});

Route::post('/item', function () {
    return 'POST item';
});

A Laravel returns a 404 Not Found error because /item does not exist.

B Laravel returns 'GET item' because GET is the default fallback.

C Laravel returns 'POST item' because POST matches all methods except GET.

D Laravel returns a 405 Method Not Allowed error because no route handles PUT for /item.

💡 Hint

Check which HTTP methods are defined for the route and what happens if the method is not matched.

Laravel returns 405 when the URL exists but the HTTP method is not supported by any route.

❓ state_output

advanced

What is the output after sending a DELETE request to this Laravel route?

Consider this route:

Route::delete('/post/{id}', function ($id) {
    return "Deleted post with ID: $id";
});

What will be the response body if a DELETE request is sent to /post/42?

Laravel

Route::delete('/post/{id}', function ($id) {
    return "Deleted post with ID: $id";
});

A Deleted post with ID: {id}

B 404 Not Found error

C Deleted post with ID: 42

D 405 Method Not Allowed error

💡 Hint

Think about how route parameters work in Laravel and how the DELETE method is matched.

The route matches DELETE requests to /post/{id} and passes the id parameter to the closure, returning the string with the actual id.

🧠 Conceptual

expert

Which HTTP method should you use in Laravel to update an existing resource partially?

In RESTful routing, which HTTP method is conventionally used to partially update an existing resource in Laravel?

A PATCH

B POST

C PUT

D DELETE

💡 Hint

PUT replaces the entire resource, but partial updates use a different method.

PATCH is used for partial updates, while PUT replaces the entire resource. POST creates new resources, DELETE removes them.