AZ-400 Question 8
Select 2You are a DevOps Engineer at an organization that uses GitHub for version control and GitHub Actions for continuous integration. Developers have complained that they frequently miss critical build failures in pull requests and cannot easily track remediation work. You want to design a feedback mechanism that (1) sends immediate notifications when builds fail, and (2) automatically creates a new GitHub issue assigned to the correct developers when a failure occurs. Which two steps should you implement to meet these requirements?
- A
Add a step in your GitHub Actions workflow to invoke the GitHub Issues API upon build failure, assigning it to the responsible team members.
- B
Configure your repository� GitHub Actions settings to skip all notifications for failed builds in pull requests.
- C
Enable email notifications in your GitHub repository settings, and use a workflow that listens for a 'workflow_run' event with a 'failure' status to auto-create and assign a new issue.
- D
Install a third-party extension to automatically convert all build failures into Azure Boards work items, bypassing GitHub Issue creation.
Show answer and explanation
Correct answers: A, C
Explanation
To set up effective feedback loops, you can leverage GitHub Actions� ability to trigger events and call the GitHub REST API. By enabling email notifications (or other communication channels) and automatically creating a GitHub Issue upon build failure, development teams gain immediate visibility and an actionable way to track remediation. For more details, refer to GitHub� official documentation on GitHub Actions workflows and GitHub Issues APIs (https://docs.github.com/en/actions and https://docs.github.com/en/rest/issues).
- A. Correct.
Option 1 is correct. GitHub Actions supports calling the GitHub REST API from within a workflow. You can check if a build step has failed and then use the 'issues' endpoint to create and assign a new issue, ensuring immediate tracking of failures.
- B. Incorrect.
Option 2 is incorrect. This option disables notifications for failed builds, which contradicts the goal of creating an immediate feedback loop for developers.
- C. Correct.
Option 3 is correct. GitHub� built-in email notifications can be integrated with a custom workflow triggered on 'workflow_run' (failure) to automate issue creation and assignment, providing immediate visibility into problems.
- D. Incorrect.
Option 4 is incorrect. Bypassing GitHub Issues altogether does not match the requirement to track failures in GitHub Issues. Additionally, this approach delegates tracking responsibilities to Azure Boards, which was not part of the stated requirement.