VM states (running, stopped, deallocated) in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if the Azure VM is currently running.

Azure

if vm.instance_view.statuses[1].code == 'PowerState/[1]':
    print('VM is running')

Drag options to blanks, or click blank then click option'

Arunning

Bstopped

Cdeallocated

Dstarting

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'stopped' or 'deallocated' instead of 'running'.

The VM's power state code for a running VM is 'PowerState/running'.

2fill in blank

medium

Complete the code to stop an Azure VM using the Azure CLI command.

Azure

az vm [1] --name MyVM --resource-group MyResourceGroup

Drag options to blanks, or click blank then click option'

Astart

Bdeallocate

Crestart

Dstop

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'deallocate' instead of 'stop' when the goal is just to stop the VM.

The 'az vm stop' command stops the VM but does not release the compute resources.

3fill in blank

hard

Fix the error in the Azure CLI command to deallocate a VM.

Azure

az vm [1] --name MyVM --resource-group MyResourceGroup

Drag options to blanks, or click blank then click option'

Astop

Bshutdown

Cdeallocate

Dpoweroff

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'stop' which only powers off the VM but does not release resources.

The correct command to release compute resources and deallocate the VM is 'az vm deallocate'.

4fill in blank

hard

Fill both blanks to check if the VM is either stopped or deallocated.

Azure

if vm.instance_view.statuses[1].code == 'PowerState/[1]' or vm.instance_view.statuses[1].code == 'PowerState/[2]':
    print('VM is not running')

Drag options to blanks, or click blank then click option'

Astopped

Brunning

Cdeallocated

Dstarting

Attempts:

3 left

💡 Hint

Common Mistakes

Including 'running' or 'starting' as non-running states.

The VM states 'stopped' and 'deallocated' both mean the VM is not running.

5fill in blank

hard

Fill all three blanks to create a dictionary mapping VM states to their meanings.

Azure

vm_states = {
    '[1]': 'VM is powered on and running',
    '[2]': 'VM is powered off but resources allocated',
    '[3]': 'VM is powered off and resources released'
}

Drag options to blanks, or click blank then click option'

Arunning

Bstopped

Cdeallocated

Dstarting

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up 'stopped' and 'deallocated' meanings.

This dictionary clearly maps each VM state to its description.

Practice

1. What does the deallocated state mean for an Azure VM?

easy

A. The VM is off and resources are freed.

B. The VM is running and using resources.

C. The VM is off but still reserving resources.

D. The VM is paused but still running.

Solution

1. Step 1: Understand VM states

   Azure VMs can be running, stopped, or deallocated. Running means active, stopped means off but resources reserved, deallocated means off and resources freed.

2. Step 2: Identify deallocated meaning

   Deallocated means the VM is turned off and Azure releases the compute resources, so you don't pay for them.

3. Final Answer:

   The VM is off and resources are freed. -> Option A

4. Quick Check:

   Deallocated = off + freed resources [OK]

Hint: Deallocated means VM off and no resources reserved [OK]

Common Mistakes:

• Confusing stopped with deallocated
• Thinking deallocated still uses resources
• Assuming deallocated means paused

2. Which Azure CLI command correctly stops a VM and releases its resources?

easy

A. az vm pause --name MyVM --resource-group MyGroup

B. az vm stop --name MyVM --resource-group MyGroup

C. az vm shutdown --name MyVM --resource-group MyGroup

D. az vm deallocate --name MyVM --resource-group MyGroup

Solution

1. Step 1: Review Azure CLI commands for VM states

   To stop a VM but keep resources, use az vm stop. To stop and free resources, use az vm deallocate.

2. Step 2: Identify command that releases resources

   az vm deallocate stops the VM and releases compute resources, matching the question.

3. Final Answer:

   az vm deallocate --name MyVM --resource-group MyGroup -> Option D

4. Quick Check:

   Deallocate command frees resources [OK]

Hint: Use 'deallocate' to stop VM and free resources [OK]

Common Mistakes:

• Using 'stop' which keeps resources reserved
• Confusing 'shutdown' with deallocate
• Using non-existent 'pause' command

3. If an Azure VM is in the stopped state, what happens to billing for compute resources?

medium

A. Billing doubles due to stopped state overhead.

B. Billing stops immediately as VM is off.

C. Billing continues because resources are reserved.

D. Billing pauses but storage costs continue.

Solution

1. Step 1: Understand billing for stopped VMs

   When a VM is stopped (not deallocated), compute resources are still reserved, so billing continues for compute.

2. Step 2: Differentiate from deallocated state

   Only when VM is deallocated are compute resources freed and billing stops for compute.

3. Final Answer:

   Billing continues because resources are reserved. -> Option C

4. Quick Check:

   Stopped = billing continues [OK]

Hint: Stopped VMs still reserve resources and incur charges [OK]

Common Mistakes:

• Assuming billing stops when VM is stopped
• Confusing storage billing with compute billing
• Thinking stopped means deallocated

4. You tried to start a VM but got an error because it is in the deallocated state. What should you do to fix this?

medium

A. Run az vm start to allocate and start the VM.

B. Run az vm stop to release resources first.

C. Run az vm restart to reset the VM state.

D. Run az vm deallocate again to confirm.

Solution

1. Step 1: Understand VM start from deallocated

   A VM in deallocated state has no resources allocated. To use it, you must start it which allocates resources and powers it on.

2. Step 2: Identify correct command to allocate and start

   az vm start allocates resources and powers on the VM, fixing the error.

3. Final Answer:

   Run az vm start to allocate and start the VM. -> Option A

4. Quick Check:

   Start command allocates resources [OK]

Hint: Use 'start' to allocate and power on deallocated VM [OK]

Common Mistakes:

• Trying to stop or deallocate an already deallocated VM
• Using restart which requires VM to be running
• Not allocating resources before starting

5. You want to save costs by stopping your VM but keep its IP address and disk data intact. Which state should you use and why?

hard

A. Use running state but reduce VM size to save costs.

B. Use stopped state because it keeps resources reserved including IP and disks.

C. Use deallocated state because it frees all resources including IP address.

D. Use stopped state because it frees compute resources but keeps IP.

Solution

1. Step 1: Understand resource reservation in stopped state

   When a VM is stopped (not deallocated), compute resources are reserved, so the IP address and disk data remain intact.

2. Step 2: Compare with deallocated state

   Deallocated frees compute resources and may release dynamic IP addresses, so IP might change.

3. Final Answer:

   Use stopped state because it keeps resources reserved including IP and disks. -> Option B

4. Quick Check:

   Stopped = keep IP and disks reserved [OK]

Hint: Stopped keeps IP and disks; deallocated frees resources [OK]

Common Mistakes:

• Choosing deallocated and losing IP address
• Thinking stopped frees compute resources
• Trying to save costs by resizing while running