Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
618 drills fit a 20-minute session. Closest fits first.
Page 3 of 26
Updates only public mutable fields and leaves ownership, status, and audit values server-controlled.
Builds a read-only EF Core projection with aggregates, stable ordering, and bounded results instead of loading an entity graph.
Carries the ASP.NET Core request token into a bounded EF Core query while keeping cancellation separate from business rollback guarantees.
Maps a named capability to an ASP.NET Core policy and enforces it at the endpoint boundary.
Uses an explicit state model for initial loading, success, empty, recoverable error, and refetching.
Produces field-keyed validation errors through one reusable endpoint boundary.
Writes a left-join aggregate that keeps active customers with no paid orders and applies date filters without changing join semantics.
Tests validation, focus, pending state, and the save contract through accessible user interactions rather than component internals.
Verifies status, content type, stable error extensions, and field errors for an invalid API request.
Implements a small validation helper for date ranges with clear error messages.
Explains how tenant query filters help, where they can be bypassed, and what extra safeguards protect tenant isolation.
Design and debug rate limiting while protecting the API without blocking legitimate users and integrations.
Explains dynamic filters and SQL injection risk with practical .NET data-access examples and production trade-offs.
Designs a pragmatic branching strategy for normal releases, hotfixes, and production traceability.
Design background jobs that handle cancellation, retries, and duplicate execution without corrupting external state.
Use Channel<T> to coordinate producer/consumer background processing inside a .NET service while respecting backpressure and shutdown.
Explains partition key selection for ordering, load distribution, hot keys, and consumer scalability.
Maps business invariants and stale-data tolerance to strong or eventual consistency, explicit failure behavior, reconciliation, and user-visible state.
Reason through mitigation choices during a live App Service production incident.
Connects orchestrator requests and limits to .NET GC, thread-pool behavior, throttling, OOM termination, and capacity planning.
Sets concurrency from the constrained resource and verifies throughput, latency, and downstream safety instead of maximizing active work.
Serializes work for the same resource while preserving concurrency across independent keys and managing keyed-lock lifetime safely.
Decide how to handle CPU-heavy work in an API without damaging request throughput or making the system unreliable.
Applies CQRS proportionally, separating model responsibilities without assuming separate databases, messaging, or event sourcing.