GenAI Leader cheat sheet
112 key facts across 4 exam domains, distilled from the full GenAI Leader revision notes — with the exam pattern behind each topic. Skim it the week of your exam.
Updated
Fundamentals of gen AI
30% of the examGenerative AI Concepts: Foundation Models, LLMs, and Business Use Cases
- Generative AI is a branch of machine learning that creates new content; traditional ML classifies or predicts.
- A foundation model is pretrained on broad data and adapted to many tasks; an LLM is a foundation model specialized in language.
- Multimodal foundation models like Gemini handle text, images, audio, and video in a single model.
- Diffusion models generate images by learning to reverse noise — the concept behind Imagen; Veo generates video.
- Supervised learning uses labeled data, unsupervised finds patterns in unlabeled data, reinforcement learns from rewards and penalties.
- The ML lifecycle runs data ingestion, data preparation, model training, model deployment, and model management — as a loop.
- Choose a foundation model by modality, context window, security, availability, cost, performance, fine-tuning, and customization — matched to the scenario.
- Gen AI business value maps to four verbs: create, summarize, discover, and automate.
How the exam tests this
The exam tests this topic mostly through definition-matching and scenario questions: expect to pick the term that fits a description (diffusion model for image generation, multimodal for mixed inputs, prompt tuning versus fine-tuning) or the ML approach that fits a dataset (labeled data signals supervised, pattern discovery in unlabeled data signals unsupervised, reward-driven learning signals reinforcement). Watch for trigger words like 'labeled', 'reward', 'context window', and 'adapt without retraining'. Foundation-model selection questions reward matching a business constraint — cost, security, modality — to the deciding factor rather than choosing the most powerful model.
Data Types in Gen AI: Quality, Structured vs Unstructured, Labeled Data
- Gen AI output quality is bounded by data quality: incomplete, inconsistent, or irrelevant data produces confident but wrong answers.
- Data quality and accessibility have six exam characteristics: completeness, consistency, relevance, availability, cost, and format.
- Structured data fits predefined rows and columns (transactions, CRM records, inventory tables); unstructured data is free-form (emails, contracts, images, audio, video).
- Unstructured data is the large majority of enterprise data, and foundation models are the first technology to unlock it at scale.
- Labeled data carries correct-answer tags and powers supervised learning; unlabeled data has none and powers unsupervised learning and foundation-model pretraining.
- Labeling is expensive human work — a key reason adapting a pretrained foundation model beats building a labeled dataset from scratch.
- Poor data quality hits the business as lost trust, bias, inflated cost, misleading decisions, and missed use cases.
- Assess data quality and accessibility before scaling a gen AI initiative, not after deployment.
How the exam tests this
Expect classification questions that hand you a concrete example — 'call-center recordings', 'a table of daily sales' — and ask whether it is structured or unstructured, or labeled or unlabeled; the tags-with-correct-answers cue signals labeled, and rows-and-columns signals structured. Scenario questions describe a gen AI project going wrong and ask which data characteristic — completeness, consistency, relevance, availability, cost, or format — is the root cause. Also watch for business-implication framing: answers linking poor data quality to lost trust, bias, and misleading output are the ones the exam rewards.
The Five Layers of the Gen AI Landscape and What They Mean for Business
- The gen AI landscape has five layers: infrastructure, models, platforms, agents, and applications, and each builds on the layer below.
- Infrastructure (TPUs, GPUs, AI Hypercomputer, Google Cloud data centers) should be consumed from a cloud provider, not built.
- The models layer is a choice among foundation models like Gemini, Gemma, Imagen, and Veo, not a mandate to train your own.
- Platforms such as Agent Platform with Model Garden are where enterprises build custom, data-grounded solutions with control over security and governance.
- Agents combine a model with reasoning and tools to complete multi-step tasks, which makes them powerful for automation but demands stronger governance.
- Applications like the Gemini app, Gemini for Google Workspace, and Gemini Enterprise deliver the fastest time to value with no development team.
- Lower layers trade speed for control and differentiation; higher layers trade customization for speed and low cost.
- Most organizations operate at two layers: applications for broad productivity, plus platforms or agents for a few differentiating use cases.
How the exam tests this
Expect scenario questions that name a business need or a Google offering and ask which layer it belongs to, for example, mapping Gemini for Google Workspace to applications, Agent Platform to platforms, or TPUs to infrastructure. You should also be ready to pick the appropriate layer for an organization's situation: applications for fast, broad productivity wins, platforms or agents for custom data-grounded solutions, and consuming rather than building the infrastructure and models layers. Distractors often confuse platforms with applications or agents with plain models.
Google's Foundation Models: Gemini, Gemma, Imagen, and Veo Explained
- Google's four named foundation models are Gemini (multimodal reasoning), Gemma (lightweight open models), Imagen (image generation), and Veo (video generation).
- Gemini is natively multimodal with a long context window, making it the choice for reasoning, conversation, document analysis, code, and mixed-input tasks.
- Gemma's open weights let organizations run and fine-tune the model on their own infrastructure, trading peak capability for control, customization, and cost efficiency.
- Imagen generates and edits still images from natural-language descriptions; Veo generates high-definition video from text or image prompts.
- Choose by modality first (image work to Imagen, video work to Veo, reasoning and language to Gemini or Gemma), then by control needs (open and self-hosted points to Gemma).
- Standard selection factors still apply: context window, cost, performance, security, availability and reliability, and the need for fine-tuning or customization.
- The models are complements: real projects combine them, and all four are accessible to builders through Model Garden on Agent Platform.
How the exam tests this
Expect direct matching questions: a scenario names a need, generating product photos, producing a short promotional video, analyzing mixed documents and images, or running a model on-premises, and you pick Imagen, Veo, Gemini, or Gemma respectively. The Gemini-versus-Gemma distinction (managed multimodal flagship versus lightweight open models) is a favorite, as is the Imagen-versus-Veo split between still images and video. Also be ready for questions that pair a model with its access path, such as Model Garden on Agent Platform for builders.
Google Cloud's gen AI offerings
35% of the examGoogle Cloud's Gen AI Strengths: Platform, Infrastructure, and Openness
- Google's AI-first approach and research heritage — including the Transformer architecture — create a short path from breakthrough to product, so customers get state-of-the-art capability and a strong roadmap.
- Enterprise-ready means five qualities: responsible, secure, private, reliable, and scalable — match the quality to the concern the exam scenario stresses.
- The comprehensive ecosystem integrates the same Gemini models across the Gemini app, Google Workspace, Gemini Enterprise, and Google Cloud, so skills, governance, and trust carry across every surface.
- The open approach — Gemma open models, Model Garden's first-party, open, and third-party catalog, and open frameworks — preserves choice and reduces lock-in.
- AI-optimized infrastructure combines the AI Hypercomputer architecture, custom-designed TPUs, the latest GPUs, and efficient global data centers, consumed on demand through cloud computing.
- Your data is not used to train Google's foundation models without permission; security, privacy, and governance controls keep enterprise data inside your boundary.
- Low-code and no-code tools, pre-trained models, and APIs democratize AI development so domain experts can build without ML engineering skills.
How the exam tests this
Expect scenario questions that name a business concern — regulated data, global scale, fear of lock-in, no ML engineers on staff — and ask which Google Cloud strength addresses it. Know the five enterprise-ready qualities (responsible, secure, private, reliable, scalable) and be able to match each to a scenario. Be ready to identify the AI Hypercomputer, custom TPUs, GPUs, and data centers as the components of AI-optimized infrastructure, and low-code tools, pre-trained models, and APIs as the levers that democratize AI development.
Prebuilt Gen AI at Work: Gemini App, Gemini Enterprise, and Workspace
- Prebuilt offerings are finished products — fastest time to value, no ML skills required — and the entry point of Google Cloud's gen AI spectrum.
- The Gemini app is a standalone multimodal assistant for individuals; Gemini Advanced adds the most capable models and Gems.
- Gems are custom, reusable versions of Gemini configured once with instructions — the answer when a scenario needs a repeatable personal specialist.
- Gemini Enterprise grounds AI in company data with multimodal search, custom agent capabilities, and the Gemini Notebook API, all permission-aware.
- Gemini for Google Workspace embeds AI in Gmail, Docs, Sheets, Slides, Meet, and Chat — assistance in the flow of work, on the user's own content.
- Distinguish the three by scope and grounding: general knowledge for one person (Gemini app), the user's own files (Workspace), the whole organization's data (Gemini Enterprise).
- Business value scales with scope: personal productivity, workforce-wide time savings, and unlocked institutional knowledge, respectively.
How the exam tests this
The exam presents workplace scenarios and asks which prebuilt offering fits: match by scope (individual versus organization) and grounding (general knowledge, the user's own Workspace content, or company-wide data). Know Gems as the named capability of Gemini Advanced, and multimodal search, custom agent capabilities, and the Gemini Notebook API as the named capabilities of Gemini Enterprise. Expect distractors that offer a custom-built solution when a prebuilt offering already covers the need.
Improving Customer Experience with Agent Search and Customer Engagement Suite
- Google Cloud improves customer experience through two families: external search offerings (Agent Search, grounding with Google Search) and the Customer Engagement Suite.
- Agent Search, on the Gemini Enterprise Agent Platform, embeds Google-quality generative search — with prebuilt RAG and grounded, cited answers — into a company's own sites and apps.
- Agent Search grounds answers in your enterprise content; grounding with Google Search adds fresh world knowledge — know which grounding a scenario needs.
- Conversational Agents resolve customer requests directly via chat and voice, blending deterministic flows with generative answers grounded in company content.
- Agent Assist is a real-time copilot for human agents: suggested responses, surfaced knowledge, transcription, and automatic summaries.
- Conversational Insights analyzes all conversations at scale for topics, sentiment, and contact drivers — enabling root-cause fixes and evidence-based coaching.
- Contact Center as a Service is the cloud-native platform underneath: omnichannel routing and telephony, elastic scale, no on-premises infrastructure.
- Business benefits to cite: higher search conversion, contact deflection, lower handle time, faster agent ramp-up, and rising customer satisfaction.
How the exam tests this
Expect scenario questions that describe a customer-experience problem and ask for the right offering: findability on your own site points to Agent Search, needing current world knowledge points to grounding with Google Search, and contact-center scenarios map to one of the four Customer Engagement Suite components. The most common trap is confusing Conversational Agents (customer-facing self-service) with Agent Assist (support for human agents) — decide by who the AI is talking to. Also be ready to name business benefits: deflection, lower handle time, higher conversion, and satisfaction gains.
How Google Cloud Empowers Developers: Agent Platform and RAG
- Agent Platform is Google Cloud's unified environment for discovering models, grounding them in company data, and building, deploying, and managing gen AI agents.
- Model Garden is a curated library of Google, open, and partner foundation models — its value is informed model choice under one set of enterprise controls.
- Agent Search delivers out-of-the-box, Google-quality search and grounded, source-referenced answers over an organization's own data.
- Agent Platform AutoML trains custom models from a company's labeled data through a guided workflow, with no training code or deep ML expertise required.
- Prebuilt RAG with Agent Search is the managed retrieval path — fastest time to value; RAG APIs are the component path for teams that need control over each pipeline step.
- Custom agents built on Agent Platform go beyond answering questions: they use instructions, grounding, and tools to complete multi-step business tasks.
- The selection rule: take the most packaged offering that meets the need — every step toward custom adds engineering cost that a specific requirement must justify.
How the exam tests this
Exam questions on this objective are matching exercises: a business scenario points to Model Garden (choosing and comparing models), Agent Search (out-of-the-box search and grounded answers over company data), Agent Platform AutoML (custom models from your own labeled data without ML expertise), or a custom agent on Agent Platform (multi-step tasks and actions). Expect at least one question contrasting prebuilt RAG with Agent Search against RAG APIs — the managed pipeline versus components you assemble. The recurring principle is to pick the most packaged offering that satisfies the stated requirement.
Gen AI Agent Tooling: Extensions, Functions, Data Stores, and Plugins
- Tools are the agent's connection to the external environment — without them a model can only generate text from frozen training data; with them an agent can retrieve live information and complete tasks.
- Extensions are standardized bridges to external APIs, executed by the agent platform on the agent's behalf.
- Functions keep execution on your side: the model outputs which function to call and with what arguments, but your application validates and runs the action — the governed choice for consequential operations.
- Data stores ground an agent in company documents and data, delivering current, cited answers that stay accurate through content updates, with no retraining.
- Plugins extend an agent into outside applications and services, reusing capabilities the business already has.
- Cloud Storage backs files and documents, databases back live records, Cloud Functions runs lightweight action logic, Cloud Run hosts containerized services, and Agent Platform is where agents are built and governed.
- Pre-built AI APIs — Speech-to-Text, Text-to-Speech, Translation, Document AI, Cloud Vision, Video Intelligence, Natural Language — give agents ready-made abilities with speech, language, images, video, and documents.
- Google AI Studio is for quick prototyping with Gemini models; Agent Studio is for building grounded, governed, production gen AI agents.
How the exam tests this
This objective is tested through one-line distinctions: extensions (platform calls external APIs), functions (your application executes the model's requested action), data stores (grounded, current, cited answers from company data), and plugins (connections into outside applications). Expect capability-to-API matching questions — a described task such as transcribing calls or reading invoices maps to Speech-to-Text or Document AI. The Agent Studio versus Google AI Studio choice appears as a scenario: prototyping and experimentation point to Google AI Studio, while grounded, governed, production agents point to Agent Studio.
Techniques to improve gen AI model output
20% of the examOvercoming Foundation Model Limitations: Grounding, RAG, and HITL
- Foundation model limitations all stem from data dependency: the model only knows what its training data contained, up to its knowledge cutoff.
- Grounding connects model output to verifiable sources; RAG implements it by retrieving relevant enterprise content and inserting it into the prompt before generation.
- Hallucinations and stale answers point to grounding and RAG as the fix; generic tone or format points to prompt engineering; persistent domain gaps point to fine-tuning.
- Human in the loop (HITL) is the standing safeguard for high-stakes and fairness-sensitive decisions, and reviewer feedback improves the system over time.
- The cost-effective sequence is prompt engineering first, grounding and RAG next, fine-tuning last — escalate only when the cheaper technique falls short.
- Continuous monitoring covers KPIs, performance tracking, drift monitoring, versioning, automatic model upgrades, and security patches — launch is the start, not the end.
- The Agent Platform Feature Store centrally manages feature data so models and agents consume consistent, governed inputs across environments.
How the exam tests this
Objective 3.1 tests whether you can match each foundation model limitation to its Google Cloud-recommended remedy. Expect scenarios where a chatbot invents answers or cites outdated information (answer: grounding or RAG), where output tone or format is wrong (prompt engineering), where a persistent domain gap remains (fine-tuning), and where high-stakes or fairness-sensitive decisions need review (human in the loop). Monitoring questions test recognition of KPIs, versioning, drift monitoring, performance tracking, automatic model upgrades, security patches, and the Agent Platform Feature Store as continuous, post-launch practices.
Prompt Engineering Techniques: Few-Shot, Role, and Chain-of-Thought
- Prompt engineering is deliberately designing the model's input — instruction, context, format, examples — and is the fastest, cheapest way to improve gen AI output.
- Zero-shot means no examples, one-shot means one, few-shot means several; add examples when output misses your format or standard, and use the fewest that work.
- Role prompting assigns a persona that steers tone, depth, and vocabulary — but it changes how the model communicates, not what it factually knows.
- Prompt chaining breaks complex work into linked steps with inspectable intermediate outputs, moving quality control into the middle of the process.
- Chain-of-thought prompting asks for step-by-step reasoning before the answer, improving multi-step logic and making conclusions auditable.
- ReAct prompting interleaves reasoning with actions such as search or tool lookups, and is the conceptual foundation of AI agents.
- Techniques combine in practice: a role plus few-shot examples inside a chain, with ReAct gathering live information, is a typical production pattern.
How the exam tests this
Objective 3.2 tests definitions and technique-to-scenario matching. Expect to distinguish zero-shot, one-shot, and few-shot by the number of examples in the prompt, and to pick the right technique for a scenario: a persona or audience need points to role prompting, a multi-stage workflow points to prompt chaining, step-by-step reasoning or auditable logic points to chain-of-thought, and a task requiring the model to gather external information mid-task points to ReAct. Also be ready to state why prompt engineering matters: it is the fastest, cheapest lever for better LLM output and requires no model changes.
Grounding Techniques: RAG, Google Search, and Sampling Settings
- Grounding connects LLM responses to verifiable data sources, reducing hallucinations and keeping answers current without retraining the model.
- First-party data is what your organization owns, third-party data is acquired from external providers, and world data is broad public knowledge such as Google Search results.
- RAG retrieves relevant content at query time and generates from it, making output more accurate, current, and attributable with citations.
- Pre-built RAG with Agent Search is the fastest path to grounding on enterprise content; RAG APIs give developers component-level control over a custom retrieval pipeline.
- Grounding with Google Search grounds responses in fresh world data, directly addressing the model's knowledge cutoff for public, time-sensitive questions.
- Temperature controls randomness (low = focused and consistent, high = varied and creative); top-p limits token selection to the smallest set whose probabilities sum to p.
- Safety settings set configurable thresholds for blocking harmful content, and output length caps response size — both tuned per use case, not fixed.
- Tokens are the unit of gen AI cost and capacity: token count and output length are how leaders control spend and response size.
How the exam tests this
The exam presents business scenarios and asks you to pick the right grounding source (first-party, third-party, or world data) or the right Google Cloud offering (pre-built RAG with Agent Search, RAG APIs, or grounding with Google Search). Expect questions on how RAG changes model output — accuracy, freshness, citations, fewer hallucinations — without retraining. Sampling questions typically describe a desired behavior, such as consistent factual answers or creative variety, and ask which parameter to adjust: temperature, top-p, token count, output length, or safety settings.
Business strategies for a successful gen AI solution
15% of the examImplementing a Transformational Gen AI Solution: The Google Cloud Steps
- A transformational gen AI solution starts from a business need and works backward to the technology, never the reverse.
- The main solution types are text generation, image generation, code generation, and personalized user experiences, and each maps to distinct business problems.
- Business requirements (outcomes, users, budget, compliance) and technical constraints (data quality, integration, skills, security) jointly determine the right solution.
- Choose the simplest approach that meets the requirement; every layer of customization adds cost, maintenance, and risk.
- The recommended integration sequence is: define vision and use cases, assess readiness, select the solution, pilot, establish governance and security, integrate and scale, then measure and iterate.
- A pilot converts uncertainty into evidence cheaply, and a pilot that prevents a costly mistake is a success.
- Impact measurement requires KPIs defined before launch and a baseline to compare against; ROI weighs total value against total cost, including governance and training.
- Most gen AI failures are strategic, caused by skipping a recommended step, not by technical shortcomings of the models.
How the exam tests this
Expect scenario questions that describe a business need and ask which type of gen AI solution fits, or that describe a struggling initiative and ask which recommended step was skipped. You should be able to order the implementation steps, distinguish business requirements from technical constraints, and pick the KPI or measurement technique that matches a stated goal. Questions reward business judgment, choosing the simplest adequate solution and piloting before scaling, over technical depth.
Secure AI and SAIF: Protecting AI Systems on Google Cloud
- Secure AI means protecting an AI system's data, models, infrastructure, and interactions from attacks and misuse across the entire ML lifecycle.
- Know the core threats conceptually: data poisoning corrupts training data, prompt injection manipulates a deployed model through its inputs, model theft steals the model asset, and evasion and leakage round out the list.
- Security must cover every lifecycle stage, data, training, deployment, and monitoring, because each stage exposes different assets and the weakest stage defines overall risk.
- SAIF is Google's conceptual framework for securing AI systems: it extends existing security foundations to AI, brings AI into threat detection, and keeps controls consistent, automated, and matched to business risk.
- SAIF's business benefits are reduced breach risk, faster and more confident AI adoption, stronger compliance posture, and preserved customer trust.
- Match the Google Cloud tools to their purpose: secure-by-design infrastructure (protected foundation with default encryption), IAM (least-privilege access control), Security Command Center (centralized posture and threat visibility), workload monitoring (anomaly detection on running systems).
- Security on Google Cloud is shared: Google secures the platform; the customer governs access, data, and acceptable use.
How the exam tests this
Expect definition and matching questions: identify what secure AI means, pick SAIF's purpose from a list of plausible descriptions, and match secure-by-design infrastructure, IAM, Security Command Center, and workload monitoring to the job each performs. Scenario questions describe an attack, poisoned training data, a manipulated prompt, an over-permissive access grant, and ask you to name the threat or the control that addresses it. Keep the lifecycle framing in mind: the exam rewards answers that place security at every stage, not just at deployment.
Responsible AI in Business: Transparency, Privacy, Bias, and Fairness
- Responsible AI is a business requirement, not just an ethical ideal — it protects trust, brand reputation, and regulatory standing.
- Google's AI Principles commit to socially beneficial AI that avoids unfair bias, is safe, accountable to people, and privacy-first — but the deploying business always retains accountability for its own use.
- Transparency means disclosing when and how AI is used; concealment turns ordinary AI limitations into trust-destroying incidents.
- Anonymization irreversibly removes identifying information; pseudonymization replaces identifiers with reversible tokens kept separately — pseudonymized data is still personal data under most privacy laws.
- Model outputs reflect training data: poor or unrepresentative data produces biased, unfair outcomes at scale, so data quality is a fairness issue.
- Accountability requires named owners, governance processes, and human oversight — especially a human in the loop for high-stakes decisions.
- Explainability, including grounding answers in cited sources, turns opaque AI assertions into verifiable ones and is often a regulatory expectation for consequential decisions.
How the exam tests this
Expect scenario questions that ask you to identify which responsible AI dimension a situation illustrates — an undisclosed chatbot (transparency), re-identifiable customer data (pseudonymization and privacy), skewed outcomes across demographic groups (bias and fairness), or an automated decision no one can justify (explainability and accountability). Know the difference between anonymization and pseudonymization precisely, and remember that Google's AI Principles include avoiding unfair bias, safety, accountability to people, and privacy by design. Questions also test the business framing: responsible AI protects trust, brand, and regulatory standing, and accountability always stays with the deploying organization.