“"The practice exams closely matched the certification objectives and helped me build confidence across every topic before my exam."”
Shekar K
Senior Machine Learning Engineer
Google doesn’t publish a passing score for this exam, and it won’t tell you how many points each question is worth — but it’s upfront that the test runs 50 to 60 questions across a two-hour window, delivered as multiple choice and multiple select, either online-proctored from home or at a test center. Two hours for up to 60 questions sounds generous until you actually sit the exam: a meaningful chunk of those questions are multi-paragraph scenarios describing a company’s data pipeline, team constraints, and a half-broken model, followed by “what should you do next?” You’re not recalling a fact — you’re weighing two or three plausible Google Cloud services against each other and picking the one that fits the stated constraints (cost, latency, team skill level, compliance). Budget roughly two minutes per question and expect to flag several for a second pass.
A newer wrinkle: as of the exam version current in 2026, a slice of the test is generative AI–specific — questions on Model Garden, Vertex AI Agent Builder, and evaluating LLM output sit alongside the classic MLOps and model-training material. If your mental model of this exam is still “mostly AutoML and TensorFlow,” you’re preparing for an older version of the test.
Weightings below are copied directly from Google’s official exam guide, current as of June 1, 2026.
Domain | Weight |
|---|---|
1. Architecting low-code AI solutions | ~13% |
2. Collaborating to manage data and models | ~16% |
3. Scaling prototypes into ML models | ~21% |
4. Serving and scaling models | ~20% |
5. Automating and orchestrating ML pipelines | ~18% |
6. Monitoring AI solutions | ~13% |
Domain 3 (scaling prototypes) and Domain 4 (serving models) together make up more than a third of the exam. If your study time is split evenly across all six domains, you’re under-investing in the two that carry the most questions.
Domain 1 covers BigQuery ML, AutoML, and building with Gemini, Imagen, and other Model Garden models — including when to fine-tune a foundation model versus calling it off the shelf.
Domain 2 is about notebooks (Vertex AI Workbench, Colab Enterprise), feature engineering at scale, and tracking experiments — the “before training” work.
Domain 3 is model and hardware selection under constraints: choosing between ARIMA, a DNN, and an LLM for the same business problem, then picking CPU, GPU, or TPU and justifying it.
Domain 4 is deployment mechanics: batch vs. online inference, canary rollouts, Feature Store at serving time, and scaling the serving backend under load.
Domain 5 is pipeline orchestration and CI/CD/CT — Vertex AI Pipelines, Kubeflow, and retraining triggers.
Domain 6 is what happens after launch: drift detection, model explainability, and securing AI systems against prompt injection and data leakage.
Three things trip people up more than the official exam guide would suggest:
Choosing between near-identical services. The exam loves putting two Google Cloud tools in front of you that could both technically solve the stated problem — BigQuery ML vs. Vertex AI AutoML, or Vertex AI Pipelines vs. Cloud Composer — and asking which one fits given a specific constraint like “the team only knows SQL” or “this needs to integrate with an existing Airflow setup.” Memorizing what each service does isn’t enough; you need to know when each one is the wrong choice.
Monitoring and drift, not just deployment. It’s easy to study hard for “how do I deploy a model” and treat Domain 6 as an afterthought. But distinguishing training-serving skew from data drift from concept drift — and knowing which Vertex AI Model Monitoring configuration catches each — comes up often enough that skipping it costs points.
The generative AI material isn’t optional anymore. Some candidates still prep as if this is purely a predictive-ML exam and treat Model Garden, prompt engineering, and LLM evaluation as a minor add-on. Given the current domain weightings, that’s a mistake — questions on evaluating gen AI output quality and optimizing Gemini-based applications for cost and latency show up across multiple domains, not just Domain 1.
Because so many questions are scenario-based rather than recall-based, drilling flashcard-style “what does BigQuery ML do” questions will only get you partway. The more useful habit is to read each practice scenario twice before looking at the answer choices, write down (even mentally) what the actual constraint is — cost, latency, interpretability, team skill — and only then evaluate the options against that constraint. When you get a question wrong here, the value isn’t the correct letter; it’s understanding which constraint you missed or misweighted. Pay close attention to explanations that compare the “almost right” wrong answer to the correct one — those pairs are exactly how the exam tests you.
Studying the services in isolation instead of practicing the trade-off reasoning between them.
Skipping hands-on time with Vertex AI entirely and relying on reading alone — several questions assume you’ve actually clicked through a training job or a pipeline run.
Treating MLOps (Domains 5 and 6) as secondary to model-building (Domain 3) when it’s nearly as heavily weighted.
Going in without current material and getting caught out by the gen AI content added to more recent versions of the exam.
New to Google Cloud but experienced with ML generally: Plan for 8–10 weeks. Spend the first few weeks mapping your existing ML knowledge onto Vertex AI’s specific services and naming conventions, then shift to scenario practice.
Already working on Google Cloud in a related role: 4–6 weeks is usually , concentrated on the services you haven’t touched day to day — Feature Store, Model Monitoring, and pipeline orchestration are common gaps even for people who use Vertex AI Training regularly.
Retaking after a fail: Don’t just redo the same study plan. Go back to your practice test results, find the domain where you scored lowest, and check whether the gap is knowledge (you don’t know the service) or judgment (you know the services but picked the wrong one under a stated constraint) — the fix is different for each professional machine learning engineer exam questions.
Google updates this exam guide periodically to track Vertex AI’s product changes, and the most recent material shift added substantial generative AI content — Model Garden, Agent Builder, and gen AI evaluation — that wasn’t part of earlier versions of the test. If you’re studying from an older guide, a course, or practice questions written before this update, you’re likely missing a meaningful share of what’s now tested. Always check the exam guide date against today before trusting a study resource’s domain breakdown.
Last updated on Oct, 28 2026