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?

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.