CLF-C02 Cloud Technology and Services Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Deploy resources across multiple Availability Zones within a single Region

  Why it's wrong here

  Availability Zones are isolated data centers within a Region, each with independent power, cooling, and networking, so a multi-AZ deployment keeps the application available if a single AZ fails. However, a regional disaster—such as a large-scale earthquake, flood, or utility grid failure—can affect every AZ in that Region simultaneously. Thus, multi-AZ redundancy is a high-availability measure, not a disaster recovery solution, because it never provides geographic separation.

• ✓

  Deploy the application in multiple AWS Regions with Route 53 failover routing

  Why this is correct

  Deploying the application in multiple AWS Regions and attaching Amazon Route 53 failover routing creates a primary/secondary architecture where Route 53 health checks continuously monitor the primary endpoint. When the health check fails, Route 53 automatically responds to DNS queries with the secondary Region's endpoint, instantly shifting traffic away from the impacted Region. Because each AWS Region is completely independent—with its own data centers, power grid, and network—this design offers true disaster recovery, allowing the application to remain reachable even if an entire Region becomes unavailable.

• ✗

  Use Reserved Instances in a single Region for guaranteed capacity

  Why it's wrong here

  Reserved Instances are a billing and pricing commitment that gives you a discounted hourly rate in exchange for a one- or three-year term, and, if you choose a zonal reservation, they can also reserve compute capacity in a specific Availability Zone. However, they are not a deployment or architecture decision; they do not place any workload in another Region or provide any automatic failover capability. If the Region hosting the instance fails, the Reserved Instance still exists but is useless because the physical instance in that Region is unavailable—so this option is entirely unrelated to disaster recovery.

• ✗

  Enable S3 versioning in a single Region

  Why it's wrong here

  S3 versioning allows you to keep multiple versions of an object within the same bucket, which protects against accidental deletion or overwrite by restoring an earlier version. But every version is stored in the same S3 bucket and in the same AWS Region as the original object, so no data is copied to another geographic location. If that Region has a catastrophic outage, the bucket and all its versions become inaccessible, meaning versioning provides data-resilience within a Region, not cross-Region disaster recovery.

Go deeper

Related to this question