CV0-004 Deployment Practice Question

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 automatically manages state

  Why it's wrong here

  Bicep is stateless: it transpiles to ARM JSON, and deployment state remains in Azure Resource Manager, not in Bicep itself. State management belongs to tools such as Terraform, whose state file tracks deployed resources and would be the right answer where drift tracking across providers is required.

• ✓

  Bicep reduces code verbosity and supports modules

  Why this is correct

  Bicep's declarative syntax removes much of ARM JSON's boilerplate, such as repeated parameters and nested resource declarations, and supports modules for reusable, composable deployments. This directly satisfies the stem's requirement for a benefit over ARM JSON templates.

• ✗

  Bicep is natively executed by Azure Resource Manager

  Why it's wrong here

  Azure Resource Manager executes the ARM JSON that Bicep transpiles into, not Bicep directly; the CLI performs the transpilation first. Native ARM execution is the property of ARM JSON templates themselves, which would be the answer if direct deployment without a build step were required.

• ✗

  Bicep supports imperative scripting

  Why it's wrong here

  Bicep is declarative, describing the desired end state that ARM reconciles; it has no imperative scripting constructs. Imperative scripting suits procedural tasks such as Azure CLI or PowerShell runbooks, where ordered commands execute sequentially rather than declaring resource definitions.