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.
42 results across 1 active filter
Page 2 of 2
Coordinates startup work, readiness, schema compatibility, warmup, and mixed-version traffic during a rolling release.
Binds typed configuration, understands property precedence, validates startup invariants, and keeps secrets outside source control.
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.
Turns a useful Aspire development model into explicit production infrastructure without treating the local AppHost as the runtime platform.
Separates traffic eligibility, process recovery, and slow startup so health checks do not amplify dependency failures or restart healthy work.
Explains how Aspire references inject resource configuration, how logical service names resolve, and why dependency wiring differs from startup readiness.
Coordinates old and new application versions, expand-and-contract schema changes, migration ownership, readiness, and rollback during rolling releases.
Reduces container privileges through non-root execution, minimal images, controlled filesystems, and explicit capability requirements.
Compares App Service WebJobs and Azure Functions for queue processing, scheduled tasks, scaling, deployment ownership, and operational isolation.
Covers configuration that must stay with a slot, such as connection strings, secrets, callback URLs, and staging-only settings.
Explains scale-out bugs from in-memory sessions, local caches, background queues, uploaded files, and per-instance behavior.
Designs scheduled work for overlap, multiple replicas, restart, failure, and durable ownership instead of assuming one execution.
Explains Aspire as a code-first application model and developer experience without confusing it with a production runtime or architecture style.
Covers custom domains, TLS, HTTPS, allowed hosts, CORS boundaries, and production-facing endpoint hygiene for App Service APIs.
Covers build-once deployment, tests, artifact traceability, slot deployment, smoke checks, approvals, and post-release monitoring.
Compares Azure hosting choices for a .NET API using operational complexity, scaling model, deployment ownership, and workload shape.
Explains local filesystem limits, multiple instances, in-memory state, distributed cache, durable storage, and scale-out-safe API design.