Architecture scenarioHard~12 minCI/CD, Git & Release Engineering Essentials / 12 of 15

Interview question

How would you deploy a .NET API change that requires a database migration without downtime?

Migration-safe deployment for a .NET API

Explains how to deploy database changes safely with .NET APIs using backward-compatible steps.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I would avoid destructive schema changes in one release. First, I would review the generated SQL and understand table size, locking, and compatibility. If the change is risky, I would use an expand-and-contract approach: add new schema safely, deploy code that supports both old and new shape, backfill data, switch usage, and remove old schema later.

Full answer below

Practice focus

Migration safety, expand-and-contract, compatibility, rollout order, rollback planning, and production risk.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Database migrations are one of the main reasons deployment safety is hard. The code and schema must be compatible during rollout.
I would avoid destructive schema changes in one release. First, I would review the generated SQL and understand table size, locking, and compatibility. If the change is risky, I would use an expand-and-contract approach: add new schema safely, deploy code that supports both old and new shape, backfill data, switch usage, and remove old schema later.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Renaming a column directly can break old instances during a rolling deployment. I would add the new column first, deploy code that can read the old shape and write both values where needed, backfill in bounded restartable batches, switch reads after verification, and remove the old column only after every running and rollback version no longer depends on it. Index creation, constraints, and data conversion receive the same compatibility treatment. The temporary complexity is deliberate: it keeps mixed versions functional and preserves a recovery path while the data transition is still in progress.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I treat schema evolution as a multi-release workflow with explicit compatibility windows. Generated SQL is reviewed against realistic table size and data distribution, and lock duration, transaction-log growth, replica lag, index build behavior, and backfill load are tested before production. Migration execution has one owner and is not raced by every application instance. Backfills checkpoint progress, throttle against database health, and verify counts and invariants before cutover. The release plan states which stages can roll back and where recovery requires a forward fix or compensating script. Dashboards and runbooks cover migration state, application errors, blocking, latency, CPU, and data mismatch through final cleanup.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Renaming or dropping columns in the same release that needs them.
Auto-running risky migrations at app startup.
Not reviewing generated SQL.
No backfill or rollback plan.

Red flagsCandidateSigns the approach is fragileSignals that an interviewer may treat as risky.Open details

Details

Only knows migration commands.
Does not consider rolling deployment.
Ignores table size and locks.
Cannot explain expand-and-contract.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What is expand-and-contract?
When is startup migration risky?
How do you backfill large tables?
What would you monitor during migration?

Continue the section

Next in CI/CD, Git & Release Engineering Essentials: Progressive Deployment

Step 13 of 15

Choose rolling, blue-green, or canary deployment

Opening drill

Architecture scenarioHard~12 minCI/CD, Git & Release Engineering Essentials / 12 of 15

Interview question

How would you deploy a .NET API change that requires a database migration without downtime?

Migration-safe deployment for a .NET API

Explains how to deploy database changes safely with .NET APIs using backward-compatible steps.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Migration safety, expand-and-contract, compatibility, rollout order, rollback planning, and production risk.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
Database migrations are one of the main reasons deployment safety is hard. The code and schema must be compatible during rollout.
I would avoid destructive schema changes in one release. First, I would review the generated SQL and understand table size, locking, and compatibility. If the change is risky, I would use an expand-and-contract approach: add new schema safely, deploy code that supports both old and new shape, backfill data, switch usage, and remove old schema later.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
Renaming a column directly can break old instances during a rolling deployment. I would add the new column first, deploy code that can read the old shape and write both values where needed, backfill in bounded restartable batches, switch reads after verification, and remove the old column only after every running and rollback version no longer depends on it. Index creation, constraints, and data conversion receive the same compatibility treatment. The temporary complexity is deliberate: it keeps mixed versions functional and preserves a recovery path while the data transition is still in progress.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
I treat schema evolution as a multi-release workflow with explicit compatibility windows. Generated SQL is reviewed against realistic table size and data distribution, and lock duration, transaction-log growth, replica lag, index build behavior, and backfill load are tested before production. Migration execution has one owner and is not raced by every application instance. Backfills checkpoint progress, throttle against database health, and verify counts and invariants before cutover. The release plan states which stages can roll back and where recovery requires a forward fix or compensating script. Dashboards and runbooks cover migration state, application errors, blocking, latency, CPU, and data mismatch through final cleanup.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Renaming or dropping columns in the same release that needs them.
Auto-running risky migrations at app startup.
Not reviewing generated SQL.
No backfill or rollback plan.

Red flagsCandidateSigns the approach is fragileSignals that an interviewer may treat as risky.Open details

Details

Only knows migration commands.
Does not consider rolling deployment.
Ignores table size and locks.
Cannot explain expand-and-contract.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

What is expand-and-contract?
When is startup migration risky?
How do you backfill large tables?
What would you monitor during migration?

Continue the section

Next in CI/CD, Git & Release Engineering Essentials: Progressive Deployment

Step 13 of 15

Choose rolling, blue-green, or canary deployment

How would you deploy a .NET API change that requires a database migration without downtime?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

How would you deploy a .NET API change that requires a database migration without downtime?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section