AZ-400 Question 7
Select 2You are building a feedback cycle for a web application that uses GitHub for source control and Azure DevOps for continuous integration and deployment. You want your development team to be quickly informed whenever a critical production issue arises, and you also want all feedback to be tracked in a central location. Which two actions should you take to design an effective feedback loop?
- A
Configure a webhook from your monitoring system that automatically creates GitHub issues when production alerts are raised.
- B
Deploy a GitHub Action that listens for newly opened issues and sends real-time notifications to the development team.
- C
Ask developers to manually review production error logs each morning and create GitHub issues when they notice recurring patterns.
- D
Set up an automatic rule to close issues older than 24 hours if no comments are added by users or developers.
- E
Use GitHub Discussions as the primary mechanism to file bugs and urgent feedback from production.
Show answer and explanation
Correct answers: A, B
Explanation
To create a robust feedback pipeline, you should combine automated issue creation (e.g., via webhooks from your monitoring system) with real-time notifications (e.g., GitHub Actions that trigger Slack/Microsoft Teams messages). GitHub Issues is the recommended channel for tracking and triaging production issues. For more information, see GitHub documentation on webhooks (https://docs.github.com/en/developers/webhooks-and-events) and GitHub Actions (https://docs.github.com/en/actions).
- A. Correct.
Correct: Webhooks allow you to automatically create a GitHub issue when an alert is triggered in your monitoring system. This ensures that any new production incidents have a corresponding issue without requiring manual intervention.
- B. Correct.
Correct: A GitHub Action listening for newly opened issues can notify the development team via email, Slack, or Microsoft Teams. This approach ensures rapid visibility and a streamlined workflow.
- C. Incorrect.
Incorrect: Relying on manual reviews of logs can delay feedback and increase the chance of missing critical issues. Automated creation of issues is more reliable for real-time alerts.
- D. Incorrect.
Incorrect: Closing issues automatically after a short time (24 hours) can lead to unresolved or missed critical issues. While some auto-close policies exist, they typically allow more time and are based on inactivity, not strict timelines.
- E. Incorrect.
Incorrect: GitHub Discussions is designed for broader conversations and community engagement. For production incidents and direct bug tracking, GitHub Issues provide better tooling, workflows, and integrations with CI/CD pipelines.