A design keeps a second site ready so the service continues if the first site fails. Which cloud trait is that?
Select an answer to reveal the explanation.
Short Explanation
You keep a second stage ready so the show goes on if the first stage goes dark. That readiness is high availability. Stretching the number of machines, billing for data that leaves, or sharing hardware with other customers is not a spare site.
Full Explanation
High availability means the service keeps running through a failure, here by having a second site ready to take over. That is the trait in the design. Rapid elasticity adds and removes capacity as demand changes. A spare site for a failure is not the same as growing because CPU is high. Metered egress is a charge for data leaving the provider. A bill does not keep a site online. Multitenancy means several customers share the underlying systems. Sharing does not fail a service over to a spare site. Exam caveat: the second site only helps if data and the failover path are actually ready. A powered-off copy that is months old is not availability. Operational check: run a failover test, confirm users reach the service at the second site, and confirm the first site can be brought back without a second outage. Fail over in a test window and confirm users still reach the service. Write down which site is primary after you fail back. Tell users which address to use during the failover test.