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.
65 results across 1 active filter
Page 2 of 3
Handles SIGTERM, traffic draining, cancellation, background work, and termination deadlines without losing accepted work or hanging rollout.
Handles an urgent production fix from verified impact and deployed provenance through minimal code, focused validation, controlled rollout, rollback readiness, and merge-forward.
Explains staging slots, validation before swap, warm-up, traffic continuity, and safer production releases for App Service APIs.
Explains deployment versus release, staged enablement, kill switches, cleanup, and App Service slot interaction.
Explains a practical approach to diagnosing failed builds, tests, package restore, environment issues, or flaky checks.
Explains a structured response to a failed production deployment in a .NET application.
Explains release notes and changelog thinking for engineering, QA, support, and product communication.
Explains semantic versioning for .NET applications and how it communicates release impact.
Covers deployment logs, startup failures, runtime stack, app settings, missing files, Key Vault references, and post-deployment diagnosis.
Explains safe migration strategy for Azure-hosted .NET APIs, including expand-contract changes, locking risk, rollback, and deployment order.
Explains same-artifact promotion, environment-specific configuration, approvals, smoke testing, drift detection, and production traceability.
Explains a practical Git workflow for a .NET team using branches, pull requests, code review, and protected main branches.
Explains how to respond to a production incident caused by a bad release.
Explains the small set of Kubernetes resources needed to run and expose a replicated stateless API without drowning the answer in platform vocabulary.
Designs logs, metrics, traces, dashboards, and alerts around user outcomes, service objectives, dependencies, saturation, privacy, cardinality, and actionable incident response.
Uses declarative infrastructure, reviewed plans, environment parameters, protected deployment identities, state management, and drift control without hiding operational risk.
Compares merge and rebase in team workflows, including history clarity, conflict handling, and shared branch safety.
Explains how to deploy database changes safely with .NET APIs using backward-compatible steps.
Explains how to monitor external and internal dependencies after a .NET service release.
Turns a useful Aspire development model into explicit production infrastructure without treating the local AppHost as the runtime platform.
Explains versioning and releasing shared .NET libraries or NuGet packages safely.
Explains how to verify a .NET release after deployment using smoke tests, metrics, logs, and business signals.
Explains useful quality gates for .NET CI pipelines, including tests, analysis, security, migrations, and smoke checks.
Separates traffic eligibility, process recovery, and slow startup so health checks do not amplify dependency failures or restart healthy work.