AZ-305 Question 193
Single answerA financial services company wants to implement a fully automated deployment process for its container-based web applications running on Azure Kubernetes Service (AKS). Each code commit should trigger a build and deployment pipeline, with environment-specific settings securely managed and the ability to roll back quickly if needed. The company operates under strict compliance requirements, so end-to-end traceability of changes and deployments is critical. Which solution should you recommend to meet these requirements?
- A
Use Azure DevOps with Azure Repos for source control, Azure Pipelines for CI/CD, securely store configuration in Azure Key Vault, and deploy to AKS using manifest files in the pipeline
- B
Use GitHub for code hosting, manually build container images on local developer machines, and deploy to AKS using kubectl commands from each environment
- C
Implement a simple FTP-based approach to upload container images and application configuration files to Azure Container Registry, then apply manual deployment scripts on AKS
- D
Use Azure App Service Web Apps for Containers with manual swaps between staging and production slots while storing environment variables in app settings
Show answer and explanation
Correct answer: A
Explanation
Azure DevOps with Azure Pipelines and Key Vault integration is a common best-practice approach for securely automating container deployments to AKS, providing traceability and consistency across environments. For more information, see Microsoft’s documentation on setting up CI/CD to AKS using Azure Pipelines: https://docs.microsoft.com/azure/devops/pipelines/targets/kubernetes.
- A. Correct.
Correct: Azure DevOps provides a fully automated CI/CD pipeline with Azure Pipelines, includes source control with Azure Repos, and allows integrating Key Vault for secure parameter management. It also offers detailed logging and traceability features that help meet strict compliance needs.
- B. Incorrect.
Incorrect: Although GitHub can host code, relying on manual image builds and deployments leads to inconsistent outcomes and lacks the full automation and traceability features required in a regulated environment.
- C. Incorrect.
Incorrect: An FTP-based approach plus manual scripts is prone to errors, lacks end-to-end traceability, and does not provide a robust automated pipeline for continuous deployment.
- D. Incorrect.
Incorrect: Azure App Service Web Apps for Containers supports deployment slots but does not natively address an AKS-based microservices deployment model, nor does it fully meet the end-to-end compliance and traceability requirements without additional tooling.