Question 531 of 823
AZ-400 Configure processes and communications Practice Question
Your team uses GitHub Issues to track work. You want to enforce that all new issues include a specific set of labels based on the issue type (bug, feature, task). What is the most efficient way to achieve this?
⚠ Common exam trap
Candidates often confuse branch protection rules or repository rulesets (which manage code changes) with issue management features, or mistakenly think CODEOWNERS can assign labels instead of reviewers.
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
✓
Create YAML-based issue forms in the .github/ISSUE_TEMPLATE folder.
GitHub issue forms, defined as YAML files in the .github/ISSUE_TEMPLATE folder, allow you to create structured templates that can enforce required fields, including mandatory label assignments. When a user submits an issue via a form, the labels specified in the template are automatically applied, ensuring consistency without manual intervention or additional automation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Configure branch protection rules to require label assignments.
Why it's wrong here
Branch protection rules govern pull request merges and branch policies (e.g., required reviewers, status checks, or linear history); they have no mechanism to enforce or require label assignments on GitHub Issues, so this option is incorrect.
- ✗
Use a CODEOWNERS file to auto-assign labels.
Why it's wrong here
A CODEOWNERS file defines which individuals or teams are automatically requested for code review based on file paths in pull requests; it does not assign or manage labels on issues, and therefore cannot enforce label usage at issue creation.
- ✓
Create YAML-based issue forms in the .github/ISSUE_TEMPLATE folder.
Why this is correct
YAML-based issue forms in the `.github/ISSUE_TEMPLATE` folder allow you to define structured issue templates with fields and a `labels:` key that automatically applies specified labels when the form is submitted, enforcing consistent label assignment at issue creation.
- ✗
Set up a repository ruleset to restrict label modifications.
Why it's wrong here
Repository rulesets enforce policies on branches and tags—such as required pull request reviews, status checks, or signing—but they do not provide settings to restrict or enforce label modifications on issues, so this cannot ensure labels are assigned.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 25, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.