AZ-400 Question 46
Select 2You are configuring a release pipeline in Azure DevOps for a team that wants to automatically attach release notes and updated API documentation with each deployment. The application exposes an OpenAPI specification for its .NET backend, and the team wants to ensure that every release publishes the latest API docs and consolidated release notes derived from recent commits. Which two actions should you include in the release pipeline to fulfill these requirements? (Choose two.)
- A
Add a manual approval gate to the release pipeline and attach a text file containing release notes for reference.
- B
Install a dedicated Marketplace task or use a custom script to extract commit information from the build artifact and generate release notes automatically.
- C
Set up a template repository variable group and manually update the release notes before each deployment.
- D
Incorporate a documentation generation step (e.g., using DocFX or a Swagger-based tool) to produce and publish updated API documentation.
Show answer and explanation
Correct answers: B, D
Explanation
To configure automated release documentation�both release notes and API documentation�in Azure DevOps, you can combine a Marketplace task or scripting approach that aggregates commit/change information into release notes (Option 2) with a pipeline step that builds and publishes API documentation (Option 4). This follows Microsoft DevOps best practices by providing consistent, automated reporting for both internal and external stakeholders. Refer to Microsoft Docs on Azure Pipelines for details on integrating custom tasks (https://learn.microsoft.com/azure/devops/pipelines/tasks) and generating documentation with tools such as DocFX (https://learn.microsoft.com/azure/devops/project/wiki/docfx-go).
- A. Incorrect.
Option 1: Incorrect. Manual approval gates can help moderate deployments, but attaching a text file alone does not provide an automated or standardized mechanism to generate or publish release notes.
- B. Correct.
Option 2: Correct. Using a specialized Marketplace extension or script to parse commit data (e.g., from Git) ensures release notes are automatically generated and attached to the release pipeline summary.
- C. Incorrect.
Option 3: Incorrect. Simply maintaining a variable group or manually updating the release notes before each deployment does not provide consistency or automation in generating release details.
- D. Correct.
Option 4: Correct. Tools like DocFX or Swagger codegen can be added as a release pipeline step to generate fresh API documentation from the OpenAPI spec, ensuring it is always up to date.