Free COMPTIA Cloud Essentials+ CLO-002 Actual Exam Questions

A/C? Disaster recovery is about bouncing back after a failure, but just having multiple copies across places sounds more like redundancy to me, especially if they don’t mention failover or recovery plans.

Maybe C. Redundancy covers having multiple copies or instances of resources spread out to avoid a single point of failure, which fits replicating in several geographic locations. Disaster recovery is more about the overall plan and steps to recover after an incident, not just the replication itself. Data sovereignty is about legal rules on where data is stored, so that doesn’t really fit here. Deduplication is about cutting down on duplicate data, so that’s off too.

Makes sense to rule out A and B right away—HTTPS is for web traffic, and RDP is mostly for Windows machines. Between C and D, SSH (C) is definitely the standard for secure remote terminal access on Linux, while VNC is more of a remote desktop tool. So, going with C seems straightforward here.

Probably C, since SSH is the standard secure way to log into Linux servers remotely.

I get why a pilot seems useful, but I think B, feasibility study, works better here. Since they already did an initial assessment, a feasibility study can summarize if the project is actually doable and worth investment. It’s a solid report for management to understand risks and benefits without jumping straight to execution. Plus, projects often need management buy-in based on feasibility before going forward with pilots or detailed plans.

I’m thinking that a pilot (D) might be a strong choice here since it shows management a working example or proof of concept, not just plans or studies. It gives something tangible to evaluate rather than just documents. But then again, is a pilot always feasible before management’s buy-in? If resources aren’t approved yet, maybe presenting a project charter (A) or feasibility study (B) is more realistic. What’s everyone’s take on whether management needs something concrete first or if they just want the plan laid out?

It’s A because putting all your eggs in one cloud basket means you’re stuck with that provider’s tools and pricing, making it tough to switch later. Data portability (B) is part of the problem but not the biggest risk itself.

Option A makes the most sense since relying on one provider limits flexibility.

E imo, because RPO directly measures the acceptable amount of data loss. RTO (A) deals with downtime length, so it doesn’t really answer the data loss part here.

Option E, RPO is about how much data you can afford to lose, not downtime.

Probably C here. Object storage is made to handle large amounts of unstructured data and is often used for long-term retention because it’s highly durable and can replicate data across multiple locations. That makes it more reliable than file or block storage for backups over time. Solid state storage (A) is fast but not really meant for long-term archival due to cost and wear. File storage (D) is traditional but less scalable and durable compared to object storage, especially at scale. Block storage (B) is usually more for performance-sensitive data, not long-term backup.

Option C is best since object storage offers high durability and scalability for backups.

A imo, vendor lock-in is obvious; E too, integration problems are common without open standards.

A/E for sure, lock-in and integration are classic pitfalls without open standards.

A. This makes the most sense since identity and access control policies define who can do what in the system. B is more about classifying data, which doesn’t directly help with user permissions. C focuses on changes to systems, not roles. D might help with procedures but won’t clarify access rights. So for understanding privileges specifically, A is the best fit here.

I’m with the idea that A fits best here, but thinking from another angle: B and C deal more with data and changes, not directly with user roles or privileges. D, the SOPs, usually cover routine tasks and procedures rather than detailed access rights. So A makes the most sense because it’s specifically about managing identities and their access levels within the company.

It’s A because regression testing is designed to catch any issues caused by new code affecting old features, unlike stress or load tests which are all about system performance under pressure.

Makes sense to go with A for regression testing here. Stress and load focus on performance under heavy use, which doesn’t fit the goal. Quality (D) is too vague and doesn’t pinpoint the need to check old functions after new ones are added. Regression directly targets that.

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.

C, because no app changes and tight deadline mean quick move as-is.

Option B could make sense if they want to move apps gradually to reduce risk, but with the end-of-month deadline, it might be too slow compared to lift and shift.

A, because RDP is designed specifically for remote desktop access.

Maybe D makes more sense if we think about modern enterprise setups where VDIs are often delivered through a web client for easier management and security. RDP could be risky if exposed directly to the internet without extra layers like a gateway. VPN (B) just connects you to the network but doesn't provide the desktop itself, and SSH (C) is mostly for command line stuff, so that’s out for a Windows GUI. So, if the question hints at secure, scalable access, HTTPS might be the better fit.

Actually, it’s definitely not A or C because maintenance agreements usually cover updates and repairs, not response times. The key here is the vendor promising a response time to the client, which is exactly what SLAs cover. Managed service agreements might include this but are broader contracts, so D fits best as it specifically defines service expectations like incident response times from the vendor to the client.

It’s D because SLAs are all about the external promises a vendor makes to the client, like guaranteed response times. The two-hour response is a classic SLA metric, not just internal coordination.

Probably D, since showing costs without forcing departments to pay might avoid internal disputes, especially if the tagging or billing systems aren’t fully mature yet. It’s a softer way to raise awareness first.

It’s D because showback gives departments visibility into their cloud usage without the conflict of actual billing, which might be better if tagging or precise allocation isn’t fully reliable yet.

C. Availability is what guarantees the system stays online and accessible. Without that, scalability or elasticity won’t matter because users can’t connect at all.

I get why availability (C) is a top pick since it’s about uptime. But what about scalability (B)? If the system suddenly needs more resources or users, a scalable CSP can prevent downtime by handling those spikes smoothly. Without that, availability might not mean much if the service chokes under load. Could scalability actually be just as important here for keeping critical servers accessible during peak times?