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.
298 results across 1 active filter
Page 2 of 13
Chooses database test infrastructure by the provider behavior a test must prove.
Builds a proportionate test plan from blast radius, failure probability, detectability, and reversibility.
Explains how unit, integration, contract, component, and end-to-end tests cover different failure boundaries.
Explains cleanup for subscriptions, timers, event listeners, and aborting stale fetches.
Explains loading, error, empty, success, refetch, stale data, and request lifecycle in client-rendered React.
Designs controlled diagnostic access, collection triggers, container permissions, artifact egress, privacy, retention, and post-capture verification.
Explains short-lived access tokens, refresh-token rotation, revocation, storage choices, and replay detection.
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.
Compares point-to-point queues with publish-subscribe topics and explains when each model fits.
Compares Redis pub/sub with durable queues when broadcasting cache invalidation or refresh events.
Explains EF Core connection resiliency and retries with practical .NET data-access examples and production trade-offs.
Keeps images environment-neutral while handling configuration precedence, secret delivery, rotation, and startup validation safely.
Connects orchestrator requests and limits to .NET GC, thread-pool behavior, throttling, OOM termination, and capacity planning.
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.
Designs useful local database and cache resources without confusing container lifetime, durable data, bind mounts, parameters, and production secrets.
Explains bind addresses, published ports, internal DNS, service identity, and why localhost changes meaning across container boundaries.
Explains process isolation, shared kernels, image-based deployment, and where containers differ operationally from virtual machines.
Explains sampling, high-cardinality labels, retention, cost, and keeping enough signal for incident diagnosis.
Explains deployment markers, version telemetry, feature-flag state, commit traceability, and incident diagnosis after releases.
Explains what belongs in runbooks, how on-call handoff preserves context, and how operational docs stay useful.
Uses resource state, structured logs, traces, metrics, health, and configuration evidence to isolate a cross-service failure.
Diagnose a .NET API that fails to start on Azure App Service after a deployment.