Free COMPTIA Cloud+ CV0-004 Actual Exam Questions

B. The question focuses on accessing data, so having the cloud content read aloud makes the most direct impact for someone visually impaired. OCR (A) might help if the data is all images, but since it just converts stuff into text, it’s not really an assistive tech by itself. Text-to-voice actually delivers the info in an accessible way, which is the main goal here. Also, since cloud data often comes in text form already, going straight to text-to-voice makes more sense for practical everyday use.

B, because hearing the data is the key benefit for visually impaired users.

Thinking about external users, moving from on-premises to cloud (C) seems logical since cloud scales better for public access compared to on-prem. But D could be tricky if user access isn’t straightforward.

C, cloud offers better external user access for on-prem apps.

Maybe A makes the most sense since it highlights the core difference: public repos are open access, while private ones need credentials. The other options seem more about features or policies that aren’t universal.

It’s A. Public repos let anyone pull images without signing in, while private ones always need some kind of permission. B is less clear since browsing features can vary a lot depending on the service.

It’s D because rehosting doesn’t touch the app, perfect for tight deadlines.

This one definitely feels like D again. Rehosting is basically moving the whole thing as-is to the cloud, so no need to mess with the app before migration. Since the question says no changes can be made upfront, that rules out B and C for sure. A doesn’t fit because you’re not retiring, just migrating. So D is the simplest and fastest approach here.

C/B? Could be hitting service quotas in certain locations since those limits can vary by region, but the availability of services (B) is also a strong contender if some regions don’t support these VDIs yet.

C/D? While regional availability (B) makes sense, I’m thinking quotas (C) could be the culprit if the company hit limits in some specific locations but not others. Deprecation (D) feels less likely since it wouldn’t usually cause random regional failures, more like a global issue. Partial outages (A) seem temporary and less selective by region too. So, I’d check the quotas next just to be sure.

D, since microservices naturally break down apps into smaller, independent parts.

It’s D because microservices let teams work independently on different components, unlike hybrid cloud which is just about where stuff runs, not how it’s architected.

B imo, since ACLs can enforce strict IP-based rules, blocking any requests not coming from the corporate VPN’s IP range. While a VPC defines the network boundary, it doesn’t automatically restrict access without specific configurations. ACLs give that granular control to deny direct public internet traffic effectively. WAF and SSH don’t really fit here since WAF is more about web app protection and SSH is just a protocol, not a network access control mechanism.

It’s B because ACLs can explicitly block traffic from outside the VPN IP range, which directly prevents public internet access regardless of VPC setup. That’s more precise than just relying on a VPC alone.

It’s C, because without proper retention, backups might get deleted too soon.

A imo, the location of backups matters a lot for long-term reporting, especially if regulations require storing data in specific geographic or secure sites. Even if retention is set, if backups aren’t stored properly, it might not meet compliance. Changing retention without considering where backups are kept could be pointless in some cases.

Probably A. Network flow logs directly show traffic volume and sources, so they’re the best way to spot DDoS activity compared to other logs that don’t focus on network patterns as clearly.

It’s C because cloud provider event logs often include security alerts and infrastructure-level events that can hint at unusual traffic patterns or resource exhaustion from DDoS. They provide a broader perspective than just instance-level logs and can also show automated mitigation actions or scaling events triggered by the attack. While network flow logs (A) are good for detailed traffic data, the cloud provider logs give context on what’s happening across the entire service stack, which is vital for spotting and responding to DDoS threats early.

Probably C here too. Most payment processors expose REST APIs since they’re easier to use and widely supported. A (RPC over SSL) feels outdated and less common for this kind of integration, plus it’s not as straightforward as REST. D (secure websockets) is more for persistent connections, like real-time updates, not typical for payment processing. B is definitely out since SQL doesn’t handle external service communication. So C makes the most sense for securely exchanging payment info between systems.

I’m also crossing off B since SQL transactions deal with database consistency rather than connecting to outside services. D, secure web sockets, are more for real-time communication but not typically used for payment processing integration. A, RPC over SSL, might handle secure calls but is less common and might be harder to maintain or scale compared to REST APIs. So C seems like the straightforward choice, as it’s designed for stateless communication and widely adopted in payment integrations. Does anyone think RPC could still have an edge here in specific scenarios?

Option D also matches the max link speed and RAID 5 requirement, plus redundant paths. It might be a better fit since it doesn’t ignore the RAID 5 rule like C does, even if IOPS are a bit lower.

I think option C is best because it hits the max link speed and has redundant fabric paths, which the SLA demands. RAID 5 in B would definitely drag down the IOPS below the 14,000 target.

B works because it includes strict access control plus consistent monitoring.

I’d rule out anything that doesn’t clearly support continuous monitoring since low risk tolerance means they can’t miss anomalies. So options without integrated anomaly detection or logging should be off the table.

For the web server CPU, average at 75% plus 20% overhead rounds nicely to 90%, so C.

Looking at the web server’s CPU usage, the average seems close to 75%, so with 20% overhead it hits around 90%, which matches option C’s 90%. For memory, the average looks near 4GB, so adding 20% brings it just over 4.8GB, rounding up to 5GB fits option B. For the DB server, I don’t think the overhead applies only to memory; CPU usage should get the same treatment. The average CPU usage hovers around 55%, and adding 20% overhead gets about 66%, which matches option B’s 65%. For memory, the average looks about 16GB, so option B’s 20GB is the best fit.

Firewall 2 looks suspicious since it might not allow return traffic from the cloud servers. Also, Router 2 probably needs updated routes for the new app servers; static routes could be causing dropped packets.

Are we sure both firewalls are correctly allowing traffic from the cloud app servers back through the VPN? Seems like a common spot to block return traffic. Also, does the VPN tunnel support bi-directional routing properly? The weighted round-robin DNS should distribute requests evenly but if only 20% succeed, maybe routing or firewall rules on either side are preventing some connections. Do we have logs showing where packets get dropped? That’d help narrow it down before picking options.

I think option C makes the most sense. The WAF is likely blocking legitimate login traffic due to strict rules, so updating the WAF to allow that traffic would fix the problem.

I noticed in the WAF logs that there’s a lot of blocked traffic related to SQL injection rules. Since login forms often include input fields that might trigger false positives, disabling or tweaking those specific SQLi rules like in option C makes sense. Also, the app servers and network devices seem fine, so it points more toward WAF filtering. Removing or modifying those strict rules for the login endpoint should get the prompt loading again without compromising overall security.