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.
46 results across 1 active filter
Page 1 of 2
Builds a small, immutable, non-root .NET runtime image with controlled inputs, external configuration, graceful lifecycle behavior, and a practical patching strategy.
Reason through mitigation choices during a live App Service production incident.
Compares rollback, roll-forward, feature kill switches, scaling, and degraded mode as incident mitigations.
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.
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 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.
Diagnose a .NET API that fails to start on Azure App Service after a deployment.
Diagnose a deployment slot swap that fails because the target app does not warm up successfully.
Identify a failed App Service deployment caused by a mismatched .NET runtime or publish target.
Diagnose authentication redirect or callback failures after a slot swap or domain change.
Investigate a production issue caused by staging and production slot configuration drifting apart.
Investigate production HTTP 500 errors that start immediately after a deployment slot swap.
Designs feature flag storage, targeting, safe defaults, auditability, and rollout observability for backend behavior.
Uses instance state, termination reasons, events, logs, configuration, probes, and resource evidence to distinguish common container startup failures.
Builds deterministic images efficiently by controlling context, restore layers, dependency inputs, and cache invalidation.
Uses Compose for reproducible local dependencies while preserving fast inner loops, realistic readiness, and clear differences from production orchestration.
Handles SIGTERM, traffic draining, cancellation, background work, and termination deadlines without losing accepted work or hanging rollout.
Explains initial incident triage: confirm impact, mitigate, assign roles, preserve evidence, and communicate.
Explains staging slots, validation before swap, warm-up, traffic continuity, and safer production releases for App Service APIs.