A financial technology startup is designing the cloud infrastructure for its payment processing API. The startup has two main operational requirements:
1. The API must continue to process transactions without interruption even if a localized power outage occurs in one of the physical datacenters within the Azure region.
2. The compute capacity must automatically expand when transaction volume spikes during business hours and contract during the night to minimize operational costs.
Which of the following cloud characteristics or architectural choices directly align with these requirements? (Select TWO)
- Deploying the API instances across multiple Availability Zones within the region to ensure high availability.Answer
- Implementing autoscale rules on the compute resources to dynamically match CPU capacity with real-time transaction volume to achieve elasticity.Answer
- CUpgrading the compute instances to a virtual machine size with more RAM and CPU cores during peak hours to achieve horizontal scalability.
- DReplicating database backups daily to a different geographical region to provide high availability during localized datacenter outages.
Answer
Deploying instances across multiple Availability Zones to ensure high availability, and implementing autoscale rules on compute resources to achieve elasticity.
The correct choices are deploying the API instances across multiple Availability Zones and implementing autoscale rules on the compute resources. Distributing resources across multiple Availability Zones provides localized fault tolerance (high availability) to survive a datacenter power outage. Autoscale rules dynamically add and remove instances based on workload, which directly implements cloud elasticity.
Step-by-Step Solution
Key Concept
Understanding the distinction between High Availability (ensuring uptime during local failures) and Elasticity (dynamic scaling to match demand).
Estimated Time:2m 0s