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 7 of 26
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 deadlocks or starvation caused by blocking on async code with Result, Wait, or GetAwaiter().GetResult().
Moves invariant-sensitive decisions toward the owning object while keeping orchestration, queries, and cross-boundary work appropriately explicit.
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.
Practices incident response after an OOM: restore service, collect evidence, identify trigger, and prevent recurrence.
Reviews a captive scoped dependency as both a lifetime and concurrency bug, then replaces it with explicit per-operation scopes and minimal immutable work data.
Explains audit fields and data change tracking with practical .NET data-access examples and production trade-offs.
Maps creation, updates, asynchronous work, validation, authorization, conflicts, and failures to useful HTTP outcomes.
Places state according to who owns it, how long it must live, and whether the URL or server is the source of truth.
Builds a proportionate test plan from blast radius, failure probability, detectability, and reversibility.
Chooses between sequence, counted, indexed, set, and dictionary contracts based on required operations and complexity.
Explains what a lambda captures, how captured state is shared, and why a long-lived callback can retain more memory than expected.
Review async .NET code that does not accept or propagate CancellationToken and explain the practical production risk.
Designs controlled diagnostic access, collection triggers, container permissions, artifact egress, privacy, retention, and post-capture verification.
Explains how environment configuration drift causes deployment bugs and how to reduce it.
Explains how later configuration providers override earlier values and keeps secrets, environment overrides, and diagnostics within explicit boundaries.