.env file and environment variables in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this Laravel config call?

Given the .env file contains APP_NAME=MyApp, what will config('app.name') return in a Laravel controller?

Laravel

<?php
// .env file
APP_NAME=MyApp

// In a controller method
return config('app.name');

A "MyApp"

B "APP_NAME"

C null

D "app.name"

💡 Hint

Remember Laravel loads .env values into config files during bootstrap.

The config('app.name') call returns the value set in config/app.php which uses env('APP_NAME', 'Laravel'). Since APP_NAME is set in .env as "MyApp", it returns "MyApp".

📝 Syntax

intermediate

Which .env syntax is correct for setting a boolean?

You want to set APP_DEBUG to true in your .env file. Which line is correct?

A APP_DEBUG=true

B APP_DEBUG=True

C APP_DEBUG=1

D APP_DEBUG='true'

💡 Hint

.env files treat all values as strings; Laravel converts some values automatically.

Laravel treats APP_DEBUG as a boolean. Setting APP_DEBUG=1 works correctly because Laravel converts '1' to true. Other options are strings and may not convert properly.

🔧 Debug

advanced

Why does env('MY_VAR') return null despite being set in .env?

You set MY_VAR=hello in your .env file but env('MY_VAR') returns null in your Laravel app. What is the most likely cause?

A The variable name is case sensitive and should be lowercase

B The .env file is missing the closing semicolon

C You need to restart the web server for .env changes to apply

D You forgot to run <code>php artisan config:cache</code> after changing .env

💡 Hint

Think about Laravel's config caching behavior.

If you have cached your config with php artisan config:cache, Laravel ignores .env changes until you clear or refresh the cache. This causes env() to return null for new variables.

❓ state_output

advanced

What is the value of config('database.default') after this .env change?

If your .env file has DB_CONNECTION=pgsql and your config/database.php uses env('DB_CONNECTION', 'mysql'), what will config('database.default') return?

A "mysql"

B "pgsql"

C null

D "DB_CONNECTION"

💡 Hint

Check how env fallback values work.

The config/database.php file uses env('DB_CONNECTION', 'mysql'). Since DB_CONNECTION is set to "pgsql" in .env, the config returns "pgsql".

🧠 Conceptual

expert

Why should sensitive keys not be committed to version control in .env?

Which is the best reason to exclude .env files containing sensitive keys from version control systems like Git?

A To prevent exposing secrets like API keys and passwords publicly

B To avoid merge conflicts when multiple developers edit the same .env

C Because Laravel automatically regenerates .env files on deployment

D Because .env files are too large and slow down Git operations

💡 Hint

Think about security risks of sharing secrets.

.env files often contain sensitive information like database passwords and API keys. Committing them publicly risks exposing these secrets to unauthorized users.