Free Microsoft GH-900 Actual Exam Questions - Question 14 Discussion

D, deploying from feature branches stops broken code hitting main early.

C/D? I’m guessing it’s not C since we definitely want testing before merging. D fits because deploying from feature branch means real checks happen before merging, preventing problems later.

It’s D because deploying from feature branches helps catch issues early before main branch contamination.

D, because it prevents unstable code from entering the main branch too soon.

It’s D. Deploying from the feature branch first is basically a safeguard to catch any bugs or issues in a real environment before those changes hit the main branch. It keeps the main branch clean and avoids last-minute surprises that could mess up the entire project. Options A and C are clearly wrong since skipping testing or deploying directly from main makes no sense. B doesn’t really fit either because deploying early isn’t about speeding up merging, it’s about making sure what you merge is solid.

D, because it’s about testing in a real setup before merging, not skipping tests.

D. It’s about making sure your changes actually work in a real environment—whether that’s staging or production—before mixing them into the main branch. This way, you catch issues early and keep the main branch stable. Options A and C don’t make sense since skipping testing or deploying directly from main can cause bigger problems. B doesn’t fit either because deploying from the feature branch isn’t about speeding up merges but about safety and validation.

Maybe D. Deploying from the feature branch first lets you catch problems early and keeps main stable, so you don’t break anything when you merge later.

It’s D, since you want to catch any issues in a controlled way before affecting main.

D. Testing on the feature branch before merging helps catch any bugs or issues early on. It’s safer because you’re not risking the stability of the main branch. Deploying straight from main without this step could cause unexpected problems for everyone relying on that branch.

D makes the most sense—deploying from the feature branch lets you test changes in a real environment before merging to main.