Free Microsoft GH-200 Actual Exam Questions - Question 9 Discussion

Good point, but A limits code changes, not necessarily workflow steps, so C feels closer here.

C imo, since required reviewers for environments explicitly trigger approval before deployment steps, which fits "workflow approval" better than general permissions.

Option A could work since branch protection rules can block progress until certain users approve changes, so it's another way to enforce user approval before continuing.

B, since granting workflow approval permissions directly controls the workflow steps.

A/D? Branch protection (A) mostly controls code merges, so maybe not for workflow approval. D sounds broader than B and might cover workflow permissions under the repo umbrella.

D imo, repository approval permissions seem broader and could cover workflows too, making sure only authorized users can greenlight the next steps regardless of environment specifics.

B, granting users workflow approval permissions directly handles the approval step.

Makes sense that C would work if the workflow involves deployment to an environment since you can gate progress with required reviewers. But if the workflow isn’t environment-specific, B could also be valid because granting workflow approval permissions lets users directly approve runs before continuing. I’d go with C if the context fits environment deployments; otherwise, B might be the safer pick.

Maybe C, adding users as required reviewers for an environment sounds like the approval step before moving on.