Azure Spot VMs for cost savings - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the VM priority as Spot for cost savings.

Azure

vm_parameters = {
  'location': 'eastus',
  'priority': '[1]'
}

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

ARegular

BSpot

CHigh

DLow

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Regular' instead of 'Spot' does not enable cost savings.

Using invalid priority values causes deployment errors.

Setting the VM priority to Spot enables cost savings by using unused Azure capacity.

2fill in blank

medium

Complete the code to set the eviction policy for the Spot VM.

Azure

vm_parameters = {
  'priority': 'Spot',
  'evictionPolicy': '[1]'
}

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

ADeallocate

BDelete

CRestart

DPause

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'Delete' will remove the VM and its data permanently.

Using unsupported eviction policies causes errors.

The eviction policy Deallocate deallocates the VM when evicted, allowing you to restart it later.

3fill in blank

hard

Fix the error in the code to correctly configure a Spot VM with eviction policy.

Azure

vm_parameters = {
  'priority': '[1]',
  'evictionPolicy': 'Deallocate'
}

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

APreemptible

BRegular

CSpot

DLow

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Preemptible' which is not a valid Azure VM priority.

Setting priority to 'Regular' disables Spot VM features.

The priority must be set to Spot to enable Spot VM features including eviction policy.

4fill in blank

hard

Fill both blanks to configure a Spot VM with eviction policy and max price.

Azure

vm_parameters = {
  'priority': '[1]',
  'evictionPolicy': '[2]',
  'maxPrice': -1
}

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

ASpot

BDelete

CDeallocate

DRegular

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Regular' priority disables Spot VM features.

Choosing 'Delete' eviction policy deletes the VM on eviction.

Setting priority to Spot enables Spot VM. Eviction policy Deallocate stops the VM on eviction. Max price -1 means pay up to the on-demand price.

5fill in blank

hard

Fill all three blanks to create a Spot VM with eviction policy, max price, and a tag for cost center.

Azure

vm_parameters = {
  'priority': '[1]',
  'evictionPolicy': '[2]',
  'maxPrice': [3],
  'tags': {
    'CostCenter': 'Finance'
  }
}

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

ARegular

BDeallocate

C-1

DSpot

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Regular' priority disables Spot VM features.

Setting maxPrice to a string instead of a number.

Omitting tags reduces resource organization.

Priority Spot enables Spot VM. Eviction policy Deallocate stops VM on eviction. Max price -1 means pay up to on-demand price. Tags help organize resources.

Practice

1. What is the main benefit of using Azure Spot VMs?

easy

A. They automatically scale without any configuration.

B. They offer significant cost savings by using unused capacity.

C. They provide unlimited storage for virtual machines.

D. They guarantee 100% uptime for critical applications.

Solution

1. Step 1: Understand Azure Spot VM purpose

   Azure Spot VMs use spare capacity in Azure data centers, which is cheaper but can be interrupted.

2. Step 2: Identify the main benefit

   The main benefit is cost savings by using this spare capacity, not guaranteed uptime or unlimited storage.

3. Final Answer:

   They offer significant cost savings by using unused capacity. -> Option B

4. Quick Check:

   Spot VMs = Cost savings [OK]

Hint: Spot VMs save money by using spare capacity [OK]

Common Mistakes:

• Thinking Spot VMs guarantee uptime
• Confusing Spot VMs with premium storage
• Assuming Spot VMs auto-scale without setup

2. Which Azure CLI command option is used to create a Spot VM?

easy

A. --priority Spot

B. --spot-enabled true

C. --priority Standard

D. --vm-type Spot

Solution

1. Step 1: Recall Azure CLI syntax for Spot VMs

   To create a Spot VM, the correct option is --priority Spot.

2. Step 2: Eliminate incorrect options

   --priority Standard is for regular VMs; --spot-enabled and --vm-type are not valid Azure CLI options.

3. Final Answer:

   --priority Spot -> Option A

4. Quick Check:

   Spot VM creation uses --priority Spot [OK]

Hint: Use --priority Spot to create Spot VMs [OK]

Common Mistakes:

• Using --priority Standard instead of Spot
• Assuming --spot-enabled is valid
• Confusing VM type options

3. What happens if the max price you set for an Azure Spot VM is lower than the current Spot price?

medium

A. The VM will run but be charged the max price you set.

B. The VM will be created but with reduced performance.

C. The VM creation will fail due to price limit.

D. The VM will be created as a standard VM instead.

Solution

1. Step 1: Understand max price behavior

   The max price sets the highest price you agree to pay for the Spot VM.

2. Step 2: Analyze what happens if max price is too low

   If the current Spot price is higher than your max price, Azure will not create the VM to avoid exceeding your limit.

3. Final Answer:

   The VM creation will fail due to price limit. -> Option C

4. Quick Check:

   Max price below Spot price = VM creation fails [OK]

Hint: Spot VM fails if max price is below current Spot price [OK]

Common Mistakes:

• Thinking VM runs at max price anyway
• Assuming VM downgrades performance
• Believing VM converts to standard automatically

4. You created a Spot VM but it was unexpectedly evicted. What is the most likely cause?

medium

A. The VM was manually deleted by another user.

B. The VM ran out of disk space.

C. The VM exceeded the max price you set.

D. Azure needed the capacity back for other workloads.

Solution

1. Step 1: Understand Spot VM eviction reasons

   Spot VMs can be evicted when Azure reclaims capacity for higher priority workloads.

2. Step 2: Identify the most common eviction cause

   The most common cause is Azure needing the capacity back, not disk space or manual deletion.

3. Final Answer:

   Azure needed the capacity back for other workloads. -> Option D

4. Quick Check:

   Spot VM eviction = Azure reclaims capacity [OK]

Hint: Spot VMs evict when Azure reclaims capacity [OK]

Common Mistakes:

• Assuming eviction is due to disk space
• Thinking eviction happens if max price exceeded
• Believing eviction is always manual

5. You want to run a batch job that can be interrupted but must save costs. Which setup best uses Azure Spot VMs?

hard

A. Create Spot VMs with a max price set to your budget and use automatic eviction handling.

B. Create standard VMs with premium SSDs for guaranteed uptime.

C. Create Spot VMs without setting max price to avoid failures.

D. Use Azure Functions instead of VMs for batch jobs.

Solution

1. Step 1: Match workload needs to Spot VM features

   Batch jobs that can be interrupted fit Spot VMs well because they save costs but may be evicted.

2. Step 2: Choose best configuration for cost and reliability

   Setting a max price controls cost, and handling eviction automatically ensures job completion despite interruptions.

3. Step 3: Eliminate other options

   Standard VMs cost more; no max price risks failures; Azure Functions are different service types.

4. Final Answer:

   Create Spot VMs with a max price set to your budget and use automatic eviction handling. -> Option A

5. Quick Check:

   Spot VMs + max price + eviction handling = cost-effective batch jobs [OK]

Hint: Set max price and handle eviction for cost-effective Spot VMs [OK]

Common Mistakes:

• Not setting max price and risking high costs
• Choosing standard VMs for interruptible jobs
• Confusing Azure Functions with Spot VMs