Why GraphQL fits NestJS architecture - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does GraphQL complement NestJS's modular design?

GraphQL and NestJS both emphasize modularity. Which statement best explains why GraphQL fits well with NestJS's architecture?

A GraphQL forces all logic into a single file, which conflicts with NestJS's modularity.

B GraphQL requires global variables, which NestJS discourages, making them incompatible.

C NestJS only supports REST APIs, so GraphQL cannot be integrated.

D GraphQL's schema-first approach aligns with NestJS's modular modules and decorators, enabling clear API boundaries.

💡 Hint

Think about how both GraphQL and NestJS organize code and define APIs.

GraphQL uses schemas and resolvers that fit naturally into NestJS modules and decorators, supporting clear separation of concerns and modular design.

❓ component_behavior

intermediate

What happens when you add GraphQL module in NestJS?

In a NestJS app, you add the GraphQLModule with autoSchemaFile enabled. What is the main effect on the app's behavior?

NestJS

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

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

A The app switches to REST API mode and disables GraphQL features.

B GraphQL queries are ignored and only REST endpoints work.

C NestJS generates a GraphQL schema automatically from resolvers and serves a GraphQL playground.

D The app throws a runtime error because autoSchemaFile is not supported.

💡 Hint

Consider what autoSchemaFile does in NestJS GraphQL setup.

autoSchemaFile tells NestJS to generate the GraphQL schema automatically from your code, enabling GraphQL playground and queries.

❓ lifecycle

advanced

How does NestJS lifecycle support GraphQL resolver execution?

Which NestJS lifecycle hook is best suited to initialize resources before a GraphQL resolver handles a request?

A onApplicationBootstrap() - runs after the app starts but after resolvers execute.

B onModuleInit() - runs once when the module is initialized, before any resolver runs.

C beforeApplicationShutdown() - runs after all resolvers finish processing.

D onModuleDestroy() - runs before the module is destroyed, unrelated to resolver execution.

💡 Hint

Think about when you want to prepare resources before any resolver runs.

onModuleInit() runs once when the module starts, making it ideal to set up resources needed by GraphQL resolvers.

📝 Syntax

advanced

Identify the correct GraphQL resolver syntax in NestJS

Which code snippet correctly defines a GraphQL query resolver in NestJS?

NestJS

import { Resolver, Query } from '@nestjs/graphql';

@Resolver()
export class SampleResolver {
  @Query(() => String)
  hello() {
    return 'Hello World';
  }
}

A The code correctly defines a GraphQL query resolver returning a string.

B The @Query decorator is missing a required name parameter, causing a syntax error.

C The resolver method must be async, so this code will cause a runtime error.

D The @Resolver decorator requires a type argument, so this code is invalid.

💡 Hint

Check the NestJS GraphQL docs for minimal resolver syntax.

The code uses @Resolver and @Query decorators correctly. The method returns a string synchronously, which is valid.

🔧 Debug

expert

Why does this NestJS GraphQL resolver throw a runtime error?

Given this resolver code, why does the app throw a runtime error when querying 'greet'?

NestJS

import { Resolver, Query } from '@nestjs/graphql';

@Resolver()
export class GreetResolver {
  @Query(() => String)
  greet() {
    return this.message.toUpperCase();
  }

  private message: string;
}

A The 'message' property is undefined because it was never initialized, causing a runtime error.

B The @Query decorator is missing parentheses, causing a syntax error.

C The method greet() must be async to return a string, so this causes a runtime error.

D The @Resolver decorator requires a type argument, so this code is invalid.

💡 Hint

Check if all properties used in the method have values before use.

The 'message' property is declared but never assigned a value, so accessing toUpperCase() on undefined causes a runtime error.