Last updated: June 2025
More cheatsheets: Cloudoku Training Cheatsheets
- 1. Compute Services
- 2. Storage Services
- 3. Database Services
- 4. Networking & Content Delivery
- 5. Security, Identity & Compliance
- 6. Analytics & Machine Learning
- 7. Developer Tools & Management
- 8. Migration & Hybrid Cloud
- 9. Application Integration
- 10. Cost Management & Optimization
- 11. Best Practices and Tips
- 12. Preparing for GCP Certifications
- Purpose: Scalable VMs in Google Cloud.
- Machine Types: E2, N2, N2D, C2, A2, custom
- Pricing Models: On-demand, preemptible, committed use, sole-tenant
- Key Features: Instance groups, autoscaling, live migration, custom images
- Example (gcloud):
gcloud compute instances create my-vm --zone=us-central1-a --machine-type=e2-medium --image-family=debian-11 --image-project=debian-cloud
- Exam Tip: Understand sustained use discounts and preemptible VMs.
- Purpose: Fully managed PaaS for web apps.
- Environments: Standard (sandboxed), Flexible (custom runtimes)
- Features: Autoscaling, zero server management, traffic splitting
- Purpose: Event-driven serverless functions.
- Triggers: HTTP, Pub/Sub, Cloud Storage, Firestore, etc.
- Example (gcloud):
gcloud functions deploy myFunction --runtime python310 --trigger-http --allow-unauthenticated
- Exam Tip: Pay only for function execution time.
- Purpose: Serverless containers (run any language in Docker containers).
- Features: HTTP endpoints, auto-scale to zero, fully managed or Anthos
- Purpose: Managed Kubernetes clusters.
- Features: Node pools, auto-upgrades, auto-repair, integrates IAM
- Purpose: Object storage for unstructured data.
- Storage Classes: Standard, Nearline, Coldline, Archive
- Features: Lifecycle management, versioning, uniform bucket-level access
- Example (gsutil):
gsutil cp file.txt gs://mybucket/
- Exam Tip: Know when to use each storage class and their cost tradeoffs.
- Purpose: Block storage for Compute Engine VMs.
- Types: Standard (HDD), Balanced/SSD, Extreme SSD, Local SSD
- Purpose: Managed NFS file storage for GKE, Compute Engine.
- Purpose: Move data into/out of GCP from cloud or on-prem.
- Purpose: Managed relational DB (MySQL, PostgreSQL, SQL Server).
- Features: Backups, failover, replicas, IAM integration
- Purpose: Horizontally scalable, strongly consistent relational DB.
- Features: Global transactions, automatic sharding, high availability
- Purpose: NoSQL document DBs for web/mobile apps.
- Features: Real-time sync, offline mode, scalable
- Purpose: NoSQL wide-column database for analytics, time series.
- Purpose: Managed Redis/Memcached cache.
- Purpose: Serverless data warehouse for analytics (see Analytics section)
- Purpose: Provision private networks, subnets, routes, firewall rules.
- Features: Shared VPC, Private Google Access, custom/auto mode
- Types: HTTP(S), SSL Proxy, TCP/UDP, Internal
- Features: Global, regional, cross-region, integrates with Cloud Armor (WAF)
- Purpose: Low-latency content delivery at edge locations.
- Purpose: Dedicated private links (Interconnect) or encrypted tunnels (VPN) to GCP.
- Purpose: Scalable, managed DNS service.
- Purpose: Manage who/what can access GCP resources (users, service accounts, roles)
- Best Practices: Least privilege, custom roles, service account separation
- Purpose: Identity management for users/devices across GCP and SaaS
- Purpose: Secure key generation, storage, and management
- Purpose: Track all admin/user/data access and API calls
- Purpose: Central security visibility and threat detection
- Purpose: DDoS and application firewall protection
- Purpose: Serverless, scalable data warehouse for analytics.
- Features: Standard SQL, federated queries, ML integration
- Example (bq):
bq query --use_legacy_sql=false 'SELECT COUNT(*) FROM `project.dataset.table`'
- Purpose: Serverless stream and batch data processing (Apache Beam)
- Purpose: Managed Spark/Hadoop clusters
- Purpose: Global messaging for event-driven systems (queues, topics)
- Purpose: Unified ML platform for building, training, deploying models
- Purpose: Business intelligence, dashboards, data visualization
- Purpose: Infrastructure as code (similar to CloudFormation/ARM templates)
- Example:
resources: - name: my-vm type: compute.v1.instance properties: zone: us-central1-a machineType: zones/us-central1-a/machineTypes/e2-medium disks: - deviceName: boot type: PERSISTENT boot: true autoDelete: true initializeParams: sourceImage: projects/debian-cloud/global/images/family/debian-11 networkInterfaces: - network: global/networks/default
- Purpose: Metrics, logs, uptime checks, alerts
- Purpose: Private Git hosting
- Purpose: CI/CD pipelines
- Purpose: Cron jobs as a service
- Purpose: Migrate VMs from on-premises or other clouds to GCP
- Purpose: Hardware transfer for large datasets
- Purpose: Manage Kubernetes clusters and workloads across hybrid/multi-cloud
- Purpose: Task queues for distributed services
- Purpose: Serverless orchestration for multi-service workflows
- Purpose: Manage and secure APIs
- Purpose: Full lifecycle API management
- Cloud Billing Reports: Track and analyze GCP spending
- Budgets and Alerts: Set spend limits and notifications
- Pricing Calculator: Estimate costs before deploying resources
- Committed Use Discounts: Save with long-term commitments
- Use labels for resource management and cost tracking
- Enforce least privilege with IAM roles
- Enable Cloud Audit Logs and review regularly
- Automate backups and disaster recovery
- Monitor with Cloud Monitoring and set alerts
- Use autoscaling for compute and managed services
- Build a study plan and get hands-on with Cloud Console & gcloud CLI
- Take Cloudoku’s practice exams and cheatsheets
- Explore Google Cloud Skills Boost, Qwiklabs, and whitepapers
Good luck on your GCP certification journey!