After a single rack failure killed on-premises apps, staff want cloud high availability. At describe depth, what does that benefit emphasize?
Select an answer to reveal the explanation.
Short Explanation
One dead rack took the whole carnival down. High availability is spreading the rides so one broken generator does not darken every booth. Cloud makes that spread-across-failures story part of the architecture conversation—not a portal lab.
Full Explanation
High availability emphasizes architectures that tolerate component or facility failures so applications stay reachable. Conceptually, that includes distributing workloads across fault domains or availability constructs rather than concentrating risk in one rack. AZ-900 stays at the benefit and describe level; it does not require performing availability-set or zone configuration as in AZ-104.