Question

Difficulty: MediumAzure Pricing Calculator and TCO Calculator

An organization planning a cloud migration needs to estimate future costs, compare potential savings, and optimize active resource spending. Match each operational task to the appropriate Azure tool or configuration step. To answer, drag each task on the left to its correct tool or step on the right.

  • Inputting current on-premises physical server counts, virtualization types, and storage capacities.TCO Calculator: Define your workloads
  • Configuring electricity costs, IT administration salaries, and facility hosting expenses.TCO Calculator: Adjust assumptions
  • Selecting specific Azure VM sizes, storage tiers, and estimating outbound data transfer bandwidth.Pricing Calculator: Estimate products
  • Reviewing automated recommendations to shut down idle virtual machines in an active subscription.Azure Advisor: Optimize costs

Answer

Inputting current on-premises infrastructure details matches TCO Calculator: Define your workloads. Configuring electricity, labor, and facility overhead costs matches TCO Calculator: Adjust assumptions. Selecting specific Azure service parameters matches Pricing Calculator: Estimate products. Reviewing recommendations for active subscriptions matches Azure Advisor: Optimize costs.
Defining workloads is the initial step of the TCO Calculator where on-premises server and storage specifications are entered. Adjusting assumptions is the second step, where ongoing operational costs like labor and electricity are customized. The Pricing Calculator is used to estimate monthly Azure product consumption by configuring specific service parameters. Azure Advisor analyzes active resource usage to provide optimization recommendations.

Step-by-Step Solution

1
Identify whether the task relates to comparing current on-premises costs to Azure or estimating new cloud deployments.
On-premises inventory and assumptions map to the TCO Calculator, whereas new Azure services map to the Pricing Calculator.
This establishes the correct primary tool context.
2
Determine the specific phase within the TCO Calculator for infrastructure vs. overhead costs.
Physical servers and storage map to the 'Define your workloads' phase, while power, cooling, and salaries map to the 'Adjust assumptions' phase.
This resolves the TCO Calculator internal workflow mappings.
3
Differentiate between pre-deployment estimation and active resource monitoring.
Selecting hypothetical VM sizes maps to the Pricing Calculator, while optimizing already deployed, idle VMs maps to Azure Advisor.
This separates pre-deployment planning from active post-deployment management.

Key Concept

Azure Pricing Calculator and TCO Calculator
Rate this question