Your team writes infrastructure in Bicep. A reviewer asks what Azure Resource Manager actually receives and processes when you deploy a Bicep file. What is the accurate description?
- ADuring deployment the Bicep CLI converts the Bicep file into a Resource Manager JSON template. Correct
- BResource Manager runs the Bicep file directly as a native runtime language without conversion.
- CThe Bicep file is uploaded to a state store and Azure compares it against a managed state file.
- DBicep is interpreted in the browser and only outputs are sent to Resource Manager.
Why A is correct: Correct. The docs state Bicep is a transparent abstraction over a Resource Manager JSON template, and during deployment the Bicep CLI converts a Bicep file into a Resource Manager JSON template.
Why B is wrong: Bicep is a transparent abstraction over JSON; the CLI converts it to a JSON template during deployment rather than running it natively.
Why C is wrong: Bicep has no state files to manage; Azure stores all state and the file is transpiled to JSON, not diffed against a state file by the CLI.
Why D is wrong: The Bicep CLI converts the whole file into a JSON template that Resource Manager processes, not just outputs from a browser.