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 4 of 26
Creates and disposes explicit service scopes for hosted, queued, and parallel work without sharing scoped dependencies across operations.
Explain why awaiting while holding synchronization resources can create deadlocks, contention, or stalled workflows.
Uses deadlock evidence to correct EF Core transaction scope, query plans, and resource order, with bounded retries only for repeat-safe victims.
Diagnose and recover from a production failure caused by rotated secrets or stale secret references.
Explains database connection pool exhaustion with practical .NET data-access examples and production trade-offs.
Traces duplicate side effects across message delivery, lock ownership, settlement, durable job state, and external idempotency, then repairs affected users safely.
Explains high database CPU after an API change with practical .NET data-access examples and production trade-offs.
Turns business recovery targets into right-sized backup, restore, standby, failover, validation, ownership, and rehearsal plans.
Define logs, metrics, traces, alerts, and dashboards needed to operate an ASP.NET Core API in production.
Design API error handling across validation errors, conflicts, auth failures, not-found responses, and unexpected exceptions.
Explains batching, tracking control, idempotency, validation, and operational safety for large EF Core imports.
Explains how EF Core SaveChanges, transactions, and an outbox keep database changes and messages consistent.
Makes POST retries return one durable business outcome by combining scoped keys, request identity, atomic ownership, response replay, and reconciliation.
Designs realistic load, stress, spike, and soak tests from workload assumptions and SLOs while correlating client results with server bottlenecks.
Chooses response cache directives for public, private, sensitive, and revalidated API data without leaking user-specific content.
Explains how systems behave when the broker is down or slow and how backpressure protects callers and dependencies.
Builds request and response contracts that tolerate independently deployed clients through explicit ownership, additive evolution, stable semantics, and measured deprecation.
Explains how to reprocess event streams safely for new projections, bug fixes, and data repair.
Designs a settings service with defaults, validation, scoped preferences, caching, and safe rollout of new settings.
Uses field data, lab evidence, and release correlation to diagnose LCP, INP, and CLS regressions without guessing.
Investigate a production API slowdown caused by blocking async calls, thread-pool pressure, and dependency waits.
Investigate a slow API by checking database queries, blocking async, dependency latency, serialization, logging, and runtime pressure.
Uses instance state, termination reasons, events, logs, configuration, probes, and resource evidence to distinguish common container startup failures.
Diagnoses thread-unsafe scoped dependencies inside parallel execution and redesigns the data boundary without exhausting shared resources.