Free Practice Questions for CompTIA CV0-004 Exam

A container image best supports continuous deployment because it packages the application along with its required libraries, dependencies, and configuration into a portable, immutable artifact. In the CompTIA Cloud+ (CV0-004) objectives related to automation, orchestration, and application deployment, containers enable consistent releases across environments (dev, test, staging, production) without repeatedly performing traditional “clean installs” on servers. Instead of reinstalling software and dependencies on every iteration, CI/CD pipelines build a new image version, push it to a registry, and deploy it through an orchestrator (such as Kubernetes). Rollouts can be performed using rolling updates or blue/green deployments, and rollbacks are simplified by redeploying a previous image tag.

A Debian package still depends on the underlying OS state and can vary between systems due to drift. Version management (source control) tracks code changes but does not solve runtime environment consistency by itself. A bare-metal server typically requires more manual provisioning and configuration management. Therefore, container images are the most direct solution for rapid, repeatable deployments with minimal overhead and high consistency.

Blue-green deployment is the strategy that can eliminate downtime, accelerate deployment, and remain cost-efficient. It involves running two identical production environments, only one of which is live at any given time (blue or green). When it's time to deploy, the new version is released to the inactive environment (green), which is then thoroughly tested. Once ready, the traffic is switched over, making the green environment live.

Deployment strategies and their impact on operations are a significant topic within the CompTIA Cloud+ examination objectives.

This incident occurred because the logging service account had excessive privileges (full directory administrator) and was able to add itself to a privileged group that grants interactive access to the virtual network console, then delete a production VM. In the CompTIA Cloud+ (CV0-004) security objectives, the primary control to prevent recurrence is enforcing least privilege using role-based access control (RBAC) and properly scoping permissions for service accounts. The logging account should be granted only the minimum rights required to collect and aggregate logs (for example, read access to resources and write access to a logging destination), and it should not have broad directory admin or console administration capabilities.

While enabling MFA (A) and using strong passwords (B) are good compensating controls, they do not correct the underlying authorization problem—an over-privileged account can still cause significant damage even if it authenticates securely. Disabling RDP (C) is unrelated to the console/API-based privilege escalation shown. Creating a scoped administrative role (D) directly reduces blast radius and prevents similar privilege misuse.

For a web application accessed by a large number of employees daily during the same time frame, the best configuration approach to resolve performance issues is to scale horizontally based on a schedule. This means adding more server instances to handle the load during known peak times.

Cloud resource scaling strategies, including scheduled horizontal scaling, are discussed in the CompTIA Cloud+ curriculum under cloud management and optimization.

Since the cloud administrator can access the application from the same site but users cannot, it suggests a possible issue with the network routing. The routing table may need to be updated to ensure that traffic from the users' location is correctly directed to the new location of the remotely hosted application after the migration. References: CompTIA Network+ Certification Study Guide by Glen E. Clarke.

The strongest control to reduce immediate data-loss risk in this scenario is to remove or restrict access to the source code repository for the departing employee. Cloud+ (CV0-004) security objectives emphasize identity and access management (IAM), least privilege, and offboarding procedures as core controls to prevent unauthorized data access. Once an employee has provided notice—especially when suspicious activity is detected—organizations should rapidly adjust permissions by disabling accounts, removing group memberships, revoking tokens/SSH keys, and limiting repository access to only what is operationally required (or eliminating it entirely). This directly stops continued exfiltration from the primary source.

A policy against password sharing (A) is important but does not address an insider with valid access. Blocking an IP (C) is brittle because the user can change networks or use VPNs, and it doesn’t fix the authorization issue. Cutting all internet access (D) is overly disruptive and may not prevent local syncing or alternative paths. Blocking USB transfers (E) doesn’t stop cloud downloads. Therefore, access removal/restriction to the repository is the most effective mitigation.

Based on the SLA requirements and the information provided in the diagram:

For the Hypervisor:

Slot A fiber channel card:

Port 1 link speed should be set to 16 Gbps since it's connected to Fabric switch A which supports 16 Gbps.

Port 2 link speed should be set to 8 Gbps because it's connected to Fabric switch B which supports up to 8 Gbps.

Slot B fiber channel card:

Port 1 link speed should be set to 16 Gbps since it's connected to Fabric switch A which supports 16 Gbps.

Port 2 link speed should be set to 8 Gbps because it's connected to Fabric switch B which supports up to 8 Gbps.

Rehosting, often referred to as "lift-and-shift," is the process of migrating an application or workload to the cloud without modifying it. This approach is suitable when there are timing constraints that prevent making changes to the application prior to migration. Rehosting can be the quickest migration strategy since it involves moving the existing applications to the cloud with minimal changes.

When a web application is accessible locally via an IP address but not via the internet, the issue likely lies with the Domain Name System (DNS). DNS is responsible for translating domain names into IP addresses. A misconfiguration in DNS records or failure in DNS resolution can prevent users from accessing the application through its domain name, even though the application itself is running and accessible via its direct IP address.

In the CompTIA Cloud+ curriculum, understanding cloud concepts and networking fundamentals, including DNS, is crucial for troubleshooting and ensuring applications are accessible and perform optimally in cloud environments.

A Content Delivery Network (CDN) is the service that will help reduce latency for a static website accessed globally. CDNs distribute content across multiple geographically dispersed servers, allowing users to connect to a server that is closer to them, thereby reducing the time it takes to load the website.

The use of CDNs is a common practice to enhance global access and improve user experience, as covered under Cloud Concepts in the CompTIA Cloud+ certification.