Loading
Pick a focused question that fits your time, stack, and interview goal.
37 results across 1 active filter
Page 1 of 2
Separates application composition in AppHost from reusable in-process defaults for telemetry, health, resilience, and service discovery.
Builds a small, immutable, non-root .NET runtime image with controlled inputs, external configuration, graceful lifecycle behavior, and a practical patching strategy.
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.
Investigate production failures caused by custom domain, DNS, TLS certificate, or HTTPS binding problems.
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 staging slots, validation before swap, warm-up, traffic continuity, and safer production releases for App Service APIs.
Explains how App Service plans provide compute capacity, how scale-out affects app instances, and why APIs need stateless design.
Explains how App Service can resolve Key Vault references through managed identity and what to watch during rotation and environment setup.
Covers App Service app settings, environment-specific configuration, restarts, slot settings, and avoiding hard-coded production values.
Covers using managed identity and Microsoft Entra authentication for Azure SQL access from a .NET API.
Explains health endpoints, readiness versus liveness, warm-up, dependency checks, and safe App Service health behavior.
Covers queue-backed work, idempotency, retries, visibility timeout, poison messages, progress tracking, and choosing Storage Queues or Service Bus.
Covers deployment logs, startup failures, runtime stack, app settings, missing files, Key Vault references, and post-deployment diagnosis.
Explains same-artifact promotion, environment-specific configuration, approvals, smoke testing, drift detection, and production traceability.
Explains the small set of Kubernetes resources needed to run and expose a replicated stateless API without drowning the answer in platform vocabulary.