Skip to content

Google Cloud Fundamentals and Production Engineering ​

Module 5 · Intermediate to senior platform/cloud engineering guide · Eight complete chapters

Google Cloud has familiar concepts for engineers coming from other providers, but its resource hierarchy, global VPC networking, project policies, IAM federation and load-balancing architecture require their own mental model. This field guide develops those fundamentals from first principles, then connects them to operational debugging and reliable system design.

Public education and accuracy

Examples use fictional marketplace infrastructure and placeholder resource names. They are teaching designs, not claims about a real production environment. Google Cloud services change rapidly: verify version, region, account policy, release stage, CLI syntax and pricing before deployment. Code snippets are educational and sometimes require prerequisites discussed in their chapters.

Prerequisites ​

Familiarity with Linux and TCP/IP, service deployment and a basic cloud model. Kubernetes and Terraform knowledge help with the examples but are not required to follow all conceptual material. For labs use a controlled Google Cloud sandbox with an approved budget, IAM rights and a cleanup plan. Read-only commands are sufficient for most investigations.

What you will learn ​

  • Explain organization, folders, projects, billing, API enablement, quotas and policy inheritance.
  • Use IAM roles, service accounts, ADC and federation without long-lived keys.
  • Design VPC/subnet, Shared VPC, firewall and hybrid routing based on actual resource scopes.
  • Trace HTTPS ingress, backend health, DNS and Cloud NAT egress end to end.
  • Operate Compute Engine templates, managed instance groups and autoscaling.
  • Choose object storage, artifacts, relational transactions, messaging, caches and analytics deliberately.
  • Correlate Cloud Monitoring, Logging, Trace and Audit Logs to a user-facing SLO.
  • Evaluate multi-zone/multi-region reliability, disaster recovery, cost and security trade-offs.

Eight main chapters ​

  1. Resource hierarchy, projects, governance and quotas: Administrative hierarchy, org policy, billing, API operations, failure cases.
  2. IAM, service accounts, ADC and workload identity: Authentication/authorization, token flow, GKE/CI federation, 403 diagnosis.
  3. VPC, Shared VPC, routes and firewall: Global VPC, regional subnets, firewall, hybrid networking and packet tracing.
  4. Cloud NAT, Cloud DNS and load balancing: HTTPS request sequence, NAT outbound mapping, proxy types, DNS and troubleshooting.
  5. Compute Engine and managed instance groups: Templates, VM boot, regional capacity, rolling updates, Spot and autohealing.
  6. Cloud Storage, Artifact Registry and data services: Objects, images, transactions, Pub/Sub idempotency and product selection.
  7. Observability, SLOs and incident diagnosis: Metrics, logs, traces, audit evidence, percentile and burn-rate reasoning.
  8. Architecture, security, DR and costs: Hypothetical marketplace design, failure domains, regional incident, trade-offs.

engineering reference and hands-on practice ​

Study order ​

Start with hierarchy and identity (Q1–Q2), which explains where permissions apply. Then work through network design and packet flow (Q3–Q4). Study compute and data guarantees (Q5–Q6), and finish with service-level observability and architecture decisions (Q7–Q8). Work through labs before answering the entire 40-question bank without notes.

AWS-to-GCP quick map ​

AWS conceptGCP conceptCaution
Organizations / OUs / accountsOrganization / folders / projectsNot one-to-one isolation or inheritance
Regional VPC + zonal subnetsGlobal VPC + regional subnetsDifferent network scope
IAM roles + STSIAM principals/roles + federation/impersonationDifferent trust model
ALB / NLBApplication / Network Load BalancersProduct classes and datapaths differ
NAT GatewayPublic NATPort and translation models differ
EC2 + ASGCompute Engine + MIGRegional distribution semantics
S3 / ECRCloud Storage / Artifact RegistryLocation, class and IAM details differ
RDS / AuroraCloud SQL and other DB productsHA/replication options differ
CloudWatch / X-RayMonitoring / Logging / Cloud TraceQuery/metric models vary

Authoritative references ​

← All modules · Start with Q1 →

Practical engineering knowledge, openly shared.