Comparison questionEasy~5 minASP.NET Core Framework Essentials / 21 of 26

Interview question

What is the difference between calls on `builder.Services` and calls on `app` in an ASP.NET Core `Program.cs` file?

Separates dependency registration from per-request middleware and endpoint composition in modern ASP.NET Core startup.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

builder.Services configures the application's dependency graph before the host is built. Calls such as AddControllers or AddDbContext register framework and application services. After builder.Build(), calls on app compose the request pipeline and map endpoints. Registration makes a capability available; pipeline configuration decides whether and where it participates in an HTTP request.

Full answer below

Practice focus

Application startup, dependency injection, middleware, endpoint mapping, host construction, and the difference between configuration time and request time.

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
Many startup bugs come from treating service registration and request handling as interchangeable. The two phases cooperate, but they create different runtime objects and solve different problems.
builder.Services configures the application's dependency graph before the host is built. Calls such as AddControllers or AddDbContext register framework and application services. After builder.Build(), calls on app compose the request pipeline and map endpoints. Registration makes a capability available; pipeline configuration decides whether and where it participates in an HTTP request.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
That distinction explains common startup bugs. AddAuthentication registers handlers, but authentication middleware must still run on the request path. MapControllers exposes controller endpoints, but it relies on controller services registered earlier. Middleware order also matters because each component can wrap or short-circuit what follows. I check both registration and pipeline placement when a feature exists in configuration but not in behavior.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I keep composition visible enough to review security, ordering, and lifetime ownership. Feature extensions may group related registrations or a documented middleware sequence, but they should not hide unrelated behavior. A focused composition test can build the host, resolve critical services, inspect endpoints, and send a representative request. That verifies the observable contract without assuming every application must copy one historical Startup layout.

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

Assuming AddAuthentication automatically authenticates every request.
Treating MapControllers as a replacement for controller service registration.
Trying to register ordinary application services after the host has been built.
Hiding security-sensitive pipeline order inside an undocumented extension method.

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

Details

Startup code cannot distinguish container composition from request execution.
A feature is considered enabled because only its Add... method is present.
Environment branches produce different middleware without integration coverage.
The team changes startup order until a bug disappears without explaining the boundary.

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.

Why are both AddAuthentication and UseAuthentication needed?
What does MapControllers add to the application?
When would you extract startup code into an extension method?

Continue the section

Next in ASP.NET Core Framework Essentials: Use, Run, and Map

Step 22 of 26

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

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 minASP.NET Core Framework Essentials / 21 of 26

Interview question

What is the difference between calls on `builder.Services` and calls on `app` in an ASP.NET Core `Program.cs` file?

Separates dependency registration from per-request middleware and endpoint composition in modern ASP.NET Core startup.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Application startup, dependency injection, middleware, endpoint mapping, host construction, and the difference between configuration time and request time.

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
Many startup bugs come from treating service registration and request handling as interchangeable. The two phases cooperate, but they create different runtime objects and solve different problems.
builder.Services configures the application's dependency graph before the host is built. Calls such as AddControllers or AddDbContext register framework and application services. After builder.Build(), calls on app compose the request pipeline and map endpoints. Registration makes a capability available; pipeline configuration decides whether and where it participates in an HTTP request.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
That distinction explains common startup bugs. AddAuthentication registers handlers, but authentication middleware must still run on the request path. MapControllers exposes controller endpoints, but it relies on controller services registered earlier. Middleware order also matters because each component can wrap or short-circuit what follows. I check both registration and pipeline placement when a feature exists in configuration but not in behavior.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I keep composition visible enough to review security, ordering, and lifetime ownership. Feature extensions may group related registrations or a documented middleware sequence, but they should not hide unrelated behavior. A focused composition test can build the host, resolve critical services, inspect endpoints, and send a representative request. That verifies the observable contract without assuming every application must copy one historical Startup layout.

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

Assuming AddAuthentication automatically authenticates every request.
Treating MapControllers as a replacement for controller service registration.
Trying to register ordinary application services after the host has been built.
Hiding security-sensitive pipeline order inside an undocumented extension method.

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

Details

Startup code cannot distinguish container composition from request execution.
A feature is considered enabled because only its Add... method is present.
Environment branches produce different middleware without integration coverage.
The team changes startup order until a bug disappears without explaining the boundary.

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.

Why are both AddAuthentication and UseAuthentication needed?
What does MapControllers add to the application?
When would you extract startup code into an extension method?

Continue the section

Next in ASP.NET Core Framework Essentials: Use, Run, and Map

Step 22 of 26

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

What is the difference between calls on `builder.Services` and calls on `app` in an ASP.NET Core `Program.cs` file?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

What is the difference between calls on `builder.Services` and calls on `app` in an ASP.NET Core `Program.cs` file?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section