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.
199 results across 1 active filter
Page 1 of 9
Turns a production-only role and payload failure into the smallest durable API regression test.
Explains physical connection reuse, pool partitioning, short ownership, exhaustion causes, diagnostics, and why increasing the pool is not the first fix.
Aggregates log entries into per-minute error counts with deterministic output.
Uses reduction, thread-local state, atomic scalar updates, or indexed output instead of mutating a shared collection from parallel workers.
Design and debug rate limiting while protecting the API without blocking legitimate users and integrations.
Checks health, authentication, and one critical read flow after deployment without creating persistent business data.
Design background jobs that handle cancellation, retries, and duplicate execution without corrupting external state.
Use CancellationToken to stop wasted work when clients disconnect, timeouts expire, or background operations are being shut down.
Explain why CancellationTokenSource lifetime matters and how careless timeout creation can leak timers or resources.
Explains dependency duration, error rate, timeout rate, query tagging, Redis latency, HTTP downstream calls, and endpoint correlation.
Use Channel<T> to coordinate producer/consumer background processing inside a .NET service while respecting backpressure and shutdown.
Chooses heap-focused GC evidence or complete process state based on memory growth, roots, hangs, crashes, locks, and collection risk.
Reason through mitigation choices during a live App Service production incident.
Chooses constraints, conditional writes, optimistic conflicts, or stronger isolation to protect a limited-resource reservation without unnecessary blocking.
Compares rollback, roll-forward, feature kill switches, scaling, and degraded mode as incident mitigations.
Chooses counters, traces, stack snapshots, GC dumps, full dumps, or a profiler from the production symptom and investigation cost.
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.
Designs a narrow covering index from predicates and ordering, then weighs eliminated lookups against storage, write overhead, cache efficiency, overlap, and maintenance cost.
Compares vendor-neutral OpenTelemetry concepts with Application Insights usage for .NET production services.
Compares Redis pub/sub with durable queues when broadcasting cache invalidation or refresh events.
Explains how later configuration providers override earlier values and keeps secrets, environment overrides, and diagnostics within explicit boundaries.
Explains EF Core connection resiliency and retries with practical .NET data-access examples and production trade-offs.
Sets concurrency from the constrained resource and verifies throughput, latency, and downstream safety instead of maximizing active work.