Laravel project structure - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Identify the purpose of the 'app' directory in Laravel

In a Laravel project, what is the main purpose of the app directory?

A It contains configuration files for the application.

B It contains the core application code like models, controllers, and services.

C It holds the database migration files and seeders.

D It stores all the public assets like images, CSS, and JavaScript files.

💡 Hint

Think about where the main PHP code for your app lives.

The app directory is where Laravel keeps the main application code such as models, controllers, and other classes that define the app's behavior.

❓ component_behavior

intermediate

What happens if you place a view file outside the 'resources/views' directory?

In Laravel, where should you place your Blade view files for them to be properly loaded? What happens if you put a view file outside the resources/views directory and try to load it?

A The view will load but without any styling or scripts.

B Laravel will automatically search all directories and load the view from anywhere.

C Laravel will not find the view and will throw a "View not found" error.

D Laravel will load the view but cache it in the wrong location.

💡 Hint

Think about how Laravel organizes views by default.

Laravel expects all Blade view files to be inside resources/views. If a view is outside this folder, Laravel cannot find it and throws an error.

📝 Syntax

advanced

Which directory contains the route definitions in a Laravel project?

Where are the route files located in a Laravel project by default?

A Within the <code>resources/views</code> directory.

B In the <code>config</code> directory.

C Inside the <code>app/Http</code> directory.

D In the <code>routes</code> directory at the project root.

💡 Hint

Routes define how URLs map to code and are usually kept separate.

Laravel stores route definitions in files inside the routes directory, such as web.php and api.php.

🔧 Debug

advanced

Why does Laravel fail to load environment variables?

You moved your Laravel project to a new server, but the app does not load environment variables from the .env file. What is the most likely cause?

A The <code>.env</code> file is missing or not readable by the server.

B The <code>config</code> directory is empty.

C The <code>app</code> directory is renamed.

D The <code>public</code> directory is missing.

💡 Hint

Environment variables come from a special file that must be present and readable.

Laravel loads environment variables from the .env file. If this file is missing or the server cannot read it, the variables won't load.

❓ state_output

expert

What is the output of accessing a route with a missing controller method?

Given a Laravel route defined as Route::get('/test', [TestController::class, 'missingMethod']); but the missingMethod does not exist in TestController, what happens when you visit /test in the browser?

A Laravel throws a 500 Internal Server Error with a message about the missing method.

B Laravel loads the default welcome page.

C Laravel returns a 404 Not Found error.

D Laravel redirects to the home page.

💡 Hint

Think about what happens when Laravel tries to call a method that does not exist.

Laravel tries to call the specified controller method. If it does not exist, it throws a 500 error indicating the method is missing.

Practice

1. Which folder in a Laravel project contains the files that define the URL routes for the application?

easy

A. config

B. app

C. resources

D. routes

Solution

1. Step 1: Understand the purpose of the routes folder

   The routes folder holds files that define how URLs map to code actions in Laravel.

2. Step 2: Compare with other folders

   The app folder contains core code, resources holds views and assets, and config stores configuration settings.

3. Final Answer:

   routes -> Option D

4. Quick Check:

   URL routes = routes folder [OK]

Hint: Routes are always in the routes folder [OK]

Common Mistakes:

• Confusing app with routes folder
• Thinking views are in routes
• Mixing config files with routes

2. Which of the following is the correct path to store Blade template files in a Laravel project?

easy

A. public/templates

B. app/Views

C. resources/views

D. config/views

Solution

1. Step 1: Identify where Blade templates are stored

   Blade templates are stored in the resources/views folder by Laravel convention.

2. Step 2: Verify other options

   app/Views is not standard, public/templates is for public assets, and config/views is not used for templates.

3. Final Answer:

   resources/views -> Option C

4. Quick Check:

   Blade templates = resources/views [OK]

Hint: Templates live in resources/views folder [OK]

Common Mistakes:

• Putting templates in app folder
• Confusing public assets with views
• Trying to store views in config folder

3. Given this Laravel project structure snippet:

app/
  Http/
    Controllers/
resources/
  views/
routes/
  web.php

Where should you place a new controller named ProductController.php?

medium

A. app/Http/Controllers/ProductController.php

B. resources/views/ProductController.php

C. routes/ProductController.php

D. app/ProductController.php

Solution

1. Step 1: Locate where controllers go in Laravel

   Controllers are placed inside app/Http/Controllers folder to handle requests.

2. Step 2: Check other folders for controllers

   resources/views is for templates, routes is for route files, and app root is not for controllers.

3. Final Answer:

   app/Http/Controllers/ProductController.php -> Option A

4. Quick Check:

   Controllers = app/Http/Controllers [OK]

Hint: Controllers live in app/Http/Controllers [OK]

Common Mistakes:

• Placing controllers in views folder
• Putting controllers directly in app root
• Confusing routes folder with controllers

4. You try to access a configuration value in Laravel using config('database.host') but get an error. What is the most likely cause?

medium

A. The routes/web.php file is empty

B. The database.php config file is missing or misnamed

C. The app/Http/Controllers folder is missing

D. The resources/views folder has no Blade files

Solution

1. Step 1: Understand how config() works in Laravel

   The config() helper reads values from files in the config folder, like database.php.

2. Step 2: Identify cause of error

   If database.php is missing or misnamed, config('database.host') cannot find the value, causing an error.

3. Final Answer:

   The database.php config file is missing or misnamed -> Option B

4. Quick Check:

   Missing config file = error on config() call [OK]

Hint: Check config files exist for config() calls [OK]

Common Mistakes:

• Blaming routes or controllers for config errors
• Ignoring missing or misnamed config files
• Assuming views affect config values

5. You want to add a new API endpoint in your Laravel app. Which folders must you update to add a route, controller, and response view correctly?

hard

A. Update routes/api.php, create controller in app/Http/Controllers, and add view in resources/views

B. Update routes/web.php, create controller in app/Models, and add view in public

C. Update config/api.php, create controller in app/Http/Controllers, and add view in resources/assets

D. Update routes/api.php, create controller in app/Http/Middleware, and add view in resources/views

Solution

1. Step 1: Identify where API routes are defined

   API routes go in routes/api.php to separate them from web routes.

2. Step 2: Locate correct controller and view folders

   Controllers belong in app/Http/Controllers, and views go in resources/views.

3. Step 3: Check incorrect options

   app/Models is for data models, public is for assets, config/api.php is not standard, and middleware folder is for request filters.

4. Final Answer:

   Update routes/api.php, create controller in app/Http/Controllers, and add view in resources/views -> Option A

5. Quick Check:

   API route + controller + view folders = Update routes/api.php, create controller in app/Http/Controllers, and add view in resources/views [OK]

Hint: API routes in routes/api.php, controllers in app/Http/Controllers [OK]

Common Mistakes:

• Putting API routes in routes/web.php
• Creating controllers in wrong folders
• Adding views outside resources/views