[Solved] Identify the issue in this guard:export class AdminGuard implements CanActivate { canActivate(context: ExecutionContext) { return context.switchToHttp().getRequest().user.isAdmin; } } | NestJS

NestJS - Authentication

Identify the issue in this guard:

export class AdminGuard implements CanActivate { canActivate(context: ExecutionContext) { return context.switchToHttp().getRequest().user.isAdmin; } }

AIt may throw an error if user is undefined

BIt always returns true regardless of user role

CIt does not implement CanActivate interface

DIt uses an incorrect method to get the request

Step-by-Step Solution

Solution:

Step 1: Check user property access
If user is undefined, accessing isAdmin causes an error.
Step 2: Guard should handle missing user safely
Proper null checks or default values are needed.
Final Answer:
It may throw an error if user is undefined -> Option A
Quick Check:
Check for undefined user before accessing properties [OK]

Quick Trick: Always verify user exists before property access [OK]

Common Mistakes:

Assuming user is always defined
Ignoring potential runtime errors

Master "Authentication" 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:

Step 1: Check user property access

Step 2: Guard should handle missing user safely

Final Answer:

Quick Check:

Want More Practice?