Choosing a machine family: E2, N4, C4
Three current machine families split cleanly by cost versus performance, and guessing the family without a load test leads to a permanently over-provisioned fleet.
Speaker notes
- E2 optimizes for cost efficiency and is the right default for anything not measurably CPU- or latency-bound — staging, dev, internal tooling. N4 is the current-generation balanced price/performance default with DDR5 memory, replacing the older N2 line. C4 delivers maximum single-thread performance and the highest vCPU counts, paired with Hyperdisk for very high IOPS.
- The decision discipline: default to E2, and only move up the family ladder once a real measured performance number justifies it — not a guess about what you'll 'probably need.'
- Tie back to the running example: Meridian runs E2 for staging/dev, N4 for the steady GPS-ingestion worker fleet, and hasn't yet needed C4 — it's flagged only as a possible dedicated fallback if the managed database tier ever needs a self-managed high-performance alternative.
Deck map
01
GCP foundations in one line
02
How the ACE exam maps to this course
03
GCP's geography and the project as the unit of isolation
04
Organization, folders, and projects
05
Org policies and how inheritance works
06
Labels, network tags, and resource manager tags
07
Billing accounts, budgets, and cost control
08
gcloud CLI, Cloud Shell, and client libraries
09
Terraform on GCP and the end of Deployment Manager
10
Gemini CLI, Cloud Assist, and Application Design Center
11
Principals, roles, bindings, and policies
12
Primitive, predefined, custom roles, and IAM conditions
13
Service accounts, keys, and impersonation
14
Workload Identity Federation
15
Break-glass access and IAM auditing
16
Choosing a machine family: E2, N4, C4
17
Disks, OS Login, and VM Manager
18
Spot VMs and managed instance groups
19
Autoscaling policies, health checks, GPUs and TPUs
20
GKE Autopilot vs Standard vs the 2026 hybrid option
21
Node pools and pod autoscaling
22
Cloud Run revisions, traffic splitting, and functions
23
Choosing between GKE, Cloud Run, and Compute Engine
24
Cloud Storage classes and lifecycle management
25
Choosing a managed database
26
The managed database lineup
27
Connection pooling, read replicas, and Pub/Sub
28
Backup, regional failover, and CMEK
29
VPC networks, subnets, and Shared VPC
30
Firewall rules, tags, and Cloud NAT
31
Load balancers, Cloud DNS, and Cloud CDN
32
VPN, Interconnect, and private access
33
How a request actually reaches shipment-api
34
Cloud Monitoring: metrics, dashboards, alerts
35
Cloud Logging: router, buckets, and audit logs
36
Trace, Profiler, Error Reporting, and Managed Prometheus
37
How the five Cloud Operations products fit together
38
Readiness checklist