A regional hospital network is planning to migrate its patient medical imaging archive and processing system to AWS. The network currently maintains physical storage arrays and server hardware on-premises, requiring significant upfront capital investments and ongoing facility maintenance. The imaging archive grows steadily, but the processing demand peaks predictably during daytime clinic hours and drops significantly at night. The network wants to align its infrastructure costs with actual usage and minimize capital expenditures (CapEx).
Which two strategies should the network implement to achieve these cloud economics goals?
- Replacing upfront physical server purchases with a pay-as-you-go pricing model for compute and storage resources.Answer
- Deploying elastic resources that automatically scale down during night hours to match the reduced demand.Answer
- CConverting ongoing operational support fees into upfront capital expenditures (CapEx) to simplify long-term budget planning.
- DOverprovisioning compute instances to permanently match peak daytime demand, ensuring sufficient headroom for archive growth.
- ERehosting the legacy system on dedicated hosts to completely eliminate all operational expenditures (OpEx).
Answer
The correct strategies are replacing upfront physical server purchases with a pay-as-you-go pricing model, and deploying elastic resources that automatically scale down during night hours.
Replacing upfront physical server purchases with a pay-as-you-go model shifts capital expenses to operating expenses. Furthermore, deploying elastic resources that scale down at night aligns capacity with actual usage, minimizing waste and reducing the Total Cost of Ownership (TCO).
Step-by-Step Solution
Key Concept
Cloud economics benefits, specifically the shift from CapEx to OpEx and the utilization of elasticity to reduce TCO.