Free COMPTIA Cloud Essentials+ CLO-002 Actual Exam Questions - Question 10 Discussion

E imo, geo-redundancy is a must for availability. Also D, zones help isolate failures locally. Locality (C) is more about latency than pure availability, so I’d skip that one.

It’s definitely D and E again for me. Zones are about isolating failures within a region to keep services up, and geo-redundancy spreads data across regions to handle bigger outages. Options like resource tagging or auto-scaling don’t really fit the availability angle—they’re more about management or performance scaling. Locality is more about compliance and latency, not availability directly, so that’s why I’d rule out C even though it feels close.

I’m thinking C and E could make sense since locality impacts where data lives and geo-redundancy helps with availability across regions. Not sure if zones here are just regional or broader though.

D/E for sure, zones and geo-redundancy are classic availability factors.

It’s E and D, since zones and geo-redundancy directly help keep data accessible.

Excluding B since data sovereignty is more legal, not about uptime. D and E fit availability better.

I’m thinking A and F can be ruled out since tagging and scaling don’t directly impact whether data is available after failures. B and C feel more compliance and latency-related, so yeah, D and E seem most about availability. But could locality (C) also indirectly affect it?

Maybe E and D. Geo-redundancy (E) ensures data isn’t lost if one region fails, and zones (D) isolate faults. B and C seem more about legal or performance issues, not direct availability.

It’s D and E for sure. Zones help keep services up if one area goes down, and geo-redundancy spreads data across places so it’s not lost. Locality (C) is more about latency and performance, not directly availability. Data sovereignty (B) deals with legal rules, which doesn’t guarantee data is always accessible. Resource tagging (A) and auto-scaling (F) don’t fit availability either since they’re about management and scalability, not keeping data online.

It’s D and E, they’re about backup and zones for availability.