Questions

15 of 25

1What built-in HTTP exceptions does NestJS provide out of the box?

2What interface must an exception filter implement and what are the two parameters of catch()?

3How do you apply an exception filter at the method, controller, and global level in NestJS?

4How do you add custom response headers or set cookies inside an exception filter in NestJS?

5How do you unit test an exception filter in NestJS?

6How do you implement a filter that adds a request correlation ID to every error response in NestJS?

7How do getResponse() and getStatus() work on an HttpException and what can getResponse() return?

8How do you create a domain-specific custom exception class in NestJS?

9How does exception filter resolution order work when multiple filters are registered at different levels in NestJS?

10How do you register multiple global filters that each handle a different exception type in NestJS?

11What does the @Catch() decorator do and what happens when you omit its argument?

12How do you extend the built-in BaseExceptionFilter to add logging while keeping default NestJS behaviour?

13How do you handle exceptions differently in a filter depending on whether the request is HTTP, WebSocket, or RPC?

14What are the two ways to register a global exception filter in NestJS and what is the key difference?

15How do interceptors and exception filters divide error-handling responsibility in NestJS?

16How do you write an exception filter that handles GraphQL errors differently from REST errors in NestJS?

17How do you prevent sensitive information from leaking through exception responses in production NestJS apps?

18How do you handle async operations inside an exception filter in NestJS, for example logging to a database?

19What is HttpException in NestJS and what two arguments does its constructor take?

20What does NestJS's built-in global exception layer do when no custom filter is registered?

21What is the cause option on HttpException and how should you use it for error tracing?

22How do you write a production-ready global all-exceptions filter that handles HttpException and unexpected errors differently?

23How do you integrate a third-party error tracker like Sentry inside a global exception filter in NestJS?

24How do you map database and ORM exceptions to HTTP exceptions using a global filter in NestJS?

25How do you re-throw an exception from within a filter to let a higher-scoped filter handle it in NestJS?

15 / 25

How do interceptors and exception filters divide error-handling responsibility in NestJS?

Interceptors via catchError() remap exception types — they convert domain or ORM errors into HttpException subclasses before the filter sees them. Exception filters shape the HTTP error response sent to the client. Interceptors fix what the exception is; filters fix how the error response looks. Interceptors run before filters in the pipeline.

Interceptor remapping vs filter formatting

Clear division of responsibility:

1
Interceptors (catchError) — translate exception types: EntityNotFoundError to NotFoundException.
2
Exception filters — format the HTTP response: shape the JSON body, set headers, log errors.
3
Interceptors run before filters in the pipeline — remap exception type first, then format the response.
4
Use interceptors when the error type needs changing; use filters when only the response format needs changing.
5
Always re-throw from interceptor catchError if the error is not handled — let the filter catch it.