AZ-400 Question 286
Select 2You oversee a private GitHub repository for a microservices project. The leadership team has asked you to provide ongoing visibility into commit frequency, pull request merges, and open issues directly within GitHub. They also want to customize charts to observe historical trends without introducing significant complexity or external tooling. Which two approaches should you recommend to meet these requirements?
- A
Access the repository's Insights tab and utilize built-in charts such as Code frequency, Commit activity, and Contributors to view and filter metrics.
- B
Create a specialized GitHub Actions workflow that publishes metrics to the repository wiki, then manually embed custom chart visualizations there.
- C
Install a third-party GitHub App from the GitHub Marketplace that provides additional analytics functionality and customizable dashboards within GitHub.
- D
Edit a .github/insights-config.yml file to define fully custom chart types directly visible in GitHub� Insights section.
Show answer and explanation
Correct answers: A, C
Explanation
GitHub automatically provides an Insights tab with built-in charts (commit activity, code frequency, etc.) for both public and private repositories. This is usually the simplest way to monitor metrics with minimal configuration. If additional or more specialized analytics are needed, integrating a third-party GitHub App from the Marketplace is a common best practice. For more information on GitHub Insights, see GitHub� documentation at https://docs.github.com/en/repositories/insights.
- A. Correct.
Option 1 is correct. GitHub� Insights tab includes built-in charts and graphs (e.g., Code frequency, Commit activity) that can be filtered by date range or contributor. These charts are ready to use and require minimal configuration.
- B. Incorrect.
Option 2 is incorrect. While you can publish data to a wiki page via GitHub Actions, it requires creating and maintaining an entirely custom process to parse data and build charts. This does not leverage GitHub� native Insights or minimal-overhead approach.
- C. Correct.
Option 3 is correct. Third-party GitHub Apps from the Marketplace can enhance or extend analytics capabilities. Many of these apps offer prebuilt or customizable dashboards for repositories without extensive manual work.
- D. Incorrect.
Option 4 is incorrect. GitHub does not provide a .github/insights-config.yml mechanism for building fully custom charts within the Insights tab. This file does not exist in standard GitHub repository configurations.