Why Cloud Computing
Cloud computing is the delivery of computing services — servers, storage, databases, networking, software, analytics, and intelligence — over the internet ("the cloud") to offer faster innovation, flexible resources, and economies of scale. Instead of owning and maintaining physical data centers, organizations rent access to technology from a cloud provider like Google Cloud.
Key Benefits and Business Drivers
OpEx over CapEx
Shift from large upfront capital expenditures (buying servers) to predictable operational expenses (pay-as-you-go). This improves cash flow and reduces financial risk.
Elasticity & Scalability
Scale resources up or down in minutes, not months. Handle traffic spikes without over-provisioning. Google Cloud autoscalers adjust capacity automatically.
Global Reach
Deploy applications across 40+ regions worldwide. Serve users with low latency from the nearest data center. Multi-region configurations provide disaster recovery.
Speed of Innovation
Provision infrastructure in seconds. Experiment with new technologies without long procurement cycles. Focus engineering time on differentiated features, not infrastructure management.
The CDL exam often frames questions around business value, not technical depth. Know how cloud computing benefits organizations financially (OpEx model, reduced TCO) and operationally (scalability, speed).
On-Premises vs. Cloud
Traditional on-premises infrastructure requires organizations to purchase, install, configure, and maintain their own servers, networking equipment, and data center facilities. This approach involves significant upfront investment, long procurement cycles (often 3-6 months), and the risk of over-provisioning or under-provisioning resources.
Cloud computing eliminates these challenges by providing on-demand access to a shared pool of configurable computing resources. Resources are provisioned in minutes, scaled automatically, and billed based on actual consumption.
| Aspect | On-Premises | Cloud (Google Cloud) |
|---|---|---|
| Capital Model | CapEx — buy hardware upfront | OpEx — pay per use |
| Provisioning | Weeks to months | Minutes to seconds |
| Scaling | Manual, limited by physical capacity | Automatic, virtually unlimited |
| Maintenance | Customer manages everything | Provider manages infrastructure |
| Global Reach | Limited to owned data centers | 40+ regions, 120+ zones worldwide |
| Disaster Recovery | Expensive secondary site required | Multi-region built-in, pay for what you use |
| Innovation | Slow procurement limits experimentation | Instant access to AI, ML, analytics services |
Five Characteristics of Cloud Computing (NIST)
The National Institute of Standards and Technology (NIST) defines cloud computing with five essential characteristics that Google Cloud fully satisfies:
- On-demand self-service — Provision resources via console or API without human interaction with the provider.
- Broad network access — Access services over the internet from any device (laptop, phone, tablet).
- Resource pooling — Provider serves multiple tenants from shared infrastructure using a multi-tenant model.
- Rapid elasticity — Scale resources up and down quickly, appearing unlimited to the consumer.
- Measured service — Usage is metered, monitored, and billed transparently (pay-as-you-go).
Cloud Service Models: IaaS, PaaS, SaaS
Cloud services are categorized into three models based on how much the provider manages versus how much the customer manages. Understanding these models is critical for the CDL exam because many questions ask you to identify the correct model for a given scenario.
Infrastructure as a Service (IaaS)
IaaS provides the fundamental building blocks: virtual machines, storage, and networking. The customer has the most control but also the most responsibility. Google Cloud IaaS examples include Compute Engine (VMs), Cloud Storage (object storage), and VPC (networking).
You manage: Operating system, middleware, runtime, applications, and data.
Google manages: Physical hardware, hypervisor, networking, and data center facilities.
Platform as a Service (PaaS)
PaaS provides a managed platform for deploying applications without managing the underlying infrastructure. Google Cloud PaaS examples include App Engine (web apps), Cloud Functions (serverless functions), and Cloud Run (serverless containers).
You manage: Application code and data.
Google manages: Everything else — OS, runtime, scaling, patching, networking.
Software as a Service (SaaS)
SaaS delivers complete applications over the internet. Users access the software through a web browser with no installation or maintenance required. Google SaaS examples include Google Workspace (Gmail, Docs, Drive), Google Meet, and Looker.
You manage: Your data and user access/permissions.
Google manages: Everything — infrastructure, platform, application, updates.
| Model | You Manage | Google Manages | GCP Examples |
|---|---|---|---|
| IaaS | OS, middleware, runtime, apps, data | Hardware, hypervisor, network | Compute Engine, Cloud Storage, VPC |
| PaaS | Application code and data | OS, runtime, scaling, infrastructure | App Engine, Cloud Run, Cloud Functions |
| SaaS | Data and user access | Everything | Google Workspace, Looker, Google Meet |
Cloud Run is sometimes classified as PaaS and sometimes as serverless. For the CDL exam, think of it as serverless PaaS — you deploy containers but Google manages everything else including scaling to zero.
FaaS — Functions as a Service
FaaS is a subset of PaaS focused on individual functions (small units of code) that execute in response to events. Cloud Functions is Google Cloud's FaaS offering. You write a single function, Google handles scaling, and you pay only when the function executes. This is ideal for event-driven microservice architectures, webhooks, and lightweight data processing tasks.
# Example: Cloud Function triggered by Cloud Storage upload
# Deployed with: gcloud functions deploy process_image \
# --runtime python311 --trigger-resource my-bucket \
# --trigger-event google.storage.object.finalize
def process_image(event, context):
"""Triggered when a file is uploaded to Cloud Storage."""
bucket = event['bucket']
name = event['name']
print(f"Processing file: gs://{bucket}/{name}")
# Call Vision API, resize image, etc.
Google Cloud Infrastructure
Google Cloud runs on the same infrastructure that powers Google Search, YouTube, and Gmail — one of the largest and most advanced computer networks in the world. Understanding this infrastructure is essential because the exam tests your knowledge of regions, zones, and how they affect availability, latency, and compliance.
Google's Global Network
Google owns and operates one of the largest private networks in the world, with over 200,000+ miles of fiber optic cable (including undersea cables) connecting data centers across continents. This private network means that traffic between Google Cloud regions stays on Google's network rather than traversing the public internet, resulting in faster speeds and higher security.
Regions
Independent geographic areas (e.g., us-central1, europe-west1). Each region has 3+ zones. Choose regions based on latency, compliance, and cost. Google Cloud has 40+ regions.
Zones
Isolated deployment areas within a region (e.g., us-central1-a). Each zone has independent power, cooling, and networking. Distribute resources across zones for high availability.
Edge Locations
Network edge points (PoPs) where Google connects to the internet. Cloud CDN caches content at these locations for low-latency delivery to end users worldwide.
Multi-Region
Services like Cloud Storage and BigQuery can be configured as multi-regional for highest availability and geo-redundancy. Data is replicated across multiple regions automatically.
Region and Zone Selection
When choosing a region for your workloads, consider these factors:
- Latency — Choose the region closest to your users for the best response times.
- Data residency & compliance — Some regulations (GDPR, data sovereignty laws) require data to stay in specific countries or regions.
- Service availability — Not all Google Cloud services are available in every region. Check service-specific documentation.
- Cost — Pricing varies by region. US regions are typically the cheapest; Asia-Pacific and South America are more expensive.
- Carbon footprint — Some regions run on more renewable energy than others. Google publishes carbon intensity per region.
Zonal vs. Regional vs. Multi-regional resources: A VM runs in one zone (zonal). A managed instance group can span zones within a region (regional). Cloud Storage buckets can be multi-regional for global availability. Higher redundancy = higher cost but better availability.
# List all available regions
gcloud compute regions list
# List zones in a specific region
gcloud compute zones list --filter="region:us-central1"
# Create a VM in a specific zone
gcloud compute instances create my-vm \
--zone=us-central1-a \
--machine-type=e2-medium \
--image-family=debian-12 \
--image-project=debian-cloud
Total Cost of Ownership (TCO)
Total Cost of Ownership is the complete cost of a technology solution over its entire lifecycle. When comparing on-premises to cloud, organizations often underestimate the hidden costs of on-premises deployments. The CDL exam expects you to understand why cloud TCO is often lower than on-premises TCO.
On-Premises Cost Components
| Category | Cost Items | Typical Impact |
|---|---|---|
| Hardware | Servers, storage arrays, networking equipment, load balancers | High CapEx, 3-5 year refresh cycles |
| Facilities | Data center space, power, cooling, physical security | Often 30-50% of total IT budget |
| Personnel | System admins, network engineers, security staff | Salaries, benefits, training |
| Software | OS licenses, database licenses, monitoring tools | Annual renewals, per-core pricing |
| Maintenance | Hardware repairs, firmware updates, contract renewals | Ongoing, unpredictable |
| Over-provisioning | Buying for peak capacity that's rarely used | Average utilization 15-25% |
| Opportunity Cost | Engineering time spent on infrastructure vs. innovation | Hard to quantify but significant |
Cloud Cost Advantages
Pay-as-you-Go
Pay only for resources you consume. No upfront investment. Compute Engine bills per second (minimum 1 minute). Stop a VM and stop paying for compute.
Sustained Use Discounts
Compute Engine automatically gives up to 30% discount for VMs that run more than 25% of a month. No commitment required — it's applied automatically.
Committed Use Discounts
Commit to 1 or 3 years of usage for up to 57% discount on compute resources. Best for predictable, steady-state workloads.
Preemptible / Spot VMs
Short-lived VMs at 60-91% discount. Google can reclaim them with 30 seconds notice. Ideal for batch processing, CI/CD, and fault-tolerant workloads.
Remember the discount types: Sustained Use = automatic, Committed Use = 1-3 year contract, Preemptible/Spot = interruptible but cheapest. The exam may ask which discount applies to a scenario.
# Google Cloud Pricing Calculator
# https://cloud.google.com/products/calculator
# Check pricing for a machine type
gcloud compute machine-types describe e2-standard-4 \
--zone=us-central1-a
# View billing account and budget alerts
gcloud billing accounts list
gcloud billing budgets list --billing-account=ACCOUNT_ID
Digital Transformation Framework
Digital transformation is the process of using digital technology to fundamentally change how an organization operates and delivers value to customers. It is not just about moving to the cloud — it involves rethinking business processes, organizational culture, and customer engagement.
Google's Transformation Cloud
Google identifies five key capabilities for successful digital transformation:
Data
Unlock value from data with BigQuery, Looker, and Dataflow. Create a data-driven culture where decisions are based on insights, not intuition.
Infrastructure
Modernize infrastructure with cloud-native services, containers, and serverless computing. Reduce operational burden and increase agility.
People
Empower employees with collaboration tools (Google Workspace), upskilling programs, and new ways of working. Culture change is the hardest part.
AI & ML
Apply AI/ML to automate processes, generate predictions, and create new customer experiences. Vertex AI makes ML accessible to all skill levels.
Cloud Maturity Model
Organizations move through stages of cloud adoption:
| Stage | Description | Characteristics |
|---|---|---|
| Tactical | Individual workload migration | Lift-and-shift, cost reduction focus, minimal process change |
| Strategic | Broader cloud adoption | Cloud-first policy, some re-architecture, team upskilling |
| Transformational | Business model innovation | Cloud-native development, data-driven culture, AI/ML integration |
Digital transformation is not just a technology project — it requires executive sponsorship, cultural change, and new operating models. The CDL exam tests whether you understand the business and organizational aspects, not just the technology.
Open Source and Open Standards
Google Cloud is a major contributor to open-source projects and supports open standards to reduce vendor lock-in. This is a key differentiator that the CDL exam emphasizes — Google wants you to know that workloads can be portable across environments.
Key Open-Source Projects from Google
| Project | Google Cloud Service | Purpose |
|---|---|---|
| Kubernetes | GKE (Google Kubernetes Engine) | Container orchestration — originally created by Google, now managed by CNCF |
| TensorFlow | Vertex AI Custom Training | ML framework for building and training models |
| Apache Beam | Dataflow | Unified batch and stream processing model |
| Istio | Anthos Service Mesh | Service mesh for microservices communication |
| Knative | Cloud Run | Serverless container platform for Kubernetes |
Benefits of Open Standards
- Portability — Move workloads between clouds or back on-premises without rewriting applications.
- No vendor lock-in — Use standard APIs and formats that work across providers.
- Community innovation — Benefit from contributions by thousands of developers worldwide.
- Talent availability — Developers skilled in Kubernetes or TensorFlow can be productive immediately.
When the exam asks about avoiding vendor lock-in or portability, think containers + Kubernetes + open-source frameworks. Google Cloud's support for open standards is a key selling point tested frequently.
Exam Tips and Key Terms
Section 1 is ~17% of the exam. Focus on understanding business value propositions (why cloud?), service model differences (IaaS vs PaaS vs SaaS), and the shared responsibility model. Questions are scenario-based, not trivia.
Quick-Reference Glossary
Practice Questions Approach
For this section, exam questions typically follow these patterns:
- "A company wants to reduce upfront IT costs..." → Answer involves OpEx model / cloud migration
- "Which service model gives the most control..." → IaaS (Compute Engine)
- "Who is responsible for securing data in GCP..." → Always the customer, regardless of service model
- "What helps avoid vendor lock-in..." → Open standards, containers, Kubernetes
- "A company needs to comply with data residency..." → Choose the appropriate region