Environment-based configuration in Express - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

How does this Express app behave with NODE_ENV set to 'production'?

Consider this Express app code snippet. What will be the response when NODE_ENV is set to 'production' and a GET request is made to '/'?

Express

const express = require('express');
const app = express();

app.get('/', (req, res) => {
  if (process.env.NODE_ENV === 'production') {
    res.send('Production mode');
  } else {
    res.send('Development mode');
  }
});

module.exports = app;

A The server throws an error because NODE_ENV is undefined.

B The server responds with 'Development mode'.

C The server responds with 'Production mode'.

D The server responds with an empty string.

💡 Hint

Check the condition that compares process.env.NODE_ENV to 'production'.

When NODE_ENV is set to 'production', the condition is true, so the response is 'Production mode'.

📝 Syntax

intermediate

Identify the syntax error in this environment config setup

Which option contains the correct syntax to load environment variables from a .env file using the dotenv package in an Express app?

Express

require('dotenv').config()

const port = process.env.PORT || 3000;

A import dotenv from 'dotenv'; dotenv.config();

B require('dotenv').config();

C require('dotenv').config

D dotenv.config()

💡 Hint

Remember to call the config function properly.

Option B correctly requires dotenv and calls config() as a function with parentheses and a semicolon.

❓ state_output

advanced

What is the value of 'dbConnectionString' after running this code?

Given this Express configuration snippet, what will be the value of dbConnectionString if NODE_ENV is 'test' and no TEST_DB_URL is set?

Express

const config = {
  development: { dbConnectionString: 'mongodb://localhost/devdb' },
  test: { dbConnectionString: process.env.TEST_DB_URL || 'mongodb://localhost/testdb' },
  production: { dbConnectionString: process.env.PROD_DB_URL }
};

const env = process.env.NODE_ENV || 'development';
const dbConnectionString = config[env].dbConnectionString;

A process.env.TEST_DB_URL

B undefined

C 'mongodb://localhost/devdb'

D 'mongodb://localhost/testdb'

💡 Hint

Look at the fallback value when TEST_DB_URL is not set.

Since TEST_DB_URL is undefined, the fallback 'mongodb://localhost/testdb' is used.

🔧 Debug

advanced

Why does this Express app always run in production mode?

This Express app always logs 'Running in production mode' even when NODE_ENV is set to 'development'. What is the bug?

Express

const express = require('express');
const app = express();

const env = process.env.NODE_ENV || 'development';

if (env = 'production') {
  console.log('Running in production mode');
} else {
  console.log('Running in development mode');
}

module.exports = app;

A The if condition uses assignment '=' instead of comparison '==='. It always sets env to 'production' and evaluates as truthy.

B process.env.NODE_ENV is not set, so env is always 'development'.

C The console.log statements are reversed.

D The app does not listen on any port.

💡 Hint

Check the if condition syntax carefully.

Using '=' assigns 'production' to env, so the condition is always true, causing the else block never to run.

🧠 Conceptual

expert

Which option best explains why environment-based configuration is important in Express apps?

Why do Express apps use environment-based configuration like NODE_ENV and .env files?

A To separate settings like database URLs and API keys for development, testing, and production without changing code.

B To make the app run faster by caching environment variables.

C To allow users to change the app's behavior by editing the source code directly.

D To force the app to always use the same configuration regardless of where it runs.

💡 Hint

Think about why different environments need different settings.

Environment-based configuration helps keep sensitive or environment-specific data outside the code and allows easy switching between setups.