For a new web application that requires a relational database management system with minimal operational overhead, the company should choose a managed SQL database on the cloud. Managed databases provide automated backups, patching, and other management tasks, reducing the administrative burden.
The use of managed services, like managed databases, to minimize operational overhead is a strategic decision in cloud computing covered in CompTIA Cloud+.

Serverless functions are ideal for running scripted tasks on a schedule because they can be triggered by events, run the task, and then shut down, incurring costs only for the actual compute time used. This eliminates the need for a continuously running server and is optimal for sporadic or scheduled tasks.
References: CompTIA Cloud+ Certification Study Guide (Exam CV0-004) by Scott Wilson and Eric Vanderburg.

This scenario describes vendor lock-in, which occurs when an organization becomes highly dependent on a specific cloud provider's proprietary services, architectures, APIs, or managed features, making migration to another provider difficult, costly, or technically impractical. In the CompTIA Cloud+ (CV0-004) objectives related to cloud design, risk management, and interoperability, vendor lock-in is a known risk that can impact long-term cost control, flexibility, and negotiating power. When applications are built around provider- specific components (such as proprietary databases, messaging services, identity integrations, serverless runtimes, or monitoring tools), moving to another provider often requires major redesign, refactoring, or data transformation-far beyond a simple "lift and shift." Option A (PaaS) is a service model and may contribute to lock-in, but it is not the situation described. Option B (oversubscription) refers to allocating more virtual resources than physically available. Option D (regulatory compliance) relates to meeting legal/industry requirements. Because the key issue is that reliance on provider-specific features prevents feasible migration, vendor lock-in is the best answer.

A hot site is a disaster recovery strategy that is cost-effective, minimizes data loss, and allows for the fastest recovery time in case of a disaster. It is an exact replica of the original site of the organization, with full computer systems as well as near-complete backups of user data. Hot sites are operational 24/7 and can take over functionality from the primary site immediately or with minimal delay. References: CompTIA Cloud+ Study Guide (Exam CV0-004) - Chapter on Disaster Recovery

A branch is the best option because it allows a development team to maintain separate lines of development from a shared codebase. In CompTIA Cloud+ (CV0-004) objectives related to DevOps practices, version control, and configuration management, branching strategies are used to support multiple feature sets, releases, and customer-specific customizations without disrupting the primary (main) code line. For example, a team can create a branch per client, per release version, or per feature set, enabling isolated development and testing while still inheriting common fixes and improvements from the main branch when appropriate.
This is especially useful when different customers require different configurations or optional modules in the same product.
A commit is simply a recorded change to code within a branch; it doesn't provide separation for different client versions by itself. A push sends committed changes to a remote repository but also doesn't address parallel code management. A merge combines branches back together, which is often done after changes are validated, but it is not the mechanism for maintaining separate client-specific variations. Therefore, branching best meets the requirement.