Cost optimization pillar in Azure - Time & Space Complexity

Time Complexity: Cost optimization pillar

O(n)

Understanding Time Complexity

We want to understand how the cost optimization steps in Azure grow as we add more resources or services.

How does the effort and operations needed change when scaling up cost-saving actions?

Scenario Under Consideration

Analyze the time complexity of this cost optimization process.

// Example: Checking and optimizing costs for multiple Azure resources
for (resource in resourceList) {
  checkCost(resource);
  if (costHigh(resource)) {
    applySavingsPlan(resource);
    resizeOrShutdown(resource);
  }
}

This sequence checks each resource's cost, then applies savings if needed.

Identify Repeating Operations

Look at what repeats as the number of resources grows.

• Primary operation: Checking cost and applying savings for each resource.
• How many times: Once per resource in the list.

How Execution Grows With Input

As you add more resources, the number of cost checks and savings actions grows directly with that number.

Input Size (n)	Approx. Api Calls/Operations
10	About 10 cost checks and possible savings actions
100	About 100 cost checks and possible savings actions
1000	About 1000 cost checks and possible savings actions

Pattern observation: The work grows evenly as you add more resources.

Final Time Complexity

Time Complexity: O(n)

This means the time to optimize costs grows in direct proportion to the number of resources.

Common Mistake

[X] Wrong: "Optimizing costs for many resources takes the same time as for one resource."

[OK] Correct: Each resource needs its own check and possible action, so time grows with the number of resources.

Interview Connect

Understanding how cost optimization scales helps you plan and explain cloud management clearly and confidently.

Self-Check

"What if we batch multiple resources together for cost checks? How would the time complexity change?"

Practice

1. What is the main goal of the Cost optimization pillar in Azure cloud?

easy

A. To improve network speed only

B. To save money by using cloud resources wisely

C. To add more storage without limits

D. To increase the number of virtual machines

Solution

1. Step 1: Understand the purpose of cost optimization

   The cost optimization pillar focuses on managing cloud spending efficiently.

2. Step 2: Identify the correct goal

   Saving money by using resources wisely matches the cost optimization goal.

3. Final Answer:

   To save money by using cloud resources wisely -> Option B

4. Quick Check:

   Cost optimization = saving money [OK]

Hint: Cost optimization means saving money smartly [OK]

Common Mistakes:

• Thinking cost optimization means adding more resources
• Confusing cost optimization with performance only
• Assuming cost optimization ignores resource usage

2. Which Azure tool helps you monitor and control your cloud spending?

easy

A. Azure Cost Management

B. Azure DevOps

C. Azure Active Directory

D. Azure Monitor Logs

Solution

1. Step 1: Identify Azure tools related to cost

   Azure Cost Management is designed to track and manage cloud expenses.

2. Step 2: Exclude unrelated tools

   DevOps is for development, Active Directory for identity, Monitor Logs for diagnostics.

3. Final Answer:

   Azure Cost Management -> Option A

4. Quick Check:

   Cost Management = spending control [OK]

Hint: Cost Management tracks spending in Azure [OK]

Common Mistakes:

• Choosing Azure DevOps for cost tracking
• Confusing Azure Monitor Logs with cost tools
• Selecting Azure Active Directory by mistake

3. You have an Azure VM running 24/7 but only need it during business hours (8 AM to 6 PM). What is the best cost optimization action?

medium

A. Keep the VM running all the time

B. Resize the VM to a larger size

C. Schedule the VM to start and stop during business hours

D. Add more storage to the VM

Solution

1. Step 1: Analyze VM usage pattern

   The VM is needed only during business hours, so running it 24/7 wastes money.

2. Step 2: Choose cost-saving action

   Scheduling start/stop saves cost by not running VM when unused.

3. Final Answer:

   Schedule the VM to start and stop during business hours -> Option C

4. Quick Check:

   Stop unused VM times = save cost [OK]

Hint: Stop VMs when not needed to save money [OK]

Common Mistakes:

• Keeping VM always on wastes money
• Resizing larger increases cost
• Adding storage does not reduce cost

4. You see a recommendation from Azure Advisor to "Right-size your VMs" but your VM is already the smallest size. What should you do?

medium

A. Check if VM is underutilized and consider shutting down

B. Ignore the recommendation because VM is smallest

C. Upgrade VM to a larger size

D. Delete the VM immediately

Solution

1. Step 1: Understand "Right-size" recommendation

   It means adjusting VM size to match workload, avoiding waste.

2. Step 2: Since VM is smallest, check if it is needed at all

   If underutilized, shutting down or deleting saves cost.

3. Final Answer:

   Check if VM is underutilized and consider shutting down -> Option A

4. Quick Check:

   Right-size means match usage, not just smallest [OK]

Hint: Right-size means match workload, not just smallest size [OK]

Common Mistakes:

• Ignoring recommendations blindly
• Upgrading VM increases cost unnecessarily
• Deleting VM without checking usage

5. Your company wants to reduce Azure costs by using reserved instances. Which approach best fits cost optimization?

hard

A. Ignore reserved instances and focus on storage only

B. Use pay-as-you-go for all workloads to stay flexible

C. Always use the largest VM size available

D. Purchase reserved instances for steady workloads to get discounts

Solution

1. Step 1: Understand reserved instances

   Reserved instances offer discounts for long-term, steady usage.

2. Step 2: Match reserved instances to steady workloads

   This reduces cost compared to pay-as-you-go for predictable use.

3. Final Answer:

   Purchase reserved instances for steady workloads to get discounts -> Option D

4. Quick Check:

   Reserved instances = save on steady use [OK]

Hint: Reserved instances save money for steady workloads [OK]

Common Mistakes:

• Using pay-as-you-go for steady workloads wastes money
• Choosing largest VM size increases cost
• Ignoring reserved instances misses savings