Skip to content

Tracks Drills Topics Technologies Tech stacks Skill areas

Tracks Drills Topics

Loading

Aporeon interview preparation

About Privacy Terms

.NET Full Stack

DevOps Basics

Practical interview coverage around Git workflow, pull requests, CI/CD, versioning, releases, failed deployments, rollback, feature flags, and production ownership.

21 drillsPractice one at a timeOrdered pathArchitecture scenarioComparison questionDebugging scenarioConcept question

Recommended start

Release Branching

Designs a pragmatic branching strategy for normal releases, hotfixes, and production traceability.

Hard~12 minStep 1 of 21

Practice this drill Choose another

Search

21 of 21 shown

1Release BranchingRecommended startDesigns a pragmatic branching strategy for normal releases, hotfixes, and production traceability.Architecture scenarioHard~12 min.NETASP.NET CoreGitPractice 2Artifact vs PackageCompares build artifacts and deployment packages in a .NET release pipeline.Comparison questionMedium~7 min.NETASP.NET CoreGitPractice 3GitHub Actions vs Azure DevOpsCompares GitHub Actions and Azure DevOps at a practical .NET team level.Comparison questionMedium~7 min.NETASP.NET CoreGitPractice 4Failed CI PipelineExplains a practical approach to diagnosing failed builds, tests, package restore, environment issues, or flaky checks.Debugging scenarioMedium~10 min.NETASP.NET CoreGitPractice 5API vs App VersioningSeparates deployable artifact identity from client-facing contract compatibility, allowing frequent releases without unnecessary API-version churn.Comparison questionMedium~7 min.NETASP.NET CoreGitPractice 6Release NotesExplains release notes and changelog thinking for engineering, QA, support, and product communication.Concept questionEasy~5 min.NETASP.NET CoreGitPractice 7Package VersioningExplains versioning and releasing shared .NET libraries or NuGet packages safely.Concept questionMedium~7 min.NETASP.NET CoreGitPractice 8Release TraceabilityExplains how to trace a production deployment back to commit, build, artifact, configuration, and approval.Concept questionMedium~7 min.NETASP.NET CoreGitPractice 9Failed DeploymentExplains a structured response to a failed production deployment in a .NET application.Debugging scenarioHard~12 min.NETASP.NET CoreGitPractice 10Smoke ChecksBuilds fast, safe deployment smoke checks that verify readiness and one critical business path, then combine their result with live telemetry to promote, pause, or roll back.Concept questionMedium~7 min.NETASP.NET CoreGitPractice 11Environment PromotionExplains promoting artifacts through dev, staging, and production while managing configuration differences safely.Concept questionMedium~7 min.NETASP.NET CoreGitPractice 12Production OwnershipExplains production ownership beyond writing code, including monitoring, alerts, support, and recovery.Concept questionEasy~5 min.NETASP.NET CoreGitPractice 13Logs Metrics AlertsDesigns logs, metrics, traces, dashboards, and alerts around user outcomes, service objectives, dependencies, saturation, privacy, cardinality, and actionable incident response.Concept questionMedium~7 min.NETASP.NET CoreGitPractice 14Bad Release IncidentExplains how to respond to a production incident caused by a bad release.Debugging scenarioHard~12 min.NETASP.NET CoreGitPractice 15Dependency MonitoringExplains how to monitor external and internal dependencies after a .NET service release.Concept questionMedium~7 min.NETASP.NET CoreGitPractice 16Approval GatesExplains when production approvals are useful and how to avoid turning them into empty bureaucracy.Architecture scenarioMedium~10 min.NETASP.NET CoreGitPractice 17Hotfix FlowHandles an urgent production fix from verified impact and deployed provenance through minimal code, focused validation, controlled rollout, rollback readiness, and merge-forward.Debugging scenarioHard~12 min.NETASP.NET CoreGitPractice 18Configuration DriftExplains how environment configuration drift causes deployment bugs and how to reduce it.Debugging scenarioMedium~10 min.NETASP.NET CoreGitPractice 19Flag CleanupManages feature flags as temporary production controls with ownership, safe defaults, targeted rollout, telemetry, audit, failure behavior, and planned removal.Concept questionMedium~7 min.NETASP.NET CoreGitPractice 20Infrastructure as CodeUses declarative infrastructure, reviewed plans, environment parameters, protected deployment identities, state management, and drift control without hiding operational risk.Architecture scenarioMedium~10 minAzureAzure DevOpsGitPractice 21Disaster RecoveryTurns business recovery targets into right-sized backup, restore, standby, failover, validation, ownership, and rehearsal plans.Architecture scenarioHard~12 min.NETApplication InsightsASP.NET CorePractice

Practice order

21 drillsOne at a time

1Release BranchingUp next / Hard / ~12 min
2Artifact vs PackageMedium / ~7 min
3GitHub Actions vs Azure DevOpsMedium / ~7 min
4Failed CI PipelineMedium / ~10 min
5API vs App VersioningMedium / ~7 min
6Release NotesEasy / ~5 min
7Package VersioningMedium / ~7 min
8Release TraceabilityMedium / ~7 min

+13 more drills in this section