ASP.NET Core Middleware & Request Pipeline 2

Question 1

What is the purpose of app.Run() in the middleware pipeline?

Accepted Answer

Adds a terminal middleware that never calls next()

Answer

app.Run() adds a terminal middleware delegate that handles requests without forwarding to any subsequent middleware.

Question 2

Which middleware enables exception handling and custom error pages in production?

Accepted Answer

UseExceptionHandler

Answer

UseExceptionHandler() catches unhandled exceptions and redirects to a custom error path in production.

Question 3

What does app.Map() do in the middleware pipeline?

Accepted Answer

Branches the pipeline based on request path

Answer

app.Map() creates a branch in the pipeline that executes when the request path starts with a specified prefix.

Question 4

In which interface must a custom middleware class implement its logic?

Accepted Answer

IMiddleware with InvokeAsync method

Answer

A class-based middleware implements IMiddleware and defines its logic in the InvokeAsync(HttpContext, RequestDelegate) method.

Question 5

What is the correct order for security middleware in ASP.NET Core?

Accepted Answer

CORS → Authentication → Authorization

Answer

The correct order is UseRouting → UseCors → UseAuthentication → UseAuthorization to ensure security works correctly.

ASP.NET Core Practice Test