How would you implement object-level authorization in MVC?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
After loading the resource I check ownership or ACL in a filter or service.
WHY — Security instead of guessing?
Why interviewers care about Security:
question about Security.
trade-offs, and what you would actually do on a .NET MVC project - not buzzwords.
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:
- 1After loading the resource
I check ownership or ACL in a filter or service.
- 2[Authorize(Roles=Admin)] is not enough
for user-owned docs.
- 3Return 404 when enumeration
is a risk.
- 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
After loading the resource I check ownership or ACL in a filter or service. [Authorize(Roles=Admin)] is not enough for user-owned docs.