Question

Difficulty: MediumUnderstand concepts of cloud economics

ShieldHealth Solutions, a health insurance provider, plans to migrate its member portal and monthly claims analysis pipeline from an on-premises data center to AWS. The portal experiences steady daily traffic with occasional massive spikes during annual open enrollment periods. The claims analysis pipeline runs once a month, requiring substantial compute power for a 12-hour window. Which TWO of the following describe cloud economic benefits or mechanisms that ShieldHealth Solutions will realize by moving to AWS?

  1. Transitioning from a capital expense (CapEx) model to an operating expense (OpEx) model, allowing the company to pay only for the infrastructure actually consumedAnswer
  2. Leveraging elasticity to dynamically scale resources to meet the demand spikes of open enrollment and monthly analysis, eliminating payments for idle capacityAnswer
  3. C
    Shifting from an operating expense (OpEx) model to a capital expense (CapEx) model to claim asset depreciation on the AWS-owned physical hardware
  4. D
    Relying on scalability to automatically reduce the physical footprint and power consumption of AWS-owned data centers during off-peak hours
  5. E
    Deploying Spot Instances for the primary weekday member portal workloads to guarantee constant service availability and eliminate billing fluctuations

Answer

Transitioning from a capital expense (CapEx) model to an operating expense (OpEx) model, and leveraging elasticity to dynamically scale resources to meet demand spikes while eliminating payments for idle capacity.
The correct options are: transitioning from a capital expense (CapEx) model to an operating expense (OpEx) model, and leveraging elasticity to scale resources dynamically to meet demand spikes. Transitioning to AWS shifts the financial model from high upfront capital investments in physical servers (CapEx) to a pay-as-you-go operating expense (OpEx) structure. Elasticity allows the company to automatically provision resources during peak periods and release them when they are not needed, avoiding costs for idle infrastructure.

Step-by-Step Solution

1
Identify the workload patterns described: a portal with steady baseline traffic and seasonal spikes (open enrollment), and a predictable but infrequent high-compute task (monthly claims analysis).
Recognize that provisioning physical hardware for peak demand is inefficient and results in high idle capacity.
This sets the foundation for applying cloud economics concepts to optimize resource utilization.
2
Analyze the financial shifts associated with cloud migration.
Determine that moving from purchasing on-premises hardware (CapEx) to paying for cloud services on demand represents a shift to OpEx.
This addresses the core difference between capital expenditures and operating expenditures in cloud environments.
3
Analyze operational efficiency mechanism for fluctuating workloads.
Determine that AWS elasticity allows the company to scale up only when needed (e.g., during open enrollment or claims analysis) and scale down to avoid paying for unused capacity.
This maps the workload requirements to the cloud concept of elasticity.

Key Concept

Cloud Economics: CapEx vs OpEx and Elasticity
Rate this question