[Solved] Why might the following NestJS controller not cache responses despite using... Why might the following NestJS controller not cache responses despite using @UseInterceptors(CacheInterceptor)? | NestJS

NestJS - Interceptors

Why might the following NestJS controller not cache responses despite using @UseInterceptors(CacheInterceptor)?

@Controller('sample')
@UseInterceptors(CacheInterceptor)
export class SampleController {
  @Get()
  async fetchData() {
    return await Promise.resolve('info');
  }
}

ABecause the CacheModule is not imported in the module

BBecause the method is asynchronous

CBecause CacheInterceptor cannot be used with @Get() methods

DBecause @UseInterceptors should be applied only on methods, not controllers

Step-by-Step Solution

Solution:

Step 1: Check prerequisites for caching
CacheInterceptor requires CacheModule to be imported and configured in the module.
Step 2: Analyze code
The controller uses CacheInterceptor but likely misses CacheModule import, so caching won't work.
Final Answer:
Because the CacheModule is not imported in the module -> Option A
Quick Check:
CacheModule import is mandatory for caching [OK]

Quick Trick: CacheModule must be imported for CacheInterceptor to work [OK]

Common Mistakes:

Thinking async methods prevent caching
Believing CacheInterceptor can't be applied at controller level

Master "Interceptors" in NestJS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Perf

More NestJS Quizzes

Why might the following NestJS controller not cache responses despite using @UseInterceptors(CacheInterceptor)?

Step 1: Check prerequisites for caching

Step 2: Analyze code

Final Answer:

Quick Check:

Want More Practice?