CompTIA Updated CV0-003 Exam Questions and Answers by jennifer

The 3-2-1 backup policy states that there should be three copies of data, stored on two different media, with one copy being off-site. The current backup solution only has one copy of data on one media (the on-site storage server). To comply with the 3-2-1 policy, the systems administrator should configure an off-site storage server for backups, which will provide another copy of data on a different media and location. Reference: CompTIA Cloud+ Certification Exam Objectives, Domain 3.0 Maintenance, Objective 3.2 Given a scenario, implement backup, restore, disaster recovery and business continuity measures.

The most likely causes of the issue where the new asynchronous workflow fails to create 50 VMs at once in the public cloud are insufficient storage and expired API token. Insufficient storage means that there is not enough disk space available in the public cloud to accommodate all the VMs that are being created simultaneously. This could result in errors or failures during the provisioning process. Expired API token means that the authentication credential that is used by the workflow to communicate with the public cloud service has expired or become invalid. This could result in errors or failures during the API calls or requests. Reference: CompTIA Cloud+ Certification Exam Objectives, Domain 4.0 Troubleshooting, Objective 4.5 Given a scenario, troubleshoot automation/orchestration issues.

Scalability is the ability of a system to handle increasing or decreasing demand by adding or removing resources accordingly. According to the web search results, scalability is one of the main benefits of using containers in a cloud environment, as containers are lightweight, portable, and independent units of software that can run on any compatible host . A containerized cluster is a group of hosts that run multiple containers and share resources and services. A containerized cluster can scale up or down easily by adding or removing hosts or containers as needed, without affecting the functionality or performance of the applications .

MFA (Multi-Factor Authentication) is a security technique that requires the user to present two or more pieces of evidence to prove their identity when they try to access a system or an application. For example, a password and a physical token, or a fingerprint and a one-time code. MFA can improve the company’s security posture by preventing unauthorized access even if the password or single-factor authentication is compromised, as the attacker would also need to have the other factors to log in. According to the web search results, MFA can prevent 99.9% of account attacks1.

SSO (Single Sign-On) is a system that allows the user to use one set of login credentials to access multiple systems and applications that previously may have each required their own logins. SSO can improve productivity and user convenience, but it does not replace MFA. In fact, SSO works in conjunction with MFA, as it can enforce MFA for all the systems and applications that are integrated with SSO2. Therefore, implementing SSO does not mean that MFA is not needed.