What is a catch-all route parameter?
PICTURE THIS: HOW TO EXPLAIN IT
IdeaRouting
HowWhat happens inside
Why they askShows real use
Simple meaning
{*path} captures remaining segments.
WHY — Routing instead of guessing?
Why interviewers care about Routing:
Routing questions separate people
who only read docs from people who shipped.
Keep it short, concrete,
and tied to .NET MVC work.
Stay structured
Name the idea, why it exists, then one short example.
Close cleanly
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:
- 1Define it
{*path} captures remaining segments.
- 2Why it exists
Useful for CMS-style pages.
- 3I register it last
so it does not swallow other routes.
- 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:
Say this line
“Useful for CMS-style pages.”
Break into beats
UsefulforCMSstylepages
Speaking order
298740833747163290
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
{*path} captures remaining segments. Useful for CMS-style pages.