CompTIA Updated CLO-002 Exam Questions and Answers by fionn

Reserved instances are a type of cloud pricing model that allows customers to reserve a certain amount of cloud resources for a fixed period of time, usually one or three years, and pay a lower rate than the on-demand or pay-as-you-go model. Reserved instances are suitable for workloads that have predictable and stable resource consumption, as they can help customers save up to 75% of the cloud costs compared to the on-demand model1. However, reserved instances also require a long-term commitment and upfront payment, which may reduce the flexibility and scalability of the cloud.

The other options are not likely to help the company reduce the cost of infrastructure:

• Pay-as-you-go: This is a type of cloud pricing model that allows customers to pay only for the resources they use, without any upfront or long-term commitment. Pay-as-you-go is suitable for workloads that have variable and unpredictable resource consumption, as it provides flexibility and scalability. However, pay-as-you-go is also the most expensive cloud pricing model, as it charges a higher rate per unit of resource than the reserved or spot instances models1.
• Spot instances: This is a type of cloud pricing model that allows customers to bid for unused cloud resources at a discounted rate, usually up to 90% lower than the on-demand model1. Spot instances are suitable for workloads that are flexible, interruptible, and not time-sensitive, as they can be terminated at any time by the cloud provider when the demand or price increases. Spot instances can help customers save a lot of money, but they also introduce a high level of uncertainty and risk to the cloud environment.
• Bring your own license: This is a type of cloud pricing model that allows customers to use their existing software licenses on the cloud, instead of purchasing new licenses from the cloud provider. Bring your own license can help customers reduce the software costs, but it does not affect the cost of infrastructure, which is based on the amount and type of cloud resources used2.

References:

• Cloud Pricing Models: On-Demand, Reserved, and Spot Instances
• Bring Your Own License (BYOL) in Cloud Computing

A statement of work (SOW) is a document that outlines the scope of a project, specific deliverables, scheduling, and additional specific details from the client/buyer1. A SOW defines what the service provider will do for the client and how they will do it, as well as the expected outcomes and quality standards2. A SOW is typically used as a supplement to a master service agreement (MSA) or a contract that establishes the general terms and conditions of the business relationship3.

References:

• CompTIA Cloud Essentials CLO-002 Certification Study Guide, Chapter 2: Business Principles of Cloud Environments, page 65
• Statement of Work (SOW): What Is It & How to Write One, The Blueprint
• Master Services Agreement vs Statement Of Work, Difference between MSA & SOW, PandaDoc

Reserved instances are a discount billing concept in which businesses can obtain significant discounts compared to standard on-demand cloud computing prices in return for committing to a specified level of usage1. Reserved instances are not physical instances, but rather a billing discount applied to the use of on-demand instances in the account2. Reserved instances can save up to 75% over equivalent on-demand capacity3. By switching the virtual machines to reserved instances, the analyst can best reduce costs without impacting performance, as long as the application’s usage pattern is predictable and consistent. Decommissioning a virtual machine might affect the performance and availability of the application. Changing to a pay-as-you-go plan might not reduce costs if the application’s usage is high and stable. Converting the application to a SaaS solution might require additional development and migration efforts, which are not feasible in this scenario. References:

• 1: AWS Cost Management & Optimization
• 2: Amazon Elastic Compute Cloud
• 3: VMware Aria Cost powered by CloudHealth

 Disaster recovery is the process of restoring the normal operations of an organization after a disruptive event, such as a natural disaster, a cyberattack, or a human error. Disaster recovery involves the planning, preparation, and implementation of strategies and procedures to minimize the impact and duration of the disruption, and to ensure the continuity and availability of the critical functions and data of the organization1

RTO and RPO are two key metrics that are used to measure and evaluate the disaster recovery capabilities and objectives of an organization. RTO stands for Recovery Time Objective, which is the maximum acceptable amount of time that an application or a service can be offline or unavailable after a disruption. RPO stands for Recovery Point Objective, which is the maximum acceptable amount of data that can be lost or unrecoverable after a disruption2

When designing a new cloud-enabled application, an organization that is considering RTO and RPO is most likely concerned about disaster recovery, as these metrics can help the organization to determine the optimal level of backup, redundancy, and recovery for the application, as well as the potential costs and risks of downtime or data loss. RTO and RPO can also help the organization to choose the appropriate cloud service model, provider, and deployment option that can meet the disaster recovery requirements and expectations of the organization and its customers3

References: CompTIA Cloud Essentials+ Certification Exam Objectives4, CompTIA Cloud Essentials+ Study Guide, Chapter 7: Cloud Security5, Cloud Essentials+ Certification Training