Root module (AppModule) in NestJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output when the AppModule imports a service but does not provide it?

Consider a NestJS AppModule that imports a service module but does not list the service in its providers array. What happens when a component inside AppModule tries to inject that service?

NestJS

import { Module } from '@nestjs/common';
import { ServiceModule } from './service.module';

@Module({
  imports: [ServiceModule],
  controllers: [],
  providers: [],
})
export class AppModule {}

// ServiceModule provides SomeService
// A controller in AppModule tries to inject SomeService

A The injection works fine because the service is exported by ServiceModule and imported by AppModule.

B The injection fails with a runtime error because AppModule does not provide the service directly.

C The injection fails with a compile-time error due to missing provider in AppModule.

D The service is instantiated twice, once in ServiceModule and once in AppModule.

💡 Hint

Think about how NestJS shares providers between modules when they are exported and imported.

When a module exports a provider and another module imports that module, the importing module can inject the exported provider without listing it in its own providers array.

📝 Syntax

intermediate

Which AppModule definition is syntactically correct in NestJS?

Choose the correct syntax for defining a root AppModule in NestJS.

A

import { Module } from '@nestjs/common';

@Module({
  imports: [],
  controllers: [],
  providers: [],
})
export default class AppModule {}

B

import { Module } from '@nestjs/common';

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

C

import { Module } from '@nestjs/common';

@Module({
  imports: [],
  controllers: [],
  providers: [],
})
class AppModule {}

D

}{ eludoMppA ssalc tropxe
)}
,][ :sredivorp  
,][ :srellortnoc  
,][ :stropmi  
{(eludoM@

;'nommoc/sjtsen@' morf } eludoM { tropmi

💡 Hint

Remember to use the correct export syntax and include semicolons.

Option B uses correct TypeScript syntax with proper export and semicolons. Option B misses semicolons and export keyword is incomplete. Option B does not export the class. Option B uses default export which is uncommon for AppModule in NestJS.

❓ lifecycle

advanced

What happens if AppModule imports two modules that provide the same service?

If AppModule imports ModuleA and ModuleB, and both provide the same service class, what will be the behavior when injecting that service in AppModule?

A The service from the last imported module overrides the previous one.

B NestJS creates two separate instances and injection is ambiguous causing an error.

C NestJS throws a runtime error due to duplicate provider tokens.

D NestJS uses the first imported module's service and ignores the second.

💡 Hint

Think about how NestJS resolves providers when duplicates exist in imports.

When multiple modules provide the same service, the last imported module's provider overrides previous ones in the dependency injection container.

🔧 Debug

advanced

Why does this AppModule fail to start with 'Nest can't resolve dependencies' error?

Examine the following AppModule code and identify the cause of the dependency resolution error.

NestJS

import { Module } from '@nestjs/common';
import { ServiceA } from './serviceA';

@Module({
  imports: [],
  controllers: [],
  providers: [ServiceA],
})
export class AppModule {}

// ServiceA depends on ServiceB but ServiceB is not provided anywhere.

A AppModule must import ServiceA's module instead of providing ServiceA directly.

B ServiceA is not exported, causing the error.

C ServiceB is missing from providers, so ServiceA's dependency cannot be resolved.

D The error is caused by missing controllers array.

💡 Hint

Check the dependencies of ServiceA and whether they are provided.

ServiceA depends on ServiceB, but ServiceB is not listed in providers or imported from another module, so NestJS cannot resolve ServiceB when creating ServiceA.

🧠 Conceptual

expert

How does the root AppModule affect global providers in a large NestJS application?

In a large NestJS app, what is the role of the root AppModule regarding global providers and their scope?

A Global providers declared in AppModule are only available to controllers, not services.

B Global providers must be declared in every feature module to be accessible.

C AppModule cannot declare global providers; only feature modules can.

D The root AppModule can declare global providers that are shared across all modules without re-importing.

💡 Hint

Consider how the global scope works in NestJS modules.

The root AppModule can declare providers with the @Global() decorator or export them so they are available application-wide without needing to import them in every module.