Comparison questionEasy~5 min

Interview question

How do `Use`, `Run`, and `Map` differ when building an ASP.NET Core middleware pipeline?

Use, Run, and Map in the ASP.NET Core middleware pipeline

Explains middleware continuation, terminal delegates, path branches, short-circuiting, and two-way request and response flow.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Use adds middleware that may do work before and after the next component. It continues by awaiting next and short-circuits when it does not call it. Run is terminal because it has no next delegate. Map creates a separate pipeline for a matching path prefix. Because control moves forward and then unwinds, order affects both request handling and response work.

Full answer below

Practice focus

Middleware composition, `RequestDelegate`, short-circuiting, path branching, response unwinding, and pipeline order.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
These three methods look similar in Program.cs, but they create different control flow. Understanding that flow makes middleware-order bugs much easier to predict.
Use adds middleware that may do work before and after the next component. It continues by awaiting next and short-circuits when it does not call it. Run is terminal because it has no next delegate. Map creates a separate pipeline for a matching path prefix. Because control moves forward and then unwinds, order affects both request handling and response work.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
For example, exception handling must wrap the components whose failures it catches, while timing middleware can start a clock, await the rest of the pipeline, and record the final status. A maintenance branch may intentionally return without calling next. MapGet and MapControllers register route endpoints; that is different from IApplicationBuilder.Map, which branches by path.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
The advanced concern is ownership of continuation and the response. Code after await next may be too late to change headers once downstream code has started the body, and a misplaced branch can bypass authentication or observability. I keep short-circuits explicit and test a matched, unmatched, rejected, and exceptional request. If the control flow cannot be read top to bottom, the pipeline is too clever.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Using Use for terminal behavior and silently forgetting to call next.
Calling next after a complete response body has already been written.
Assuming code after await next runs before the endpoint.
Creating a branch that unintentionally bypasses security or telemetry middleware.

Red flagsCandidateSigns the approach is fragileSignals that an interviewer may treat as risky.Open details

Details

Middleware continuation depends on undocumented conditions.
A terminal delegate appears before endpoints that still need to run.
Path branching is confused with endpoint route mapping.
No tests prove which components execute for matched and rejected requests.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What does short-circuiting mean in middleware?
Why does code after await next run on the response path?
How is app.Map different from app.MapGet?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

2 linked

Next interviewer turn

Continue the conversation with a linked follow-up drill.

Response Already Started

Prerequisite

Review this first if the current drill feels shaky.

Middleware Ordering

Practice route

Read core answer Review checklist Follow-up prompts Track progress

Finished this drill?

Practice freely. Sign in only when you want to save completion, confidence, notes, or bookmarks.

New to Aporeon? Create account

Drill details

Share the question with a concise Core-answer excerpt and invite other developers to add their perspective.

Was this drill useful?

Help improve the interview library.

Found this answer useful?

Say thanks with a standalone, one-time $5 contribution. No account required.

No subscription or perks.Choose another amount

Human editorial direction

Aporeon is shaped by Aleksandar Tomovski, a software developer with experience on both sides of technical interviews. Content is reviewed for accuracy, natural spoken delivery, useful depth, and honest trade-offs.

About the creator Editorial standards

Opening drill

Comparison questionEasy~5 min

Interview question

How do `Use`, `Run`, and `Map` differ when building an ASP.NET Core middleware pipeline?

Use, Run, and Map in the ASP.NET Core middleware pipeline

Explains middleware continuation, terminal delegates, path branches, short-circuiting, and two-way request and response flow.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Middleware composition, `RequestDelegate`, short-circuiting, path branching, response unwinding, and pipeline order.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
These three methods look similar in Program.cs, but they create different control flow. Understanding that flow makes middleware-order bugs much easier to predict.
Use adds middleware that may do work before and after the next component. It continues by awaiting next and short-circuits when it does not call it. Run is terminal because it has no next delegate. Map creates a separate pipeline for a matching path prefix. Because control moves forward and then unwinds, order affects both request handling and response work.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
For example, exception handling must wrap the components whose failures it catches, while timing middleware can start a clock, await the rest of the pipeline, and record the final status. A maintenance branch may intentionally return without calling next. MapGet and MapControllers register route endpoints; that is different from IApplicationBuilder.Map, which branches by path.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
The advanced concern is ownership of continuation and the response. Code after await next may be too late to change headers once downstream code has started the body, and a misplaced branch can bypass authentication or observability. I keep short-circuits explicit and test a matched, unmatched, rejected, and exceptional request. If the control flow cannot be read top to bottom, the pipeline is too clever.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Using Use for terminal behavior and silently forgetting to call next.
Calling next after a complete response body has already been written.
Assuming code after await next runs before the endpoint.
Creating a branch that unintentionally bypasses security or telemetry middleware.

Red flagsCandidateSigns the approach is fragileSignals that an interviewer may treat as risky.Open details

Details

Middleware continuation depends on undocumented conditions.
A terminal delegate appears before endpoints that still need to run.
Path branching is confused with endpoint route mapping.
No tests prove which components execute for matched and rejected requests.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What does short-circuiting mean in middleware?
Why does code after await next run on the response path?
How is app.Map different from app.MapGet?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

2 linked

Next interviewer turn

Continue the conversation with a linked follow-up drill.

Response Already Started

Prerequisite

Review this first if the current drill feels shaky.

Middleware Ordering

How do `Use`, `Run`, and `Map` differ when building an ASP.NET Core middleware pipeline?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

Prerequisite

How do `Use`, `Run`, and `Map` differ when building an ASP.NET Core middleware pipeline?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

Prerequisite