Instiq
Chapter 4 · Modernize infrastructure and applications with Google Cloud·v1.0.0·Updated 7/30/2026·~16 min

What's changed: Created Cloud Digital Leader Chapter 4 (Domain 4 "Modernization": migration and computing = approaches (lift-and-shift/move-and-improve/rebuild)/Compute Engine/Spot VM; serverless, containers, APIs, hybrid = GKE/Cloud Run/Cloud Run functions/App Engine/Apigee/GKE).

4.2Serverless, containers, APIs, and hybrid

Key points

Understand containers and managed Kubernetes (GKE), the selection of serverless options (Cloud Run, Cloud Run functions, App Engine), the value of connecting systems with APIs and Apigee, and GKE for hybrid and multicloud.

Cloud-native apps gain scalability, portability, and operational efficiency when run on containers or serverless. For Cloud Digital Leader, understand these options and "when to use which."

4.2.1Containers and GKE

Containers package an app and its dependencies into a lightweight, portable unit, with portability—running the same everywhere—as the key benefit. Running many containers in production needs Kubernetes for automated placement, scaling, and self-healing; on Google Cloud, managed Kubernetes Google Kubernetes Engine (GKE) provides this. GKE suits large-scale, complex microservices where you want Kubernetes-level control.

4.2.2Serverless

ServiceBest forCharacteristic
Cloud RunRun containers serverlessScale from zero, pay per use
Cloud Run functionsEvent-driven small functionsRun on a trigger
App EngineFully managed web app platformPaaS, focus on the app

Serverless runs code without managing servers, autoscaling with demand and billing only for usage. Cloud Run runs containers serverless and scales to zero when there is no traffic. Cloud Run functions suits event-driven small tasks like "process a file when it is uploaded." App Engine is a fully managed web app platform (PaaS). When you want to eliminate server operations and focus on building, serverless is the fast path.

4.2.3APIs and hybrid/multicloud

An API is the "interface" through which systems exchange functions and data. Well-designed APIs let you keep existing systems while integrating new services and even offer them externally (monetization). Google Cloud’s Apigee is an API management platform to securely publish and manage APIs. When you want to run containers consistently across on-premises or other clouds, GKE (formerly Anthos) enables hybrid/multicloud.

Exam point

Common: requirement → service. E.g., "operate large microservices on Kubernetes" = GKE; "run containers serverless, scale to zero" = Cloud Run; "small task on an event like upload" = Cloud Run functions; "fully managed web app platform" = App Engine; "securely publish/manage APIs" = Apigee; "consistent operations across on-prem/other clouds" = GKE.

Warning

Watch the mix-ups: (1) GKE (keep Kubernetes control) vs Cloud Run (simple serverless)—same containers, different operating models. (2) Cloud Run functions = event-driven functions; Cloud Run = containers. (3) Apigee = API management, not a compute platform. (4) GKE/Anthos = hybrid/multicloud consistent operations.

For networking and connectivity, know Cloud Load Balancing (distributes load across servers), Cloud CDN (serves from Google edges near users for speed), Cloud VPN (encrypted tunnel to on-premises), and Cloud Interconnect (dedicated, stable, low-latency links). For AI, AutoML builds custom models from data with little code, and for identity, Cloud Identity manages organization users/groups/SSO.

Diagram of three compute options—VMs (Compute Engine), containers (GKE), serverless (Cloud Run/Cloud Run functions/App Engine)—ordered by decreasing management effort.
Compute options

4.2.4Section summary

  • Containers = portability; large-scale operations = GKE (managed Kubernetes)
  • Serverless = Cloud Run (containers, scale to zero) / Cloud Run functions (event-driven) / App Engine (PaaS)
  • Value of connecting via APIs → Apigee (API management); hybrid/multicloud → GKE

Sign in to track progress — Log in.

Quick check

(just a quick review)

Q1. Which Google Cloud managed Kubernetes operates many containers in production with automated placement, scaling, and self-healing?

Q2. Which service runs containers serverless and can scale to zero when there is no traffic?

Q3. Which best suits event-driven small tasks like "process a file when it is uploaded"?

Q4. Which Google Cloud service securely publishes and manages APIs and governs their use?

Q5. Which enables consistent container operations across on-premises and other clouds for hybrid/multicloud?

Q6. Which best describes a key benefit of containers?

Check your understandingPractice questions for Chapter 4: Modernize infrastructure and applications with Google Cloud

Keep track of your progress

The full study guide is free to read. Sign up free to practice with the question bank, track what you have read, review your mistakes, and highlight passages.