CLO-002 Practice Questions

Redundancy is a term that describes the approach of replicating cloud resources in several different

geographic locations. Redundancy can increase the availability, reliability, and performance of cloud

services by providing backup or alternative resources in case of failures, disasters, or high demand.

Redundancy can also reduce latency by serving users from the nearest location. Redundancy can be

implemented at different levels, such as data, network, server, or application. For example, a geo-

distributed database is a type of redundancy that offers asynchronous replication across two data

centers or cloud regions1. Redundancy is different from disaster recovery, deduplication, and data

sovereignty, which are other terms related to cloud computing. Disaster recovery is a term that

describes the process of restoring normal operations after a disaster or disruption. Disaster recovery

can involve using redundant resources, but it is not the same as redundancy. Deduplication is a term

that describes the technique of eliminating redundant copies of data from a storage device, which

can reduce the storage space required and improve the efficiency of the storage system.

Deduplication does not involve replicating cloud resources in different locations, but rather

consolidating and removing duplicates. Data sovereignty is a term that describes the legal and

regulatory aspects of data storage and processing in different geographic locations. Data sovereignty

can affect the choice of cloud regions and providers, as some countries or regions may have specific

laws or regulations that govern the access, transfer, and protection of data. Data sovereignty does

not imply redundancy, but rather compliance. Therefore, the correct term for replicating cloud

resources in several different geographic locations is redundancy. Reference: Geography and regions

| Documentation | Google Cloud, What is Database Geo-Distribution? - Yugabyte, Georedundancy:

geographical redundancy | Stackscale.

Secure Shell (SSH) is a protocol that allows secure and encrypted communication between a client

and a server over a network. SSH can be used to log in to a remote Linux server that is hosted in a

public cloud, as well as to execute commands, transfer files, or tunnel other protocols. SSH uses

public-key cryptography to authenticate the client and the server, and to encrypt the data exchanged

between them. SSH is widely supported by most Linux distributions and cloud providers, and it can

be accessed by various tools, such as PuTTY, OpenSSH, or WinSCP. SSH is more secure and reliable

than other protocols, such as RDP, VNC, or Telnet, which may not support encryption, authentication,

or compression. Reference: CompTIA Cloud Essentials+ Certification Exam Objectives1, CompTIA

Cloud Essentials+ Study Guide, Chapter 6: Cloud Connectivity and Load Balancing2, How To Use The

Remote Desktop Protocol To Connect To A Linux Server2

A project charter is a document that defines the scope, objectives, and stakeholders of a project. It

also provides a high-level overview of the project’s benefits, risks, assumptions, constraints, and

deliverables. A project charter is used to gain the support and approval of upper management and

other key stakeholders before initiating a project. A project charter is one of the outputs of the cloud

assessment process, which involves evaluating the feasibility, suitability, and readiness of an

organization to adopt cloud services. Reference: CompTIA Cloud Essentials+ (CLO-002) Study Guide,

Chapter 4: Cloud Assessment, Section 4.1: Cloud Assessment Process, page 9712; CompTIA Cloud

Essentials+ Certification Exam Objectives, Objective 4.1: Given a scenario, analyze and report the

outputs of a cloud assessment, page 143

Vendor lock-in is the type of risk that is most likely to be associated with moving all data to one

cloud provider. Vendor lock-in refers to the situation where a customer is dependent on a particular

vendor’s products and services to such an extent that switching to another vendor becomes difficult,

time-consuming, or expensive. Vendor lock-in can limit the customer’s flexibility, choice, and control

over their cloud environment, and expose them to potential issues such as price increases, service

degradation, security breaches, or compliance violations. Vendor lock-in can also prevent the

customer from taking advantage of new technologies, innovations, or opportunities offered by other

vendors. Vendor lock-in can be caused by various factors, such as proprietary formats, standards, or

protocols, lack of interoperability or compatibility, contractual obligations or penalties, or high

switching costs12

Reference: CompTIA Cloud Essentials+ Certification Exam Objectives3, CompTIA Cloud Essentials+

Study Guide, Chapter 2: Business Principles of Cloud Environments2, Moving All Data to One Cloud

Provider: Understanding Risks1

RPO stands for recovery point objective, which is the maximum amount of data loss that a company

can tolerate in the event of a disaster, failure, or disruption. RPO is measured in time, from the point

of the incident to the last valid backup of the data. RPO helps determine how frequently the

company needs to back up its data and how much data it can afford to lose. For example, if a

company has an RPO of one hour, it means that it can lose up to one hour’s worth of data without

causing significant harm to the business. Therefore, it needs to back up its data at least every hour to

meet its RPO.

RPO is different from other metrics such as RTO, TCO, MTTR, and ROI. RTO stands for recovery time

objective, which is the maximum amount of time that a company can tolerate for restoring its data

and resuming its normal operations after a disaster. TCO stands for total cost of ownership, which is

the sum of all the costs associated with acquiring, maintaining, and operating a system or service

over its lifetime. MTTR stands for mean time to repair, which is the average time that it takes to fix a

faulty component or system. ROI stands for return on investment, which is the ratio of the net profit

to the initial cost of a project or investment. Reference: Recovery Point Objective: A Critical Element

of Data Recovery - G2, What is a Recovery Point Objective? RPO Definition + Examples, Cloud

Computing Pricing Models - CompTIA Cloud Essentials+ (CLO-002) Cert Guide

Object storage is a type of cloud storage that stores data as objects, which consist of data, metadata,

and a unique identifier. Object storage is ideal for backing up and retaining data for long periods of

time, as it offers the following benefits:

Scalability: Object storage can store virtually unlimited amounts of data, as objects are stored in a flat

namespace that can span multiple servers, clusters, or regions. Object storage does not have the

limitations of hierarchical file systems or block storage volumes, which can become fragmented or

inefficient as they grow.

Durability: Object storage can ensure high levels of data durability, as objects are replicated across

multiple locations or zones. Object storage also supports versioning, which allows users to keep

multiple versions of the same object and restore them if needed. Object storage can also use erasure

coding, which splits objects into data and parity fragments and distributes them across different

nodes, enabling data recovery in case of failures.

Cost-effectiveness: Object storage can reduce the cost of storing data for long periods of time, as it

typically uses commodity hardware and low-cost disks. Object storage also offers tiered storage

options, which allow users to move data between different performance and price levels based on

their access frequency and retention requirements. For example, users can store data in cold or

archive tiers, which offer lower storage costs but higher retrieval latency and fees.

Solid state storage is a type of storage that uses flash memory chips to store data. Solid state storage

offers high performance, low latency, and low power consumption, but it is also more expensive and

less durable than other types of storage. Solid state storage is more suitable for storing data that

requires frequent and fast access, such as databases, applications, or operating systems, rather than

backing up and retaining data for long periods of time.

Block storage is a type of storage that divides data into fixed-sized blocks and assigns them unique

identifiers. Block storage is commonly used to create storage volumes that can be attached to virtual

machines or servers and act as local disks. Block storage offers high performance, low latency, and

flexibility, but it also has some drawbacks for backing up and retaining data for long periods of time,

such as:

Scalability: Block storage has limited scalability, as storage volumes have a fixed size and capacity

that cannot be easily changed. Block storage also requires more management and maintenance, as

users have to provision, format, mount, and backup storage volumes manually or using scripts.

Durability: Block storage has lower durability, as storage volumes are vulnerable to corruption,

deletion, or failure. Block storage does not support versioning, which means users cannot restore

previous versions of their data. Block storage also does not use erasure coding, which means users

have to rely on RAID or other backup methods to ensure data redundancy and availability.

Cost-effectiveness: Block storage has higher cost, as it typically uses more expensive and power-

hungry disks. Block storage also charges users based on the provisioned size of the storage volumes,

regardless of how much data they actually store. Block storage also incurs additional costs for data

transfer, snapshot, and backup services.

File storage is a type of storage that organizes data into files and folders within a hierarchical file

system. File storage is commonly used to store and share data that can be accessed by multiple users

or applications using standard protocols, such as NFS or SMB. File storage offers simplicity,

compatibility, and convenience, but it also has some limitations for backing up and retaining data for

long periods of time, such as:

Scalability: File storage has limited scalability, as file systems have a maximum number of files and

folders that they can support. File storage also suffers from performance degradation and

inefficiency as file systems grow larger and more complex. File storage also requires more

management and maintenance, as users have to create, delete, move, and backup files and folders

manually or using scripts.

Durability: File storage has lower durability, as files and folders are susceptible to corruption,

deletion, or failure. File storage does not support versioning, which means users cannot restore

previous versions of their data. File storage also does not use erasure coding, which means users

have to rely on RAID or other backup methods to ensure data redundancy and availability.

Cost-effectiveness: File storage has higher cost, as it typically uses more expensive and power-hungry

disks. File storage also charges users based on the provisioned size of the file systems, regardless of

how much data they actually store. File storage also incurs additional costs for data transfer,

snapshot, and backup services. Reference:

CompTIA Cloud Essentials+ CLO-002 Study Guide, Chapter 2: Cloud Concepts, Section 2.5: Cloud

Storage, pages 66-69

6 Types of Backups for Cloud Storage

4 Types of Cloud Backup Services and How to Choose

Cloud or tape for long-term data retention?

How to Set Up Backup Retention to Purge Older Backups

A proprietary SaaS solution is one that uses a specific vendor’s software and platform, which may

not be compatible with other vendors’ solutions or industry standards. This can result in vendor lock-

in, which means that the organization becomes dependent on the vendor and cannot easily switch to

another provider or solution without significant costs or risks. Vendor lock-in can also limit the

organization’s ability to negotiate better terms or prices with the vendor. Integration issues can arise

when the proprietary SaaS solution does not support open standards, which are widely accepted and

interoperable protocols or formats that enable different systems or applications to communicate and

exchange data. Open standards can facilitate integration with other cloud or on-premise solutions, as

well as enhance portability and scalability of the cloud services. If the SaaS solution does not adopt

open standards, the organization may face challenges or limitations in integrating the solution with

its existing or future IT environment, which can affect the functionality, performance, and security of

the cloud services. Reference: CompTIA Cloud Essentials+ Certification Study Guide, Second Edition

(Exam CLO-002), Chapter 2: Cloud Concepts, Section 2.3: Cloud Service Models, p. 62-63.

An identity and access control management policy is a document that defines the roles,

responsibilities, and rules for managing the identities and access rights of users in an

organization1. It specifies how users are authenticated, authorized, and audited when they access

the organization’s resources, such as systems, applications, data, and networks1. An identity and

access control management policy also describes the processes and procedures for creating,

modifying, suspending, and deleting user accounts and privileges, as well as the standards and

guidelines for selecting and managing passwords, tokens, certificates, and other authentication

factors1. An identity and access control management policy can help the systems administrator

understand the user privileges for each role in the company, as it defines the access levels and

permissions that are granted to different types of users, such as employees, contractors, vendors,

partners, and customers1. The policy also outlines the criteria and conditions for granting, changing,

or revoking access rights, based on the principle of least privilege and the need-to-know basis1. By

following the identity and access control management policy, the systems administrator can ensure

that the new user for the human resources department has the appropriate and secure access to the

resources that are relevant to their job function and responsibilities1. Reference: 1: CompTIA Cloud

Essentials+ Certification Study Guide, Second Edition (Exam CLO-002), Chapter 3: Cloud Planning,

Section 3.2: Cloud Adoption, Subsection 3.2.1: Identity and Access Management

Regression testing is the best testing technique to ensure that the existing functionalities are not

compromised by the addition of a new functionality. Regression testing is the type of testing

performed to ensure that a code change in software does not affect the product’s existing

functionality. This ensures that the product functions correctly with new functionality, bug fixes, or

changes to existing features. To validate the impact of the shift, previously executed test cases are re-

executed1. Regression testing can be done manually or by using automated tools. Some of the most

commonly used tools for regression testing are Selenium, WATIR, QTP, RFT, Winrunner, and Silktest2.

Reference: CompTIA Cloud Essentials+ CLO-002 Study Guide, Chapter 5: Cloud Service Operations,

Section 5.3: Cloud Service Testing, p. 217-2181

Cloud data availability is the process of ensuring that data is accessible to end users and applications,

when and where they need it. It defines the degree or extent to which data is readily usable along

with the necessary IT and management procedures, tools and technologies required to enable,

manage and continue to make data available1. Cloud data availability is influenced by several

aspects, such as:

Zones: Zones are logical or physical partitions of a cloud region that have independent power,

cooling, and networking infrastructure. They are designed to isolate failures within a region and

provide high availability and fault tolerance for cloud services and data. For example, Google

Cloud2 and Azure3 offer availability zones that allow users to distribute their resources and data

across multiple zones within a region, ensuring that if one zone experiences an outage, the other

zones can continue to function and serve the data.

Geo-redundancy: Geo-redundancy is the practice of replicating or storing data across multiple

geographic locations or regions. It is intended to improve data availability and durability by

protecting data from regional disasters, network failures, or malicious attacks. For example, Google

Cloud2 and Azure3 offer geo-redundant storage options that allow users to store their data in two or

more regions, ensuring that if one region becomes unavailable, the data can be accessed from

another region.

Resource tagging is the practice of assigning metadata or labels to cloud resources, such as instances,

volumes, or buckets. It is used to organize, manage, and monitor cloud resources and data, but it

does not directly affect data availability.

Data sovereignty is the concept that data is subject to the laws and regulations of the country or

region where it is stored or processed. It is a legal and compliance issue that affects data security,

privacy, and governance, but it does not directly affect data availability.

Locality is the concept that data is stored or processed close to the source or destination of the data.

It is used to optimize data performance, latency, and bandwidth, but it does not directly affect data

availability.

Auto-scaling is the practice of automatically adjusting the amount or type of cloud resources, such as

instances, nodes, or pods, based on the demand or load of the data. It is used to optimize data

efficiency, scalability, and reliability, but it does not directly affect data availability. Reference:

Cloud Storage | Google Cloud

Data Availability: Ensuring Continued Functioning of Business Ops

What are Azure availability zones? | Microsoft Learn

What is Data Availability? - Definition from Techopedia