A community theater company plans to migrate its ticketing platform to AWS. The platform receives extremely high volumes of traffic during the first hour of ticket releases for major shows, but experiences negligible traffic during the rest of the month. The theater needs to avoid paying for idle infrastructure and eliminate upfront server procurement costs.
Which two AWS cloud economics concepts or benefits should the theater leverage to meet these requirements? (Select TWO.)
- Replacing upfront capital expenses with variable operational expensesAnswer
- Leveraging elasticity to dynamically adjust resource capacity to match actual demandAnswer
- CConverting variable operational expenses into fixed capital expenses to guarantee predictable budgeting
- DPermanently provisioning resources at peak capacity levels to guarantee scalability
- EUsing a rehosting migration strategy to automatically redesign the application into serverless functions
Answer
The theater company should replace upfront capital expenses with variable operational expenses, and leverage elasticity to dynamically adjust resource capacity to match actual demand.
The correct options identify two core AWS cloud economics benefits: shifting upfront capital expenses (CapEx) to variable operational expenses (OpEx), and using elasticity to scale resources dynamically. By trading capital expenses for operational expenses, the theater avoids upfront server purchasing costs. By leveraging elasticity, the ticketing system dynamically provisions resources to handle the sudden burst of ticket buyers and downscales during idle periods to prevent wasted expenditures.
Step-by-Step Solution
Key Concept
AWS Cloud Economics (CapEx to OpEx shift and Elasticity)
Estimated Time:1m 0s