VM states (running, stopped, deallocated) in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding VM State Impact on Billing

You have an Azure VM that you stopped from the Azure portal. What is the billing state of this VM?

A You are billed only for storage but not compute because the VM is deallocated.

B You are not billed at all because the VM is stopped and deallocated automatically.

C You are still billed for the VM's compute resources because the VM is only stopped but not deallocated.

D You are billed for both compute and storage because the VM is running.

💡 Hint

Stopping a VM from the portal does not always release compute resources.

Stopping a VM from the Azure portal stops the OS but does not deallocate the VM. Compute resources are still reserved and billed. To stop billing compute, the VM must be deallocated.

🧠 Conceptual

intermediate

Difference Between Stopped and Deallocated States

Which statement correctly describes the difference between the 'Stopped' and 'Deallocated' states of an Azure VM?

A 'Stopped' means the VM is deleted; 'Deallocated' means the VM is paused.

B 'Stopped' means the VM is powered off but compute resources are still reserved; 'Deallocated' means compute resources are released.

C 'Stopped' means the VM is running but idle; 'Deallocated' means the VM is running with no network.

D 'Stopped' and 'Deallocated' are the same state with different names.

💡 Hint

Think about resource reservation and billing implications.

'Stopped' means the VM is powered off but compute resources remain allocated and billed. 'Deallocated' means the VM is fully shut down and compute resources are released, stopping billing for compute.

❓ Configuration

advanced

Automating VM Deallocation via Azure CLI

You want to write an Azure CLI command to stop and deallocate a VM named 'webserver1' in resource group 'prod-rg'. Which command correctly achieves this?

A az vm deallocate --resource-group prod-rg --name webserver1

B az vm shutdown --resource-group prod-rg --name webserver1

C az vm stop --resource-group prod-rg --name webserver1

D az vm power-off --resource-group prod-rg --name webserver1

💡 Hint

Stopping a VM does not deallocate it. Which command explicitly deallocates?

'az vm deallocate' stops the VM and releases compute resources, putting it in the deallocated state. 'az vm stop' only stops the VM but keeps compute allocated.

❓ Architecture

advanced

Designing Cost-Efficient VM Usage

You have a development VM that is used only during business hours (9am-5pm). To minimize costs, which VM state management strategy is best?

A Delete the VM at 5pm and recreate it at 9am to save costs.

B Stop the VM at 5pm and start it at 9am to avoid compute charges during off-hours.

C Leave the VM running but shut down the OS at 5pm to save costs.

D Deallocate the VM at 5pm and start it at 9am to avoid compute charges during off-hours.

💡 Hint

Consider which state stops billing for compute resources.

Deallocating the VM releases compute resources and stops billing for compute. Stopping the VM without deallocation still incurs compute charges. Deleting and recreating is inefficient and slow.

❓ security

expert

Security Implications of VM States

Which VM state provides the highest security assurance that the VM is not accessible over the network and cannot be accidentally started?

A Stopped (deallocated)

B Stopped (allocated)

C Paused

D Running

💡 Hint

Think about network accessibility and resource allocation.

A VM in the 'Stopped (deallocated)' state has its compute resources released, is not running, and is not accessible over the network. This state prevents accidental start and network exposure. 'Stopped (allocated)' VMs may still have network interfaces active.