Azure Savings Plans - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an Azure Savings Plan with a one-year commitment.

Azure

az savingsplan create --name mySavingsPlan --term [1]

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

AP3Y

BP1Y

CP6M

DP5Y

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a commitment period longer than intended.

Using unsupported commitment durations.

The commitment period for this Savings Plan is set to one year using P1Y.

2fill in blank

medium

Complete the code to specify the scope of the Azure Savings Plan to a subscription.

Azure

az savingsplan create --name mySavingsPlan --scope [1]

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

Asubscription

Bresource-group

Cmanagement-group

Dtenant

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing resource-group scope with subscription scope.

Using tenant scope which is broader than subscription.

The scope subscription limits the Savings Plan to a single Azure subscription.

3fill in blank

hard

Fix the error in the command to specify the product type for the Azure Savings Plan.

Azure

az savingsplan create --name mySavingsPlan --product [1]

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

AVirtualMachines

BVMs

Cvirtualmachines

DCompute

Attempts:

3 left

💡 Hint

Common Mistakes

Using uppercase letters in product names.

Using shorthand or incorrect product names.

The product type must be Compute to be valid in the Azure CLI.

4fill in blank

hard

Fill both blanks to create a Savings Plan with a three-year commitment and scope set to management group.

Azure

az savingsplan create --term [1] --scope [2]

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

AP3Y

Bsubscription

Cmanagement-group

DP1Y

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up subscription and management group scopes.

Choosing incorrect commitment durations.

The commitment is set to P3Y and the scope to management-group to apply savings across multiple subscriptions.

5fill in blank

hard

Fill all three blanks to create a Savings Plan named 'plan1' with a one-year commitment, product 'Compute', and scope 'subscription'.

Azure

az savingsplan create --name [1] --term [2] --product [3] --scope "/subscriptions/12345678-1234-1234-1234-123456789012"

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

Aplan1

BP1Y

CCompute

DplanA

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect plan names.

Wrong commitment or product strings.

The Savings Plan is named plan1, has a P1Y commitment, and targets the Compute product.

Practice

1. What is the main benefit of using Azure Savings Plans?

easy

A. Lowering costs by committing to use services over time

B. Increasing the speed of virtual machines

C. Automatically scaling app services

D. Improving security of cloud resources

Solution

1. Step 1: Understand the purpose of Azure Savings Plans

   Azure Savings Plans are designed to reduce costs by committing to use certain Azure services over a period.

2. Step 2: Compare options to the main benefit

   Options A, B, and D describe performance or security improvements, which are not the primary goal of Savings Plans.

3. Final Answer:

   Lowering costs by committing to use services over time -> Option A

4. Quick Check:

   Cost savings = Lowering costs by commitment [OK]

Hint: Savings Plans reduce cost by commitment, not performance [OK]

Common Mistakes:

• Confusing cost savings with performance improvements
• Thinking Savings Plans improve security
• Assuming Savings Plans scale resources automatically

2. Which of the following is the correct Azure CLI command to create a savings plan?

easy

A. az savingsplan deploy --name MyPlan --scope subscription

B. az savingsplan new --name MyPlan --scope subscription

C. az savings create --plan MyPlan --scope subscription

D. az savings-plan create --name MyPlan --scope subscription

Solution

1. Step 1: Identify the correct Azure CLI syntax for savings plans

   The official command to create a savings plan uses az savings-plan create with parameters like --name and --scope.

2. Step 2: Check other options for invalid commands

   Options B, C, and D use incorrect verbs or command structures not supported by Azure CLI.

3. Final Answer:

   az savings-plan create --name MyPlan --scope subscription -> Option D

4. Quick Check:

   Correct CLI command = az savings-plan create [OK]

Hint: Use 'az savings-plan create' to make a new plan [OK]

Common Mistakes:

• Using 'new' instead of 'create' in CLI
• Mixing 'savings' and 'savingsplan' commands
• Incorrect parameter names

3. Given a steady workload of virtual machines running 24/7, what is the expected behavior when applying an Azure Savings Plan?

medium

A. Costs for the virtual machines will decrease due to the commitment

B. Virtual machines will automatically increase CPU cores

C. The workload will be moved to a cheaper region

D. Virtual machines will restart daily to apply savings

Solution

1. Step 1: Understand how Savings Plans affect steady workloads

   Azure Savings Plans reduce costs by committing to usage, so steady workloads like 24/7 VMs benefit from lower prices.

2. Step 2: Eliminate options unrelated to cost savings

   Options A, B, and C describe changes to performance, location, or VM behavior, which Savings Plans do not cause.

3. Final Answer:

   Costs for the virtual machines will decrease due to the commitment -> Option A

4. Quick Check:

   Steady workload + Savings Plan = Lower cost [OK]

Hint: Savings Plans cut cost, not change VM specs or location [OK]

Common Mistakes:

• Thinking Savings Plans change VM performance
• Assuming workload moves to cheaper regions automatically
• Believing VMs restart to apply savings

4. You tried to create an Azure Savings Plan but received an error: "Invalid scope parameter." What is the most likely cause?

medium

A. The savings plan name is too long

B. The scope value is not a valid subscription or resource group ID

C. You did not specify the VM size

D. The Azure CLI version is outdated

Solution

1. Step 1: Analyze the error message about scope

   The error "Invalid scope parameter" indicates the scope argument is incorrect or malformed.

2. Step 2: Identify what scope should be

   Scope must be a valid subscription ID or resource group ID; an invalid or mistyped value causes this error.

3. Final Answer:

   The scope value is not a valid subscription or resource group ID -> Option B

4. Quick Check:

   Invalid scope = wrong subscription/resource ID [OK]

Hint: Check scope is valid subscription or resource group ID [OK]

Common Mistakes:

• Ignoring scope format and using wrong IDs
• Blaming name length for scope errors
• Not updating Azure CLI before retrying

5. A company has fluctuating app service usage but wants to save costs with Azure Savings Plans. Which strategy best fits their needs?

hard

A. Avoid savings plans and pay pay-as-you-go only

B. Commit to the highest possible usage to cover all peaks

C. Commit to a savings plan based on their average steady usage to maximize savings

D. Create multiple savings plans for each app service separately

Solution

1. Step 1: Understand Savings Plans suit steady predictable usage

   Savings Plans work best when usage is steady; fluctuating usage means committing to average steady usage is optimal.

2. Step 2: Evaluate options for cost efficiency

   Commit to the highest possible usage to cover all peaks wastes money by committing to peak usage; C misses savings; D complicates management without extra benefit.

3. Final Answer:

   Commit to a savings plan based on their average steady usage to maximize savings -> Option C

4. Quick Check:

   Average steady usage commitment = best savings [OK]

Hint: Commit to average steady usage, not peaks, for best savings [OK]

Common Mistakes:

• Committing to peak usage wastes money
• Avoiding savings plans due to usage fluctuation
• Creating many small savings plans unnecessarily