NestJS Research & Evidence-Based Practice 2

Question 1

When researching NestJS interceptors, you find they implement which interface to handle request/response transformation?

Accepted Answer

NestInterceptor

Answer

NestInterceptor is the interface that interceptors must implement, providing the intercept() method with access to the execution context and call handler.

Question 2

Based on NestJS documentation, which decorator is used to bind a specific interceptor to a single route handler rather than the entire controller?

Accepted Answer

@UseInterceptors()

Answer

@UseInterceptors() can be applied at the method level to scope an interceptor to a single route handler.

Question 3

Evidence from NestJS performance benchmarks suggests that which caching strategy is natively supported via @nestjs/cache-manager?

Accepted Answer

Read-through caching with in-memory store

Answer

@nestjs/cache-manager provides read-through caching with an in-memory store by default, and supports Redis via additional adapters.

Question 4

When reviewing NestJS CLI documentation, which command generates a complete CRUD resource with controller, service, module, and DTO files?

Accepted Answer

nest generate resource

Answer

nest generate resource (or nest g res) scaffolds a full CRUD resource including controller, service, module, DTOs, and entity files.

Question 5

Research into NestJS dependency injection shows that which scope causes a new provider instance to be created for every incoming request?

Accepted Answer

REQUEST

Answer

REQUEST scope creates a new instance of the provider for each incoming HTTP request, which is useful for request-scoped state.

NestJS Practice Test

NestJS Practice Test

NestJS Research & Evidence-Based Practice 2