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 22 of 26
Builds fast, safe deployment smoke checks that verify readiness and one critical business path, then combine their result with live telemetry to promote, pause, or roll back.
Explains server rendering, client rendering, static rendering, freshness, SEO, personalization, and performance trade-offs.
Explains asynchronous-looking state updates, batching, functional setters, and avoiding stale values.
Explains session state choices for scaled-out ASP.NET Core APIs and when Redis-backed state is appropriate.
Distinguishes operators that can yield incrementally from operators that must consume substantial input before producing results.
Selects synchronous calls, asynchronous messaging, or a deliberate combination based on user feedback, coupling, latency, durability, and failure behavior.
Explain when Task.Run is useful, when async/await is enough, and why Task.Run is usually wrong for I/O in ASP.NET Core.
Compare Task and Thread in .NET, including abstraction level, scheduling, and when direct thread management is rarely appropriate.
Combines schema diffing, real provider tests, consumer expectations, generated clients, semantic scenarios, and rollout evidence to prevent accidental API breaks.
Tests asynchronous completion, caller cancellation, owned timeouts, cleanup, and race-sensitive side effects deterministically with controlled dependencies and bounded diagnostics.
Distinguishes observable contracts from incidental calls while preserving important interaction assertions.
Explains component tests that assert user-visible behavior instead of implementation details.
Uses runtime-supported initialization rather than timing-dependent manual checks and defines failure, retry, and disposal behavior explicitly.
Distinguish timeouts from cancellation and explain how to combine them around external calls and request handling.
Uses live runtime and application counters to classify CPU, memory, GC, exception, request, and ThreadPool symptoms before deeper collection.
Explains post-incident review, root cause, contributing factors, action items, tests, alerts, runbooks, and ownership.
Explains closed, open, and half-open behavior, failure classification, recovery probes, and the limits of circuit breakers.
Explains the boundary between OAuth/OIDC identity, application users, claims mapping, roles, and app-specific permissions.
Explains when a reducer clarifies related state transitions and when independent state remains simpler.
Explains policy-based authorization, requirements, handlers, claims, capabilities, and resource-aware checks.
Uses EF Core context pooling only when reusable context state, tenant isolation, and underlying connection state are controlled and tested.
Explains delayed delivery, scheduled work, reminders, retry timing, cancellation, and clock-related trade-offs.
Explains when EF Core compiled queries help, what they do not fix, and how to measure their value.
Explains when set-based EF Core updates are better than loading entities and where lifecycle behavior can differ.