The answer is Bicep template files stored in source control. Bicep is the correct choice because it is a domain-specific language designed for Azure deployments that offers a cleaner, more readable syntax compared to ARM JSON templates, making code reviews straightforward and reducing the risk of syntax errors. This directly supports the requirement for readable infrastructure as code that can be versioned and deployed repeatedly every sprint via CI/CD pipelines. On the AZ-104 exam, this scenario tests your understanding of declarative IaC tools and their trade-offs; a common trap is choosing ARM templates because they are more familiar, but the question explicitly prioritizes readability and ease of review. Remember the memory tip: Bicep is like a friendly wrapper around ARM—if the question emphasizes human readability and clean syntax, Bicep is the answer.
AZ-104 Deploy and Manage Azure Compute Practice Question
This AZ-104 practice question tests your understanding of deploy and manage azure compute. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Source control folder:
- /infra/main.bicep
- /infra/parameters/prod.bicepparam
- /infra/modules/vm.bicep
Snippet:
resource vm 'Microsoft.Compute/virtualMachines@2023-09-01' = {
name: vmName
location: location
}
Goal: Reuse the same definition for every sprint release.
Based on the exhibit, the operations team wants to store the VM deployment definition in source control and deploy the same group of Azure VMs every sprint. The code should be readable and easy to review. What should they use?
Source control folder:
- /infra/main.bicep
- /infra/parameters/prod.bicepparam
- /infra/modules/vm.bicep
Snippet:
resource vm 'Microsoft.Compute/virtualMachines@2023-09-01' = {
name: vmName
location: location
}
Goal: Reuse the same definition for every sprint release.
A
Bicep template files stored in source control.
Bicep is a declarative infrastructure-as-code format that is concise, readable, and easy to review in pull requests. It is well suited to repeatable Azure deployments from source control and supports modular design for VM infrastructure. This matches the team’s requirement for a readable, versioned deployment definition.
B
Manual creation in the Azure portal.
Why wrong: Portal-based deployment is not code-based and is harder to review, repeat, and track across sprints.
C
A one-time Azure CLI command typed into Cloud Shell.
Why wrong: A one-time command may create resources, but it is not the same as a reusable, source-controlled deployment definition.
D
A resource lock on the subscription.
Why wrong: A resource lock helps protect existing resources, but it does not define or deploy the VM infrastructure.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Bicep template files stored in source control.
Bicep is a domain-specific language (DSL) for deploying Azure resources that provides a cleaner, more readable syntax compared to ARM JSON templates. Storing Bicep files in source control enables versioning, code review, and repeatable deployments via CI/CD pipelines, which aligns with the requirement to deploy the same VM group every sprint. The declarative nature of Bicep ensures the deployment definition is both human-readable and machine-executable.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Bicep template files stored in source control.
Why this is correct
Bicep is a declarative infrastructure-as-code format that is concise, readable, and easy to review in pull requests. It is well suited to repeatable Azure deployments from source control and supports modular design for VM infrastructure. This matches the team’s requirement for a readable, versioned deployment definition.
Related concept
Read the scenario before looking for a memorised answer.
✗
Manual creation in the Azure portal.
Why it's wrong here
Portal-based deployment is not code-based and is harder to review, repeat, and track across sprints.
✗
A one-time Azure CLI command typed into Cloud Shell.
Why it's wrong here
A one-time command may create resources, but it is not the same as a reusable, source-controlled deployment definition.
✗
A resource lock on the subscription.
Why it's wrong here
A resource lock helps protect existing resources, but it does not define or deploy the VM infrastructure.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse a deployment tool (like Bicep or ARM templates) with a management tool (like resource locks) or assume that a one-time CLI command is sufficient for repeatable deployments, overlooking the need for version-controlled, reviewable infrastructure-as-code.
Trap categories for this question
Command / output trap
A one-time command may create resources, but it is not the same as a reusable, source-controlled deployment definition.
Detailed technical explanation
How to think about this question
Bicep files are transpiled into ARM JSON templates before deployment, but they offer modularity via modules and support for loops, conditions, and parameter files, which simplifies complex VM deployments. Under the hood, Bicep uses the same Azure Resource Manager API as ARM templates, ensuring full compatibility. In a real-world scenario, teams often combine Bicep with Azure DevOps or GitHub Actions to automate deployments, where the Bicep file's readability accelerates code reviews and reduces errors in multi-environment rollouts.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-104 question in full detail.
Deploy and Manage Azure Compute — This question tests Deploy and Manage Azure Compute — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Bicep template files stored in source control. — Bicep is a domain-specific language (DSL) for deploying Azure resources that provides a cleaner, more readable syntax compared to ARM JSON templates. Storing Bicep files in source control enables versioning, code review, and repeatable deployments via CI/CD pipelines, which aligns with the requirement to deploy the same VM group every sprint. The declarative nature of Bicep ensures the deployment definition is both human-readable and machine-executable.
What should I do if I get this AZ-104 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Based on the exhibit, the team wants a readable, repeatable deployment definition stored in source control. Which approach should they use for the Azure resources?
easy
A.Azure Policy because it enforces the deployment automatically.
✓ B.Bicep because it provides a concise declarative syntax for Azure deployments.
C.A runbook in Azure Automation because it is always easier to read than templates.
D.A resource lock because it prevents unauthorized changes to the deployment.
Why B: Bicep is a domain-specific language (DSL) that provides a concise, declarative syntax for deploying Azure resources. It is designed to be more readable than ARM templates and can be stored in source control, enabling repeatable, version-controlled deployments. This directly meets the team's requirement for a readable, repeatable deployment definition.
Last reviewed: Jun 11, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.