AZ-305 Question 195
Single answerYou are designing an automated deployment solution for a microservices-based application running in Azure. The application code is stored in a GitHub repository, and you need to implement continuous integration and continuous delivery (CI/CD) so that new code changes trigger automated builds, tests, and deployments to both staging and production environments. The infrastructure should also be defined as code to ensure consistent provisioning across environments. Which approach should you recommend to meet these requirements in a streamlined and efficient manner?
- A
Build and deploy the application manually from Visual Studio, with no infrastructure as code.
- B
Use Azure DevOps Pipelines and ARM templates for both CI/CD and automated environment provisioning.
- C
Use GitHub Actions and Bicep templates to manage CI/CD and automated infrastructure deployments.
- D
Employ an on-premises Jenkins server that triggers manual deployments to Azure VMs.
Show answer and explanation
Correct answer: C
Explanation
GitHub Actions provides a native integration with GitHub, allowing you to automate the entire software development lifecycle using workflows. By pairing GitHub Actions with Bicep templates, you can both build and deploy the application while automatically provisioning or updating Azure resources. This meets the requirements for a seamless CI/CD process and infrastructure as code. For more information, see Microsoft's documentation on GitHub Actions for Azure (https://docs.github.com/actions/automating-your-workflow-with-github-actions) and Bicep (https://docs.microsoft.com/azure/azure-resource-manager/bicep).
- A. Incorrect.
Option 1 is incorrect because manual deployment and no infrastructure as code do not meet the requirement for automated, consistent deployments across multiple environments.
- B. Incorrect.
Option 2 could be viable in many cases, but it is not the most streamlined if you already have code in GitHub. While it does support infrastructure as code and CI/CD, you would need to integrate Azure DevOps with GitHub as an external repository and potentially manage multiple connections.
- C. Correct.
Option 3 is correct. GitHub Actions integrates directly with your GitHub repository, enabling automated builds, tests, and deployments. Bicep templates ensure that infrastructure is provisioned consistently as part of the pipeline, fulfilling both the CI/CD and infrastructure-as-code requirements.
- D. Incorrect.
Option 4 is incorrect because using an on-premises Jenkins server introduces extra complexity with additional maintenance overhead. Also, this approach lacks integrated infrastructure-as-code tooling out of the box for Azure.