AZ-400 Question 50
Select 2Your team is building a new application in Azure DevOps. They want to automate the generation of release notes from commit messages in Git to keep documentation updated in the Azure DevOps Wiki. The release notes must be automatically added to the Wiki whenever changes are merged into the main branch. Which two tasks are needed in your pipeline configuration to automatically populate your Wiki with newly generated Markdown release notes? (Choose two.)
- A
A task that parses Git commit messages and generates a Markdown file containing the release notes
- B
A task that updates the project's main README.md file directly in the repository
- C
A build artifact publish step that stores the generated Markdown file for later use in a separate pipeline
- D
A specialized script or extension that updates the Azure DevOps Wiki with the newly generated Markdown file
- E
A code coverage task that transforms test results into Markdown and publishes them to the Wiki
Show answer and explanation
Correct answers: A, D
Explanation
To automate documentation creation from Git history, you typically use a script or extension to parse commit messages and generate a structured Markdown file, then another step to push this file to the Wiki using the Azure DevOps REST API or a marketplace extension. Microsoft� best practices recommend a dedicated pipeline or pipeline stage for documentation tasks, ensuring changes are automatically reflected as soon as new commits are integrated.
- A. Correct.
Correct. You need a process to extract relevant commit messages from Git and format them into a Markdown file. This ensures the release notes are clearly documented.
- B. Incorrect.
Incorrect. Simply editing the README.md in the repository does not constitute an automated approach for updating the Wiki and could cause confusion between the main project documentation and continuous release notes.
- C. Incorrect.
Incorrect. While publishing artifacts is a valid practice, it does not directly update the Wiki with newly generated release notes. Artifacts are typically stored for reusability or deployment, but do not accomplish the required automation on their own.
- D. Correct.
Correct. After generating the Markdown file, you need a mechanism�often in the form of a script or extension�to push those notes to the Wiki so that documentation remains current.
- E. Incorrect.
Incorrect. Although code coverage reports are useful, they do not address generating and publishing release notes from commit messages. The task focuses on test result data rather than documentation based on commit history.