Question

Your team maintains Infrastructure as Code for Azure Machine Learning using Bicep. You must deploy identical workspace resources to three environments (dev, test, prod) that differ only in resource names, SKU tiers, and network settings. You want to avoid duplicating Bicep files and keep a single source of truth in your Git repository. Which approach best achieves consistent, environment-specific deployments?

Accepted Answer

Create one Bicep module for the workspace and supply environment-specific values through separate parameter files (e.g., dev.bicepparam, prod.bicepparam) referenced at deployment time.

Answer

Copy the Bicep template into three folders (dev, test, prod) and hardcode the differing values in each copy.

Answer

Use a single Bicep file with the resource values hardcoded for prod, then manually edit the file before each dev or test deployment.

Answer

Store all environment values as Azure CLI environment variables and inline them with string concatenation in one Bicep file without parameters.