Loading
Pick a focused question that fits your time, stack, and interview goal.
199 results across 1 active filter
Page 7 of 9
Uses an actual execution plan, row-flow evidence, runtime measurements, and representative parameters to diagnose a slow query without guessing.
Explains how to inspect, fix, replay, skip, or archive dead-letter messages without repeating bad side effects.
Implements safe redaction of known sensitive keys in a dictionary before logging.
Replaces a parent query plus one status query per row with one server-side projection.
Handles the request body as a forward-only resource, buffers only when necessary, and enforces limits before large input consumes the service.
Explains why committed headers cannot be replaced, how streaming failures behave, and how middleware preserves response ownership.
Implements a bounded async retry helper that respects cancellation and does not retry every exception blindly.
Wraps a complete explicit transaction in the provider execution strategy and creates fresh context state for each retry attempt.
Classifies retryable outcomes and applies bounded attempts, exponential backoff, jitter, deadlines, and idempotency.
Explains why Redis connections are reused, how timeouts protect API threads, and how to diagnose client-side Redis pressure.
Reviews and stages destructive EF Core schema changes around live data, locks, mixed application versions, recovery, and rollback.
Explains how to choose rollback, swap-back, hotfix, or roll-forward after a failed Azure App Service deployment.
Persists domain state and its outbox message in one SaveChanges transaction without publishing inside the request transaction.
Wraps a pooled DbContext factory so every request assigns tenant state before a global query filter can run.
Sets bounded timeout and deadline policies across callers, APIs, databases, and external services without hiding unknown outcomes.
Builds dependency-specific timeout budgets that contain slow SQL, HTTP, and cache calls without creating unsafe retries or ambiguous writes.
Investigate deadlocks or starvation caused by blocking on async code with Result, Wait, or GetAwaiter().GetResult().
Adds a stable query tag and inspects generated SQL without embedding user data or enabling unsafe global logging.
Diagnose thread-pool starvation caused by blocking work, unbounded concurrency, or sync-over-async in .NET APIs.
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.
Tests that an unexpected failure returns a safe correlation identifier and records the same value in structured logs.
Explains tracing one user action across browser, frontend server, API, dependencies, logs, metrics, and safe diagnostics.
Uses live runtime and application counters to classify CPU, memory, GC, exception, request, and ThreadPool symptoms before deeper collection.