Azure Pricing practice questions

Elasticity

Why wrong: Incorrect. Elasticity is the ability to automatically provision and de-provision resources to match demand. While it can impact cost, it does not directly describe the shift from CapEx to OpEx.

High availability

Why wrong: Incorrect. High availability refers to ensuring applications remain operational despite component failures (e.g., via redundancy across multiple servers or data centers). It does not address the financial model of paying for resources.

Predictable performance

Why wrong: Incorrect. Predictable performance means that resources deliver consistent throughput and latency, often guaranteed by service-level agreements. It is not related to the financial shift from CapEx to OpEx.

High availability

Why wrong: High availability ensures that applications and data remain accessible despite component failures. While Azure provides availability guarantees, the question focuses on the shift from upfront hardware purchases to monthly consumption-based payments, not on uptime or fault tolerance.

Elasticity

Why wrong: Elasticity is the ability to automatically scale resources up or down based on demand. Although Azure enables elasticity, the scenario specifically describes a change in financial model (upfront cost vs. monthly consumption), not the ability to adjust resource quantity dynamically.

Disaster recovery

Why wrong: Disaster recovery involves replicating data and applications to another region to protect against catastrophic failures. The question does not mention any backup, replication, or recovery requirements; it focuses solely on the financial purchasing model.

High availability

Why wrong: Incorrect. High availability refers to ensuring services remain operational even during failures, not the pricing model.

Scalability

Why wrong: Incorrect. Scalability is the ability to increase or decrease resources as needed, not the pricing model.

Disaster recovery

Why wrong: Incorrect. Disaster recovery involves replicating and recovering data or applications after a disaster, not the pricing model.

Reserved instances

Why wrong: Reserved instances require a prepaid commitment for a 1- or 3-year term, providing a discount but not a pay-as-you-go model.

Spot VMs

Why wrong: Spot VMs offer lower cost but can be evicted by Azure when capacity is needed; they are not a consistent pay-as-you-go model.

Hybrid Benefit

Why wrong: Azure Hybrid Benefit is a licensing discount program for certain Microsoft software, not a pricing model for general resource consumption.

On-premises is an operational expenditure (OpEx), while Azure is a capital expenditure (CapEx).

Why wrong: This statement is reversed. On-premises requires significant upfront capital investment, making it CapEx, not OpEx. Azure's pay-as-you-go model is OpEx because it is a recurring operational cost based on consumption.

Both on-premises and Azure are classified as capital expenditures (CapEx).

Why wrong: This is incorrect because Azure's pay-as-you-go model lacks the upfront investment and asset depreciation characteristic of CapEx. Azure spending is an operational cost.

Both on-premises and Azure are classified as operational expenditures (OpEx).

Why wrong: This is incorrect. On-premises infrastructure purchases are not operational costs; they are capital investments that provide long-term value and are depreciated. Only Azure's consumption-based model is OpEx.

Rapid elasticity

Why wrong: Rapid elasticity refers to the ability to quickly scale resources up or down, often automatically, to meet demand. The scenario describes a billing model based on actual consumption, not the speed of scaling.

Resource pooling

Why wrong: Resource pooling means the provider's computing resources are shared across multiple customers, with resources dynamically assigned as needed. The scenario focuses on pay-per-use billing, not multi-tenancy or resource sharing.

Broad network access

Why wrong: Broad network access means cloud resources are accessible over the internet via standard protocols (e.g., HTTPS, RDP) from a variety of devices. The scenario does not describe network accessibility; it describes a billing model.

Scalability to handle variable demand

Why wrong: Scalability is the ability to increase or decrease resources based on demand, which does not directly describe the change from upfront hardware purchases to monthly consumption-based billing.

High availability through geographic redundancy

Why wrong: High availability focuses on keeping applications and data accessible despite failures, not on the financial model of paying for only what you use.

Resource pooling through multi-tenancy

Why wrong: Resource pooling allows the provider to serve multiple customers from shared physical resources, which can lower costs but does not directly describe the shift from CapEx to OpEx in the customer's billing structure.

High availability – redundant infrastructure ensures the application stays online.

Why wrong: High availability focuses on minimizing downtime through redundancy, not on paying only for used resources. This option does not address the cost model requirement.

Elasticity – resources can automatically scale out and in based on demand.

Why wrong: Elasticity is the ability to dynamically adjust resources to match workload changes. While related to cost efficiency, it does not directly describe the billing model of paying only for consumed resources.

Disaster recovery – data and applications are backed up to another region.

Why wrong: Disaster recovery provides business continuity after a failure, but it is not related to the billing model or cost structure described in the requirement.

Scalability

Why wrong: Scalability is the ability to increase or decrease resources based on demand. It does not describe the change from upfront capital costs to pay-as-you-go pricing.

High availability

Why wrong: High availability ensures that services remain operational with minimal downtime. It is unrelated to the cost structure shift from capital to operational expenses.

Resource pooling

Why wrong: Resource pooling is a cloud characteristic where the provider's compute resources are shared across multiple customers. It does not directly relate to the financial model of paying for usage rather than owning assets.

You make large upfront investments in hardware that you own and depreciate

Why wrong: Large upfront hardware investments describe the CapEx model of traditional on-premises IT.

You purchase cloud capacity in bulk at the beginning of each year

Why wrong: Bulk upfront purchasing is not the primary cloud model; consumption-based billing is.

You lease physical servers from the cloud provider for a fixed monthly fee

Why wrong: Cloud abstracts physical servers; you consume logical compute resources, not lease specific hardware.

The ability to automatically replace failed resources without human intervention

Why wrong: Automatic resource replacement describes reliability, not predictability.

The guarantee that all data is stored within a specific geographic region

Why wrong: Data residency is a compliance feature, not specifically cloud predictability.

The ability to deploy identical environments for development and production

Why wrong: Identical environment deployment describes consistency/repeatability through IaC, not cloud predictability.

Paying a fixed monthly fee regardless of actual resource usage

Why wrong: Fixed monthly fees regardless of usage is a flat-rate model, not consumption-based.

Purchasing capacity upfront for a year at a discounted rate

Why wrong: Upfront annual purchases describe Reserved Instances, not consumption-based pricing.

Paying a per-user license fee for cloud software access

Why wrong: Per-user licensing is a common SaaS model but is not specifically 'consumption-based' pricing.

Analyze historical spending on existing Azure resources

Why wrong: Historical spending analysis is done in Azure Cost Management; Pricing Calculator is for pre-deployment estimates.

Compare Azure prices against AWS and Google Cloud prices

Why wrong: The TCO Calculator compares on-premises to Azure; the Pricing Calculator estimates Azure costs only.

Automatically optimize spending by terminating unused resources

Why wrong: Cost optimization recommendations are from Azure Advisor; the Pricing Calculator only estimates costs.

You pay a fixed monthly fee regardless of how many resources you use

Why wrong: Fixed monthly fees are a flat-rate model; consumption-based pricing varies with actual usage.

You must purchase at least 12 months of capacity regardless of usage

Why wrong: 12-month purchases describe Reserved Instances (with discounts); consumption-based billing has no minimums.

You pay based on the performance level of the service, not actual usage

Why wrong: Some premium tiers cost more, but consumption-based billing still charges for actual usage quantities.

Pay-as-you-go

Why wrong: Pay-as-you-go has no commitment and charges full price — Reservations provide the commitment-based discount.

Azure Spot pricing

Why wrong: Spot pricing uses spare capacity at large discounts but resources can be evicted — Reservations guarantee committed capacity.

Azure Dev/Test pricing

Why wrong: Dev/Test pricing applies to non-production environments — Reservations are for production workloads with term commitments.

Storing all data on physical servers in the customer's own building

Why wrong: On-premises storage is traditional IT; cloud computing delivers services over the internet.

Using only virtual machines in a third-party data center

Why wrong: Cloud includes many services beyond VMs; it also includes managed databases, AI, and analytics.

A type of software that runs in web browsers without installation

Why wrong: Browser-based software is one type of cloud service (SaaS); cloud computing is broader.

All data transfer (inbound and outbound) is charged at the same rate

Why wrong: Azure charges for outbound data; inbound data is free.

Data transfer is entirely free within Azure regardless of direction or region

Why wrong: Outbound data and cross-region data transfer incur charges; only inbound is free.

Data transfer is charged based on the speed of the transfer, not the amount

Why wrong: Azure charges based on the volume (GB) of data transferred, not transfer speed.