Why configuration management matters in NestJS - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use configuration management in NestJS?

Which of the following best explains why configuration management is important in a NestJS application?

A It automatically updates the application dependencies to the latest versions.

B It compiles the NestJS application into a single executable file.

C It allows the application to change settings without modifying code, making it easier to adapt to different environments.

D It provides a graphical user interface for managing database records.

💡 Hint

Think about how apps behave differently in development, testing, and production.

Configuration management lets you keep environment-specific settings separate from your code. This helps you run the same app in different places without changing the code itself.

❓ component_behavior

intermediate

Behavior of ConfigService in NestJS

What will be the output of the following code snippet when the environment variable PORT is set to 3000?

NestJS

import { ConfigService } from '@nestjs/config';

const configService = new ConfigService();
const port = configService.get('PORT');
console.log(port);

A 3000

B undefined

C null

D Throws an error because ConfigService is not injected

💡 Hint

ConfigService reads environment variables by default.

ConfigService reads environment variables like PORT and returns their values. However, ConfigService should be injected by NestJS's dependency injection system. Instantiating it directly without injection will not load environment variables, so it will not return '3000'.

📝 Syntax

advanced

Correct way to load configuration in NestJS

Which option correctly shows how to load a configuration file using ConfigModule in a NestJS application?

NestJS

import { ConfigModule } from '@nestjs/config';

@Module({
  imports: [
    // Which option is correct here?
  ],
})
export class AppModule {}

A ConfigModule.forRoot({ envFilePath: '.env' })

B ConfigModule.load('.env')

C ConfigModule.forFeature('.env')

D ConfigModule.register({ path: '.env' })

💡 Hint

Check the official method to load environment files in ConfigModule.

ConfigModule.forRoot accepts an option 'envFilePath' to specify the environment file to load. Other methods do not exist or are incorrect.

🔧 Debug

advanced

Why does ConfigService return undefined?

Given this NestJS service code, why does configService.get('DATABASE_URL') return undefined? @Module({ imports: [ConfigModule.forRoot()], }) export class AppModule {} @Injectable() export class DatabaseService { constructor(private configService: ConfigService) {} getDatabaseUrl() { return this.configService.get('DATABASE_URL'); } }

A ConfigService must be manually instantiated with new before use.

B The environment variable DATABASE_URL is not set in the environment or .env file.

C ConfigModule.forRoot() must be called with isGlobal: false to work.

D The get method requires a second argument to specify a default value.

💡 Hint

Check if the environment variable exists where the app runs.

If DATABASE_URL is not set in the environment or .env file, ConfigService.get returns undefined because it cannot find the value.

❓ lifecycle

expert

When is configuration loaded in NestJS lifecycle?

At what point in the NestJS application lifecycle is the configuration loaded and available via ConfigService?

A During the application bootstrap phase, before any modules are initialized.

B After all modules have been initialized and the application is listening.

C Only when the first service requests a configuration value.

D After the main controller handles its first request.

💡 Hint

Think about when environment variables must be ready for use.

ConfigModule.forRoot loads configuration during the bootstrap phase, making ConfigService values available to all modules and services during initialization.