MVC architecture in Laravel - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does MVC stand for in Laravel?

MVC stands for Model-View-Controller. It is a design pattern that separates an application into three main parts to organize code and responsibilities.

beginner

What is the role of the Model in Laravel's MVC?

The Model handles data and business logic. It interacts with the database and manages data retrieval, storage, and validation.

beginner

What does the Controller do in Laravel's MVC?

The Controller receives user input, processes it (often using Models), and returns a response, usually by selecting a View to display.

beginner

What is the purpose of the View in Laravel's MVC?

The View displays the user interface. It shows data to the user and formats the output, usually using Blade templates in Laravel.

beginner

How does Laravel help organize MVC components?

Laravel provides folders like app/Models for Models, app/Http/Controllers for Controllers, and resources/views for Views, keeping code clean and easy to find.

In Laravel MVC, which component handles database queries?

A Controller

B View

C Model

D Route

The Model is responsible for interacting with the database and managing data.

Which Laravel folder typically contains the Controller files?

A app/Models

B app/Http/Controllers

C resources/views

D public

Controllers are stored in app/Http/Controllers in Laravel.

What is the main job of the View in Laravel MVC?

A Display data to the user

B Handle database logic

C Process user input

D Manage routes

The View shows data and user interface elements to the user.

Which Laravel feature is commonly used to create Views?

A Blade templates

B Eloquent ORM

C Middleware

D Artisan commands

Blade is Laravel's templating engine used to build Views.

In MVC, where should business logic mainly reside?

A View

B Controller

C Route

D Model

Business logic belongs in the Model to keep code organized and reusable.

Explain the responsibilities of Model, View, and Controller in Laravel's MVC architecture.

Think about who talks to the database, who shows the screen, and who manages the flow.

Describe how Laravel organizes MVC components in its folder structure.

Remember the main folders where each part lives.

Practice

1. In Laravel's MVC architecture, which component is responsible for handling user input and application logic?

easy

A. Controller

B. Model

C. View

D. Route

Solution

1. Step 1: Understand MVC roles

   Model handles data, View handles UI, Controller handles logic and user input.

2. Step 2: Identify the component for logic

   Controller processes requests, applies logic, and returns responses.

3. Final Answer:

   Controller -> Option A

4. Quick Check:

   Logic and input handling = Controller [OK]

Hint: Controller = logic and input handler in MVC [OK]

Common Mistakes:

• Confusing Model with Controller
• Thinking View handles logic
• Assuming Route handles logic

2. Which of the following is the correct way to define a route that calls the show method of UserController in Laravel?

easy

A. Route::get('/user/{id}', [UserController, 'show']);

B. Route::get('/user/{id}', 'show@UserController');

C. Route::get('/user/{id}', function() { UserController@show(); });

D. Route::get('/user/{id}', 'UserController@show');

Solution

1. Step 1: Recall Laravel route syntax

   Routes use Route::get('uri', 'Controller@method') format for controller methods.

2. Step 2: Match correct syntax

   Route::get('/user/{id}', 'UserController@show'); matches this pattern exactly; others have syntax errors or wrong order.

3. Final Answer:

   Route::get('/user/{id}', 'UserController@show'); -> Option D

4. Quick Check:

   Correct route syntax = Route::get('/user/{id}', 'UserController@show'); [OK]

Hint: Use 'Controller@method' string in routes [OK]

Common Mistakes:

• Using array without quotes
• Swapping controller and method order
• Using anonymous function incorrectly

3. Given this Laravel controller method, what will be the output when accessing /welcome route?

public function welcome() {
    $name = 'Alice';
    return view('greeting', ['name' => $name]);
}

Assuming the greeting.blade.php view contains:

<h1>Hello, {{ $name }}!</h1>

medium

A. Error: Undefined variable $name

B. Hello, Alice!

C. Hello, $name!

D. Hello, !

Solution

1. Step 1: Understand data passing to view

   The controller passes ['name' => 'Alice'] to the view as variable $name.

2. Step 2: Interpret Blade template output

   The view uses {{ $name }} which outputs 'Alice' safely inside <h1> tags.

3. Final Answer:

   <h1>Hello, Alice!</h1> -> Option B

4. Quick Check:

   Passed variable rendered correctly = <h1>Hello, Alice!</h1> [OK]

Hint: Variables passed to view appear as {{ $variable }} [OK]

Common Mistakes:

• Expecting raw variable name output
• Confusing PHP variable syntax inside Blade
• Assuming missing variable error

4. Identify the error in this Laravel controller method:

public function index() {
    $users = User::all;
    return view('users.index', compact('users'));
}

medium

A. Missing parentheses after all() method

B. Incorrect view name syntax

C. compact() should be replaced with array()

D. User model not imported

Solution

1. Step 1: Check method call syntax

   User::all is a method and requires parentheses: User::all() to fetch all users.

2. Step 2: Verify other parts

   View name and compact usage are correct; import is assumed correct or handled by namespace.

3. Final Answer:

   Missing parentheses after all() method -> Option A

4. Quick Check:

   Method calls need () = Missing parentheses after all() method [OK]

Hint: Remember to add () when calling methods [OK]

Common Mistakes:

• Forgetting parentheses on method calls
• Misusing compact() function
• Assuming view name syntax error

5. You want to display a list of products with their categories in a Laravel app using MVC. Which approach correctly follows MVC principles?

hard

A. Use Controller only to render HTML, fetching done in View

B. Write SQL queries directly in the View to get products and categories

C. Fetch products and categories in Controller, pass to View, and display there

D. Put all fetching and HTML rendering inside the Model

Solution

1. Step 1: Recall MVC responsibilities

   Model handles data, Controller handles logic and data fetching, View handles display.

2. Step 2: Evaluate options

   Fetch products and categories in Controller, pass to View, and display there correctly fetches data in Controller and passes it to View for display, following MVC.

3. Final Answer:

   Fetch products and categories in Controller, pass to View, and display there -> Option C

4. Quick Check:

   Controller fetches, View displays = Fetch products and categories in Controller, pass to View, and display there [OK]

Hint: Controller fetches data; View only displays it [OK]

Common Mistakes:

• Putting SQL in Views
• Mixing data logic in Models with display
• Letting Views fetch data