What does a controller do in ASP.NET MVC?
PICTURE THIS: A REST CALL
Simple meaning
It receives the HTTP request, talks to services or models, and picks a view or result.
WHY — MVC instead of guessing?
Why interviewers care about MVC:
who only read docs from people who shipped.
and tied to .NET MVC work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1It receives the HTTP
request, talks to services or models, and picks a view or result.
- 2Why it exists
Fat controllers are a smell.
- 3How it works
I keep actions thin.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
It receives the HTTP request, talks to services or models, and picks a view or result. Fat controllers are a smell.