AZ-400 Question 127
Single answerYour development team stores all microservices code in GitHub and wants to automate continuous deployment for each service with minimal operational overhead. They also need integrated secret management on a fully hosted build platform. Which deployment automation solution best meets these requirements?
- A
Use Jenkins Pipelines on self-hosted servers for complete customizability
- B
Use GitHub Actions with GitHub-hosted runners to manage pipelines and secrets natively
- C
Implement Azure Pipelines in Azure DevOps with a Microsoft-hosted agent
- D
Adopt a third-party CI/CD tool (e.g., TeamCity) running in Azure virtual machines
Show answer and explanation
Correct answer: B
Explanation
GitHub Actions is designed for seamless integration with GitHub repositories, offering hosted runners and built-in secret management functionality. Microsoft documentation (https://docs.github.com/en/actions) recommends GitHub Actions when you need a straightforward, tightly coupled CI/CD pipeline for projects stored in GitHub without additional overhead. Azure Pipelines is another robust option, particularly when integrated with broader Azure DevOps capabilities, but for minimal overhead within GitHub, GitHub Actions is often the more streamlined solution.
- A. Incorrect.
Option 1 (Use Jenkins Pipelines...) is incorrect because it requires managing your own Jenkins infrastructure. This increases operational overhead for installation, maintenance, and scaling, which does not match the requirement of minimal overhead.
- B. Correct.
Option 2 (Use GitHub Actions...) is correct. GitHub Actions natively integrates with code repositories in GitHub, supports fully hosted runners, and provides integrated secret storage (via GitHub Secrets). This matches all requirements of minimal overhead, no separate infrastructure, and automated deployments.
- C. Incorrect.
Option 3 (Implement Azure Pipelines...) is a valid choice for many scenarios. However, it requires setting up an Azure DevOps organization and connecting GitHub repositories, which adds complexity compared to a fully GitHub-based solution. It can be used if broader Azure DevOps features are needed, but it is not the most direct fit for the stated minimal overhead requirement.
- D. Incorrect.
Option 4 (Adopt a third-party CI/CD tool...) also involves managing additional tooling and infrastructure. Although it might offer flexibility, it does not meet the requirement for a directly integrated, minimal-overhead solution.