EstatePulse Analytics runs large-scale property valuation models that execute heavily during the first week of every month when new market reports are released, but the system is idle for the rest of the month. Currently, they host this on-premises using high-performance hardware purchased upfront that has hit its maximum capacity, causing delays during peak periods. They are planning to migrate this workload to AWS.
Which two of the following benefits represent how this migration aligns with the core concepts of AWS cloud economics? (Select TWO.)
- Shifting from upfront Capital Expenditures (CapEx) to a pay-as-you-go Operating Expenditure (OpEx) model, paying only for the compute resources consumed.Cevap
- Utilizing elasticity to automatically provision instances during peak valuation weeks and terminate them during idle periods to prevent paying for unused capacity.Cevap
- CTransitioning to a model where AWS assumes full responsibility for configuring database schemas and operating system patching.
- DAllocating fixed maximum capacity statically across the entire month using On-Demand instances to eliminate the risk of performance bottlenecks.
- ECommitting to a -year Reserved Instance contract for the entire peak compute capacity to handle the highly variable and short-duration workloads.
Cevap
Shifting from upfront Capital Expenditures (CapEx) to a pay-as-you-go Operating Expenditure (OpEx) model, paying only for the compute resources consumed, and utilizing elasticity to automatically provision instances during peak valuation weeks and terminate them during idle periods to prevent paying for unused capacity.
The correct options are shifting from upfront Capital Expenditures to a pay-as-you-go Operating Expenditure model, and utilizing elasticity to provision and terminate instances. Under an OpEx model, the company avoids upfront physical server costs, and with elasticity, they can match supply with dynamic demand, avoiding paying for idle servers when the monthly reports are completed.
Adım Adım Çözüm
Anahtar Kavram
Cloud Economics: CapEx vs OpEx shift and Elasticity