Loading
Pick a focused question that fits your time, stack, and interview goal.
57 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 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.
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.
Explains when production approvals are useful and how to avoid turning them into empty bureaucracy.
Explains how to trace a production deployment back to commit, build, artifact, configuration, and approval.
Explains how Aspire references inject resource configuration, how logical service names resolve, and why dependency wiring differs from startup readiness.
Compares revert and reset, especially for shared branches and production-safe history.
Compares rollback and roll-forward decisions after a failed production deployment.