What is OutputCache policy in .NET 7+?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
Server-side caching of endpoint output with policies for duration and tags.
WHY — ASP.NET instead of guessing?
Why interviewers care about ASP.NET:
who only read docs from people who shipped.
and tied to .NET 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:
- 1Server-side caching of endpoint
output with policies for duration and tags.
- 2Why it exists
Tag-based eviction refreshes after writes.
- 3I never cache personalized
authenticated HTML without vary-by rules.
- 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
Server-side caching of endpoint output with policies for duration and tags. Tag-based eviction refreshes after writes.