CV0-004 Exam Dumps : CompTIA Cloud+ (V4)

A container image is used to deliver code quickly and efficiently across the development, test, and production environments. Container images are lightweight, standalone, executable software packages that include everything needed to run a piece of software, including the code, runtime, system tools, libraries, and settings. References: CompTIA Cloud+ Study Guide (Exam CV0-004) - Chapter on Cloud Deployment Methods

The connectivity issue between the application server and the MySQL database server in different subnets is likely due to the MySQL Server Stateful Firewall's inbound rules. The application server has an IP of 192.168.1.10, but the MySQL server's inbound rules only permit IP 192.168.1.10/32 on port 3306. This rule allows only a single IP address (192.168.1.10) to communicate on port 3306, which is typical for MySQL. However, if the application server's IP is not 192.168.1.10 or the application is trying to communicate on a different port, it would be blocked. To fix the communication issue, the cloud engineer should address the inbound rules on the MySQL Server Stateful Firewall to ensure that the application server’s IP address and the required port are allowed. References: Based on the information provided in the question and general networking principles.

When an organization can predict demand spikes (such as seasonal sales), the most cost-effective approach is to use scheduled scaling—a scaling configuration tied to a known timeline. In the CompTIA Cloud+ (CV0-004) objectives covering elasticity, scaling strategies, and cost optimization, scheduled scaling allows the business to increase capacity shortly before the surge begins and reduce it immediately after the event ends. This minimizes cost by ensuring resources run only for the required window, while still maintaining performance and availability during peak traffic.

Option A (least-connections) improves how traffic is distributed but does not add capacity; it cannot prevent resource exhaustion if the backend pool is undersized. Option C (reconfiguring to have more resources—vertical scaling) can help performance but often increases cost continuously and may introduce downtime or scaling limits. Option D (deploying additional compute in advance) can meet the requirement, but it may waste money if instances remain overprovisioned longer than necessary. Therefore, enabling a scheduled scaling configuration for the identified timeline best meets the need at minimal cost.