Describe cloud concepts practice questions

The consumption-based model charges only for resources actually used.

By definition you pay for what you consume and for as long as you consume it, with no up-front purchase and no charge for idle capacity. A fixed fee, buying full capacity, and owning depreciating hardware all describe non-consumption or on-premises models.

1. Recall the phrase pay only for what you use.
2. Match it to paying for actual usage.
3. Reject fixed fees and up-front hardware purchases.

Exam tip: The consumption-based model means paying only for the resources you use, with no charge for idle capacity.

Paying only for temporary, used capacity is consumption-based pricing.

Adding capacity for a peak and paying only for those weeks is pay-as-you-go, the consumption-based model. Shared responsibility is a security split, hybrid is a deployment mix, and CapEx is an up-front purchase, so none fit a scenario about paying for used capacity.

1. Spot the trigger: paying only for the weeks of extra capacity.
2. Map paying for what you use to the consumption-based model.
3. Eliminate security, deployment, and CapEx options.

Exam tip: Scaling spend up and down with real demand and paying only for what you use signals the consumption-based model.

Buying owned datacenter hardware up front is a capital expense.

A capital expense is a large up-front purchase of assets you own, such as servers and networking gear, which matches the scenario. OpEx, consumption charges, and subscriptions are all ongoing, usage-based, or recurring service costs, not up-front asset purchases.

1. Note the key detail: a large up-front purchase of owned hardware.
2. Match up-front asset ownership to CapEx.
3. Eliminate the ongoing-cost options (OpEx, consumption, subscription).

Exam tip: Buying and owning datacenter hardware up front is a capital expense (CapEx).

Paying monthly for consumed cloud resources is an operating expense.

An operating expense is an ongoing cost for a service you consume, billed as you go, which exactly matches a monthly Azure bill with no hardware to own. CapEx, depreciating assets, and one-time purchases all involve buying and owning assets, which is not happening here.

1. Identify the pattern: recurring bill for consumed resources, nothing owned.
2. Match ongoing service cost to OpEx.
3. Reject options tied to owning or depreciating assets.

Exam tip: Paying as you go for cloud resources you consumed is an operating expense (OpEx).

Adopting the cloud shifts spending from CapEx to OpEx.

On-premises requires large up-front hardware purchases (CapEx), while the cloud charges ongoing pay-as-you-go costs (OpEx), so the shift is CapEx to OpEx. The reversed and unchanged options contradict how consumption-based cloud billing works.

1. Classify on-premises spending as CapEx.
2. Classify cloud spending as OpEx.
3. Conclude the move is a CapEx-to-OpEx shift.

Exam tip: Moving to the cloud generally shifts spending from a capital expense to an operating expense.

The provider always secures the physical datacenter and hosts.

In the shared responsibility model, the physical datacenters, hosts, and network are always the provider's responsibility regardless of service type. The customer never manages the physical layer, so the options assigning it to the customer or splitting it are wrong.

1. Recall the always-provider responsibilities: physical datacenter, hosts, network.
2. Assign physical security to the provider.
3. Eliminate any option giving the customer physical responsibility.

Exam tip: The cloud provider always secures the physical datacenters and hosts, no matter the service type.