Why production readiness matters in NestJS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the core module in a NestJS application.

NestJS

import { [1] } from '@nestjs/common';

Drag options to blanks, or click blank then click option'

AController

BModule

CInjectable

DService

Attempts:

3 left

💡 Hint

Common Mistakes

Using Controller instead of Module

Using Injectable instead of Module

The Module decorator is used to define a module in NestJS, which is essential for organizing the application structure.

2fill in blank

medium

Complete the code to create a basic controller in NestJS.

NestJS

@Controller('[1]')
export class AppController {}

Drag options to blanks, or click blank then click option'

Acontroller

Bservice

Cmodule

Dapp

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'service' as route prefix

Using 'module' as route prefix

The @Controller('app') decorator defines a controller with the route prefix 'app'.

3fill in blank

hard

Fix the error in the provider registration to ensure production readiness.

NestJS

@Module({
  providers: [[1]],
})
export class AppModule {}

Drag options to blanks, or click blank then click option'

AHttpModule

BAppController

CAppService

DConfigModule

Attempts:

3 left

💡 Hint

Common Mistakes

Registering controllers as providers

Registering modules as providers

Providers like AppService should be registered in the providers array to be injectable and used properly.

4fill in blank

hard

Fill both blanks to configure environment variables and enable validation for production readiness.

NestJS

import { [1] } from '@nestjs/config';

@Module({
  imports: [[2].forRoot({ isGlobal: true })],
})
export class AppModule {}

Drag options to blanks, or click blank then click option'

AConfigModule

BValidationPipe

CConfigService

DHttpModule

Attempts:

3 left

💡 Hint

Common Mistakes

Using ValidationPipe instead of ConfigModule

Importing ConfigService directly

ConfigModule is imported and configured globally to manage environment variables, which is key for production readiness.

5fill in blank

hard

Fill all three blanks to set up a global validation pipe and enable CORS for production readiness.

NestJS

async function bootstrap() {
  const app = await NestFactory.create(AppModule);
  app.useGlobalPipes(new [1]());
  app.enableCors({ origin: [2] });
  await app.listen([3]);
}

Drag options to blanks, or click blank then click option'

AValidationPipe

B'*'

C3000

DHttpException

Attempts:

3 left

💡 Hint

Common Mistakes

Using HttpException instead of ValidationPipe

Setting CORS origin to an invalid value

Using a wrong port number

The ValidationPipe ensures input validation globally. Enabling CORS with origin '*' allows all origins. Listening on port 3000 is a common default.