AZ-900 Practice Question 67: Template Specs Versioning
Microsoft Azure Fundamentals (AZ-900) · Test 7 · question 7 of 10
A platform team has ARM templates that many application teams across the company should be able to deploy, without those teams being able to edit the templates themselves. The platform team also wants to publish incremental versions of the templates over time and control who may deploy which version using Azure RBAC. Which capability fits these requirements?
Show answer and explanation
Answer:
A template spec is "a resource type for storing an ARM template... for later deployment," built specifically to "share ARM templates with other users in your organization." Access is controlled with Azure RBAC, and "users only need read access to the template spec to deploy its template," so application teams can deploy without being able to modify it. Template specs also support versioning, with each version addressable by its own resource ID, so the platform team can publish updates without disturbing teams still deploying an older version.
Option A is wrong because policy initiatives group compliance rules for assignment, not deployable infrastructure templates; an initiative can't be "deployed" the way a template is. Option B named a real, adjacent service, but Microsoft is retiring Azure Blueprints (phased retirement began July 2026, full retirement January 2027) in favor of template specs plus Azure Deployment Stacks, so it isn't the current, forward-compatible answer. Option C is wrong because sharing templates through a storage account means either making them public or managing access with SAS tokens, the fragile, hard-to-govern pattern template specs were built to replace.
Reference: Create and deploy template specs