AZ-400 Question 51
Select 2You are working on an Azure DevOps project that includes multiple services, each with its own repository. You want to automatically compile release notes from Git commit messages and publish them as documentation in your Azure DevOps Wiki. Which two actions should you take to achieve this using standard Azure DevOps capabilities?
- A
Install a release notes extension from the Azure DevOps Marketplace and configure a pipeline task to parse commit messages into Markdown-format release notes.
- B
Create a custom build step that increments the major version of your application on every commit to ensure versioning details are automatically captured in the documentation.
- C
Publish the generated Markdown content to the Azure DevOps Wiki by using a dedicated pipeline task to commit the files into the Wiki repository or Wiki folder path.
- D
Rely solely on the built-in commit history view in Azure DevOps to act as your complete automated documentation source.
Show answer and explanation
Correct answers: A, C
Explanation
To automate documentation creation from Git history, you typically set up an Azure DevOps Pipeline that runs after each commit or release. A release notes extension can parse the Git commit messages, format them as Markdown, and then publish them to your Wiki using a dedicated task. This approach aligns with Azure DevOps best practices for maintaining up-to-date, easily accessible documentation. For more details, refer to Microsoft documentation on configuring build pipelines and the Azure DevOps Marketplace for release notes extensions: https://docs.microsoft.com/azure/devops/pipelines/overview and https://marketplace.visualstudio.com/search?term=release%20notes&target=AzureDevOps.
- A. Correct.
Option 1: CORRECT. Installing a release notes extension (such as 'Generate Release Notes (Cross-Platform)' in the Azure DevOps Marketplace) and configuring a pipeline task to parse commit messages into Markdown is a common approach to automating the creation of documentation from Git history.
- B. Incorrect.
Option 2: INCORRECT. While incrementing the major version might be useful for version tracking, it does not inherently convert commit messages into documentation. This step alone does not fulfill the requirement of generating and publishing release notes.
- C. Correct.
Option 3: CORRECT. Once you have generated the content (e.g., Markdown files), publishing it to the Azure DevOps Wiki via a dedicated pipeline task is a valid approach. It ensures that the newly created or updated documentation is immediately available for the team in the Wiki.
- D. Incorrect.
Option 4: INCORRECT. The built-in commit history view is helpful for tracking changes but does not create curated documentation or release notes. It won�t provide release notes in Markdown form, nor will it provide a single, consolidated reference document in the Wiki.