ACorrect
Elasticity — automatically scale resources up and down.
Correct. Scale up automatically when traffic increases and scale down when it decreases. Fixed purchasing sized for the peak is no longer needed.
A company's traffic varies significantly by season. Which combination of AWS characteristics can handle the traffic variation while minimizing wasted cost? (Choose TWO.)
1 / 1
Select all that apply
CorrectA, B
Explanation
A question asking for the two AWS characteristics that handle seasonal traffic variation while minimizing wasted cost.
- 1「traffic variation」Demand rises and falls significantly by season.
BCorrect
Pay-as-you-go — billing based on usage.
Correct. You pay only for what you use, so there is no charge for idle resources. Combined with elasticity, waste is reduced to zero.
CIncorrect
Redundancy — placing multiple instances.
Redundancy is a design that provides multiple copies of the same component so that the service keeps running even if one fails.
It increases fault tolerance, a different goal from elasticity that follows capacity to seasonal traffic variation, so it is incorrect.
DIncorrect
Region distribution — deploying across multiple Regions.
Region distribution deploys across multiple Regions to achieve disaster recovery and geographic low latency.
It is about geographic placement, a different concept from elasticity that scales capacity with demand, so it is incorrect.
EIncorrect
Availability — assurance of service continuity.
Availability is a metric that indicates the percentage of time a service is operating normally (such as 99.9%).
It concerns the assurance of uptime, which differs from a mechanism that scales capacity with traffic variation, so it is incorrect.
Key Takeaway
Only elasticity + pay-as-you-go together create the benefit of “no fixed purchasing sized for the peak.” Either one alone is not enough. Multiple-response questions often ask about benefits that hold only when several elements are combined.