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 108

Question 1070

Within a jointly maintained Google Cloud data science workspace, the following condition occurs: A numeric risk feature contains occasional physically impossible sensor spikes that inflate its fitted scale and degrade otherwise normal predictions. Collaborators must avoid expanding data access or breaking experiment reproducibility. Which result is the strongest postchange evidence of success?

  1. A newly started Workbench or Colab Enterprise runtime reproduces the complete experiment without undocumented manual cell order.
  2. Long-tail shuffle tasks shorten and the normalized output row count matches a reference implementation.
  3. A held-out clean sample preserves meaningful ranges while invalid spikes trigger visible data-quality exceptions.
  4. The scheduled query produces equivalent daily features with less service orchestration and within the run window.

Explanation

Correct Answer

C:

A held-out clean sample preserves meaningful ranges while invalid spikes trigger visible data-quality exceptions. This is specific acceptance evidence for outlier handling before feature standardization. A scaler learned from corrupted or held-out values can distort typical feature magnitudes and leak evaluation information. It confirms the controlled correction: Quarantine invalid spikes and fit a robust transformation using training data only, then apply it consistently at inference. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A numeric risk….

Incorrect Answers

A:

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 outlier handling before feature standardization issue. The direct test is: A held-out clean sample preserves meaningful ranges while invalid spikes trigger visible data-quality exceptions.

B:

Long-tail shuffle tasks shorten and the normalized output row count matches a reference implementation. This result could demonstrate success for managed spark join-key skew repair but not for the stated outlier handling before feature standardization issue. The direct test is: A held-out clean sample preserves meaningful ranges while invalid spikes trigger visible data-quality exceptions.

D:

The scheduled query produces equivalent daily features with less service orchestration and within the run window. This result could demonstrate success for bigquery versus dataflow preparation selection but not for the stated outlier handling before feature standardization issue. The direct test is: A held-out clean sample preserves meaningful ranges while invalid spikes trigger visible data-quality exceptions.

Question 1071

During model-training validation on a Google Cloud experimental project, the following condition occurs: A product search team trains a binary spam classifier to find the most semantically relevant help article for a free-text question. The change should preserve a meaningful independent model-quality comparison. Select TWO: the decisive diagnostic step and the targeted repair for this specific issue.

  1. Benchmark compatible TPU and GPU configurations and select hardware based on measured throughput and target budget.
  2. Inspect task requirements for retrieval ranking, available query-document pairs, embedding similarity and labeled relevance examples.
  3. Inspect feature modality, example counts, training cost, validation scores and latency requirements.
  4. Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision.
  5. Evaluate ARIMA_PLUS or an appropriate time-series forecasting model before adopting an expensive generative approach.

Explanation

Correct Answers

B:

Inspect task requirements for retrieval ranking, available query-document pairs, embedding similarity and labeled relevance examples. This inspects evidence relevant to embedding retrieval versus text classifier. A binary classifier assigns predefined labels; semantic search needs query-to-document relevance ranking. After identifying the cause, the matching correction is: Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision. This matters here because during model-training validation on a Google Cloud experimental project, the following condition occurs: A product….

D:

Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision. This is the targeted corrective response for embedding retrieval versus text classifier. A binary classifier assigns predefined labels; semantic search needs query-to-document relevance ranking. Verify the diagnosis using: Inspect task requirements for retrieval ranking, available query-document pairs, embedding similarity and labeled relevance examples. Confirm success using: Relevant articles rank highly for unseen paraphrased queries and retrieval hit rate is measured against judgments. This matters here because during model-training validation on a Google Cloud experimental project, the following condition occurs: A product….

Incorrect Answers

A:

Benchmark compatible TPU and GPU configurations and select hardware based on measured throughput and target budget. This is an action or diagnostic relevant to tpu versus gpu for tensorflow workload, not one of the required two steps. In this scenario verify: Inspect task requirements for retrieval ranking, available query-document pairs, embedding similarity and labeled relevance examples. Then correct: Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision.

C:

Inspect feature modality, example counts, training cost, validation scores and latency requirements. This is an action or diagnostic relevant to deep model versus gradient boosted trees on tabular, not one of the required two steps. In this scenario verify: Inspect task requirements for retrieval ranking, available query-document pairs, embedding similarity and labeled relevance examples. Then correct: Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision.

E:

Evaluate ARIMA_PLUS or an appropriate time-series forecasting model before adopting an expensive generative approach. This is an action or diagnostic relevant to forecast trend and seasonality versus llm, not one of the required two steps. In this scenario verify: Inspect task requirements for retrieval ranking, available query-document pairs, embedding similarity and labeled relevance examples. Then correct: Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision.

Question 1072

During a production ML inference release on Google Cloud, the following condition occurs: An internal fraud scorer sends sensitive feature vectors to a publicly accessible prediction endpoint even though clients are inside a controlled VPC. The service must meet its agreed quality and latency requirements. Which targeted engineering change most directly addresses the failure?

  1. Deploy a supported private endpoint or constrained private network path with least-privilege caller authorization.
  2. Test a supported post-training quantization or optimization path and release only if target quality remains acceptable.
  3. Pin releases to reviewed immutable image digests and record image plus model artifact versions.
  4. Add guarded traffic shifts and automatic rollback to the retained healthy revision when threshold alarms trip.

Explanation

Correct Answer

A:

Deploy a supported private endpoint or constrained private network path with least-privilege caller authorization. This is the targeted corrective response for private endpoint for regulated inference traffic. Network exposure and IAM controls are complementary; a public endpoint adds attack surface even with authentication. Verify the diagnosis using: Examine endpoint exposure settings, caller IAM, VPC routes, private connectivity and data egress requirements. Confirm success using: Approved in-network clients can invoke predictions while unapproved public network paths cannot reach the service. This matters here because an internal fraud scorer sends sensitive feature vectors to a publicly accessible prediction endpoint even though….

Incorrect Answers

B:

Test a supported post-training quantization or optimization path and release only if target quality remains acceptable. This action addresses inference optimization using quantization, not the failure in the described private endpoint for regulated inference traffic case. The targeted correction is: Deploy a supported private endpoint or constrained private network path with least-privilege caller authorization.

C:

Pin releases to reviewed immutable image digests and record image plus model artifact versions. This action addresses model artifact image digest reproducibility, not the failure in the described private endpoint for regulated inference traffic case. The targeted correction is: Deploy a supported private endpoint or constrained private network path with least-privilege caller authorization.

D:

Add guarded traffic shifts and automatic rollback to the retained healthy revision when threshold alarms trip. This action addresses model traffic rollback on high error rate, not the failure in the described private endpoint for regulated inference traffic case. The targeted correction is: Deploy a supported private endpoint or constrained private network path with least-privilege caller authorization.

Question 1073

During an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A reporting team exports millions of BigQuery rows to a laptop for daily scoring although a trained BigQuery ML model already exists in the dataset. The owners require measurable quality and controlled operating cost. Which outcome most directly demonstrates a successful, measurable fix?

  1. The scheduled report processes the full authorized partition and stores traceable predictions without a local export.
  2. A controlled raw record yields the same transformed feature representation for evaluation and production SQL inference.
  3. The chosen version meets task quality, inference cost and license rules on a documented representative evaluation set.
  4. Predictions contain sensible numeric estimates and holdout MAE or RMSE is measured against actual monetary values.

Explanation

Correct Answer

A:

The scheduled report processes the full authorized partition and stores traceable predictions without a local export. This is specific acceptance evidence for bigquery ml sql batch prediction integration. In-database prediction avoids unnecessary bulk data transfer when model and features are already in BigQuery. It confirms the controlled correction: Use ML.PREDICT on the appropriate BigQuery ML model within a controlled SQL batch job, writing results to governed tables. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….

Incorrect Answers

B:

A controlled raw record yields the same transformed feature representation for evaluation and production SQL inference. This result could demonstrate success for bigquery ml transform serving parity but not for the stated bigquery ml sql batch prediction integration issue. The direct test is: The scheduled report processes the full authorized partition and stores traceable predictions without a local export.

C:

The chosen version meets task quality, inference cost and license rules on a documented representative evaluation set. This result could demonstrate success for model garden task and license selection but not for the stated bigquery ml sql batch prediction integration issue. The direct test is: The scheduled report processes the full authorized partition and stores traceable predictions without a local export.

D:

Predictions contain sensible numeric estimates and holdout MAE or RMSE is measured against actual monetary values. This result could demonstrate success for bigquery ml linear regression for continuous value but not for the stated bigquery ml sql batch prediction integration issue. The direct test is: The scheduled report processes the full authorized partition and stores traceable predictions without a local export. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….

Question 1074

While reproducing a training orchestration incident in isolated staging, the following condition occurs: A model registry entry lacks the upstream version of the training feature table, preventing investigators from reconstructing a reported prediction. The team requires an idempotent pipeline behavior and traceable evidence. Select TWO: the decisive diagnostic step and the targeted repair for this specific issue.

  1. Inspect ML Metadata execution links, table snapshots, transformations and model version lineage.
  2. Compare serialized preprocessing artifacts, schema versions, train-time transformations and live request feature IDs.
  3. Tune component resource requests/limits and stream or partition embeddings rather than materializing every vector at once.
  4. Record governed dataset snapshot and transformation versions as pipeline inputs linked to the resulting model artifact.
  5. Require inference contract and integration tests with representative requests before promoting each candidate artifact.

Explanation

Correct Answers

A:

Inspect ML Metadata execution links, table snapshots, transformations and model version lineage. This inspects evidence relevant to model feature lineage for audit. Model weights alone do not capture the data lineage necessary to reproduce and investigate predictions. After identifying the cause, the matching correction is: Record governed dataset snapshot and transformation versions as pipeline inputs linked to the resulting model artifact. This matters here because while reproducing a training orchestration incident in isolated staging, the following condition occurs: A model….

D:

Record governed dataset snapshot and transformation versions as pipeline inputs linked to the resulting model artifact. This is the targeted corrective response for model feature lineage for audit. Model weights alone do not capture the data lineage necessary to reproduce and investigate predictions. Verify the diagnosis using: Inspect ML Metadata execution links, table snapshots, transformations and model version lineage. Confirm success using: An audit can resolve model version to exact source data and processing code without guessing by timestamps. This matters here because while reproducing a training orchestration incident in isolated staging, the following condition occurs: A model….

Incorrect Answers

B:

Compare serialized preprocessing artifacts, schema versions, train-time transformations and live request feature IDs. This is an action or diagnostic relevant to training serving preprocessing artifact sharing, not one of the required two steps. In this scenario verify: Inspect ML Metadata execution links, table snapshots, transformations and model version lineage. Then correct: Record governed dataset snapshot and transformation versions as pipeline inputs linked to the resulting model artifact.

C:

Tune component resource requests/limits and stream or partition embeddings rather than materializing every vector at once. This is an action or diagnostic relevant to custom kfp component resource limits, not one of the required two steps. In this scenario verify: Inspect ML Metadata execution links, table snapshots, transformations and model version lineage. Then correct: Record governed dataset snapshot and transformation versions as pipeline inputs linked to the resulting model artifact.

E:

Require inference contract and integration tests with representative requests before promoting each candidate artifact. This is an action or diagnostic relevant to continuous delivery integration contract tests, not one of the required two steps. In this scenario verify: Inspect ML Metadata execution links, table snapshots, transformations and model version lineage. Then correct: Record governed dataset snapshot and transformation versions as pipeline inputs linked to the resulting model artifact. This matters here because while reproducing a training orchestration incident in isolated staging, the following condition occurs: A model….

Question 1075

During a controlled replay of the data and model handoff to a second engineering team, the following condition occurs: A team imports a pretrained JAX checkpoint in a notebook but assumes its model weights and device setup will load unchanged in a PyTorch-only runtime. The handoff must preserve privacy, lineage and testable behavior. What implementation change resolves the specific issue without substituting an unrelated fix?

  1. Choose a compatible Model Garden model/runtime or perform a validated checkpoint conversion before training.
  2. Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts.
  3. Push aggregations into BigQuery or stream bounded samples to the notebook rather than materializing the whole table.
  4. Revoke and rotate the exposed key and use managed workload identity or approved short-lived credentials with least privilege.

Explanation

Correct Answer

A:

Choose a compatible Model Garden model/runtime or perform a validated checkpoint conversion before training. This is the targeted corrective response for model garden jax accelerator compatibility. Framework-native checkpoints and runtime APIs are not automatically interchangeable across ML libraries. Verify the diagnosis using: Inspect saved artifact format, framework versions, device placement requirements and the model card's supported execution paths. Confirm success using: A clean notebook loads the exact model revision, runs representative inputs and reports consistent outputs. This matters here because during a controlled replay of the data and model handoff to a second engineering team, the following condition….

Incorrect Answers

B:

Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts. This action addresses managed spark join-key skew repair, not the failure in the described model garden jax accelerator compatibility case. The targeted correction is: Choose a compatible Model Garden model/runtime or perform a validated checkpoint conversion before training.

C:

Push aggregations into BigQuery or stream bounded samples to the notebook rather than materializing the whole table. This action addresses notebook memory exhaustion on full data extraction, not the failure in the described model garden jax accelerator compatibility case. The targeted correction is: Choose a compatible Model Garden model/runtime or perform a validated checkpoint conversion before training. This matters here because during a controlled replay of the data and model handoff to a second engineering team, the following condition….

D:

Revoke and rotate the exposed key and use managed workload identity or approved short-lived credentials with least privilege. This action addresses workbench credentials embedded in repository, not the failure in the described model garden jax accelerator compatibility case. The targeted correction is: Choose a compatible Model Garden model/runtime or perform a validated checkpoint conversion before training.

Question 1076

During a production ML inference release on Google Cloud, the following condition occurs: A deployment grants every project member broad model prediction permissions merely to make a limited partner integration work. The service must meet its agreed quality and latency requirements. Which evidence most directly establishes what is wrong with this AI or ML workflow?

  1. Inspect endpoint revision metrics, release alarms, traffic fractions and availability of the prior known-good model.
  2. Inspect batch size, kernel utilization, per-request overhead, queue wait and latency percentiles.
  3. Inspect quota errors, retry behavior, queue occupancy, tail latency and autoscaling upper limits.
  4. Examine effective IAM bindings, invocation audit logs and the intended partner service account identity.

Explanation

Correct Answer

D:

Examine effective IAM bindings, invocation audit logs and the intended partner service account identity. This inspects evidence relevant to public endpoint iam oversharing. Endpoint invoker permissions should follow least privilege, rather than expanding access for convenience. After identifying the cause, the matching correction is: Restrict invoke access to the necessary principal and endpoint, using appropriate short-lived authentication. This matters here because a deployment grants every project member broad model prediction permissions merely to make a limited partner….

Incorrect Answers

A:

Inspect endpoint revision metrics, release alarms, traffic fractions and availability of the prior known-good model. This examines model traffic rollback on high error rate rather than the specific mechanism reported here. It is not the decisive first check for public endpoint iam oversharing. The relevant evidence is: Examine effective IAM bindings, invocation audit logs and the intended partner service account identity.

B:

Inspect batch size, kernel utilization, per-request overhead, queue wait and latency percentiles. This examines dynamic batch serving for gpu saturation rather than the specific mechanism reported here. It is not the decisive first check for public endpoint iam oversharing. The relevant evidence is: Examine effective IAM bindings, invocation audit logs and the intended partner service account identity.

C:

Inspect quota errors, retry behavior, queue occupancy, tail latency and autoscaling upper limits. This examines predictive serving rate limit and backpressure rather than the specific mechanism reported here. It is not the decisive first check for public endpoint iam oversharing. The relevant evidence is: Examine effective IAM bindings, invocation audit logs and the intended partner service account identity.

Question 1077

While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A demand model trains on moving averages computed after the prediction cutoff, so the held-out forecast benefits from future sales updates. Engineers need an auditable, resource-aware correction to the issue. Which targeted engineering change most directly addresses the failure?

  1. Choose a decision threshold using acceptable recall and alert burden with a validated independent cohort.
  2. Reduce per-device batch size or use validated gradient accumulation or mixed precision where compatible.
  3. Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping.
  4. Recompute lagged windows using only prior observations and validate with rolling-origin splits.

Explanation

Correct Answer

D:

Recompute lagged windows using only prior observations and validate with rolling-origin splits. This is the targeted corrective response for temporal training label leakage in rolling windows. Temporal features formed after prediction time leak future observations into model training and evaluation. Verify the diagnosis using: Inspect feature computation cutoffs, window frame bounds, label timestamps and time-aware evaluation splits. Confirm success using: Every evaluation feature is available at its simulated prediction time and later-period scores remain stable. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….

Incorrect Answers

A:

Choose a decision threshold using acceptable recall and alert burden with a validated independent cohort. This action addresses cost-sensitive threshold for rare positives, not the failure in the described temporal training label leakage in rolling windows case. The targeted correction is: Recompute lagged windows using only prior observations and validate with rolling-origin splits.

B:

Reduce per-device batch size or use validated gradient accumulation or mixed precision where compatible. This action addresses gpu out-of-memory batch control, not the failure in the described temporal training label leakage in rolling windows case. The targeted correction is: Recompute lagged windows using only prior observations and validate with rolling-origin splits.

C:

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 temporal training label leakage in rolling windows case. The targeted correction is: Recompute lagged windows using only prior observations and validate with rolling-origin splits.

Question 1078

During an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A support assistant includes a full 200-page manual in every prompt despite users asking brief questions, producing excessive latency and cost. The owners require measurable quality and controlled operating cost. What implementation change resolves the specific issue without substituting an unrelated fix?

  1. Use Cloud Translation API for supported text translation, then separately validate downstream classification against localized content.
  2. Use an appropriate Document AI processor for form or invoice extraction and validate required fields before downstream posting.
  3. Use a BigQuery ML LINEAR_REG or suitable regression model with a numeric target and evaluate continuous-error metrics on held-out records.
  4. Retrieve only relevant passages with provenance and use a concise structured prompt with measured token limits.

Explanation

Correct Answer

D:

Retrieve only relevant passages with provenance and use a concise structured prompt with measured token limits. This is the targeted corrective response for gemini prompt context token budget. Unfocused context consumes tokens and can distract generation; targeted retrieval can reduce cost without discarding needed facts. Verify the diagnosis using: Inspect prompt token usage, retrieval relevance, model context requirements, answer grounding and p95 latency across queries. Confirm success using: On held-out questions, answers remain grounded while input tokens and p95 response latency decline. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….

Incorrect Answers

A:

Use Cloud Translation API for supported text translation, then separately validate downstream classification against localized content. This action addresses translate api for multilingual product descriptions, not the failure in the described gemini prompt context token budget case. The targeted correction is: Retrieve only relevant passages with provenance and use a concise structured prompt with measured token limits. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….

B:

Use an appropriate Document AI processor for form or invoice extraction and validate required fields before downstream posting. This action addresses document ai structured invoice extraction, not the failure in the described gemini prompt context token budget case. The targeted correction is: Retrieve only relevant passages with provenance and use a concise structured prompt with measured token limits.

C:

Use a BigQuery ML LINEAR_REG or suitable regression model with a numeric target and evaluate continuous-error metrics on held-out records. This action addresses bigquery ml linear regression for continuous value, not the failure in the described gemini prompt context token budget case. The targeted correction is: Retrieve only relevant passages with provenance and use a concise structured prompt with measured token limits. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….

Question 1079

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. Select TWO: the decisive diagnostic step and the targeted repair for this specific issue.

  1. Tune supported distributed batch sizing, communication strategy or placement after measuring the bottleneck.
  2. Reduce per-device batch size or use validated gradient accumulation or mixed precision where compatible.
  3. Persist versioned checkpoints in durable Cloud Storage and make the training code resume optimizer and model state.
  4. Compare training and validation curves, learning-rate schedule and the checkpoint corresponding to minimum validation loss.
  5. Inspect shutdown events, checkpoint directory, durable artifact transfers and restoration logic after simulated interruptions.

Explanation

Correct Answers

C:

Persist versioned checkpoints in durable Cloud Storage and make the training code resume optimizer and model state. This is the targeted corrective response for training checkpoint persistence across interruptions. Preemptible execution can end abruptly; local-only state is not a durable recovery mechanism. Verify the diagnosis using: Inspect shutdown events, checkpoint directory, durable artifact transfers and restoration logic after simulated interruptions. Confirm success using: A controlled interruption resumes near the saved step without restarting training from zero. This matters here because during model-training validation on a Google Cloud experimental project, the following condition occurs: A weeklong….

E:

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. This matters here because during model-training validation on a Google Cloud experimental project, the following condition occurs: A weeklong….

Incorrect Answers

A:

Tune supported distributed batch sizing, communication strategy or placement after measuring the bottleneck. This is an action or diagnostic relevant to distributed gradient communication bottleneck, not one of the required two steps. In this scenario verify: Inspect shutdown events, checkpoint directory, durable artifact transfers and restoration logic after simulated interruptions. Then correct: Persist versioned checkpoints in durable Cloud Storage and make the training code resume optimizer and model state.

B:

Reduce per-device batch size or use validated gradient accumulation or mixed precision where compatible. This is an action or diagnostic relevant to gpu out-of-memory batch control, not one of the required two steps. In this scenario verify: Inspect shutdown events, checkpoint directory, durable artifact transfers and restoration logic after simulated interruptions. Then correct: Persist versioned checkpoints in durable Cloud Storage and make the training code resume optimizer and model state.

D:

Compare training and validation curves, learning-rate schedule and the checkpoint corresponding to minimum validation loss. This is an action or diagnostic relevant to early stopping on validation divergence, not one of the required two steps. In this scenario verify: Inspect shutdown events, checkpoint directory, durable artifact transfers and restoration logic after simulated interruptions. Then correct: Persist versioned checkpoints in durable Cloud Storage and make the training code resume optimizer and model state.

Question 1080

During a production ML inference release on Google Cloud, the following condition occurs: A document classification service sends huge media files through synchronous prediction calls whose processing exceeds clients' timeout limits. The service must meet its agreed quality and latency requirements. What should the engineer inspect before selecting a correction?

  1. Inspect traffic-splitting capabilities, release guardrails, rollback triggers and representative online metrics.
  2. Compare request rate, queue depth, GPU utilization, per-instance concurrency and p95 response latency.
  3. Examine endpoint exposure settings, caller IAM, VPC routes, private connectivity and data egress requirements.
  4. Review payload size distributions, request duration, response timeout policies and tolerance for deferred completion.

Explanation

Correct Answer

D:

Review payload size distributions, request duration, response timeout policies and tolerance for deferred completion. This inspects evidence relevant to online prediction timeout and batch fallback. Synchronous request limits cannot be solved merely by expanding the model context or retrying indefinitely. After identifying the cause, the matching correction is: Use asynchronous or batch processing with durable job status for oversized workloads, reserving online calls for bounded requests. This matters here because a document classification service sends huge media files through synchronous prediction calls whose processing….

Incorrect Answers

A:

Inspect traffic-splitting capabilities, release guardrails, rollback triggers and representative online metrics. This examines canary gradual traffic rollout rather than the specific mechanism reported here. It is not the decisive first check for online prediction timeout and batch fallback. The relevant evidence is: Review payload size distributions, request duration, response timeout policies and tolerance for deferred completion.

B:

Compare request rate, queue depth, GPU utilization, per-instance concurrency and p95 response latency. This examines throughput-based autoscaling versus cpu metric rather than the specific mechanism reported here. It is not the decisive first check for online prediction timeout and batch fallback. The relevant evidence is: Review payload size distributions, request duration, response timeout policies and tolerance for deferred completion.

C:

Examine endpoint exposure settings, caller IAM, VPC routes, private connectivity and data egress requirements. This examines private endpoint for regulated inference traffic rather than the specific mechanism reported here. It is not the decisive first check for online prediction timeout and batch fallback. The relevant evidence is: Review payload size distributions, request duration, response timeout policies and tolerance for deferred completion.

Professional Machine Learning Engineer Practice Tests