Resource controllers in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this resource controller route?

Consider a Laravel resource controller registered as Route::resource('photos', PhotoController::class);. What URL and HTTP method will trigger the edit method of PhotoController?

A PUT /photos/{photo}/edit

B POST /photos/{photo}/edit

C GET /photos/{photo}/edit

D GET /photos/edit/{photo}

💡 Hint

Remember the RESTful conventions for resource controllers in Laravel.

The edit method is accessed via a GET request to /photos/{photo}/edit. This URL shows a form to edit the photo resource.

❓ state_output

intermediate

What is the value of $request->method() in the update method?

In a Laravel resource controller, the update method is called when submitting an edit form. What HTTP method does $request->method() return inside the update method?

A PUT

B PATCH

C GET

D POST

💡 Hint

Laravel uses a special hidden input to spoof HTTP methods in forms.

The update method responds to PUT or PATCH requests. Standard Laravel edit forms use @method('PUT'), so $request->method() returns PUT.

📝 Syntax

advanced

Which option correctly registers a resource controller with only index and show methods?

You want to register a resource controller but only allow the index and show methods. Which route registration is correct?

A Route::resource('posts', PostController::class)->except(['create', 'edit']);

B Route::resource('posts', PostController::class)->filter(['index', 'show']);

C Route::resource('posts', PostController::class)->methods(['index', 'show']);

D Route::resource('posts', PostController::class)->only(['index', 'show']);

💡 Hint

Check Laravel's resource route options for limiting methods.

The only method limits the resource routes to specified methods. except excludes methods but is not the best choice here. methods and filter do not exist.

🔧 Debug

advanced

Why does this resource controller method not receive the model instance?

Given this resource controller method:

public function show(Post $post) { return view('post.show', compact('post')); }

And this route registration:

Route::resource('posts', PostController::class);

Why might $post be null or cause an error?

A The model class <code>Post</code> does not exist.

B The route parameter name does not match the method parameter name.

C The controller method is missing a return statement.

D The route is missing a middleware for authentication.

💡 Hint

Check the route parameter names and method parameter names for exact match.

Laravel uses route model binding by matching the route parameter name with the method parameter name. If they differ, Laravel cannot inject the model instance.

🧠 Conceptual

expert

What is the main advantage of using resource controllers in Laravel?

Why do developers prefer using resource controllers instead of defining individual routes for each CRUD action?

A They automatically generate all standard CRUD routes with consistent naming and HTTP methods.

B They allow defining routes without any controller methods.

C They disable CSRF protection for all routes automatically.

D They force all routes to use the GET method for simplicity.

💡 Hint

Think about how resource controllers help organize routes and methods.

Resource controllers provide a clean, standardized way to create all CRUD routes with proper HTTP verbs and route names, reducing repetitive code and improving maintainability.