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.

Practice

1. Which HTTP method in Laravel routing is typically used to retrieve data from the server without changing it?

easy

A. GET

B. POST

C. PUT

D. DELETE

Solution

1. Step 1: Understand HTTP methods purpose

   GET requests are designed to fetch or read data without modifying it.

2. Step 2: Match method to Laravel routing

   In Laravel, routes defined with GET respond to data retrieval requests.

3. Final Answer:

   GET -> Option A

4. Quick Check:

   GET = Read data [OK]

Hint: GET is for reading data, no changes made [OK]

Common Mistakes:

• Confusing POST with GET for data retrieval
• Using PUT or DELETE for fetching data
• Thinking GET modifies data

2. Which of the following is the correct Laravel route definition for handling a POST request to '/submit'?

easy

A. Route::get('/submit', [FormController::class, 'store']);

B. Route::post('/submit', [FormController::class, 'store']);

C. Route::put('/submit', [FormController::class, 'store']);

D. Route::delete('/submit', [FormController::class, 'store']);

Solution

1. Step 1: Identify the HTTP method for creating data

   POST is used to send data to the server, typically for creating resources.

2. Step 2: Match Laravel route syntax for POST

   Route::post() defines a route that listens for POST requests.

3. Final Answer:

   Route::post('/submit', [FormController::class, 'store']); -> Option B

4. Quick Check:

   POST route syntax = Route::post('/submit', [FormController::class, 'store']); [OK]

Hint: Use Route::post() for form submissions [OK]

Common Mistakes:

• Using Route::get() for POST requests
• Mixing PUT or DELETE with form submission
• Incorrect method name in route definition

3. Given the following Laravel routes, what HTTP method should you use to update a user's profile?

Route::get('/user/{id}', [UserController::class, 'show']);
Route::post('/user', [UserController::class, 'store']);
Route::put('/user/{id}', [UserController::class, 'update']);
Route::delete('/user/{id}', [UserController::class, 'destroy']);

medium

A. PUT

B. GET

C. POST

D. DELETE

Solution

1. Step 1: Identify route for updating data

   The route with Route::put() is used for updating existing resources.

2. Step 2: Match HTTP method to update action

   PUT method is the standard for updating a resource like a user profile.

3. Final Answer:

   PUT -> Option A

4. Quick Check:

   Update = PUT method [OK]

Hint: PUT updates existing data, POST creates new [OK]

Common Mistakes:

• Using POST instead of PUT for updates
• Confusing GET with update actions
• Using DELETE to update data

4. You wrote this Laravel route to delete a post:

Route::post('/post/{id}', [PostController::class, 'destroy']);

Why might this cause a problem when trying to delete a post?

medium

A. The URL should not include an {id} parameter

B. Route syntax is incorrect for any HTTP method

C. The controller method name 'destroy' is invalid

D. POST method is not intended for deleting resources

Solution

1. Step 1: Understand HTTP methods for resource deletion

   DELETE method is the standard for deleting resources, not POST.

2. Step 2: Identify mismatch in route method

   Using Route::post() for deletion can cause unexpected behavior or conflicts.

3. Final Answer:

   POST method is not intended for deleting resources -> Option D

4. Quick Check:

   DELETE method needed for deletion [OK]

Hint: Use Route::delete() for deleting resources [OK]

Common Mistakes:

• Using POST instead of DELETE for deletions
• Ignoring HTTP method conventions
• Assuming controller method name causes error

5. You want to create a Laravel API that supports full CRUD operations on a 'product'. Which set of HTTP methods and routes correctly matches the standard RESTful pattern?

hard

A. Route::put('/product', [ProductController::class, 'index']);\nRoute::delete('/product', [ProductController::class, 'store']);\nRoute::get('/product/{id}', [ProductController::class, 'update']);\nRoute::post('/product/{id}', [ProductController::class, 'destroy']);

B. Route::post('/product', [ProductController::class, 'index']);\nRoute::get('/product', [ProductController::class, 'store']);\nRoute::delete('/product/{id}', [ProductController::class, 'update']);\nRoute::put('/product/{id}', [ProductController::class, 'destroy']);

C. Route::get('/product', [ProductController::class, 'index']);\nRoute::post('/product', [ProductController::class, 'store']);\nRoute::put('/product/{id}', [ProductController::class, 'update']);\nRoute::delete('/product/{id}', [ProductController::class, 'destroy']);

D. Route::delete('/product', [ProductController::class, 'index']);\nRoute::put('/product', [ProductController::class, 'store']);\nRoute::post('/product/{id}', [ProductController::class, 'update']);\nRoute::get('/product/{id}', [ProductController::class, 'destroy']);

Solution

1. Step 1: Match HTTP methods to CRUD actions

   GET for reading list (index), POST for creating (store), PUT for updating, DELETE for deleting.

2. Step 2: Verify route patterns and controller methods

   Routes in Route::get('/product', [ProductController::class, 'index']);\nRoute::post('/product', [ProductController::class, 'store']);\nRoute::put('/product/{id}', [ProductController::class, 'update']);\nRoute::delete('/product/{id}', [ProductController::class, 'destroy']); correctly pair HTTP methods with controller actions and URL patterns.

3. Final Answer:

   Route::get('/product', [ProductController::class, 'index']);\nRoute::post('/product', [ProductController::class, 'store']);\nRoute::put('/product/{id}', [ProductController::class, 'update']);\nRoute::delete('/product/{id}', [ProductController::class, 'destroy']); -> Option C

4. Quick Check:

   GET, POST, PUT, DELETE with correct methods = Route::get('/product', [ProductController::class, 'index']);\nRoute::post('/product', [ProductController::class, 'store']);\nRoute::put('/product/{id}', [ProductController::class, 'update']);\nRoute::delete('/product/{id}', [ProductController::class, 'destroy']); [OK]

Hint: Follow REST: GET-read, POST-create, PUT-update, DELETE-remove [OK]

Common Mistakes:

• Mixing HTTP methods and controller actions
• Incorrect URL patterns for resource IDs
• Using wrong methods for CRUD operations