AZ-400 Practice Question: Design and implement build and release pipelines
Your organization uses GitHub Actions and needs to enforce that all workflows pass required checks before a pull request can be merged. Which GitHub feature should you configure?
⚠ Common exam trap
Candidates often confuse workflow triggers (which control when automation runs) with branch protection rules (which enforce that automation results are satisfied before merging).
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Branch protection rules with required status checks
Branch protection rules with required status checks enforce that all configured GitHub Actions workflows must pass before a pull request can be merged. This ensures that any workflow defined in the repository (e.g., CI, linting, security scans) produces a successful check run, and the merge is blocked if any required check fails or is pending.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Workflow triggers
Why it's wrong here
Workflow triggers (push, pull_request, schedule, workflow_dispatch) determine when a GitHub Actions workflow is instantiated, but they do not gate mergeability. A trigger only starts a run; it cannot block or require anything on a pull request, so it is unrelated to enforcing CI pass conditions before a merge.
- ✓
Branch protection rules with required status checks
Why this is correct
Branch protection rules with required status checks enforce that a pull request cannot be merged until the specified GitHub Actions checks (reported as commit statuses, e.g., from a job's `check_run` or `status` context) succeed. The protected branch's `required_status_checks` context verifies the list of checks, and the merge is rejected if any required check is failing, pending, or absent — this is the correct GitHub-native mechanism for CI gating.
- ✗
Required reviewers
Why it's wrong here
Required reviewers require human approval from specified users or teams (or a specified number of reviewers) before a pull request can be merged. They are a branch protection setting focused on manual code review, not on automated build/test/quality checks, so they cannot enforce that a GitHub Actions workflow passes before merge (though they are often used alongside required status checks).
- ✗
Environment protection rules
Why it's wrong here
Environment protection rules are associated with GitHub Actions environments (e.g., `production`) and control when jobs referencing that environment can run, typically requiring manual approval for deployments. They do not apply to pull request merge requirements; they only protect the execution of deployment jobs, so they cannot enforce CI status checks for merging into a branch.
Go deeper
Related to this question
Learn chapter
Designing a Security and Compliance Plan
Key term
Pull request
A pull request is a way for a developer to propose changes to a codebase and ask other team members to review and merge them into the main project.
Key term
Repository
A repository is a central storage location where software packages, code, or configuration files are kept, managed, and distributed for use by IT systems.
About these practice questions
This AZ-400 question is part of Courseiva's 823-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-400 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-400 exam.