Config caching in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What does Laravel's config caching do?

Laravel offers a command to cache configuration files. What is the main benefit of using config caching in a Laravel application?

A It encrypts config files to secure sensitive data.

B It combines all config files into a single file to speed up config loading.

C It automatically updates config files when environment variables change.

D It disables config files to improve performance.

💡 Hint

Think about how loading many files can affect performance.

Config caching merges all config files into one cached file. This reduces file reads and speeds up config loading.

❓ component_behavior

intermediate

Effect of config caching on config changes

If you run php artisan config:cache and then change a value in config/app.php, what will happen when you reload your Laravel app?

A The app will ignore the cached config and load the new config files.

B The app will automatically detect and use the new config values immediately.

C The app will use the old cached config values until you clear or refresh the cache.

D The app will throw an error because config files changed after caching.

💡 Hint

Think about what caching means for file changes.

After caching config, Laravel uses the cached file. Changes to config files won't apply until cache is cleared or rebuilt.

📝 Syntax

advanced

Identify the correct command to cache config

Which of the following artisan commands correctly caches the configuration in Laravel?

A php artisan cache-config

B php artisan cache:config

C php artisan config-cache

D php artisan config:cache

💡 Hint

Check the exact artisan command syntax.

The correct command is php artisan config:cache. Others are invalid and cause errors.

🔧 Debug

advanced

Why does config caching cause stale environment variables?

After running php artisan config:cache, you notice your app does not reflect changes made in the .env file. Why does this happen?

A Because config caching stores environment variables at cache time, so changes in <code>.env</code> are ignored until cache is rebuilt.

B Because Laravel does not support environment variables in config files.

C Because the <code>.env</code> file is deleted after caching config.

D Because config caching disables environment variables for security.

💡 Hint

Think about when environment variables are loaded in relation to caching.

Config caching compiles config and environment variables into one file. Changes to .env won't apply until cache is cleared and rebuilt.

❓ lifecycle

expert

Order of commands to update config cache after changes

You updated your .env and config/database.php files. Which sequence of commands correctly updates the config cache to reflect these changes?

A 1,2

B 3,1,2

C 1,2,3,4

D 2,1,3

💡 Hint

Focus on clearing and then caching config only.

The correct lifecycle is to clear the config cache, then rebuild it. cache:clear clears other caches but is not required here. config:refresh is not a valid command.