GCP-CDL Study Guide: The Cloud Digital Leader Exam Is a Translation Exam, So Learn the Phrasebook
The Cloud Digital Leader exam never asks you to configure anything. Each question describes a business situation in plain words, such as a retailer with a deadline, a bank worried about regulators or a CIO who wants to stop buying servers, and asks which idea or product fits. Passing is mostly a matter of translation: hearing the business sentence and recognising the cloud concept behind it. This guide is built as a phrasebook for that translation, followed by the pairs of look-alike ideas that cause most wrong answers.
Study guide · Google Cloud Certified Cloud Digital Leader (GCP-CDL)

The exam
50 to 60 multiple choice and multiple select questions in 90 minutes (this site's mock exam uses 55). Google does not publish a pass mark on the exam page or in the exam guide, so check the official exam page for current details. Six sections: Digital Transformation with Google Cloud, Exploring Data Transformation with Google Cloud, Innovating with Google Cloud Artificial Intelligence, Modernize Infrastructure and Applications with Google Cloud, and Trust and Security with Google Cloud at 18% each, and Scaling with Google Cloud Operations at 10%.
The even weighting is the first thing to plan around: no single section can carry you, and the one you find dull is worth as much as the one you enjoy. The second is the question style. Of the 278 GCP-CDL questions we wrote for this question bank, 146 (53%) are use-case questions ("a company wants X; what should it choose?"), and not one contains a command or a console step.
The phrasebook
Read the stem for the phrase that decides, then translate it. These are the translations that come up again and again.
| The business says | The concept is |
|---|---|
| "We keep our data centre and also use one public cloud" | Hybrid cloud (multicloud needs more than one public provider) |
| "We stop buying servers and pay monthly for what we use" | CapEx to OpEx |
| "Include staff time, power and hardware refreshes in the comparison" | Total cost of ownership |
| "Move it quickly, change nothing, the vendor package cannot be modified" | Rehost (lift and shift) onto Compute Engine |
| "Keep the code, but stop running our own database server" | Replatform, for example to Cloud SQL |
| "The monolith is slow to change" | Refactor; containers, GKE or Cloud Run |
| "Analysts need SQL over years of history, no servers" | BigQuery; Looker to present it |
| "Act on events as they happen" | Streaming: Pub/Sub ingests, Dataflow processes |
| "Transcription before peak season, no ML staff" | A pre-trained API |
| "Our analysts only know SQL and want predictions" | BigQuery ML |
| "Partners must use our APIs securely, and we want to charge for them" | Apigee |
| "Employees reach one internal app without a VPN" | Identity-Aware Proxy |
| "Data must stay encrypted even while it is processed" | Confidential Computing |
| "Stop a team from using more than X" | A quota (an alerts-only budget only warns) |
The service models, said three ways
A surprising number of questions are the same idea in three costumes. With IaaS (virtual machines) you control and patch the operating system. With PaaS you write code on a platform the provider runs. With SaaS you simply use the software. The more managed the service, the more the provider secures, but under the shared responsibility model the customer always owns its data and who can access it, even in SaaS. Google adds the idea of shared fate: shared responsibility plus active help through secure blueprints, guidance and tools.
Beginner tip: keep an error log of pairs, not of questions. Every time you miss or guess a practice question, write one line: the two ideas you confused (for example "replatform vs refactor") and the phrase in the stem that should have decided it ("code stays the same"). After three or four practice sets, sort the lines. The same few pairs tend to come back, and revising them takes ten minutes instead of a re-read of everything.
Six pairs that decide most questions
- Region vs zone. A zone is a failure domain inside a region. Several zones protect against a zone failure; several regions protect against a regional one, at more cost and effort.
- Latency vs bandwidth. Delay versus capacity. "Users far away wait too long" is latency.
- Database vs data warehouse vs data lake. A database runs an application, a warehouse combines data for analysis and reporting, a lake keeps raw data of every type.
- Machine learning vs generative AI vs agentic AI. ML predicts, generative AI creates new content, agentic AI plans and acts towards a goal through tools.
- Replication vs backup. Replication keeps a copy elsewhere and survives a site failure, but it also copies mistakes. After an accidental deletion only a backup brings the data back.
- SLI vs SLO vs SLA. Measured, targeted, promised. The SLI is the measured value, the SLO is the internal target, the SLA is the contract with consequences.
Going deeper: why lift and shift alone does not make things cheaper
Rehosting moves a server into a virtual machine of about the same size, which keeps running and billing around the clock, as the old server did. The savings that cloud promises come from paying only for what is used: autoscaling that shrinks capacity at night, managed services that remove patching and backup work, serverless products that scale to zero, Spot VMs for interruptible jobs. A rehosted workload uses none of these yet. That is why the exam treats rehosting as a fast, low-risk first step and why answers that promise lower cost or more agility "because we moved to the cloud" are usually wrong. The gains arrive later, as each workload adopts managed or autoscaling features.
Security and operations, in leadership words
Security questions name a worry, not a product. "Find and rank risks across the organisation" is Security Command Center. "Who is targeting us?" is Google Threat Intelligence. "Bring detection and response together" is Google Security Operations. "Screen prompts and responses of our AI apps" is Model Armor. "Find and de-identify personal data" is Sensitive Data Protection. "Protect the website from DDoS and web attacks" is Cloud Armor. Learn the authentication, authorisation and auditing trio as "who you are, what you may do, what happened".
The operations section (10%) is mostly money and reliability: CapEx and OpEx, budgets and quotas, Spot VMs for interruptible work, the four golden signals (latency, traffic, errors, saturation) and the SLI/SLO/SLA trio.
A study plan for six even sections
Give each of the five 18% sections roughly equal time and the operations section about half as much. A workable order: digital transformation and the service models first, because their vocabulary appears everywhere; then data, then AI (which builds on the data vocabulary); then modernisation and APIs; then security; then operations. Finish with mixed practice sets and the 90-minute clock, and answer every question, since a blank is always wrong.
Practise
Practise in the question bank: every question explains each option, right and wrong. Start with the domain you just studied, then take a timed mock exam.
- GCP-CDL exam page · All 338 GCP-CDL questions · Timed mock exam · 15-day study plan
- By domain: Digital Transformation with Google Cloud · Exploring Data Transformation with Google Cloud · Innovating with Google Cloud Artificial Intelligence · Modernize Infrastructure and Applications with Google Cloud · Trust and Security with Google Cloud · Scaling with Google Cloud Operations
Section weights as listed in Google's Cloud Digital Leader exam guide. Product names in this exam change with Google's branding; check the current official exam page.