1)IaaS, PaaS, and SaaS in Cloud Computing

Cloud computing is categorized into three main service models: Infrastructure as a Service
(IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS).

1. Infrastructure as a Service (IaaS)

IaaS provides virtualized computing resources over the internet. It includes servers, storage,
networking, and virtualization. Users do not manage the underlying hardware but can
deploy and configure software as needed.

Characteristics of IaaS

✔ Resources are provided on-demand

✔ Allows dynamic scaling
✔ Pay-as-you-go pricing model
✔ Multi-user accessibility on shared hardware

Benefits of IaaS

✔ Cost-effective (no need to buy hardware)

✔ Scalable and flexible
✔ Reliable and secure
✔ Increases productivity

Examples of IaaS

• Google Compute Engine

• Amazon Web Services (AWS) EC2

• Microsoft Azure Virtual Machines

2. Platform as a Service (PaaS)

PaaS provides a development environment that includes runtime, development tools,

middleware, and database management. It allows developers to build, test, and deploy
applications without managing infrastructure.

Characteristics of PaaS

✔ Integrated development environment (IDE)

✔ Multi-tenant architecture (multiple users can access the platform)
✔ Automatic software updates and maintenance
✔ Supports programming languages and frameworks

Benefits of PaaS
✔ Faster development and deployment
✔ Cost-effective
✔ Supports team collaboration
✔ High scalability

Examples of PaaS

• Google App Engine

• AWS Elastic Beanstalk

• Microsoft Azure App Services

3. Software as a Service (SaaS)

SaaS delivers software applications over the internet, eliminating the need for installation
and maintenance on local machines. Users can access SaaS applications through a web
browser.

Characteristics of SaaS

✔ Software is centrally managed

✔ Users do not need to install or maintain software
✔ Automatic updates and security patches
✔ Subscription-based pricing

Benefits of SaaS

✔ Reduces IT workload
✔ Accessible from anywhere
✔ Cost-efficient (no software purchase needed)
✔ Easy to scale and update

Examples of SaaS

• Google Docs

• Gmail

• Microsoft Office 365

Comparison of IaaS, PaaS, and SaaS

Feature IaaS PaaS SaaS

Virtualized computing
Definition Development platform Web-based software
resources

User Full control over Minimal control (only

Control over applications
Control infrastructure app usage)

AWS EC2, Google Google App Engine, AWS Google Docs, Gmail,
Examples
Compute Engine Elastic Beanstalk Office 365

Conclusion

IaaS, PaaS, and SaaS are essential models of cloud computing, each serving different needs.
IaaS is ideal for businesses needing infrastructure, PaaS is best for developers, and SaaS is
most suitable for end-users.
2)Google Cloud Console and Resource Management

Google Cloud provides four ways to access and interact with its services:

1. Cloud Console (Graphical User Interface)

2. Cloud SDK and Cloud Shell

3. APIs

4. Cloud Console Mobile App

1. Google Cloud Console

The Cloud Console is a web-based GUI that allows users to deploy, manage, and
troubleshoot resources. It includes features like:

• Resource Monitoring – Check health and performance

• Budget Control – Set limits to manage costs

• Search & SSH Access – Quickly locate and connect to instances

2. Google Cloud Resource Hierarchy

Google Cloud organizes resources in four levels:

1. Resources – Virtual Machines, Storage, BigQuery Tables

2. Projects – Containers for resources

3. Folders – Grouping projects under an organization

4. Organization Node – The top-level entity managing all folders and projects

Each project has a Project ID (unique & immutable), Project Name (user-defined), and
Project Number (Google-generated). The Resource Manager API helps in managing projects
programmatically.

3. Billing in Google Cloud

Billing is categorized into:

• Self-Serve (Online) – Paid via credit/debit card

• Invoiced (Offline) – Payment through check or wire transfer

Billing follows:

• Monthly Billing – Charges applied once a month

• Threshold Billing – Charges applied when a spending limit is reached

Cloud Billing Reports allow tracking costs based on projects, services, and regions.
4. Budgeting and Cost Control

Budgets help track spending against planned costs. Alerts are triggered when certain
thresholds (e.g., 50%, 90%, 100%) are met. Users can set budgets at the billing account or
project level and automate cost control actions.

5. Quotas in Google Cloud

Quotas prevent excessive resource usage due to errors or attacks. Two types of quotas exist:

1. Rate Quotas – Limit API request rates (e.g., 1,000 GKE API calls per 100 sec)

2. Allocation Quotas – Limit total resources (e.g., max 5 VPC networks per project)

Quotas can be increased by requesting changes from Google Cloud Support.

3)Install and Configure the Cloud SDK

1. Introduction to Cloud SDK

The Cloud SDK (Software Development Kit) is a collection of tools for managing Google
Cloud resources and services. It includes:

• gcloud CLI – Main command-line interface for Google Cloud.

• gsutil – Command-line tool for Google Cloud Storage.

• bq – CLI for BigQuery operations.

2. Installation of Cloud SDK

To install the Cloud SDK, follow these steps:

1. Visit cloud.google.com/sdk.

2. Select your operating system (Windows, macOS, or Linux).

3. Download the appropriate installer.

4. Follow OS-specific installation instructions.

After installation, the Cloud SDK tools are available under the bin directory.

3. Initial Configuration of Cloud SDK

After installing the Cloud SDK, configure it using:

gcloud init

This command performs:

Authentication – Authorizes access to Google Cloud using user credentials.
Configuration Setup – Sets project, region, and zone defaults.

4. Cloud Shell

Google Cloud Shell provides command-line access via a Debian-based virtual machine with:

• 5GB of persistent storage

• Pre-installed Cloud SDK tools

• Code editor for real-time development

To activate Cloud Shell, go to console.cloud.google.com and click the Cloud Shell icon.

5. gcloud CLI - Key Commands

Basic Commands:

• gcloud version – Displays installed version.

 • gcloud info – Shows configuration details.

• gcloud help – Provides command help.

Project Management:

• gcloud projects list – Lists available projects.

• gcloud projects create PROJECT_ID – Creates a new project.

• gcloud projects delete PROJECT_ID – Deletes a project.

Authentication Commands:

• gcloud auth login – Logs into a Google account.

• gcloud auth list – Displays authenticated accounts.

Configuration Commands:

• gcloud config set project PROJECT_ID – Sets the active project.

• gcloud config set compute/zone ZONE – Sets the default zone.

• gcloud config list – Lists all current settings.

6. Google Cloud APIs and Client Libraries

• Google Cloud provides APIs for accessing services like Compute Engine, Storage, and
AI.

• Use Cloud Client Libraries (available in Python, Java, Go, Node.js, etc.) for API access.

• APIs must be enabled in the Google Cloud Console before use.

7. Cloud Console Mobile App

• Allows monitoring and managing Google Cloud resources via mobile.

• Supports starting/stopping VMs, checking logs, and billing alerts.

• Available on Google Play Store & Apple App Store.

4)Cloud vs. Traditional Architecture (13 Marks)

1. Introduction

Architecture plays a crucial role in how applications and services are deployed. Traditional
architecture relies on on-premises infrastructure, while cloud architecture leverages remote
servers hosted by cloud providers like AWS, Google Cloud, or Azure.

2. Key Differences Between Cloud and Traditional Architecture

Aspect Traditional Architecture Cloud Architecture

On-premises servers and data Virtual servers hosted by cloud

Infrastructure
centers providers

Limited, requires manual Highly scalable with on-demand

Scalability
hardware upgrades resources

High upfront investment in

Cost Pay-as-you-go pricing model
hardware
Aspect Traditional Architecture Cloud Architecture

Requires dedicated IT staff for

Maintenance Managed by the cloud provider
maintenance

Security managed by cloud providers

Security Controlled by in-house IT teams
with advanced tools

Deployment Time-consuming, involves

Fast, deploy resources in minutes
Time hardware setup

Disaster
Requires backup infrastructure Built-in disaster recovery options
Recovery

Limited to physical location or Accessible from anywhere via the

Access
VPN internet

3. Diagram: Cloud vs. Traditional Architecture

Here’s a visual representation of the two architectures:

Traditional Architecture

• On-premises data centers

• Physical servers, networking, and storage

• Limited scalability

• High maintenance costs

[Users] → [Firewall] → [On-Premises Servers] → [Storage / Database]

→ [Network Switch] → [Backup Server]

Cloud Architecture

• Virtualized resources (IaaS, PaaS, SaaS)

• Auto-scaling and high availability

• Pay-as-you-go model

• Managed by cloud providers

[Users] → [Internet] → [Cloud Provider (AWS/GCP/Azure)] → [Compute / Storage /

Database]

→ [Auto-Scaling] → [Load Balancer]

4. Advantages of Cloud Over Traditional Architecture

Cost-Efficient – No need for costly on-premises infrastructure.

Scalability – Easily scale up or down based on demand.
Global Accessibility – Access applications from anywhere.
Automated Maintenance – Security updates and backups managed by cloud providers.
Faster Deployment – Applications can be deployed in minutes.

5. Conclusion

Traditional architecture provides full control over infrastructure but comes with high costs
and maintenance challenges. Cloud architecture, on the other hand, offers scalability,
flexibility, and cost-effectiveness, making it ideal for modern applications.