Database configuration in Laravel - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Laravel Database Default Connection

In Laravel's config/database.php, what does the 'default' key specify?

A The default database username for all connections.

B The default database password for all connections.

C The name of the database connection Laravel uses by default for all queries.

D The default database port number for all connections.

💡 Hint

Think about what Laravel needs to know first when connecting to a database.

The 'default' key tells Laravel which database connection to use if none is specified explicitly in queries.

❓ component_behavior

intermediate

Effect of Changing DB_CONNECTION in .env

If you change DB_CONNECTION in your Laravel .env file from mysql to sqlite but do not update config/database.php, what will happen when you run database queries?

A Laravel will throw an error because the .env and config/database.php are out of sync.

B Laravel will use the SQLite connection settings from <code>config/database.php</code> and connect to SQLite.

C Laravel will continue using MySQL connection settings ignoring the .env change.

D Laravel will connect to MySQL but use SQLite syntax for queries.

💡 Hint

Remember how Laravel uses environment variables to configure connections.

Laravel reads the DB_CONNECTION from the .env file and uses the matching connection settings from config/database.php. So changing .env to 'sqlite' makes Laravel use SQLite settings.

📝 Syntax

advanced

Correct Laravel Database Connection Array Syntax

Which of the following is the correct syntax for defining a MySQL connection in config/database.php?

A 'mysql' => [ 'driver' => 'mysql', 'host' => env('DB_HOST', '127.0.0.1'), 'port' => env('DB_PORT', '3306'), 'database' => env('DB_DATABASE', 'forge'), 'username' => env('DB_USERNAME', 'forge'), 'password' => env('DB_PASSWORD', ''), 'charset' => 'utf8mb4', 'collation' => 'utf8mb4_unicode_ci', 'prefix' => '', 'strict' => true, 'engine' => null ],

B 'mysql' => ( 'driver' => 'mysql', 'host' => 'localhost', 'port' => 3306, 'database' => 'forge', 'username' => 'forge', 'password' => '', 'charset' => 'utf8mb4', 'collation' => 'utf8mb4_unicode_ci', 'prefix' => '', 'strict' => true, 'engine' => null ),

C 'mysql' => { 'driver': 'mysql', 'host': 'localhost', 'port': 3306, 'database': 'forge', 'username': 'forge', 'password': '', 'charset': 'utf8mb4', 'collation': 'utf8mb4_unicode_ci', 'prefix': '', 'strict': true, 'engine': null },

D 'mysql' => [ 'driver' => 'mysql', 'host' => 'localhost', 'port' => 3306, 'database' => 'forge', 'username' => 'forge', 'password' => '', 'charset' => 'utf8mb4', 'collation' => 'utf8mb4_unicode_ci', 'prefix' => '', 'strict' => true, 'engine' => null ],

💡 Hint

Remember PHP array syntax and data types for boolean values.

Option A uses correct PHP array syntax with square brackets and uses boolean true without quotes. Option A uses parentheses which is invalid for arrays. Option A uses curly braces and colons which is JavaScript syntax, not PHP. Option A uses string 'true' instead of boolean true.

🔧 Debug

advanced

Diagnosing Laravel Database Connection Failure

You get a SQLSTATE[HY000] [1045] Access denied for user error when running Laravel migrations. Which of the following is the most likely cause?

A The Laravel cache is not cleared after changing migration files.

B The database server is down and unreachable.

C The database name in config/database.php is misspelled.

D The database username or password in the .env file is incorrect or missing.

💡 Hint

Access denied errors usually relate to credentials.

Error 1045 means the database rejected the username or password. This usually means the credentials in .env are wrong or missing.

❓ state_output

expert

Result of Changing Database Configuration at Runtime

In Laravel, if you call config(['database.default' => 'sqlite']); at runtime, what will be the effect on subsequent database queries?

A The change will not affect queries because the database connection is cached at boot.

B Queries will randomly switch between the old and new connections.

C Laravel will throw an error because the default connection cannot be changed at runtime.

D Subsequent queries will use the SQLite connection without restarting the app.

💡 Hint

Think about when Laravel loads and caches configuration values.

Laravel loads and caches database connections at boot. Changing config at runtime does not affect the active connection unless the app is restarted or cache cleared.

Practice

1. What is the main purpose of the .env file in Laravel's database configuration?

easy

A. To write SQL queries directly

B. To store user session data

C. To define routes for the application

D. To securely store database connection details like username and password

Solution

1. Step 1: Understand the role of the .env file

   The .env file holds environment-specific settings, including sensitive data like database credentials.

2. Step 2: Identify what is stored in .env for database

   It stores host, database name, username, and password securely, keeping them out of code files.

3. Final Answer:

   To securely store database connection details like username and password -> Option D

4. Quick Check:

   .env stores sensitive config = B [OK]

Hint: Remember .env keeps secrets safe, not code or queries [OK]

Common Mistakes:

• Thinking .env stores SQL queries
• Confusing .env with route files
• Assuming .env stores user data

2. Which of the following is the correct way to set the database connection type in Laravel's .env file?

easy

A. DB_CONNECTION=mysql

B. DATABASE=mysql

C. DB_TYPE=mysql

D. CONNECTION_DB=mysql

Solution

1. Step 1: Recall Laravel's .env database config keys

   Laravel uses keys starting with DB_, such as DB_CONNECTION for the driver type.

2. Step 2: Match the correct key for connection type

   The correct key is DB_CONNECTION, set to the database type like mysql, pgsql, sqlite.

3. Final Answer:

   DB_CONNECTION=mysql -> Option A

4. Quick Check:

   DB_CONNECTION sets driver = C [OK]

Hint: DB_CONNECTION is the exact key for database type [OK]

Common Mistakes:

• Using DATABASE or DB_TYPE instead of DB_CONNECTION
• Mixing key order or spelling
• Forgetting to set DB_CONNECTION at all

3. Given this .env snippet:

DB_CONNECTION=pgsql
DB_HOST=127.0.0.1
DB_PORT=5432
DB_DATABASE=mydb
DB_USERNAME=user
DB_PASSWORD=pass

What database type will Laravel connect to?

medium

A. MySQL

B. PostgreSQL

C. SQLite

D. SQL Server

Solution

1. Step 1: Check the DB_CONNECTION value

   The value is 'pgsql', which is the driver name for PostgreSQL in Laravel.

2. Step 2: Match driver to database type

   'pgsql' corresponds to PostgreSQL, not MySQL, SQLite, or SQL Server.

3. Final Answer:

   PostgreSQL -> Option B

4. Quick Check:

   DB_CONNECTION=pgsql means PostgreSQL = A [OK]

Hint: pgsql means PostgreSQL, mysql means MySQL [OK]

Common Mistakes:

• Confusing pgsql with MySQL
• Ignoring DB_CONNECTION value
• Assuming default is MySQL always

4. You wrote this in your .env file:

DB_CONNECTION=mysql
DB_HOST=localhost
DB_PORT=3306
DB_DATABASE=myapp
DB_USERNAME=root
DB_PASSWORD=

But Laravel throws a connection error. What is the most likely cause?

medium

A. Empty DB_PASSWORD causes authentication failure

B. DB_PORT 3306 is incorrect for MySQL

C. DB_HOST should be an IP address, not 'localhost'

D. DB_CONNECTION should be 'pgsql' for MySQL

Solution

1. Step 1: Review the DB_PASSWORD value

   The password is empty, which may cause authentication failure if MySQL requires a password.

2. Step 2: Check other config values

   DB_PORT 3306 is correct for MySQL, DB_HOST 'localhost' is valid, and DB_CONNECTION 'mysql' is correct.

3. Final Answer:

   Empty DB_PASSWORD causes authentication failure -> Option A

4. Quick Check:

   Empty password often blocks login = A [OK]

Hint: Empty password often causes connection errors [OK]

Common Mistakes:

• Assuming port 3306 is wrong
• Thinking localhost is invalid
• Mixing DB_CONNECTION values

5. You want to configure Laravel to use two different databases: one MySQL and one SQLite. How should you set this up in Laravel's configuration?

hard

A. Use only one database type per Laravel project; multiple are not supported

B. Set DB_CONNECTION in .env to both 'mysql,sqlite' separated by comma

C. Define both connections in config/database.php and set DB_CONNECTION in .env to the default

D. Create two separate .env files, one for each database

Solution

1. Step 1: Understand Laravel's multiple connection support

   Laravel supports multiple database connections defined in config/database.php under 'connections'.

2. Step 2: Set default connection in .env and use others explicitly

   DB_CONNECTION in .env sets the default. You can use other connections by specifying their names in code.

3. Final Answer:

   Define both connections in config/database.php and set DB_CONNECTION in .env to the default -> Option C

4. Quick Check:

   Multiple connections in config, default in .env = D [OK]

Hint: Use config/database.php for multiple connections, .env for default [OK]

Common Mistakes:

• Trying to list multiple DB_CONNECTION values in .env
• Creating multiple .env files
• Thinking Laravel can't handle multiple databases