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.
1225 drills fit a 20-minute session. Closest fits first.
Page 14 of 52
Explains token storage, cookies, XSS, CSRF, and why browser UI never replaces server authorization.
Uses an actual execution plan, row-flow evidence, runtime measurements, and representative parameters to diagnose a slow query without guessing.
Separates traffic eligibility, process recovery, and slow startup so health checks do not amplify dependency failures or restart healthy work.
Repairs a workflow when a remote operation may have succeeded but local state, messages, and callbacks disagree.
Explains how to inspect, fix, replay, skip, or archive dead-letter messages without repeating bad side effects.
Uses metadata-driven behavior deliberately and protects reflection-dependent code when publishing with trimming or ahead-of-time compilation.
Evaluates repositories by domain language, query ownership, and substitutability instead of treating them as a mandatory wrapper around DbSet.
Handles the request body as a forward-only resource, buffers only when necessary, and enforces limits before large input consumes the service.
Coordinates server retry signals with client backoff, deadlines, idempotency, overload protection, and bounded retry budgets.
Reviews a proposed response-field rename by finding consumers, classifying the break, choosing a migration path, and proving rollout and removal are safe.
Reviews and stages destructive EF Core schema changes around live data, locks, mixed application versions, recovery, and rollback.
Coordinates old and new application versions, expand-and-contract schema changes, migration ownership, readiness, and rollback during rolling releases.
Protects source, dependencies, workflows, build identities, runners, artifacts, and deployment verification while preserving traceability and patch response.
Designs cancellation-aware response streaming with bounded memory, correct resource ownership, and practical download behavior.
Investigate blocked request threads and thread-pool starvation caused by Result, Wait, or GetAwaiter().GetResult().
Verifies migration SQL, data preservation, production-provider behavior, mixed application versions, backfills, and expand-contract releases.
Combines protocol stubs, contract checks, sandbox tests, and failure simulation without depending on live production services.
Diagnose thread-pool starvation caused by blocking work, unbounded concurrency, or sync-over-async in .NET APIs.
Diagnose an ASP.NET Core API that becomes slow because request threads are blocked or exhausted.
Connects HTTP preconditions to atomic database concurrency checks and honest 412 or 428 API behavior.
Explains read models for complex API screens with practical .NET data-access examples and production trade-offs.
Explains how Suspense boundaries stream useful page regions while coordinating loading, errors, and data ownership.
Makes consumer-side deduplication atomic with the business change while supporting concurrent delivery, retention, replay, and failed processing.
Balances strict script policy with per-request nonces, dynamic rendering, third-party scripts, caching, and operational rollout.