Reviewing an ARM Template from the Virtual Machine Blade
Short answer
B The Virtual Machine blade cannot show Jon Ross's ARM template; open the resource group's Deployments history to review the original template.
Question
the solution satisfies the requirements.
Your company has an azure subscription that includes a storage account, a resource group, a blob container and a file share.
A colleague named Jon Ross makes use of a solitary Azure Resource Manager (ARM) template to deploy a virtual machine and an additional Azure Storage
account.
You want to review the ARM template that was used by Jon Ross.
Solution: You access the Virtual Machine blade.
Does the solution meet the goal?
Key Takeaways
The question tests where deployment-time ARM templates are stored, and the trap is confusing a template review with exporting the current-state configuration of a single resource.
This AZ-104 scenario asks whether opening the Virtual Machine blade lets you review the ARM template Jon Ross used to deploy a VM plus a second storage account. The page establishes that it does not: the correct path is the resource group's Deployments history, where the original template, parameters, and outputs are retained.
Common mistake: Choosing A (Yes) — learners assume the VM blade or its Export template option reveals the original ARM template, but that export generates a new snapshot of the VM's present state and omits the storage account entirely.
Expert Analysis
Why the Answer Is Correct
Accessing the Virtual Machine blade cannot satisfy the goal, so the answer is B (No). The blade surfaces the VM's own properties, monitoring, disks, and networking, and its "Export template" function only regenerates a new template reflecting the VM's current configuration. Jon's goal was to review a single ARM template that deployed both the VM and an additional storage account, and that deployment record lives at the resource group (or subscription/management group) level under Deployments. As kjbalamurugan outlined, you open the Resource Group, select Deployments, pick the specific timestamped deployment, and then view the template, parameters, and outputs used.Why the Other Options Are Wrong
Option A would only hold if the VM blade exposed the original deployment artifact, which it does not; the exported template is a snapshot of current state, not the artifact Jon submitted. khengoolman emphasized this distinction, noting you want the template Jon used rather than an export that "will not include the template for the storage, for example." Diedo reinforced the same gap: "But there are 2 different resources here. The Storage Account resource would be missing." Any configuration drift since deployment would further make the VM-only export unfaithful to Jon's original template.Community Comment Notes
The comments converge firmly on B, with d0bermannn summarizing it as "it is so easy =B. No ))" and later pointing to the "rg blade, as for one hundred q ago." arkause noted that "You can view deployments history on - single resource level - resource group level - subscription level - management group level," confirming the proper location. thesagarlee usefully separated the two export modes, explaining that "Save from history: This option retrieves an exact copy of a template used fo..." deployment, which is exactly what this scenario requires.Official Reference
https://learn.microsoft.com/en-us/azure/azure-resource-manager/templates/view-template
This link opens the official vendor documentation in a new tab.
Exam Strategy
On these paired "Does the solution meet the goal?" items, always check whether the named blade captures the whole deployment scope: a single-resource blade never shows a multi-resource ARM template. For template review questions, default to the resource group's Deployments history rather than any Export template button.
Frequently Asked Questions
Why doesn't Export template on the VM blade show Jon's original ARM template?
Where can I find the actual template Jon Ross used for the deployment?
Discussion 47 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 30 of 47
-
Madbo 👍 40No, accessing the Virtual Machine blade does not provide access to the ARM template used by Jon Ross to deploy the virtual machine and an additional Azure Storage account. The Virtual Machine blade only displays information about the virtual machine itself and its related resources, but not the ARM template used to deploy it. To review the ARM template used by Jon Ross, you need to access the deployment history of the resource group where the virtual machine and additional storage account were deployed. This will show all deployments made to the resource group, including the ARM template used for the deployment.
-
khengoolman 👍 13Because you want to review the template that Jon used, not export the current configuration of the VM, which will not include the template for the storage, for example, additionally, the VM may have been changed, we don't know.
-
d0bermannn 👍 10it is so easy =B. No ))
-
arkadius 👍 7 Answered BYou can view deployments history on - single resource level - resource group level - subscription level - management group level
-
thesagarlee 👍 6here are two ways to export a template: Export from resource group or resource: This option generates a new template from existing resources. The exported template is a "snapshot" of the current state of the resource group. You can export an entire resource group or specific resources within that resource group. Save from history: This option retrieves an exact copy of a template used for deployment. You specify the deployment from the deployment history.
Show 25 more comments
-
NaoVaz 👍 5 Answered BTo get a ARM template from deployed resources, one must go to the Resource Group Page and see\export the previously done deployments:
-
jacksparrowtabali 👍 5All templates in a RG are stored in Deployments within the the resource group level
-
Diedo 👍 4But there are 2 different resources here. The Storage Account resource would be missing.
-
d0bermannn 👍 4rg blade, as for one hundred q ago
-
kjbalamurugan 👍 3 Answered BTo view the ARM template used by Jon Ross, you should: Navigate to the Resource Group where the VM and storage account were deployed. Select "Deployments" from the left menu. Choose the specific deployment (usually listed by timestamp). From there, you can view the ARM template, parameters, and outputs used in that deployment.
-
je_it 👍 3B. To review the ARM template, you need to access the deployment history of the resource group where the virtual machine and additional storage account were deployed. You can access the deployment history by navigating to the “Deployments” blade of the resource group in the Azure portal.
-
dnt91 👍 3 Answered Ayou can access the template through the VM blade. Go to Automation > Export Template. Azure will generate a template representing the current VM Configuration.
-
petersoliman 👍 3 Answered BB is the Answer You review the ARM template from the Azure Resource Group Deployment, Deployments Tab.
-
edengoforit 👍 3Answer is No: go to Resource Group Pane -> Deployment -> Check whatever required -> View Template
-
UmbongoDrink 👍 3 Answered BYou should use the Resource Group blade
-
Shonennn 👍 2 Answered BThe Virtual Machine blade only displays information about the virtual machine itself and its related resources
-
TokpaCamara 👍 2Answer B. You should use Ressource Group blade to export one to all resources inside the resource group.
-
Snownoodles 👍 2There is also an "export template" link on VM blade, why cannot we use it? So the answer should be "Yes"
-
berich11 👍 2 Answered BNO! Accessing the VM blade does not provide access to the ARM template.
-
fiahbone 👍 2 Answered BNot shown here. Need to go to recourse group and the Deployments tab.
-
xell_ 👍 2Why are the words used in the questions on here so awkward?
-
Ashfaque_9x 👍 2 Answered BYou should go to Resource Group and then Deployments.
-
Saaaii666 👍 2Export template shows only VM related ARM JSON.
-
AK4U_111 👍 2Resource Groups > RG > Deployments > JSON
-
Prano 👍 2Ans : B RG blade
-
abdelilahfa 👍 1 Answered BTracked deployments: In the Azure portal, you can review the deployment history and get information about the template deployment. You can see the template that was deployed, the parameter values passed in, and any output values. Other infrastructure as code services aren't tracked through the portal. Tracked deployments: In the Azure portal, you can review the deployment history and get information about the template deployment. You can see the template that was deployed, the parameter values passed in, and any output values. Other infrastructure as code services aren't tracked through the portal.
-
Miguel Angel 👍 1 Answered BEsto no cumple el objetivo. Desde el blade de una máquina virtual puedes ver la configuración de la VM, pero no la plantilla ARM completa utilizada para desplegar todos los recursos (la VM y la cuenta de almacenamiento adicional). Para revisar la plantilla ARM utilizada en un despliegue, normalmente debes acceder a: Resource Group → Deployments (Implementaciones). Seleccionar la implementación correspondiente. Ver Template (Plantilla). Ahí se encuentra la plantilla ARM asociada al despliegue completo.
-
tyleractivate 👍 1 Answered BTo export one or more resources from a resource group: 1. Select the resource group that contains the resources you want to export. 2. Select one or more resources by selecting the checkboxes. To select all, select the checkbox on the left of Name. The Export template menu item only becomes enabled after you've selected at least one resource. 3. Select Export template.
-
dmchandrasinghe 👍 1 Answered BThe VM blade is just a "view" of the current VM state. It doesn't show you how it was deployed (the template code). ARM templates are stored in the Resource Group's deployment history, not in individual resource blades
-
victorio_27 👍 1 Answered Bes la B ya que cuando tu creas un ARM template de una VM solo puedes crear dentro todo con respecto a la VM mas no con le storgae account
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.
Related Analysis
Practice All AZ-104 Questions
Access 100 questions with complete answers and detailed explanations.
View Full AZ-104 Practice Test →