Comparison questionMedium~7 minASP.NET Core Framework Essentials / 10 of 26

Interview question

When would you choose controllers, and when would you choose minimal APIs?

Controllers vs minimal APIs in ASP.NET Core

Compare endpoint styles in real services, including organization, conventions, testing, filters, and OpenAPI behavior.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Controllers group actions into classes and use MVC conventions, attributes, filters, and action results. Minimal APIs map endpoints directly with route mappings and can be concise. I use controllers when a large resource-oriented API benefits from structure and conventions. I use minimal APIs for small services, focused endpoint groups, or internal APIs where directness improves readability.

Full answer below

Practice focus

endpoint style judgment, maintainability, API size, cross-cutting behavior, and team conventions

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 matters
Controllers and minimal APIs share the same ASP.NET Core host but offer different organization and extension models. The useful choice is the one that keeps a service's endpoint contracts consistent as it grows.
Controllers group actions into classes and use MVC conventions, attributes, filters, and action results. Minimal APIs map endpoints directly with route mappings and can be concise. I use controllers when a large resource-oriented API benefits from structure and conventions. I use minimal APIs for small services, focused endpoint groups, or internal APIs where directness improves readability.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Controllers fit well when a service benefits from MVC conventions, action filters, formatter behavior, established versioning patterns, and resource-oriented grouping. Minimal APIs fit focused services or vertical slices where route groups, typed results, endpoint filters, and direct dependency parameters keep the flow easy to follow. Both styles support authorization, OpenAPI, validation, and thin transport handlers. I would not mix them randomly per developer preference; the team needs one default plus clear exceptions so error handling and metadata do not drift.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I evaluate the complete endpoint model rather than counting lines of setup code. I check how the chosen style expresses shared conventions, API versions, filters, model binding, response metadata, test fixtures, and discoverability across dozens of endpoints. Minimal handlers should delegate business work rather than accumulating inline logic, while controllers should not become large service classes. A migration between styles is usually a transport refactor and should preserve routes, status codes, schemas, authorization, and observability through contract tests. The application layer stays independent so endpoint style can evolve without rewriting use cases.

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

Saying controllers are obsolete
Saying minimal APIs are only demos
Putting all minimal handlers in one file
Creating huge controller actions
Mixing endpoint styles without conventions

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Chooses based on fashion
Cannot organize minimal APIs beyond examples
Thinks controllers solve architecture automatically
Ignores documentation/testing effects

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.

How would you organize 80 minimal endpoints?
How do typed results help?
How would authorization work in both styles?
When is mixing both acceptable?

Interviewer notesInterviewerInterviewer notesWhat the interviewer is listening for.Open details

Details

Good candidates compare maintainability and team conventions, not only syntax.

Recruiter notesRecruiterRecruiter notesHow to frame the answer for screening conversations.Open details

Details

This is current ASP.NET Core knowledge with a practical architecture angle.

Continue the section

Next in ASP.NET Core Framework Essentials: Endpoint Filters vs MVC Filters

Step 11 of 26

Endpoint filters vs MVC filters in ASP.NET Core

Opening drill

Comparison questionMedium~7 minASP.NET Core Framework Essentials / 10 of 26

Interview question

When would you choose controllers, and when would you choose minimal APIs?

Controllers vs minimal APIs in ASP.NET Core

Compare endpoint styles in real services, including organization, conventions, testing, filters, and OpenAPI behavior.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

endpoint style judgment, maintainability, API size, cross-cutting behavior, and team conventions

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 matters
Controllers and minimal APIs share the same ASP.NET Core host but offer different organization and extension models. The useful choice is the one that keeps a service's endpoint contracts consistent as it grows.
Controllers group actions into classes and use MVC conventions, attributes, filters, and action results. Minimal APIs map endpoints directly with route mappings and can be concise. I use controllers when a large resource-oriented API benefits from structure and conventions. I use minimal APIs for small services, focused endpoint groups, or internal APIs where directness improves readability.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Controllers fit well when a service benefits from MVC conventions, action filters, formatter behavior, established versioning patterns, and resource-oriented grouping. Minimal APIs fit focused services or vertical slices where route groups, typed results, endpoint filters, and direct dependency parameters keep the flow easy to follow. Both styles support authorization, OpenAPI, validation, and thin transport handlers. I would not mix them randomly per developer preference; the team needs one default plus clear exceptions so error handling and metadata do not drift.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I evaluate the complete endpoint model rather than counting lines of setup code. I check how the chosen style expresses shared conventions, API versions, filters, model binding, response metadata, test fixtures, and discoverability across dozens of endpoints. Minimal handlers should delegate business work rather than accumulating inline logic, while controllers should not become large service classes. A migration between styles is usually a transport refactor and should preserve routes, status codes, schemas, authorization, and observability through contract tests. The application layer stays independent so endpoint style can evolve without rewriting use cases.

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

Saying controllers are obsolete
Saying minimal APIs are only demos
Putting all minimal handlers in one file
Creating huge controller actions
Mixing endpoint styles without conventions

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Chooses based on fashion
Cannot organize minimal APIs beyond examples
Thinks controllers solve architecture automatically
Ignores documentation/testing effects

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.

How would you organize 80 minimal endpoints?
How do typed results help?
How would authorization work in both styles?
When is mixing both acceptable?

Interviewer notesInterviewerInterviewer notesWhat the interviewer is listening for.Open details

Details

Good candidates compare maintainability and team conventions, not only syntax.

Recruiter notesRecruiterRecruiter notesHow to frame the answer for screening conversations.Open details

Details

This is current ASP.NET Core knowledge with a practical architecture angle.

Continue the section

Next in ASP.NET Core Framework Essentials: Endpoint Filters vs MVC Filters

Step 11 of 26

Endpoint filters vs MVC filters in ASP.NET Core

When would you choose controllers, and when would you choose minimal APIs?

Practice focus

Answer path

Why this matters

Review signals

Follow-up prompts

Continue the section

When would you choose controllers, and when would you choose minimal APIs?

Practice focus

Answer path

Why this matters

Review signals

Follow-up prompts

Continue the section