Question 450
An infrastructure team must deploy the same four-VM application topology into dev, test and production subscriptions. VM names must incorporate the environment; all VMs need standardized `CostCenter` and `Owner` tags, with only subnet IDs and size differing by environment. Reviewers require a reproducible declared configuration. Which approach best meets the requirement?
Explanation
Correct Answer
Bicep defines resource type, name and tags declaratively while separate parameter inputs vary subnet and size by deployment environment. This creates reviewable, repeatable topology rather than relying on hand-built VMs.
Incorrect Answers
Manual portal creation and post-hoc tagging produces mutable configuration with avoidable drift and does not deliver the requested declarative topology across subscriptions.
Compute Gallery distributes image versions; it does not express each environment’s VM resource names, Azure resource tags, NIC attachments or infrastructure deployment parameters.
Reader cannot create VMs, and one display name cannot model distinct per-environment resource instances or their required tags and network attachments.