cert
cert-1
cert-2

Pass Google Professional Machine Learning Engineer Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
Professional Machine Learning Engineer Exam - Verified By Experts
Professional Machine Learning Engineer Premium Bundle
$29.98

Professional Machine Learning Engineer Premium Bundle

$79.99
$109.97
  • Premium File 402 Questions & Answers. Last update: Nov 13, 2026
  • Training Course 69 Video Lectures
  • Study Guide 376 Pages
 
$109.97
$79.99
accept 47 downloads in last 7 days
block-screenshots
Purchase Google Professional Machine Learning Engineer Exam Training Products Individually
Google Professional Machine Learning Engineer Premium File
Premium File 402 Q&A
$76.99$69.99
Google Professional Machine Learning Engineer Video Training Course
Training Course 69 Lectures
$21.99 $19.99
Google Professional Machine Learning Engineer PDF Study Guide
Study Guide 376 Pages
$21.99 $19.99
Google Professional Machine Learning Engineer Practice Test 12

Question 110

During a production ML inference release on Google Cloud, the following condition occurs: A marketing model scores ten million customers every midnight, but engineers keep a low-latency online endpoint running continuously for the once-daily batch. The service must meet its agreed quality and latency requirements. Which technical explanation best accounts for the reported behavior?

  1. Index ordering is part of the model contract; separate stale label dictionaries can silently corrupt inference.
  2. CPU usage can be weakly related to accelerator or queue-bound inference workloads.
  3. Mutable tags can point to new image content, defeating reproducibility even if the deployment text is unchanged.
  4. Batch workloads need throughput and scheduling guarantees, whereas real-time endpoints serve interactive low-latency calls.

Explanation

Correct Answer

D:

Batch workloads need throughput and scheduling guarantees, whereas real-time endpoints serve interactive low-latency calls. This explains the mechanism behind batch versus online inference schedule and why the described failure is possible. A discriminating investigation is: Examine scoring cadence, input size, end-to-end completion window, idle endpoint cost and per-record response requirements. The corresponding repair is: Choose a managed batch inference or scheduled container batch workflow instead of an always-on online endpoint.

Incorrect Answers

A:

Index ordering is part of the model contract; separate stale label dictionaries can silently corrupt inference. This principle describes custom postprocessing label mapping drift, which is not the cause of the observed batch versus online inference schedule failure. The controlling explanation is: Batch workloads need throughput and scheduling guarantees, whereas real-time endpoints serve interactive low-latency calls.

B:

CPU usage can be weakly related to accelerator or queue-bound inference workloads. This principle describes throughput-based autoscaling versus cpu metric, which is not the cause of the observed batch versus online inference schedule failure. The controlling explanation is: Batch workloads need throughput and scheduling guarantees, whereas real-time endpoints serve interactive low-latency calls.

C:

Mutable tags can point to new image content, defeating reproducibility even if the deployment text is unchanged. This principle describes model artifact image digest reproducibility, which is not the cause of the observed batch versus online inference schedule failure. The controlling explanation is: Batch workloads need throughput and scheduling guarantees, whereas real-time endpoints serve interactive low-latency calls.

Question 111

During a postdeployment AI safety and reliability review, the following condition occurs: A transaction fraud model's feature distributions stay nearly unchanged while the relationship between inputs and observed fraud outcomes deteriorates. The model owner must provide repeatable evidence rather than a cosmetic dashboard change. Which evidence most directly establishes what is wrong with this AI or ML workflow?

  1. Examine explanation distributions, feature generation changes, protected attribute proxies and prediction outcomes by cohort.
  2. Inspect inference event IDs, timestamps, later label keys and the quality monitoring join schema.
  3. Compare time-stratified labeled performance, feature distribution stability and delayed ground truth coverage.
  4. Review prompt token counts, output length, cache behavior, p95 model latency and cost per successful task.

Explanation

Correct Answer

C:

Compare time-stratified labeled performance, feature distribution stability and delayed ground truth coverage. This inspects evidence relevant to concept drift with stable feature statistics. Concept drift changes conditional label relationships and may occur without obvious marginal feature drift. After identifying the cause, the matching correction is: Monitor outcome-based quality metrics on matured cohorts and retrain when verified concept drift is significant.

Incorrect Answers

A:

Examine explanation distributions, feature generation changes, protected attribute proxies and prediction outcomes by cohort. This examines feature attribution drift after deployment rather than the specific mechanism reported here. It is not the decisive first check for concept drift with stable feature statistics. The relevant evidence is: Compare time-stratified labeled performance, feature distribution stability and delayed ground truth coverage.

B:

Inspect inference event IDs, timestamps, later label keys and the quality monitoring join schema. This examines ground truth association for quality monitoring rather than the specific mechanism reported here. It is not the decisive first check for concept drift with stable feature statistics. The relevant evidence is: Compare time-stratified labeled performance, feature distribution stability and delayed ground truth coverage.

D:

Review prompt token counts, output length, cache behavior, p95 model latency and cost per successful task. This examines llm latency and cost token regression rather than the specific mechanism reported here. It is not the decisive first check for concept drift with stable feature statistics. The relevant evidence is: Compare time-stratified labeled performance, feature distribution stability and delayed ground truth coverage.

Question 112

During model-training validation on a Google Cloud experimental project, the following condition occurs: A weeklong custom training job uses preemptible capacity but saves checkpoints only to a temporary local container filesystem. The change should preserve a meaningful independent model-quality comparison. Which evidence most directly establishes what is wrong with this AI or ML workflow?

  1. Inspect gradient ranges, loss-scaling logs, overflow events and the affected operations with test batches.
  2. Review parameter ranges, total trial count, training budget and the metric used to rank completed experiments.
  3. Examine model governance constraints, feature sensitivity, explanation fidelity and performance of simpler interpretable baselines.
  4. Inspect shutdown events, checkpoint directory, durable artifact transfers and restoration logic after simulated interruptions.

Explanation

Correct Answer

D:

Inspect shutdown events, checkpoint directory, durable artifact transfers and restoration logic after simulated interruptions. This inspects evidence relevant to training checkpoint persistence across interruptions. Preemptible execution can end abruptly; local-only state is not a durable recovery mechanism. After identifying the cause, the matching correction is: Persist versioned checkpoints in durable Cloud Storage and make the training code resume optimizer and model state.

Incorrect Answers

A:

Inspect gradient ranges, loss-scaling logs, overflow events and the affected operations with test batches. This examines mixed precision overflow diagnosis rather than the specific mechanism reported here. It is not the decisive first check for training checkpoint persistence across interruptions. The relevant evidence is: Inspect shutdown events, checkpoint directory, durable artifact transfers and restoration logic after simulated interruptions.

B:

Review parameter ranges, total trial count, training budget and the metric used to rank completed experiments. This examines hyperparameter search budget limit rather than the specific mechanism reported here. It is not the decisive first check for training checkpoint persistence across interruptions. The relevant evidence is: Inspect shutdown events, checkpoint directory, durable artifact transfers and restoration logic after simulated interruptions.

C:

Examine model governance constraints, feature sensitivity, explanation fidelity and performance of simpler interpretable baselines. This examines interpretability-constrained model baseline rather than the specific mechanism reported here. It is not the decisive first check for training checkpoint persistence across interruptions. The relevant evidence is: Inspect shutdown events, checkpoint directory, durable artifact transfers and restoration logic after simulated interruptions.

Question 113

During a controlled replay of the data and model handoff to a second engineering team, the following condition occurs: Two ML engineers rerun the same notebook and obtain incompatible model artifacts because one environment silently installs a newer Python library release. The handoff must preserve privacy, lineage and testable behavior. Which result is the strongest postchange evidence of success?

  1. Independent notebook runs resolve the same approved libraries and produce comparable metric and artifact outputs.
  2. A clean notebook loads the exact model revision, runs representative inputs and reports consistent outputs.
  3. A newly started Workbench or Colab Enterprise runtime reproduces the complete experiment without undocumented manual cell order.
  4. For every row the feature version predates its prediction cutoff and prospective holdout quality is realistic.

Explanation

Correct Answer

A:

Independent notebook runs resolve the same approved libraries and produce comparable metric and artifact outputs. This is specific acceptance evidence for notebook dependency lock reproducibility. Notebook cells alone do not capture interpreter and package state; reproducibility depends on the execution environment. It confirms the controlled correction: Pin compatible dependency versions in a reproducible environment specification and validate fresh builds on clean runtimes.

Incorrect Answers

B:

A clean notebook loads the exact model revision, runs representative inputs and reports consistent outputs. This result could demonstrate success for model garden jax accelerator compatibility but not for the stated notebook dependency lock reproducibility issue. The direct test is: Independent notebook runs resolve the same approved libraries and produce comparable metric and artifact outputs.

C:

A newly started Workbench or Colab Enterprise runtime reproduces the complete experiment without undocumented manual cell order. This result could demonstrate success for notebook transient state and execution order but not for the stated notebook dependency lock reproducibility issue. The direct test is: Independent notebook runs resolve the same approved libraries and produce comparable metric and artifact outputs.

D:

For every row the feature version predates its prediction cutoff and prospective holdout quality is realistic. This result could demonstrate success for point-in-time feature leakage prevention but not for the stated notebook dependency lock reproducibility issue. The direct test is: Independent notebook runs resolve the same approved libraries and produce comparable metric and artifact outputs.

Question 114

During a regulated MLOps pipeline deployment, the following condition occurs: A distributed batch preprocessing workflow launches thousands of Ray tasks but loses intermediate outputs after one worker fails because object references are not persisted appropriately. The workflow must be repeatable and protect the last approved production model. Which diagnostic check should be performed FIRST to isolate the described cause?

  1. Inspect component input parameters, artifact provenance, caching settings and source snapshot identifiers.
  2. Inspect Cloud Build substitutions, commit SHAs, model registry versions, signed image digests and approval records.
  3. Inspect task lineage, retries, durable checkpoints, object-store pressure and failed worker logs.
  4. Inspect incoming schema versions, validation logs, casting rules and downstream prediction anomalies.

Explanation

Correct Answer

C:

Inspect task lineage, retries, durable checkpoints, object-store pressure and failed worker logs. This inspects evidence relevant to ray distributed task failure isolation. Distributed in-memory object stores are not durable archival storage; failure recovery needs explicit design. After identifying the cause, the matching correction is: Use supported Ray retry policies and durable checkpoints at suitable stage boundaries instead of relying only on worker memory.

Incorrect Answers

A:

Inspect component input parameters, artifact provenance, caching settings and source snapshot identifiers. This examines kubeflow component cache invalidation rather than the specific mechanism reported here. It is not the decisive first check for ray distributed task failure isolation. The relevant evidence is: Inspect task lineage, retries, durable checkpoints, object-store pressure and failed worker logs.

B:

Inspect Cloud Build substitutions, commit SHAs, model registry versions, signed image digests and approval records. This examines cloud build release version promotion rather than the specific mechanism reported here. It is not the decisive first check for ray distributed task failure isolation. The relevant evidence is: Inspect task lineage, retries, durable checkpoints, object-store pressure and failed worker logs.

D:

Inspect incoming schema versions, validation logs, casting rules and downstream prediction anomalies. This examines serving schema validation component rather than the specific mechanism reported here. It is not the decisive first check for ray distributed task failure isolation. The relevant evidence is: Inspect task lineage, retries, durable checkpoints, object-store pressure and failed worker logs.

Question 115

During a regulated MLOps pipeline deployment, the following condition occurs: A data ingestion pipeline changes a numeric feature into a string, but the model-serving path accepts it and silently substitutes missing values. The workflow must be repeatable and protect the last approved production model. What implementation change resolves the specific issue without substituting an unrelated fix?

  1. Configure failure and stale-model alerts tied to actionable run-status and freshness service objectives.
  2. Enforce a shared typed schema contract and reject incompatible feature versions before training or inference.
  3. Package the fitted preprocessing component with the model and apply the same validated transform in both paths.
  4. Fail protected build or release stages when prohibited vulnerabilities exist and require documented exceptions for approved deviations.

Explanation

Correct Answer

B:

Enforce a shared typed schema contract and reject incompatible feature versions before training or inference. This is the targeted corrective response for serving schema validation component. Silent casting can hide producer errors and produce invalid model inputs across pipeline boundaries. Verify the diagnosis using: Inspect incoming schema versions, validation logs, casting rules and downstream prediction anomalies. Confirm success using: An incompatible payload fails visibly while compatible older versions follow documented conversion rules.

Incorrect Answers

A:

Configure failure and stale-model alerts tied to actionable run-status and freshness service objectives. This action addresses pipeline notification alert on silent failure, not the failure in the described serving schema validation component case. The targeted correction is: Enforce a shared typed schema contract and reject incompatible feature versions before training or inference.

C:

Package the fitted preprocessing component with the model and apply the same validated transform in both paths. This action addresses training serving preprocessing artifact sharing, not the failure in the described serving schema validation component case. The targeted correction is: Enforce a shared typed schema contract and reject incompatible feature versions before training or inference.

D:

Fail protected build or release stages when prohibited vulnerabilities exist and require documented exceptions for approved deviations. This action addresses cloud build container security gate, not the failure in the described serving schema validation component case. The targeted correction is: Enforce a shared typed schema contract and reject incompatible feature versions before training or inference.

Question 116

While reproducing a training orchestration incident in isolated staging, the following condition occurs: A fraud classifier is retrained every night despite true chargeback outcomes arriving weeks later, producing highly incomplete recent labels. The team requires an idempotent pipeline behavior and traceable evidence. What implementation change resolves the specific issue without substituting an unrelated fix?

  1. Filter validated completed-dataset events and enforce an idempotent manifest-based training trigger.
  2. Require candidate evaluation against a governed baseline with an enforced acceptance threshold before promotion.
  3. Use a retraining policy with significant trigger thresholds, independent evaluation and staged deployment approval.
  4. Train only on adequately matured labeled cohorts and monitor recent feature drift separately until outcomes arrive.

Explanation

Correct Answer

D:

Train only on adequately matured labeled cohorts and monitor recent feature drift separately until outcomes arrive. This is the targeted corrective response for scheduled retraining on delayed ground truth. Unobserved outcomes cannot serve as reliable supervised labels regardless of the desired retraining schedule. Verify the diagnosis using: Inspect label arrival times, cohort maturity, feedback collection coverage and effective training cutoffs. Confirm success using: Training manifests exclude unlabeled recent transactions and measured metrics use verified ground truth.

Incorrect Answers

A:

Filter validated completed-dataset events and enforce an idempotent manifest-based training trigger. This action addresses eventbridge equivalent event trigger on storage, not the failure in the described scheduled retraining on delayed ground truth case. The targeted correction is: Train only on adequately matured labeled cohorts and monitor recent feature drift separately until outcomes arrive.

B:

Require candidate evaluation against a governed baseline with an enforced acceptance threshold before promotion. This action addresses model evaluation gate before deployment, not the failure in the described scheduled retraining on delayed ground truth case. The targeted correction is: Train only on adequately matured labeled cohorts and monitor recent feature drift separately until outcomes arrive.

C:

Use a retraining policy with significant trigger thresholds, independent evaluation and staged deployment approval. This action addresses canary failure feedback into ct policy, not the failure in the described scheduled retraining on delayed ground truth case. The targeted correction is: Train only on adequately matured labeled cohorts and monitor recent feature drift separately until outcomes arrive.

Question 117

While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A model fits in one GPU but a huge dataset takes too long to process, and engineers propose splitting its layers between devices without memory pressure. Engineers need an auditable, resource-aware correction to the issue. Which targeted engineering change most directly addresses the failure?

  1. Reduce the learning rate and use justified parameter-efficient tuning or partial freezing with a controlled evaluation set.
  2. Prefer suitable data parallel replicas with synchronized gradient aggregation, then benchmark scale efficiency.
  3. Evaluate ARIMA_PLUS or an appropriate time-series forecasting model before adopting an expensive generative approach.
  4. Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping.

Explanation

Correct Answer

B:

Prefer suitable data parallel replicas with synchronized gradient aggregation, then benchmark scale efficiency. This is the targeted corrective response for distributed data parallel gradient synchronization. When a model fits on each worker, partitioning training data is often more suitable than splitting the model itself. Verify the diagnosis using: Measure model footprint, per-device utilization, communication cost and batch throughput on one and multiple accelerators. Confirm success using: More replicas shorten epoch time without materially changing convergence or causing network communication to dominate.

Incorrect Answers

A:

Reduce the learning rate and use justified parameter-efficient tuning or partial freezing with a controlled evaluation set. This action addresses fine-tuning catastrophic forgetting, not the failure in the described distributed data parallel gradient synchronization case. The targeted correction is: Prefer suitable data parallel replicas with synchronized gradient aggregation, then benchmark scale efficiency.

C:

Evaluate ARIMA_PLUS or an appropriate time-series forecasting model before adopting an expensive generative approach. This action addresses forecast trend and seasonality versus llm, not the failure in the described distributed data parallel gradient synchronization case. The targeted correction is: Prefer suitable data parallel replicas with synchronized gradient aggregation, then benchmark scale efficiency.

D:

Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping. This action addresses hyperparameter search budget limit, not the failure in the described distributed data parallel gradient synchronization case. The targeted correction is: Prefer suitable data parallel replicas with synchronized gradient aggregation, then benchmark scale efficiency.

Question 118

As the team tests a new governed AI release against adversarial and normal data, the following condition occurs: A public conversational app relies on a single instruction asking the model to avoid prohibited content but does not test or screen generated responses. The fix must retain legitimate model usefulness and appropriate controls. Which targeted engineering change most directly addresses the failure?

  1. Restrict dataset and bucket access by principal and resource; enforce approved egress controls and audit sensitive reads.
  2. Apply supported safety filters and output policy checks with a controlled refusal or human review path for blocked results.
  3. Evaluate and address documented subgroup disparities using appropriate fairness metrics and approved data/model changes.
  4. Add groundedness and factual correctness checks to a representative gen AI evaluation suite and tune retrieval or prompting accordingly.

Explanation

Correct Answer

B:

Apply supported safety filters and output policy checks with a controlled refusal or human review path for blocked results. This is the targeted corrective response for gen ai output safety policy enforcement. Prompt wording alone is not a reliable comprehensive safety boundary for public generative applications. Verify the diagnosis using: Review the business safety taxonomy, representative adversarial evaluation prompts, safety-filter configuration and escalation design. Confirm success using: Red-team test prompts trigger expected safeguards while legitimate requests continue to receive useful responses.

Incorrect Answers

A:

Restrict dataset and bucket access by principal and resource; enforce approved egress controls and audit sensitive reads. This action addresses training data exfiltration through broad access, not the failure in the described gen ai output safety policy enforcement case. The targeted correction is: Apply supported safety filters and output policy checks with a controlled refusal or human review path for blocked results.

C:

Evaluate and address documented subgroup disparities using appropriate fairness metrics and approved data/model changes. This action addresses model feature bias by subgroup, not the failure in the described gen ai output safety policy enforcement case. The targeted correction is: Apply supported safety filters and output policy checks with a controlled refusal or human review path for blocked results.

D:

Add groundedness and factual correctness checks to a representative gen AI evaluation suite and tune retrieval or prompting accordingly. This action addresses generative ai factual grounding evaluation, not the failure in the described gen ai output safety policy enforcement case. The targeted correction is: Apply supported safety filters and output policy checks with a controlled refusal or human review path for blocked results.

Question 119

Within a jointly maintained Google Cloud data science workspace, the following condition occurs: An image labeling task sends full customer identity and contact records to external annotators although only product photographs need annotation. Collaborators must avoid expanding data access or breaking experiment reproducibility. Which outcome most directly demonstrates a successful, measurable fix?

  1. Annotators can complete validated labels without seeing identifying data and the project retains compliant traceability.
  2. A production model identifier resolves to its training execution, immutable artifacts, approvals and input dataset.
  3. A held-out clean sample preserves meaningful ranges while invalid spikes trigger visible data-quality exceptions.
  4. Known records retrieve corresponding historical and current feature values for the intended entity without mismatched accounts.

Explanation

Correct Answer

A:

Annotators can complete validated labels without seeing identifying data and the project retains compliant traceability. This is specific acceptance evidence for data minimization for labeling inputs. Protecting data in transit does not excuse sending unnecessary sensitive attributes to a third-party workflow. It confirms the controlled correction: Redact or tokenize unnecessary identifying fields before labeling and limit access to approved mappings.

Incorrect Answers

B:

A production model identifier resolves to its training execution, immutable artifacts, approvals and input dataset. This result could demonstrate success for ml metadata lineage for production model but not for the stated data minimization for labeling inputs issue. The direct test is: Annotators can complete validated labels without seeing identifying data and the project retains compliant traceability.

C:

A held-out clean sample preserves meaningful ranges while invalid spikes trigger visible data-quality exceptions. This result could demonstrate success for outlier handling before feature standardization but not for the stated data minimization for labeling inputs issue. The direct test is: Annotators can complete validated labels without seeing identifying data and the project retains compliant traceability.

D:

Known records retrieve corresponding historical and current feature values for the intended entity without mismatched accounts. This result could demonstrate success for feature store online and offline entity alignment but not for the stated data minimization for labeling inputs issue. The direct test is: Annotators can complete validated labels without seeing identifying data and the project retains compliant traceability.

Question 120

During model-training validation on a Google Cloud experimental project, the following condition occurs: An existing TensorFlow training pipeline has large dense matrix operations and engineers select a TPU solely from marketing without checking model operation support. The change should preserve a meaningful independent model-quality comparison. Which outcome most directly demonstrates a successful, measurable fix?

  1. The chosen accelerator meets throughput and convergence expectations without unsupported operations or unstable retracing.
  2. Scale efficiency improves and model quality remains stable without synchronization stalls dominating every step.
  3. GPU utilization and examples per second rise without changing model accuracy or violating data-order requirements.
  4. The training manifest contains traceable permitted sources and safety tests detect known prohibited outputs.

Explanation

Correct Answer

A:

The chosen accelerator meets throughput and convergence expectations without unsupported operations or unstable retracing. This is specific acceptance evidence for tpu versus gpu for tensorflow workload. TPU and GPU performance depends on operations, data pipeline and framework integration, not headline compute alone. It confirms the controlled correction: Benchmark compatible TPU and GPU configurations and select hardware based on measured throughput and target budget.

Incorrect Answers

B:

Scale efficiency improves and model quality remains stable without synchronization stalls dominating every step. This result could demonstrate success for distributed gradient communication bottleneck but not for the stated tpu versus gpu for tensorflow workload issue. The direct test is: The chosen accelerator meets throughput and convergence expectations without unsupported operations or unstable retracing.

C:

GPU utilization and examples per second rise without changing model accuracy or violating data-order requirements. This result could demonstrate success for accelerator starvation from slow input pipeline but not for the stated tpu versus gpu for tensorflow workload issue. The direct test is: The chosen accelerator meets throughput and convergence expectations without unsupported operations or unstable retracing.

D:

The training manifest contains traceable permitted sources and safety tests detect known prohibited outputs. This result could demonstrate success for fine-tuning image generator data rights but not for the stated tpu versus gpu for tensorflow workload issue. The direct test is: The chosen accelerator meets throughput and convergence expectations without unsupported operations or unstable retracing.

Professional Machine Learning Engineer Practice Tests