Bird
0
0

Why might you choose functional middleware over class-based middleware in NestJS?

hard📝 Conceptual Q10 of 15
NestJS - Middleware
Why might you choose functional middleware over class-based middleware in NestJS?
ABecause functional middleware supports dependency injection better
BFor simple, lightweight middleware without dependency injection
CBecause class-based middleware cannot access request or response
DBecause functional middleware automatically handles exceptions
Step-by-Step Solution
Solution:

  1. Step 1: Compare middleware types

    Functional middleware is simpler and lighter, suitable for straightforward tasks without needing DI.

  2. Step 2: Understand class-based middleware features

    Class-based middleware supports dependency injection, which functional middleware does not.

  3. Final Answer:

    For simple, lightweight middleware without dependency injection -> Option B

  4. Quick Check:

    Functional middleware = simple, no DI [OK]
Quick Trick: Use functional middleware for simple tasks without DI [OK]
Common Mistakes:
  • Thinking functional middleware supports DI
  • Believing class middleware cannot access req/res
  • Assuming functional middleware handles errors automatically

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More NestJS Quizzes
Authentication - Protected routes with guards - Quiz 10hard Database with TypeORM - TypeORM module setup - Quiz 12easy Database with TypeORM - Relations (OneToMany, ManyToOne, ManyToMany) - Quiz 9hard Database with TypeORM - Migrations - Quiz 10hard Database with TypeORM - Query builder - Quiz 11easy Database with TypeORM - Migrations - Quiz 15hard Interceptors - Interceptor interface - Quiz 1easy Interceptors - Cache interceptor - Quiz 4medium Middleware - Why middleware processes requests before handlers - Quiz 12easy Middleware - Applying middleware to routes - Quiz 13medium