Question

Your team manages an Azure AI Foundry project using infrastructure-as-code. You author a Bicep template that provisions the Foundry resource, a project, and a model deployment. During CI/CD you must be able to re-run the same deployment repeatedly (for example after adding a new model deployment) without recreating existing resources or causing errors, and the deployment name for each model must be supplied at build time per environment. Which approach best meets these requirements?

Accepted Answer

Deploy the Bicep template with 'az deployment group create' in Incremental mode and pass the model deployment name as a template parameter.

Answer

Deploy the Bicep template with 'az deployment group create' using Complete mode so any drift is corrected on each run.

Answer

Hardcode the model deployment name in the Bicep resource and run 'az deployment group create --confirm-with-what-if' each time.

Answer

Convert the Bicep file to an ARM template and deploy it with 'az group create' passing environment values as tags.