[Solved] Consider this guard implementation:canActivate(context: ExecutionContext) { const request = context.... }What will be the result if the 'authorization' header is not present in the request? | NestJS

NestJS - Guards

Consider this guard implementation:

canActivate(context: ExecutionContext) {
  const request = context.switchToHttp().getRequest();
  return request.headers['authorization'] === 'Bearer token123';
}

What will be the result if the 'authorization' header is not present in the request?

AThe guard retries fetching the header

BThe guard throws an exception due to undefined header

CThe guard returns true, allowing access

DThe guard returns false, denying access

Step-by-Step Solution

Solution:

Step 1: Analyze the guard logic
The guard checks if the 'authorization' header equals a specific string.
Step 2: Consider missing header scenario
If the header is missing, request.headers['authorization'] is undefined, so the comparison returns false.
Final Answer:
The guard returns false, denying access -> Option D
Quick Check:
Missing header means condition fails, so access denied. [OK]

Quick Trick: Missing header causes guard to deny access [OK]

Common Mistakes:

Assuming missing headers cause exceptions
Thinking guard returns true by default

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

Consider this guard implementation:

Step 1: Analyze the guard logic

Step 2: Consider missing header scenario

Final Answer:

Quick Check:

Want More Practice?