Why controllers organize request handling in Laravel - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a controller method that handles a request.

Laravel

public function index() {
    return view([1]);
}

Drag options to blanks, or click blank then click option'

A'home.index'

Bhome.index

C"home.index"

Dhome_index

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting quotes around the view name

Using dot notation without quotes

The view function expects the view name as a string in quotes.

2fill in blank

medium

Complete the code to import the base Controller class in Laravel.

Laravel

use [1];

Drag options to blanks, or click blank then click option'

AApp\Http\Controllers\Controller

BIlluminate\Http\Controller

CApp\Controller

DHttp\Controllers\Controller

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong namespace for Controller

Missing the full namespace path

Laravel controllers extend the base Controller class located in App\Http\Controllers\Controller.

3fill in blank

hard

Fix the error in the controller method to correctly retrieve all users.

Laravel

public function showUsers() {
    $users = User::[1]();
    return view('users.list', ['users' => $users]);
}

Drag options to blanks, or click blank then click option'

AgetAll

Bretrieve

Call

Dfetch

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like getAll or fetch

Forgetting parentheses after method name

The correct Eloquent method to get all records is all().

4fill in blank

hard

Fill both blanks to define a controller method that validates a request and stores a new post.

Laravel

public function store(Request $request) {
    $validated = $request->[1]([ 'title' => 'required', 'body' => 'required' ]);
    Post::[2]($validated);
    return redirect()->route('posts.index');
}

Drag options to blanks, or click blank then click option'

Avalidate

Bsave

Ccreate

Dstore

Attempts:

3 left

💡 Hint

Common Mistakes

Using save() on the model class instead of create()

Not validating request data before saving

The validate method checks the request data, and create saves a new model instance.

5fill in blank

hard

Fill all three blanks to define a controller method that updates a user and redirects with a success message.

Laravel

public function update(Request $request, $id) {
    $user = User::findOrFail([1]);
    $user->update($request->[2]());
    return redirect()->route('users.show', [3])->with('success', 'User updated!');
}

Drag options to blanks, or click blank then click option'

A$id

Ball

Dinput

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong variable names for user id

Using input() instead of all() for update data

Not passing id to redirect route

Use $id to find the user, all() to get all request data, and $id again for the redirect parameter.

Practice

1. Why do Laravel applications use controllers to handle requests instead of putting all code in routes?

easy

A. To organize code and separate routing from business logic

B. Because routes cannot handle HTTP requests

C. To make the application run faster

D. Because controllers automatically create database tables

Solution

1. Step 1: Understand the role of routes and controllers

   Routes define URL patterns, but controllers hold the logic to respond to those URLs.

2. Step 2: Recognize the benefit of separation

   Separating routing and logic keeps code organized and easier to maintain as the app grows.

3. Final Answer:

   To organize code and separate routing from business logic -> Option A

4. Quick Check:

   Controllers organize request handling = A [OK]

Hint: Controllers separate logic from routes for cleaner code [OK]

Common Mistakes:

• Thinking routes handle all logic
• Believing controllers speed up the app
• Assuming controllers create database tables

2. Which of the following is the correct way to define a controller method to handle a GET request in Laravel?

easy

A. public show() { return 'page'; }

B. public function show() { return view('page'); }

C. function show() { echo 'page'; }

D. def show() { return view('page'); }

Solution

1. Step 1: Recall Laravel controller method syntax

   Methods must be public functions inside a controller class.

2. Step 2: Check each option's syntax

   public function show() { return view('page'); } uses correct PHP syntax with public function and returns a view.

3. Final Answer:

   public function show() { return view('page'); } -> Option B

4. Quick Check:

   Laravel controller methods = public function [OK]

Hint: Use 'public function' for controller methods in Laravel [OK]

Common Mistakes:

• Omitting 'public' keyword
• Using wrong function syntax
• Using Python or other language syntax

3. Given this controller method in Laravel:

public function greet() { return 'Hello, Laravel!'; }

What will be the output when this method is called by a route?

medium

A. The view named 'Hello, Laravel!'

B. A blank page

C. An error because return type is missing

D. Hello, Laravel!

Solution

1. Step 1: Understand what the method returns

   The method returns a plain string 'Hello, Laravel!'.

2. Step 2: Know Laravel's response behavior

   Returning a string from a controller sends that string as the HTTP response body.

3. Final Answer:

   Hello, Laravel! -> Option D

4. Quick Check:

   Return string from controller = output string [OK]

Hint: Return strings directly to send text response [OK]

Common Mistakes:

• Expecting a view instead of string
• Thinking missing return type causes error
• Assuming blank page means success

4. This Laravel controller method has an error:

public function index() { echo 'Welcome'; }

What is the problem with this code?

medium

A. Using echo instead of return causes no response

B. Method must be private, not public

C. Missing semicolon after echo statement

D. Controller methods cannot output text

Solution

1. Step 1: Identify how Laravel expects responses

   Laravel expects controller methods to return responses, not echo output directly.

2. Step 2: Understand echo vs return in Laravel

   Echo sends output immediately but Laravel won't capture it as a proper HTTP response.

3. Final Answer:

   Using echo instead of return causes no response -> Option A

4. Quick Check:

   Use return, not echo, in controller methods [OK]

Hint: Always return response, never echo in controllers [OK]

Common Mistakes:

• Thinking echo works like return
• Believing method visibility is wrong
• Ignoring Laravel response rules

5. You want to organize your Laravel app so that all user-related request handling is in one place. Which approach best uses controllers to achieve this?

hard

A. Put all user logic directly inside web.php routes file

B. Create separate controllers for each user action like ShowUserController, EditUserController

C. Create a UserController with methods like show(), edit(), and update()

D. Write user logic inside middleware instead of controllers

Solution

1. Step 1: Understand controller grouping best practices

   Grouping related actions in one controller keeps code organized and easier to maintain.

2. Step 2: Evaluate options for organizing user logic

   Create a UserController with methods like show(), edit(), and update() groups user actions in UserController, which is standard Laravel practice.

3. Final Answer:

   Create a UserController with methods like show(), edit(), and update() -> Option C

4. Quick Check:

   Group related actions in one controller = B [OK]

Hint: Group related request methods in one controller class [OK]

Common Mistakes:

• Scattering user logic in routes file
• Creating too many single-action controllers
• Using middleware for business logic