Fundamental
Prepare and test your skills
Fundamental
Prepare and test your skills
Hybrid Cloud Combines CapEx and OpEx
Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An enterprise maintains its core legacy database on dedicated physical servers within its on-premises datacenter, requiring substantial upfront investment for physical hardware, facility upkeep, and routine maintenance.
To manage unpredictable traffic surges during peak retail seasons without buying excess hardware, the company expands its web front-end applications into Microsoft Azure, paying only for the compute and storage capacity consumed during active operations.
Which cloud deployment and financial approach describes this combined operational model?
Explanations
A community cloud model that eliminates all operational expenditures (OpEx) by sharing public cloud subscriptions across independent organizations
A community cloud model that eliminates all operational expenditures (OpEx) by sharing public cloud subscriptions across independent organizations
What a Community Cloud Model Is
A community cloud is a collaborative cloud computing environment shared by several organizations with common concerns, such as regulatory compliance, security requirements, or shared industry missions (for example, healthcare networks or government agencies).
Why It Doesn't Meet the Requirement
- Does not eliminate operational costs: Cloud computing cannot eliminate Operational Expenditure (OpEx); running workloads in any cloud model generates continuous ongoing costs for power, software licenses, or consumption-based billing.
- Misapplies the scenario: The enterprise described is managing its own internal on-premises datacenter alongside Azure public cloud resources to handle seasonal demand, not sharing infrastructure with external partner organizations.
- Inaccurate billing governance: Organizations do not combine public cloud subscriptions to completely remove operating expenses.
Key Characteristics of Community Clouds
- Shared organizational focus: Infrastructure is provisioned for exclusive use by a specific community of consumers with shared goals.
- Joint governance or third-party hosting: The environment may be owned, managed, and operated by one or more organizations in the community or a third party.
- Distributed cost sharing: Members distribute infrastructure costs among participating entities rather than eliminating operational costs entirely.
This Answer Would Be Correct If
Multiple distinct enterprises in the same industry created a jointly funded, shared cloud platform to achieve regulatory compliance or share specific vertical industry datasets.
Additional Context
Both private and public cloud models incur operational costs; the distinguishing factor is whether infrastructure is acquired through upfront capital outlays (CapEx) or variable pay-as-you-go consumption (OpEx).
A hybrid cloud model combining upfront capital expenditure (CapEx) for private infrastructure with consumption-based operational expenditure (OpEx) for public cloud services
A hybrid cloud model combining upfront capital expenditure (CapEx) for private infrastructure with consumption-based operational expenditure (OpEx) for public cloud services
What a Hybrid Cloud Model with Mixed Financial Approaches Is
A hybrid cloud model connects an organization's on-premises private cloud or local datacenter infrastructure with a public cloud provider such as Microsoft Azure. From a financial perspective, this model integrates two distinct expenditure methods: Capital Expenditure (CapEx) for physical, owned hardware and Operational Expenditure (OpEx) for cloud-based services.
How It Meets the Enterprise Requirements
- Protects existing capital investments: The organization retains its dedicated on-premises servers for core database workloads, leveraging existing CapEx investments in hardware, power, cooling, and physical security.
- Enables flexible public cloud bursting: Azure resources scale dynamically during peak shopping events, utilizing a consumption-based (pay-as-you-go) pricing model where costs are treated as OpEx and accrue only when services run.
- Eliminates unnecessary hardware overprovisioning: By bursting into Azure, the business avoids buying expensive physical machines that would sit idle outside seasonal peak periods.
Key Advantages of Combining CapEx and OpEx in Hybrid Environments
- Financial flexibility: Organizations align IT spending with real-time business demand rather than forecasting peak capacity years in advance.
- Optimal workload placement: Predictable, steady-state workloads run on already amortized private infrastructure, while volatile workloads run on public cloud infrastructure.
- Granular cost management: Cloud management tools allow precise tracking of consumption metrics (such as compute hours, data transfers, and storage volume).
- Reduced total cost of ownership (TCO): Eliminates the ongoing depreciation and maintenance overhead of idle backup physical servers.
Why This Is Optimal
This hybrid approach provides the perfect balance of regulatory control and financial efficiency. Instead of funding huge capital reserves to meet temporary peaks, the enterprise leverages the elastic, consumption-based billing of the public cloud while maintaining control of critical assets on-premises.
A public cloud model utilizing upfront capital expenditure (CapEx) to purchase and manage physical server racks inside Azure datacenters
A public cloud model utilizing upfront capital expenditure (CapEx) to purchase and manage physical server racks inside Azure datacenters
What This Option Describes
This option incorrectly claims that using a public cloud involves purchasing physical hardware, server racks, and datacenter floor space through an upfront Capital Expenditure (CapEx) model.
Why It Doesn't Meet the Requirement
- Misunderstands public cloud ownership: In a public cloud like Azure, the cloud provider (Microsoft) owns, manages, and maintains all underlying physical hardware, facilities, and network infrastructure.
- Inaccurate billing model: Public cloud consumers do not make large upfront capital investments to purchase server racks. Instead, they operate on a consumption-based model (OpEx) where they pay strictly for the virtual resources, compute time, and storage capacity used.
- Ignores the on-premises integration: The scenario explicitly incorporates the organization's existing on-premises private datacenter, which makes the deployment a hybrid environment rather than an exclusively public cloud deployment.
Key Characteristics of Public Cloud Billing
- No upfront hardware investment: Users provision virtual machines, serverless components, and platform services without purchasing physical equipment.
- Subscription and consumption pricing: Costs are incurred based on usage intervals such as seconds, minutes, hours, or volume of data processed.
- Shared physical infrastructure: Hardware is multitenant and managed entirely by the cloud vendor.
This Answer Would Be Correct If
This concept would only apply if an enterprise were building out an on-premises private datacenter or purchasing physical co-location cage space directly from a facility provider.
Additional Context
While customers can reserve compute capacity in Azure for one- or three-year terms to achieve significant discounts, these reservations represent billing commitments for operational capacity, not the physical purchase of datacenter hardware.
A private cloud model utilizing consumption-based billing (OpEx) where public cloud providers invoice per-second usage for locally owned on-premises servers
A private cloud model utilizing consumption-based billing (OpEx) where public cloud providers invoice per-second usage for locally owned on-premises servers
What a Private Cloud Model Is
A private cloud consists of computing resources dedicated exclusively to one business or organization. It can be physically located at the company’s on-premises datacenter or hosted by a third-party service provider.
Why It Doesn't Meet the Requirement
- Mischaracterizes private cloud financing: Traditional private cloud infrastructure requires significant upfront Capital Expenditure (CapEx) for physical servers, network switches, storage arrays, and virtualization software licenses.
- Misattributes billing mechanisms: Public cloud providers do not automatically invoice per-second consumption for an organization's proprietary, locally owned on-premises servers.
- Omits public cloud elasticity: A purely private cloud environment lacks the seamless, on-demand public cloud scalability needed to burst seasonal workloads into Azure.
Key Characteristics and Limitations of Private Clouds
- High upfront financial commitments: Organizations must purchase physical infrastructure upfront and absorb depreciation.
- Full maintenance accountability: The organization is responsible for hardware replacement, power, cooling, and facility security.
- Fixed capacity boundaries: Scaling requires procuring, racking, and configuring additional physical hardware, which takes weeks or months.
This Answer Would Be Correct If
The scenario described an organization that exclusively hosts all workloads on its own internal hardware without bursting into Azure or utilizing public cloud elasticity.
Additional Context
While hybrid management solutions can extend Azure management control planes to on-premises servers, the underlying on-premises physical hardware still represents a private capital expenditure distinct from public cloud consumption billing.
Try 10 interactive questions like this one, free
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
- 688 practice questions across all 3 exam domains
- Every answer explained: why it is right, and why the others are not
- Scout, an AI tutor that answers your follow-up questions
- Readiness tracking by domain, so you know when to book the exam
Related questions
Keep the momentum going with these hand-picked practice scenarios
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure ExpressRoute
Define cloud models, including public, private, and hybrid
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Azure Dedicated Host
Define cloud models, including public, private, and hybrid
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Hybrid Cloud
Define cloud models, including public, private, and hybrid
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Hybrid Cloud Model
Define cloud models, including public, private, and hybrid
FundamentalAZ-900 Microsoft Azure Fundamentals Exam
Shared Responsibility Model
Define cloud models, including public, private, and hybrid
ExpertAZ-500 Microsoft Azure Security Technologies Exam
Application Permissions vs Delegated Permissions
Configure app registration permission scopes
Last updated Validated