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.
878 drills fit a 10-minute session. Closest fits first.
Page 18 of 37
Chooses a deployment strategy from capacity, compatibility, risk, observability, and rollback needs, then defines progressive promotion and abort signals.
Selects small structural and behavioral patterns from the problem being solved instead of pattern-name recognition.
Separates ordinal identity comparison from culture-aware display ordering and keeps hash-based collection semantics consistent.
Chooses database test infrastructure by the provider behavior a test must prove.
Explains inward dependency flow, stable business policy, adapters, and when a smaller project structure is enough.
Explains cleanup for subscriptions, timers, event listeners, and aborting stale fetches.
Uses complexity as a first filter while accounting for constants, locality, allocations, data size, and the complete operation sequence.
Explains short-lived access tokens, refresh-token rotation, revocation, storage choices, and replay detection.
Compares cache-aside, read-through, and write-through by read and write ownership, freshness, failure behavior, invalidation, fallback, stampede control, and operational complexity.
Designs a narrow covering index from predicates and ordering, then weighs eliminated lookups against storage, write overhead, cache efficiency, overlap, and maintenance cost.
Explains when CSRF matters, how cookies change browser behavior, and what mitigations fit API clients.
Compares vendor-neutral OpenTelemetry concepts with Application Insights usage for .NET production services.
Separates prompt-requested JSON, parseable JSON modes, and provider-enforced schema adherence.
Separates application instruction attacks from attempts to bypass a model's safety behavior and explains their overlapping defenses.
Compares Redis pub/sub with durable queues when broadcasting cache invalidation or refresh events.
Explains how roles group permissions while API policies enforce specific capabilities and resource rules.
Combines focused collaborators for independent behavior while recognizing cases where a genuine stable hierarchy remains simpler.
Choose between ConcurrentDictionary and explicit locks when managing concurrent in-memory data.
Explain what ConfigureAwait(false) does, why it mattered historically, and how to reason about it in ASP.NET Core and library code.
Keeps images environment-neutral while handling configuration precedence, secret delivery, rotation, and startup validation safely.
Separates ephemeral instance files from durable data and sends logs, uploads, caches, and diagnostics to storage with explicit lifecycle ownership.
Uses immutable image identity, controlled promotion, registry security, and deliberate base-image rebuilding instead of mutable latest tags.
Explains bind addresses, published ports, internal DNS, service identity, and why localhost changes meaning across container boundaries.
Distinguishes request and response media types and designs predictable negotiation, rejection, documentation, and caching behavior.