[Solved] Identify the issue in this guard code:canActivate(context: ExecutionContext): boolean { const request = context.switchToHttp().getRequest(); if (!request.... | NestJS

NestJS - Guards

Identify the issue in this guard code:

canActivate(context: ExecutionContext): boolean {
  const request = context.switchToHttp().getRequest();
  if (!request.user) {
    throw new UnauthorizedException('User missing');
  }
  return request.user.isVerified;
}

AUsing switchToHttp() instead of getRequest()

BThrowing an exception inside canActivate instead of returning false

CReturning a boolean instead of a Promise<boolean>

DNot checking if isVerified is defined

Step-by-Step Solution

Solution:

Step 1: Understand guard behavior
Guards should return true or false to allow or deny access.
Step 2: Analyze exception usage
Throwing exceptions inside canActivate is discouraged; returning false is preferred for denying access.
Final Answer:
Throwing an exception inside canActivate instead of returning false -> Option B
Quick Check:
Guards return booleans, not exceptions. [OK]

Quick Trick: Guards should return false, not throw exceptions [OK]

Common Mistakes:

Throwing errors instead of returning false
Confusing synchronous and asynchronous returns

Master "Guards" in NestJS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Perf

More NestJS Quizzes

Identify the issue in this guard code:

Step 1: Understand guard behavior

Step 2: Analyze exception usage

Final Answer:

Quick Check:

Want More Practice?