Skill area
Deployment safety, environment promotion, rollback, feature flags, release traceability, and production change control.
Practice items tagged with Release Engineering.
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.
Preparation paths where this taxonomy appears in the track scope.
Logs, metrics, traces, alerts, triage, mitigation, and post-incident learning.
A practical production-ownership track covering observability foundations, correlation IDs, structured logs, dependency telemetry, OpenTelemetry, health checks, sampling, incident triage, slow API diagnosis, post-release failures, downstream dependency incidents, missing logs, queue backlogs, auth failures, SLO alerts, dashboards, release correlation, mitigation choices, post-incident reviews, runbooks, and capacity/backpressure signals.
App Service, identity, secrets, deployments, observability, and background work.
A focused Azure track for .NET backend and full-stack candidates who need to explain production hosting, safe releases, App Service behavior, managed identity, Key Vault, Azure SQL, Application Insights, and queue-based work.