Free CompTIA Cloud+ CV0-003 Practice Test

Retention refers to the length of time that backup copies are kept before they are deleted or archived to comply with the organization's data retention policy. It is an essential part of a backup strategy because it dictates how long the data can be recovered from backups after the original data is altered or deleted. Answers referring to the frequency of backups (how often backups are performed) or the 3-2-1 rule (a strategy involving multiple copies and formats of data storage) do not directly pertain to the length of time backups are kept, thus are incorrect in this context.

'Costs' is the correct answer because this metric is specifically used to track the financial aspect of resource utilization, helping organizations understand their spending on cloud services. Chargebacks and showbacks are methods of allocating these costs back to the departments or customers responsible for incurring them. Other metrics, like 'Capacity' and 'Connectivity', involve the technical aspects of resource usage and network performance respectively, and do not directly address financial tracking, making them incorrect choices for this question.

A serverless computing model is ideal for high-volume, event-driven applications because it abstracts the underlying infrastructure away from the developer, automatically handles scaling to meet the number of requests, and is cost-efficient as it is typically billed based on the number of executions. The other options, such as deploying on virtual machines or using PaaS, involve more overhead in terms of infrastructure management and may not handle rapid scaling as effectively as serverless.

A Configuration Management Database (CMDB) is used to maintain information about hardware and software assets (commonly referred to as Configuration Items or CIs) and their relationships. This helps organizations understand the relationships between these assets and provides a structured way of tracking their configurations, which is essential for troubleshooting, change management, and compliance with regulations.

In a cross-service migration, it is essential to understand the compatibility between services, particularly when migrating from one SaaS provider to another. Compatibility issues may arise due to differences in features, protocols, or data formats between the services. Therefore, ensuring that the new service supports all the necessary features and can handle data from the old service is crucial for a smooth transition. Other options, such as account permissions or hypervisor compatibilities, are less relevant for SaaS migrations, as these aspects are generally managed by the service provider.

This statement is false because LDAP, in its basic form, does not guarantee the encryption of data in transit. LDAP transmits data in plaintext by default, which can be intercepted and read by unauthorized parties. To secure LDAP communication, one must use LDAP over SSL (LDAPS) or start a Transport Layer Security (TLS) session over the standard LDAP connection to encrypt the data in transit. Therefore, additional configuration or the use of supplementary protocols is necessary to ensure data encryption with LDAP.

The correct answer is 'Cold storage' because this type of storage tier is designed for data that is infrequently accessed and tolerates longer retrieval times, making it cost-effective for long-term storage needs. 'Hot storage' is incorrect as it is meant for frequently accessed data and comes with a higher cost. 'Multi-regional storage' relates to data availability across regions and doesn't imply lower costs for long-term storage. 'Glacier' is a specific service offered by AWS and not a storage tier category, which may mislead as the correct generalized choice for the scenario given.

The correct answer is The ping command, since it sends ICMP echo requests to the target host and listens for ICMP echo replies. This process allows the administrator to assess if the host is reachable and the round-trip time for the packet. Other commands listed might be used for different purposes; for instance, The traceroute command would show the path taken by packets to reach the destination, The netstat command displays network connections, routing tables, interface statistics, masquerade connections, and multicast memberships, and The nslookup command is used to query the DNS to obtain domain name or IP address mapping.

The correct answer is 'VM-Host Affinity'. This rule will ensure that the VMs processing sensitive data are bound to a particular subset of hosts that are dedicated for this purpose and do not run on the same physical hosts as VMs handling less sensitive data. 'VM-VM Anti-Affinity', though close, is incorrect because it would only prevent the VMs from residing on the same host but doesn't prevent them from sharing the host with other non-related VMs. 'Host-Host Affinity' is not a legitimate rule in the context of VM placement strategies. 'VM-Host Anti-Affinity' is also incorrect, as this would prevent the sensitive VMs from running on the specified hosts, the opposite of the requirement.

A Web Application Firewall (WAF) is designed to monitor, filter, and block harmful traffic to and from a web application. It specifically looks for patterns and attacks that could compromise a web application, such as SQL injection and cross-site scripting, which are common vulnerabilities exploited by attackers.

The public cloud model is best suited for the company's needs because it provides resources and services that are hosted off-premises and managed by the cloud service provider. This offers the required elasticity and pay-as-you-go pricing structure. The private cloud model, while it offers greater control and security, would still involve investment in infrastructure and cannot offer the same level of elasticity and cost efficiency for public-facing services. Hybrid models incorporate elements of both public and private clouds and may be overkill for a company simply looking to extend IT capabilities without the need for data center investments or integration with on-premises resources. Community clouds cater to specific groups and are not necessarily optimized for public-facing services or the flexible cost models the scenario describes.

Vertical scaling, also known as 'scaling up', involves adding resources such as CPU and memory to an existing server or virtual machine. It does not require changing the application code or adding more instances, which distinguishes it from horizontal scaling, also known as 'scaling out', that involves adding more servers to handle the load. Elasticity refers to the automated process of scaling resources to match demand, but does not specify which type of scaling is used. Throughput optimization is not a scaling method but rather a concept of maximizing the rate of processing data.

Hardware requirements are directly related to the allocation of physical resources such as CPU, memory, and storage in a cloud environment. Capacity planning must account for these resources to ensure the infrastructure can handle the expected load. Other options such as 'Business need analysis' and 'Trend analysis' are important considerations but do not directly pertain to the allocation of physical resources. 'Licensing' impacts software accessibility and cost but not the physical resource allocation.

Auto-scaling policies that adjust resources automatically in response to the web traffic provide the most effective means to handle varying load, such as peak usage times, ensuring that service availability is maintained without manual intervention. Workload distribution can enhance performance but may not automatically adjust to traffic spikes. A cold site provides a backup in case of a complete site failure and won't help with immediate traffic load. Biannual failover testing is important for disaster recovery preparedness but does not address the immediacy of peak load times.

Auto-scaling is the correct answer because it enables a cloud environment's compute resources to automatically scale up or down based on the current demand. This is particularly useful for scenarios like sales events, where traffic can unpredictably surge, and manual scaling might not be timely or efficient. Horizontal scaling involves adding more instances of the same type, which is what auto-scaling does. Vertical scaling, while sometimes useful, involves adding more power (CPU, RAM) to the existing instances, which has its limits and can't be done on-the-fly as easily as horizontal scaling. Cloud bursting could handle extra load, but it is a more complex solution that involves spilling over into another cloud provider's space, rather than scaling within the same environment; usually, this would be used when a private cloud's resources are temporarily insufficient.