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.
460 drills fit a 10-minute session. Closest fits first.
Page 4 of 20
Explains how to choose rollback, swap-back, hotfix, or roll-forward after a failed Azure App Service deployment.
Explains how multiple worker instances share queue work and what limits safe scaling.
Builds dependency-specific timeout budgets that contain slow SQL, HTTP, and cache calls without creating unsafe retries or ambiguous writes.
Builds a story about taking responsibility for a production bug, mitigating impact, and preventing recurrence.
Designs integration tests for authentication, capabilities, ownership, account status, and cross-tenant isolation without bypassing the real authorization pipeline.
Tests durable background processing across duplicate delivery, retries, acknowledgement timing, crashes, poison messages, and observable completion.
Explains how to diagnose and mitigate a downstream dependency slowing the API through timeouts, retries, and degraded behavior.
Explains how to investigate queue age, backlog, worker health, poison messages, dependency failures, and safe catch-up.
Use correlation IDs, structured logs, and logging scopes to make API failures traceable in production.
Explains how query tags, request correlation, and telemetry help connect slow SQL back to code paths.
Redesigns read-heavy shared state so readers observe a complete version without coordinating every access through a lock.
Use OpenAPI for API design, client integration, testing, and contract review in ASP.NET Core services.
Explains scale-out bugs from in-memory sessions, local caches, background queues, uploaded files, and per-instance behavior.
Covers large exports, uploads, and API responses where bounded memory matters more than convenience.
Explains cache memory growth, eviction, size limits, stale data, and why cache design needs explicit bounds.
Diagnoses lost struct mutations and explains how readonly access can trigger defensive copies.
Uses reduction, thread-local state, atomic scalar updates, or indexed output instead of mutating a shared collection from parallel workers.
Explains trusted tenant context, membership checks, tenant-scoped queries, cache keys, and background job propagation.
Explains admin list/edit/delete workflows with capability checks, audit events, confirmation, validation, and recovery.
Explains caching and revalidation choices for static, dynamic, user-specific, and frequently changing data.
Chooses constraints, conditional writes, optimistic conflicts, or stronger isolation to protect a limited-resource reservation without unnecessary blocking.
Explains composite index column order with practical .NET data-access examples and production trade-offs.
Explains EF Core connection resiliency and retries with practical .NET data-access examples and production trade-offs.
Explains sampling, high-cardinality labels, retention, cost, and keeping enough signal for incident diagnosis.