Infrastructure as code (IaC) is a DevOps practice that uses code to define and deploy infrastructure, such as networks, virtual machines, load balancers, and connection topologies1. IaC ensures consistency, repeatability, and scalability of the infrastructure, as well as enables automation and orchestration of the provisioning process2. IaC is different from infrastructure templates, which are predefined configurations that can be reused for multiple deployments3. Infrastructure orchestration is the process of coordinating multiple automation tasks to achieve a desired state of the infrastructure4. Infrastructure automation is the broader term for any technique that uses technology to perform infrastructure tasks without human intervention5.
Reference:
CompTIA Cloud Essentials CLO-002 Certification Study Guide, Chapter 4: Operating in the Cloud, page 137 What is infrastructure as code (IaC)?, Azure DevOps | Microsoft Learn CompTIA Cloud Essentials+ Certification Study Guide, Second Edition (Exam CLO-002), Chapter 4: Operating in the Cloud, page 137 Infrastructure Automation: 7 DevOps Tools for Orchestration, Secrets Management, and More, Apriorit Blog Infrastructure As Code Vs Configuration Management, DevOpsCube Blog

Monthly cloud service costs are best described as operating expenditures. Operating expenditures (OPEX) are the ongoing costs of running a business or a service, such as rent, utilities, salaries, maintenance, and subscriptions1. Cloud services are typically paid on a monthly or annual basis, depending on the usage and the service level agreement. Cloud services reduce the need for capital expenditures (CAPEX), which are the upfront costs of acquiring assets, such as hardware, software, or infrastructure1. Fixed expenditures are the costs that do not change regardless of the level of output or activity, such as rent or insurance2. Personnel expenditures are the costs of hiring, training, and retaining employees, such as salaries, benefits, or taxes3. Reference: CompTIA Cloud Essentials+ Certification | CompTIA IT Certifications, CompTIA Cloud Essentials CLO-002 Certification Study Guide, Fixed Costs Definition, Personnel Costs Definition

According to the CompTIA Cloud Essentials objectives and documents, sandboxing is the best option for the DevOps team that wants to document the upgrade steps for its public database solution. Sandboxing is a technique that creates a virtual environment that is isolated from the production systems and allows the team to replicate multiple installations without affecting the real data or applications. Sandboxing is useful for testing, debugging, and experimenting with new features or configurations in a safe and controlled way. Sandboxing can also help the team to identify and resolve any potential issues or errors before deploying the upgrade to the production environment.
The other options are not as suitable for the team’s needs. Containerization is a method of packaging software code with the necessary dependencies and libraries to run it on any platform or cloud. Containerization is beneficial for creating portable and scalable applications that can run consistently across different environments. However, containerization does not provide a dedicated virtual environment that is separate from the production systems, nor does it allow the team to replicate multiple installations of the same software. Cold storage is a type of data storage that is used for infrequently accessed or archived data. Cold storage is typically cheaper and slower than hot storage, which is used for frequently accessed or active data. Cold storage is not relevant for the team’s need to document the upgrade steps for its public database solution, as it does not involve data storage or access. Infrastructure as code is a practice of managing and provisioning cloud infrastructure using code or scripts, rather than manual processes or graphical user interfaces. Infrastructure as code is advantageous for automating and standardizing the deployment and configuration of cloud resources, such as servers, networks, or storage. However, infrastructure as code does not provide a dedicated virtual environment that is separate from the production systems, nor does it allow the team to replicate multiple installations of the same software.

RDP stands for Remote Desktop Protocol, which is a protocol that allows a user to remotely access and control a Windows-based computer or virtual desktop from another device over a network. RDP can be used to provide access to a Windows VDI, which is a virtual desktop infrastructure that delivers Windows desktops and applications as a cloud service. RDP can provide a full graphical user interface, keyboard, mouse, and audio support, as well as features such as clipboard sharing, printer redirection, and file transfer. RDP can be accessed by using the built-in Remote Desktop Connection client in Windows, or by using third-party applications or web browsers. RDP is more suitable for accessing a Windows VDI than other protocols, such as VPN, SSH, or HTTPS, which may not support the same level of functionality, performance, or security. 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 Server1

The least costing server is the application server because it has the lowest used space and allocated space. The file server should have storage increased due to over 70% utilization because it has the highest used space and allocated space. To calculate the cost of each server, we can use the following formula:
Cost = ($1.50 x Used space) + ($0.75 x Allocated space)
Using this formula, we can find the cost of each server as follows:
Application server: Cost = ($1.50 x 186 GB) + ($0.75 x 250 GB) = $279 + $187.50 = $466.50 Mail server: Cost = ($1.50 x 250 GB) + ($0.75 x 300 GB) = $375 + $225 = $600 File server: Cost = ($1.50 x 450 GB) + ($0.75 x 500 GB) = $675 + $375 = $1050 The application server has the lowest cost of $466.50, while the file server has the highest cost of $1050. To find the utilization percentage of each server, we can use the following formula:
Utilization = (Used space / Allocated space) x 100%
Using this formula, we can find the utilization percentage of each server as follows:
Application server: Utilization = (186 GB / 250 GB) x 100% = 74.4%
Mail server: Utilization = (250 GB / 300 GB) x 100% = 83.3%
File server: Utilization = (450 GB / 500 GB) x 100% = 90%
The file server has the highest utilization percentage of 90%, which means that it is running out of storage space and may affect its performance and availability. The application server has the lowest utilization percentage of 74.4%, which means that it has some unused storage space and may be overprovisioned. Therefore, the file server should have storage increased to reduce its utilization and improve its efficiency, while the application server is costing the firm the least and does not need any changes in its storage allocation. Reference: CompTIA Cloud Essentials+ CLO-002 Study Guide, Chapter 3: Cloud Business Principles, Section 3.4: Cloud Billing and Cost Management, Page 87 and [Cloud Storage Utilization and Optimization | CloudHealth by VMware]

Backup and recovery of data is considered a concept of availability, which is one of the three pillars of information security, along with confidentiality and integrity. Availability means that data and systems are accessible and usable by authorized users when needed. Backup and recovery of data ensures that data can be restored in case of loss, corruption, or disaster, and that business operations can continue or resume with minimal downtime. Cloud backup and recovery involves creating and storing copies of data in a secondary, offsite storage location, and using the copies to restore the original data in the event of data loss1. Cloud backup and recovery offers many benefits, such as scalability, cost-effectiveness, reliability, and automation234. Reference: Cloud Essentials+ CLO-002 Study Guide, Chapter 2: Cloud Concepts, Section 2.3: Explain aspects of IT security in the cloud, p. 47. Backup And Disaster Recovery | Google CloudHow does backup and data recovery work in the Cloud? – Devoteam G CloudData Recovery Explained | IBMWhat is Cloud Backup and Recovery | Rackspace Technology

The cost savings by converting all four of the cloud servers to reserved instances can be calculated as follows:
The current pricing is $200 per month per server, which means the total cost for keeping three servers online for another nine months is $200 x 3 x 9 = $5,400, and the total cost for keeping one server online for a year is $200 x 1 x 12 = $2,400. The total cost for all four servers is $5,400 + $2,400 = $7,800.
The sale price of $1,500 per year per reserved instance means the total cost for converting all four servers to reserved instances is $1,500 x 4 = $6,000.
The cost savings by converting all four servers to reserved instances is $7,800 – $6,000 = $1,800.

Before initiating the project, the first step should be to identify the key stakeholders. The key stakeholders are the individuals or groups who have an interest or influence in the outcome of the project. They may include internal or external parties, such as executives, managers, employees, customers, suppliers, regulators, or partners1. Identifying the key stakeholders is important for several reasons, such as:
Aligning the project goals and expectations: The key stakeholders can help to define the vision, scope, objectives, and requirements of the project. They can also provide feedback and approval throughout the project lifecycle. By involving the key stakeholders from the start, the project team can ensure that the project meets the needs and expectations of the stakeholders and delivers the desired value2.
Securing the project resources and support: The key stakeholders can help to allocate the necessary resources and support for the project, such as budget, time, personnel, equipment, or data. They can also help to resolve any issues or conflicts that may arise during the project. By engaging the key stakeholders from the start, the project team can ensure that the project has the adequate resources and support to succeed3.
Managing the project risks and changes: The key stakeholders can help to identify and mitigate the potential risks and changes that may affect the project, such as technical, operational, legal, or regulatory challenges. They can also help to communicate and implement the changes to the relevant parties. By collaborating with the key stakeholders from the start, the project team can ensure that the project adapts to the changing environment and minimizes the negative impacts4.
The other options are not as suitable as identifying the key stakeholders for the first step of the project because:
The required network performance: The required network performance is the level of quality and speed that the network needs to provide for the cloud application. The required network performance is an important factor to consider for the project, but it is not the first step. The required network performance depends on the type, size, and location of the cloud application, which are determined by the key stakeholders’ input5.
The desired CSP: The desired CSP is the cloud service provider that offers the cloud services and infrastructure for the cloud application. The desired CSP is an important factor to consider for the project, but it is not the first step. The desired CSP depends on the features, benefits, and pricing of the cloud services and infrastructure, which are evaluated by the key stakeholders’ criteria.
The required cloud services: The required cloud services are the cloud-based resources and capabilities that the cloud application needs to function. The required cloud services are an important factor to consider for the project, but they are not the first step. The required cloud services depend on the functionality, scalability, and security of the cloud application, which are defined by the key stakeholders’ requirements.
The required amount of storage: The required amount of storage is the amount of disk space that the cloud application needs to store its data. The required amount of storage is an important factor to consider for the project, but it is not the first step. The required amount of storage depends on the volume, variety, and velocity of the data, which are influenced by the key stakeholders’ expectations.
Reference:
1: What is a Stakeholder? – Project Management Institute
2: How to Identify Project Stakeholders – Smartsheet
3: How to Engage Stakeholders in Your Project – Clarizen
4: How to Manage Stakeholder Risk and Change – ProjectManager.com
5: Network Performance Requirements for Cloud Migration – Riverbed
6: How to Choose a Cloud Service Provider – IBM Cloud
7: Cloud Services: Types, Benefits, and Challenges – BMC Blogs
8: Cloud Storage: What It Is and How to Use It – Lifewire

An SLA (service level agreement) is a contract between a cloud service provider and a cloud customer that defines the expected level of service, performance, availability, and reliability of the cloud service. An SLA also specifies the contractually allowed downtime for a cloud-hosted application, which is the maximum amount of time that the application can be unavailable or inaccessible without violating the SLA. The contractually allowed downtime is usually expressed as a percentage of uptime, such as 99.9% or 99.99%, which corresponds to a certain number of hours or minutes per year, month, week, or day. For example, an SLA with 99.9% uptime means that the cloud service can be down for up to 8.76 hours per year, or 43.8 minutes per month, or 10.1 minutes per week, or 1.44 minutes per day. If the cloud service provider fails to meet the SLA, the cloud customer may be entitled to compensation or other remedies, such as credits, refunds, or termination of the contract. Reference: CompTIA Cloud Essentials+ CLO-002 Certification Study Guide, page 27-28; CompTIA Cloud Essentials+ Certification Training, CertMaster Learn for Cloud Essentials+, Module 2: Business Principles of Cloud Environments, Lesson 2.4: Cloud Service Agreements, Topic 2.4.2: Service Level Agreements