AZ-400 Design and implement source control Practice Question
An organization has multiple Git repositories. Developers often forget to update the repository README file after making changes. What is the most effective way to ensure the README is always up-to-date?
⚠ Common exam trap
Candidates often choose repository templates because they enforce structure, but they miss that templates only apply at creation time. The real challenge is keeping the README current with ongoing changes, which requires automated enforcement in the CI/CD pipeline.
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
✓
Add a task in the CI pipeline that checks if the README was modified
Adding a task in the CI pipeline that checks whether the README was modified directly enforces that developers include README updates in the same pull request that contains code changes. This ensures the README stays current with the codebase. In Azure Repos, CI pipelines can easily validate file changes using scripts or tasks. Option C (repository template) only ensures a README exists for new repositories but does not enforce updates after initial creation, so it does not address the core issue of keeping the README up-to-date over time.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Apply a label to PRs that touch certain files and require review
Why it's wrong here
Applying labels to PRs does not enforce README updates; it only adds a visual indicator and requires manual review, which can be overlooked.
- ✓
Add a task in the CI pipeline that checks if the README was modified
Why this is correct
Adding a CI pipeline task that checks if the README was modified automatically verifies that any code changes are accompanied by a corresponding README update, ensuring the README remains accurate.
- ✗
Use a repository template with a mandatory README file structure
Why it's wrong here
Using a repository template ensures a README exists at repository creation, but it does not guarantee updates after subsequent changes, so it fails to address the ongoing maintenance issue.
- ✗
Require a pull request comment that confirms README update
Why it's wrong here
Requiring a PR comment is a manual process that depends on developer honesty and can be easily forgotten or bypassed.
Go deeper
Related to this question
Learn chapter
Introduction to DevOps and Azure DevOps
Key term
Git
Git is a version control system that tracks changes to files so multiple people can work on the same project without overwriting each other's work.
Key term
Pipeline
A pipeline is an automated series of steps that takes code from development to production, ensuring quality and speed.
About these practice questions
Courseiva writes every AZ-400 question from scratch — 823 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.