Cloud Computing Services

` GEN CC501 Consume Cloud Computing Services

Competence

RQF Level: 5 Learning Hours

50
Credits: 5

Sector: ICT a nd Multimedia

Trade: Computer System and Architecture

Module Type: General Module

Curriculum: ICTCSA501 TVET CERTIFICATE V IN COMPUTER

SYSTEM AND ARCHITECTURE

Copyright: © Rwanda TVET Board, 2024

Issue Date: March, 2024

2024 -25
1|Page PREPARED BY Eng ISHEMAAbdon
Purpose This general module describes the skills, knowledge and
statement attitudes required to consume cloud computing services. This
module is intended to prepare learners pursuing TVET Level
5 in Computer System and Architecture. Upon completion of
this module, the learner will be able to Create Cloud
Computing Account, manage cloud computing resources, and
perform maintenance on cloud computing environment.
Elements of Competence and Performance Criteria
Elements of Performance criteria
competence
1. Create 1.1 Cloud Computing Service Models Are Properly Selected in
Cloud Line with Cloud Compliance Standards And Business Needs
Computin
1.2 Cloud Computing Service Provider Is Appropriately
g Account Selected
Based on SLA (Service Level Agreement)
1.3 customer’s account is appropriately managed based on
service deployment models and user needs
2. Manage 2.1 cloud resources are effectively provisioned based on
cloud workload demands
computin 2.2 cloud resources are properly monitored in accordance
g with scaling strategies for optimal performance
resources
2.3 cloud resources utilization is correctly optimized in
accordance with resource constraints
2.4 cloud environment security measures are properly
applied based on service provider requirement and SLA
3. Perform 3.1 Cloud resources backup strategies are appropriately
Maintenance applied based on industry standards for data resilience
3.2 Patches are effectively applied based on the latest stable
versions
3.3 Errors are correctly fixed based on cloud computing
service functionality

2|Page PREPARED BY Eng ISHEMAAbdon

Learning outcome 1: Create Cloud Computing Account

1.1 Selection of Cloud Computing Service Models

1.1.1 Definition of Key Terms:

Cloud Computing:
A technology that enables access to shared pools of configurable
system resources (like networks, servers, storage, applications, and
services) over the internet, providing scalable computing power without
requiring direct active management by the user. This allows users to
access computing services as per demand, typically in a pay-as-you-go
model.

Service Models:
These are the different categories of cloud services based on the level
of control and management provided to users, mainly categorized as
Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and
Software as a Service (SaaS).

3|Page PREPARED BY Eng ISHEMAAbdon

1.1.2 Description of Cloud Computing Service Models:

Service: This term in cloud computing is the concept of being able to use reusable,
fine-grained components across a vendor’s network

Cloud computing service models define how cloud services are offered to users. The
three primary service models are:

Infrastructure as a Service (IaaS)

IaaS provides basic computing resources such as virtual machines, storage, and
networks. It allows businesses to rent IT infrastructure from a cloud provider,
reducing the need for physical data centers.

 Use Cases: Web hosting, backup and recovery, high-performance computing.

 Examples: Amazon Web Services (AWS), Microsoft Azure, Google Cloud.

Platform as a Service (PaaS)

PaaS delivers a complete development and deployment platform, allowing

developers to build, test, and manage applications without worrying about the
underlying infrastructure. It includes tools for developing and deploying apps more
efficiently.

 Use Cases: Software development, API management, data integration.

 Examples: Heroku, Google App Engine, Microsoft Azure App Service.

4|Page PREPARED BY Eng ISHEMAAbdon

 Software as a Service (SaaS)

SaaS delivers software applications over the internet on a subscription basis. Users
can access software directly from a web browser without installing or maintaining
the software themselves.

 Use Cases: Customer Relationship Management (CRM), enterprise

applications, email.
 Examples: Google Workspace, Salesforce, Microsoft 365.

1.1.3 Selection Criteria of Cloud Computing Service Models:

User Needs:
Depending on the user’s technical capabilities and the level of control
they require, the service model can be selected.
Example: A company requiring full control over its infrastructure might
choose IaaS, while one focused on software without wanting to manage
infrastructure might prefer SaaS.
 IaaS: Suitable for users who want control over infrastructure (e.g.,
custom application development).
 PaaS: Ideal for developers focused on building applications
without worrying about managing servers.
 SaaS: Best for users who need ready-to-use software without
technical setup (e.g., office suites).

5|Page PREPARED BY Eng ISHEMAAbdon

 Pricing:
Each model has different pricing structures. IaaS is typically pay-per-use
based on the resources consumed, while PaaS and SaaS may have
subscription-based models.
 IaaS: Pay for what you use (e.g., compute power, storage).
 PaaS: Pay based on application usage and platform capacity.
 SaaS: Typically subscription-based pricing.
Operation:
Based on operational needs, such as scalability, speed, and control, a
business might opt for different service models. If rapid development is
a priority, PaaS is ideal, while IaaS may be better for extensive
customization.
 IaaS: Full control over the environment; requires more technical
expertise.
 PaaS: Streamlined development environment; faster application
deployment.
 SaaS: Minimal management required; instant access to software
applications.

1.2 Selection of Cloud Computing Service Provider

1.2.1 Description of SLA:

Definition:
Service Level Agreement (SLA) is a contract between the service
provider and the user, outlining the level of service expected. It includes
details about performance metrics, uptime, responsibilities, and
penalties for non-compliance.
Components:
Key components of an SLA include service scope, performance
guarantees (like uptime and response time), security measures,
compliance, data management policies, and remedies for breaches.
 Service scope: Defines what services are covered.
 Performance metrics: Specifies uptime and response times.
 Remedies: Details on how failures or breaches will be handled.
 Security measures: Defines how security and compliance will be
enforced.
 Data policies: Covers how data is managed, stored, and accessed.
Types of SLAs:
 Customer-based SLA: Specific to one user or group of users.
 Service-based SLA: For a specific service provided to multiple
users.
 Multi-level SLA: A combination of customer-based and service-
based elements.
Benefits:
 Provides clarity on expectations
 improves accountability
 enhances customer trust

6|Page PREPARED BY Eng ISHEMAAbdon

  ensures service reliability.

1.2.2 Description of Cloud Computing Service Providers:

Definition:
Cloud service providers offer IT services (such as computing power,
storage, and applications) to users via the internet, allowing them to
scale resources as needed without owning physical hardware.
Types:

1. Private Cloud: Infrastructure dedicated to a single organization,

offering higher control and security but at higher costs.
2. Public Cloud: Services are offered over the public internet and shared
between users. It is cost-effective but may pose potential security risks.
3. Hybrid Cloud: Combines public and private cloud features, offering
flexibility and balancing cost-efficiency with security.
4. Multi-cloud: Usage of multiple cloud services from different providers,
optimizing performance and cost.

Case Studies:
 Private Cloud
 Pros: Greater control, higher security, and compliance capabilities.
 Cons: Higher costs, limited scalability.
 Public Cloud
 Pros: Cost-effective, scalable, and easy to set up.
 Cons: Less control over data security and compliance.
 Hybrid Cloud
 Pros: Flexibility, optimized cost, and better management of
sensitive data.
 Cons: More complex to implement and manage.

1.2.3 Selection Criteria of Cloud Computing Service Providers:

User Needs:
Based on business requirements such as security, scalability, and
flexibility, the cloud provider should be selected. For example, a
business handling sensitive data may opt for a private or hybrid cloud.
Pricing:
Pricing models vary by provider and should be compared based on the
resources consumed, support offered, and long-term scalability.
Operations:
The efficiency of a provider’s data management, uptime, and ease of
scaling must be factored in.

1.3 Management of Customer’s Account

7|Page PREPARED BY Eng ISHEMAAbdon

1.3.1 Description:

Managing a cloud customer’s account involves overseeing the usage, billing,

security, and overall service engagement with the cloud provider. This includes
account creation, monitoring consumption, managing access, and ensuring security
protocols.

Types of Customer Accounts:

 Individual Account: Typically for single-user access to cloud services,
billed based on usage or subscription.
 Business Account: Provides access to multiple users under one
umbrella, with detailed billing and usage reporting for each team or
department.
Usage and Billing:
Cloud services are typically billed either by subscription or on a pay-as-
you-go basis, depending on the resources consumed. Regular
monitoring is needed to avoid overuse and unexpected costs.
Security and Access Control:
Managing permissions and security is critical to protect data. This
includes enabling multi-factor authentication, creating access policies,
and regular audits of who has access to what services.

1.3.2 Creation of Account:

Creating a cloud account usually involves selecting a provider, registering for a

service, choosing a subscription or payment model, and setting up necessary user
permissions and security protocols.

Steps for Creating an Account with a Cloud Computing Provider

Creating an account with a cloud provider typically involves the following steps:

1. Select a Cloud Service Provider

 Choose a provider based on your needs (e.g., Amazon Web Services (AWS), Google Cloud
Platform (GCP), Microsoft Azure).
 Visit the provider’s website to start the account creation process.

2. Sign Up for an Account

 Navigate to the “Sign Up” or “Create Account” page on the cloud provider’s website.
 Provide basic details like:
o Full Name
o Email Address
o Contact Information
o Organization Name (for business accounts)
 Choose whether you're creating an individual or business account.

8|Page PREPARED BY Eng ISHEMAAbdon

3. Choose an Authentication Method

 Set up your username and password.

 Some providers may require multi-factor authentication (MFA), where you link an additional
method like:
o SMS verification
o Authenticator app (e.g., Google Authenticator)
o Email verification

4. Provide Payment Information

 Add a payment method (credit card, debit card, PayPal, or bank account).
 Many providers offer free tiers or free trials, but payment information is often required for future
billing.
 Ensure to review any charges or usage limits related to the free tier.

5. Select the Services and Subscription Plan

 Once your account is set up, select which cloud services you want to use (e.g., compute, storage,
databases).
 Choose the pricing model based on your needs:
o Pay-as-you-go (most common for IaaS/PaaS)
o Subscription-based for SaaS products
o Reserved instances for long-term use at a lower cost

Steps for Creating an Account with a Cloud Computing Provider

Creating an account with a cloud provider typically involves the following steps:

1. Select a Cloud Service Provider

 Choose a provider based on your needs (e.g., Amazon Web Services (AWS), Google
Cloud Platform (GCP), Microsoft Azure).
 Visit the provider’s website to start the account creation process.

2. Sign Up for an Account

 Navigate to the “Sign Up” or “Create Account” page on the cloud provider’s website.
 Provide basic details like:
o Full Name
o Email Address
o Contact Information
o Organization Name (for business accounts)
 Choose whether you're creating an individual or business account.

3. Choose an Authentication Method

9|Page PREPARED BY Eng ISHEMAAbdon

  Set up your username and password.
 Some providers may require multi-factor authentication (MFA), where you link
an additional method like:
o SMS verification
o Authenticator app (e.g., Google Authenticator)
o Email verification

4. Provide Payment Information

 Add a payment method (credit card, debit card, PayPal, or bank account).
 Many providers offer free tiers or free trials, but payment information is often
required for future billing.
 Ensure to review any charges or usage limits related to the free tier.

5. Select the Services and Subscription Plan

 Once your account is set up, select which cloud services you want to use (e.g.,
compute, storage, databases).
 Choose the pricing model based on your needs:
o Pay-as-you-go (most common for IaaS/PaaS)
o Subscription-based for SaaS products
o Reserved instances for long-term use at a lower cost

6. Configure Your Account Settings

 Set up billing preferences (monthly/annual billing, alert notifications for usage

limits).
 Define administrative roles and set up any necessary user roles or permissions if
it’s a business account.
 For business accounts, configure Identity and Access Management (IAM) for
users:
o Define roles (e.g., Admin, Developer, Finance).
o Assign access levels to users based on their roles.

7. Set Up Security and Access Controls

 Enable multi-factor authentication (MFA) if it wasn’t set during sign-up for added
security.
 Configure role-based access control (RBAC) to restrict who has access to certain
cloud resources.
 Set up security policies regarding data encryption, access logging, and auditing.

8. Verify Account and Start Using Cloud Services

 You will typically receive an email confirmation to verify your account.

 Once verified, you can log in and access the dashboard of the cloud provider to
begin deploying and managing cloud resources.

9. Monitor Usage and Set Up Billing Alerts

10 | P a g e PREPARED BY Eng ISHEMAAbdon

  After the account setup, monitor your resource usage from the cloud provider’s
dashboard.
 Set up billing alerts to receive notifications if your usage exceeds a certain
threshold.

1.3.3 Identity and Access Management (IAM):

IAM is a framework used to ensure that the right individuals have the right access to
cloud resources. It allows administrators to manage who can access what, and
define roles and policies that dictate permissions across an organization. Key
features include role-based access control (RBAC) and multi-factor authentication
(MFA).

 Role-based Access Control (RBAC): Assigning permissions based on the

role of the user.
 Multi-factor Authentication (MFA): Adding an extra layer of security by
requiring additional verification beyond passwords.

1.3.4 Backup and Disaster Recovery:

A critical aspect of managing cloud services is implementing a solid backup and

disaster recovery strategy. This involves regularly backing up data to prevent loss
and creating a recovery plan that ensures continuity in the event of system failure
or data breach. Cloud providers often offer automatic backup and recovery services
as part of their offerings.

 Backup: Regularly storing copies of data to prevent loss in case of failures or

breaches.
 Disaster Recovery: Having a strategy in place to restore services and data
after a system failure, cyberattack, or natural disaster. Cloud providers often
offer automatic backup and disaster recovery services.

11 | P a g e PREPARED BY Eng ISHEMAAbdon

Learning outcome 2: Manage cloud computing resources

2.1 Provisioning Cloud Resources

2.1.1. Description of Cloud Resources

Definition:
Cloud resources refer to various computing services offered over the
internet by cloud providers. These resources include servers, storage,
databases, networking, software, analytics, and more. Cloud resources
allow businesses to access scalable and flexible IT resources without
investing in on-premise infrastructure.
Types:

 Virtual Machines (VMs): Simulated computing environments that act

like physical computers.
 Databases: Managed services that provide scalable storage and
retrieval of structured data.
 Storage: Cloud-based data storage solutions that offer scalable,
durable, and accessible data storage.
 Network: Virtual networking resources, including load balancers,
firewalls, and virtual networks.
 Container Services: Enable the deployment of applications in
lightweight, portable containers.

2.1.2. Performing Cloud Resource Provisioning

Assessment of Requirements:
Before provisioning resources, assess the specific needs of the application or
system in terms of:

 Compute Power: The processing power required for the tasks.

 Memory: RAM requirements for smooth operation.
 Storage: Data storage needs, including type (block, object, file) and capacity.
 Network Requirements: Bandwidth, latency, and security measures.

Selection of Cloud Resources:

Based on the assessment, choose the appropriate resources:

 Virtual Machines (VMs) for general computing.

 Databases for data management (e.g., SQL, NoSQL).
 Storage for storing files, backups, etc.
 Networking Components like virtual networks, load balancers, and security
groups.

12 | P a g e PREPARED BY Eng ISHEMAAbdon

 Configure Cloud Resources:
Once selected, the resources are configured based on usage needs, including:

 CPU and memory allocation for VMs.

 Defining storage size and type (SSD or HDD).
 Networking setup with security rules (e.g., firewalls, VPNs).
 Configuring database size, backup, and recovery settings.

2.1.3. Deprovisioning Cloud Resources

 Deprovisioning involves safely removing or shutting down resources that

are no longer needed to avoid unnecessary costs. It includes archiving data if
necessary and ensuring proper removal to avoid security breaches.

2.2. Monitoring Cloud Resources

2.2.1. Identification of Cloud Monitoring Tools

Digital Ocean Monitoring and Uptime: Provides detailed insights into the
health of cloud resources, including server performance, CPU usage, and
downtime.

AWS CloudWatch: A monitoring and observability service that provides real-

time data and alerts for AWS resources and applications.
Microsoft Azure Monitor: Provides a full stack of observability for
monitoring Azure infrastructure, applications, and network performance.
Google Cloud Operations: Formerly Stackdriver, this suite offers
performance monitoring, logging, and alerting across Google Cloud services.

2.2.2. Description of Scaling Strategies

Vertical Scaling:
Increasing the capacity of an individual resource (e.g., upgrading a VM’s CPU
or RAM). It is useful for applications with growing performance needs that
cannot be distributed across multiple instances.
Horizontal Scaling:
Adding more instances of resources, such as VMs or containers, to distribute
the load. It is ideal for applications designed to run across multiple machines
in parallel.

2.2.3. Applying Cloud Monitoring Tools

 Set up monitoring services such as AWS CloudWatch or Google Cloud

Operations.
 Configure alerts for critical performance metrics (CPU usage, memory, disk
I/O).
 Visualize performance metrics through dashboards and reports.

13 | P a g e PREPARED BY Eng ISHEMAAbdon

2.3. Optimization of Cloud Resources Utilization

2.3.1. Identifying Cloud Resources Utilization Optimization

Strategies:

 Right-Sizing Resources: Adjust resource sizes (e.g., VMs) based on current

usage.
 Auto-Scaling: Automatically increase or decrease resources based on
demand to avoid under or over-provisioning.
 Using Reserved Instances: Purchase instances for long-term use at
reduced rates.
 Data Lifecycle Management: Automatically archive or delete unused data
to save on storage costs.

Best Practices:

 Regularly review usage patterns to adjust resources.

 Use auto-scaling features where possible.
 Optimize storage by choosing appropriate tiers (e.g., hot vs. cold storage).

2.3.2. Applying Cloud Resources Utilization Optimization Strategies

 Implement right-sizing on VMs and databases.

 Enable auto-scaling for compute resources.
 Use monitoring tools to track usage and automatically adjust resources.

2.4. Applying Cloud Environment Security Measures

2.4.1. Description of Security Measures

Definition:
Cloud security measures are techniques and tools designed to safeguard
data, applications, and services within a cloud environment from potential
threats.
Types:

 Encryption: Protecting data at rest and in transit using encryption protocols.

 Firewalls and Security Groups: Protecting resources by defining rules for
incoming and outgoing traffic.
 Identity and Access Management (IAM): Controlling access to resources
by assigning permissions to users and groups.
 Data Backup and Recovery: Implementing automated backup and recovery
solutions to safeguard data.

Benefits:

 Protects sensitive data and applications.

14 | P a g e PREPARED BY Eng ISHEMAAbdon

  Ensures compliance with security regulations.
 Mitigates risks of data breaches and cyber-attacks.

2.4.2. Identifying Cloud Environment Security Measures

 Encryption: Use strong encryption protocols for all data.

 IAM: Implement least-privilege access control to minimize risks.
 Firewalls: Use firewalls and virtual private cloud (VPC) configurations to
isolate and protect resources.
 Multi-Factor Authentication (MFA): Enable MFA for all user accounts to
add an extra layer of protection.

2.4.3. Securing the Cloud Environment

 Regularly audit access control settings to ensure proper permission levels.

 Apply encryption to sensitive data and enforce security policies across all
resources.
 Continuously monitor cloud environments for vulnerabilities and patch them
promptly.

15 | P a g e PREPARED BY Eng ISHEMAAbdon

Learning outcome 3: Perform Maintenance

3.1. Applying Cloud Resources Backup Strategies

3.1.1 Description

Cloud resource backup is a crucial aspect of cloud computing management that

ensures data protection, availability, and recovery in the event of data loss,
corruption, or system failures. Implementing effective backup strategies is vital for
maintaining the integrity and continuity of operations.

Backup Definition

Backup refers to creating copies of data, configurations, or entire system

environments to preserve and safeguard them from data loss or corruption due to
unforeseen events.

Types of Backups

 Full Backup: A complete copy of all data is stored at a specific point in time.
 Incremental Backup: Only changes made since the last backup (whether full
or incremental) are stored.
 Differential Backup: All changes made since the last full backup are stored,
regardless of previous incremental or differential backups.
 Mirror Backup: An exact copy of selected files, continuously synchronized
with the source, with no data compression.

Benefits of Backup

 Data Protection: Safeguards against accidental deletion, hardware failures,

and malicious attacks.
 Business Continuity: Ensures minimal disruption to operations in case of
system failures.
 Disaster Recovery: Provides recovery options for restoring data after major
failures, natural disasters, or cyber-attacks.
 Compliance: Helps meet legal and regulatory requirements for data
retention and protection.

3.1.2. Identification of Backup Strategies

Selecting an appropriate backup strategy depends on the organization’s needs,

infrastructure, and resources. Factors to consider include:

16 | P a g e PREPARED BY Eng ISHEMAAbdon

  Recovery Point Objective (RPO): Defines how much data the organization
can afford to lose between backups.
 Recovery Time Objective (RTO): Specifies the amount of time required to
recover data after an incident.
 Data Retention Policy: Determines how long backups should be stored and
how often they should be refreshed.
 Frequency of Backups: Depending on the system’s activity level, backups
can be performed daily, weekly, or even hourly.

3.1.3. Implement Cloud Backup Strategies

 Cloud-based Backup: Utilize cloud services such as AWS Backup, Azure

Backup, or Google Cloud Storage to automatically back up files and virtual
environments.
 Hybrid Backup Solutions: Implement both on-premise and cloud backup
solutions to increase redundancy and reliability.
 Snapshot Backups: Capture snapshots of entire system states at regular
intervals, allowing for quick recovery.
 Automated Backup Scheduling: Set up automatic, scheduled backups to
ensure data is regularly and reliably backed up without manual intervention.

3.2. Applyisng Patches

3.2.1. Description of Patches

Patches are updates or modifications to software designed to address bugs, security

vulnerabilities, and performance issues. They help ensure systems remain up-to-
date, secure, and stable.

Patch Definition

A patch is a piece of code or update applied to software to fix vulnerabilities,

enhance features, or improve system performance.

Types of Patches

 Security Patches: Fix security vulnerabilities and protect systems from

potential exploits.
 Bug Fix Patches: Correct errors or bugs in the software code that cause
malfunctions.
 Feature Update Patches: Add new functionality or improve existing
features in software.
 Hotfixes: Urgent updates that are applied immediately to address critical
issues or security vulnerabilities.

Working Operations of Patches

17 | P a g e PREPARED BY Eng ISHEMAAbdon

  Patch Testing: Before deployment, patches are tested in a staging
environment to ensure compatibility and avoid unintended consequences.
 Patch Deployment: Patches are rolled out to production systems, usually
with minimal downtime.
 Patch Validation: After patch deployment, the system is monitored to
ensure stability and effectiveness.

3.2.2. Implementation of Different Patch Types

 Manual Patch Installation: Administrators manually apply patches, usually

in small environments.
 Automated Patch Management: Use of tools like Windows Server Update
Services (WSUS) or third-party solutions to automate patch deployment
across multiple systems.
 Rolling Patches: Gradual application of patches to minimize downtime by
updating parts of the system in stages.

3.3. Fixing Errors inCloud Computing Services

3.3.1. Description of Cloud Errors

Cloud errors refer to any malfunction or fault that affects the performance,
availability, or reliability of cloud-based services. These errors may arise from
software bugs, configuration issues, resource limits, or external attacks.

Cloud Error Definition

A cloud error is any disruption or issue in a cloud environment that impedes normal
operations or affects service performance, security, or availability.

18 | P a g e PREPARED BY Eng ISHEMAAbdon

 Types of Cloud Errors

 System Failure: Unexpected downtime or performance degradation of cloud

infrastructure.
 Configuration Errors: Incorrect settings or misconfigurations leading to
failures or security vulnerabilities.
 Network Errors: Issues in connectivity or data transmission that hinder
access to cloud resources.
 Security Breaches: Unauthorized access or attacks exploiting vulnerabilities
in cloud services.

3.3.2. Identification of Different Error Fixing Solutions

To effectively manage cloud errors, organizations must identify the cause and
implement appropriate solutions. Common approaches include:

Automated Remediation: Leverage automation tools to detect, diagnose,

and resolve issues without manual intervention. These tools can restart
services, adjust resource allocations, or apply patches.
Manual Troubleshooting: In complex cases, administrators investigate logs,
performance metrics, and system behaviors to identify and resolve errors.
Software Updates and Patching: Applying patches and updates to cloud
platforms or applications to fix bugs and improve performance.
Scaling Resources: Adjusting resource allocations, such as CPU, memory, or
storage, to meet demand and prevent performance bottlenecks.
Data Recovery and Backup Restoration: In case of data corruption or loss,
recovery solutions focus on restoring data from backups or snapshots.

3.3.3. Apply Error Fixing Solutions

 Automated Solutions: Implement AI-powered tools to automatically detect

and fix errors, such as AWS Lambda or Google Cloud Functions.
 Manual Solutions: For complex issues, system administrators use detailed
logs, diagnostic tools, and performance monitoring to identify and address
errors.

3.3.4. Error Solution Documentation

Proper documentation of cloud errors and their resolutions is critical for future
reference and system optimization. Documentation should include:

Root Cause: The underlying reason for the cloud error, such as a failed
server or network congestion.
Procedures: The steps taken to identify and diagnose the issue.
Solution: The applied fix, whether through automated tools, manual
troubleshooting, or resource scaling.

19 | P a g e PREPARED BY Eng ISHEMAAbdon