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.
34 results across 1 active filter
Page 1 of 2
Separates deployable artifact identity from client-facing contract compatibility, allowing frequent releases without unnecessary API-version churn.
Designs a pragmatic branching strategy for normal releases, hotfixes, and production traceability.
Compares build artifacts and deployment packages in a .NET release pipeline.
Explains how environment configuration drift causes deployment bugs and how to reduce it.
Explains the difference between deploying code and releasing functionality to users using feature flags.
Explains promoting artifacts through dev, staging, and production while managing configuration differences safely.
Manages feature flags as temporary production controls with ownership, safe defaults, targeted rollout, telemetry, audit, failure behavior, and planned removal.
Compares GitHub Actions and Azure DevOps at a practical .NET team level.
Explains how tags and release branches support traceability, hotfixes, and production versioning.
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.
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.
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.