AZ-305 ยท Application architecture design
Automated deployment: IaC, stacks, pipelines and slots
Infrastructure as code with Bicep, ARM templates and Terraform, deployment stacks, CI/CD with GitHub Actions or Azure Pipelines, deployment slots and blue-green releases.
Key points
- ARM templates: JSON; Bicep: concise, transpiles to ARM JSON, no state file; Terraform: HCL, multicloud, state file.
- Deployment stacks: resources as one unit (resource group, subscription, management group).
- actionOnUnmanage: detachAll, deleteResources, deleteAll; deny settings: none, denyDelete, denyWriteAndDelete.
- CI/CD: GitHub Actions or Azure Pipelines; deployment slots: staging, warm-up, swap, swap back to roll back.
Source: https://learn.microsoft.com/en-us/azure/azure-resource-manager/bicep/deployment-stacks
Practice questions
What happens to a Bicep file when Azure deploys it?
- It is transpiled into an ARM JSON template
- It is converted into a Terraform HCL file
- It is compiled into an Azure PowerShell script
- It is stored as a state file in a storage account
Show answer
Answer: A. It is transpiled into an ARM JSON template
Bicep is transpiled into an ARM JSON template, which Azure Resource Manager then deploys. Bicep does not keep a state file (that is Terraform), and it is not converted to PowerShell or HCL.
Which benefits do App Service deployment slots give a release process?
- Validate a new version in staging while production runs
- Swap the warmed-up staging slot into production
- Roll back quickly by swapping the slots again
- Deploy the app to a second Azure region automatically
- Remove the need to define infrastructure as code
Show answer
Answer: A. Validate a new version in staging while production runs, B. Swap the warmed-up staging slot into production, C. Roll back quickly by swapping the slots again
You deploy to a staging slot and validate it while production keeps serving, the swap warms the new version up before it takes traffic, and swapping back is a fast rollback. Slots do not replace infrastructure as code, and they share the App Service plan rather than adding a separate region.
Deny settings on a deployment stack also stop data-plane changes, such as adding a secret to a managed key vault or uploading a blob to a managed storage account.
Show answer
Answer: False
False. Deny settings apply only to control-plane operations on the resources the stack explicitly manages. Data-plane items like secrets or blob containers are outside the stack, and implicitly created resources are not covered either.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
