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 17

Question 160

As the team tests a new governed AI release against adversarial and normal data, the following condition occurs: A deployed risk model receives income values far outside the training distribution but the dashboard checks only endpoint availability. The fix must retain legitimate model usefulness and appropriate controls. Which configuration or procedure is the most appropriate correction?

  1. Adopt justified seasonal baselines or cohorts and tune alert thresholds without suppressing severe shifts.
  2. Capture immutable prediction identifiers and join verified outcome records to the corresponding earlier inference request.
  3. Configure Agent Platform Model Monitoring on relevant features with representative baseline and actionable drift alerts.
  4. Investigate attribution drift, remove invalid proxy features if warranted and retrain with appropriate validation.

Explanation

Correct Answer

C:

Configure Agent Platform Model Monitoring on relevant features with representative baseline and actionable drift alerts. This is the targeted corrective response for input data distribution drift alarm. HTTP health is not evidence that incoming feature distributions still resemble training data. Verify the diagnosis using: Inspect live feature histograms, training baselines, data-capture completeness and drift metric thresholds. Confirm success using: A synthetic distribution shift triggers an attributable alert while an unchanged control sample stays within tolerance.

Incorrect Answers

A:

Adopt justified seasonal baselines or cohorts and tune alert thresholds without suppressing severe shifts. This action addresses model monitoring false-alert seasonality, not the failure in the described input data distribution drift alarm case. The targeted correction is: Configure Agent Platform Model Monitoring on relevant features with representative baseline and actionable drift alerts.

B:

Capture immutable prediction identifiers and join verified outcome records to the corresponding earlier inference request. This action addresses ground truth association for quality monitoring, not the failure in the described input data distribution drift alarm case. The targeted correction is: Configure Agent Platform Model Monitoring on relevant features with representative baseline and actionable drift alerts.

D:

Investigate attribution drift, remove invalid proxy features if warranted and retrain with appropriate validation. This action addresses feature attribution drift after deployment, not the failure in the described input data distribution drift alarm case. The targeted correction is: Configure Agent Platform Model Monitoring on relevant features with representative baseline and actionable drift alerts.

Question 161

While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: An engineer runs an unbounded grid across learning rates, depths and regularization values, using expensive accelerators without a metric-driven stopping rule. Engineers need an auditable, resource-aware correction to the issue. Which underlying engineering principle explains why the original approach fails?

  1. Cloud accelerators have regional quota and stock limits distinct from an application's logical training configuration.
  2. Search quality depends on comparable objectives and resource limits, not exhaustive combinations at any cost.
  3. Fine-tuning technical feasibility does not confer rights to reuse restricted training images or ignore model safety.
  4. Notebook filesystem locations are not portable contracts for managed container training jobs.

Explanation

Correct Answer

B:

Search quality depends on comparable objectives and resource limits, not exhaustive combinations at any cost. This explains the mechanism behind hyperparameter search budget limit and why the described failure is possible. A discriminating investigation is: Review parameter ranges, total trial count, training budget and the metric used to rank completed experiments. The corresponding repair is: Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping.

Incorrect Answers

A:

Cloud accelerators have regional quota and stock limits distinct from an application's logical training configuration. This principle describes accelerator quota and regional availability, which is not the cause of the observed hyperparameter search budget limit failure. The controlling explanation is: Search quality depends on comparable objectives and resource limits, not exhaustive combinations at any cost.

C:

Fine-tuning technical feasibility does not confer rights to reuse restricted training images or ignore model safety. This principle describes fine-tuning image generator data rights, which is not the cause of the observed hyperparameter search budget limit failure. The controlling explanation is: Search quality depends on comparable objectives and resource limits, not exhaustive combinations at any cost.

D:

Notebook filesystem locations are not portable contracts for managed container training jobs. This principle describes custom training input schema mismatch, which is not the cause of the observed hyperparameter search budget limit failure. The controlling explanation is: Search quality depends on comparable objectives and resource limits, not exhaustive combinations at any cost.

Question 162

As the team tests a new governed AI release against adversarial and normal data, the following condition occurs: A product team interprets a high feature attribution for zip code as proof that changing a customer's address would cause a credit decision to improve. The fix must retain legitimate model usefulness and appropriate controls. Which TWO selections represent the correct investigation and remediation together? Select TWO.

  1. Reduce unnecessary few-shot context or use targeted retrieval and evaluate an appropriate lower-latency model where safe.
  2. Treat retrieved text as untrusted data, isolate instructions, restrict tool actions and apply appropriate Model Armor screening.
  3. Inspect explanation method assumptions, correlated input features, counterfactual evidence and the model's actual causal validity.
  4. Inspect input logs, sensitivity classifications, prompt assembly and approved data-processing boundaries.
  5. Present feature attributions as model-decision associations and use proper causal analysis before making intervention claims.

Explanation

Correct Answers

C:

Inspect explanation method assumptions, correlated input features, counterfactual evidence and the model's actual causal validity. This inspects evidence relevant to explainability versus causal claim. Predictive importance is not causal proof; attribution techniques describe model behavior under their assumptions. After identifying the cause, the matching correction is: Present feature attributions as model-decision associations and use proper causal analysis before making intervention claims.

E:

Present feature attributions as model-decision associations and use proper causal analysis before making intervention claims. This is the targeted corrective response for explainability versus causal claim. Predictive importance is not causal proof; attribution techniques describe model behavior under their assumptions. Verify the diagnosis using: Inspect explanation method assumptions, correlated input features, counterfactual evidence and the model's actual causal validity. Confirm success using: Review documentation correctly distinguishes model influence from proven real-world causal effects.

Incorrect Answers

A:

Reduce unnecessary few-shot context or use targeted retrieval and evaluate an appropriate lower-latency model where safe. This is an action or diagnostic relevant to llm latency and cost token regression, not one of the required two steps. In this scenario verify: Inspect explanation method assumptions, correlated input features, counterfactual evidence and the model's actual causal validity. Then correct: Present feature attributions as model-decision associations and use proper causal analysis before making intervention claims.

B:

Treat retrieved text as untrusted data, isolate instructions, restrict tool actions and apply appropriate Model Armor screening. This is an action or diagnostic relevant to prompt injection through retrieved documents, not one of the required two steps. In this scenario verify: Inspect explanation method assumptions, correlated input features, counterfactual evidence and the model's actual causal validity. Then correct: Present feature attributions as model-decision associations and use proper causal analysis before making intervention claims.

D:

Inspect input logs, sensitivity classifications, prompt assembly and approved data-processing boundaries. This is an action or diagnostic relevant to sensitive identifiers leaked to llm prompts, not one of the required two steps. In this scenario verify: Inspect explanation method assumptions, correlated input features, counterfactual evidence and the model's actual causal validity. Then correct: Present feature attributions as model-decision associations and use proper causal analysis before making intervention claims.

Question 163

As the team tests a new governed AI release against adversarial and normal data, the following condition occurs: A product support bot submits raw customer payment and identity records to a generative service even though the question only needs an order status summary. The fix must retain legitimate model usefulness and appropriate controls. Which TWO selections form an appropriate before-and-after verification pair? Select TWO.

  1. An evaluation fixture correctly associates each matured label with exactly one prior prediction.
  2. Attack-bearing documents fail to redirect privileged behavior while legitimate grounded answers remain available.
  3. Test prompts preserve support utility without exposing real account identifiers to unauthorized model requests.
  4. Inspect attachment ingestion, trust boundaries, malicious prompt examples and deployed Model Armor filter results.
  5. Inspect input logs, sensitivity classifications, prompt assembly and approved data-processing boundaries.

Explanation

Correct Answers

C:

Test prompts preserve support utility without exposing real account identifiers to unauthorized model requests. This is specific acceptance evidence for sensitive identifiers leaked to llm prompts. Sensitive information should be shared only when necessary and permitted; ordinary prompting is not an exemption from privacy controls. It confirms the controlled correction: Minimize or tokenize personal fields before generation and enforce access and retention controls on any necessary context.

E:

Inspect input logs, sensitivity classifications, prompt assembly and approved data-processing boundaries. This inspects evidence relevant to sensitive identifiers leaked to llm prompts. Sensitive information should be shared only when necessary and permitted; ordinary prompting is not an exemption from privacy controls. After identifying the cause, the matching correction is: Minimize or tokenize personal fields before generation and enforce access and retention controls on any necessary context.

Incorrect Answers

A:

An evaluation fixture correctly associates each matured label with exactly one prior prediction. This relates to ground truth association for quality monitoring but does not establish the requested before-and-after evidence. The actual diagnostic is: Inspect input logs, sensitivity classifications, prompt assembly and approved data-processing boundaries. The specific acceptance result is: Test prompts preserve support utility without exposing real account identifiers to unauthorized model requests.

B:

Attack-bearing documents fail to redirect privileged behavior while legitimate grounded answers remain available. This relates to prompt injection through retrieved documents but does not establish the requested before-and-after evidence. The actual diagnostic is: Inspect input logs, sensitivity classifications, prompt assembly and approved data-processing boundaries. The specific acceptance result is: Test prompts preserve support utility without exposing real account identifiers to unauthorized model requests.

D:

Inspect attachment ingestion, trust boundaries, malicious prompt examples and deployed Model Armor filter results. This relates to model armor untrusted content screening but does not establish the requested before-and-after evidence. The actual diagnostic is: Inspect input logs, sensitivity classifications, prompt assembly and approved data-processing boundaries. The specific acceptance result is: Test prompts preserve support utility without exposing real account identifiers to unauthorized model requests.

Question 164

During a controlled replay of the data and model handoff to a second engineering team, the following condition occurs: A shared prototype notebook can read entire sensitive production BigQuery datasets because its attached credentials are inherited from a broadly privileged user. The handoff must preserve privacy, lineage and testable behavior. Select TWO: the decisive diagnostic step and the targeted repair for this specific issue.

  1. Inspect feature quantiles, physical validity bounds, missingness and training-only fit statistics against independent validation data.
  2. Review notebook execution identity, effective IAM roles, dataset access policies and audit records for protected tables.
  3. Refactor hidden state into explicit inputs and functions and add a clean-kernel end-to-end execution gate.
  4. Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts.
  5. Use a narrowly scoped service identity or approved user access, least-privilege dataset views and separated development data.

Explanation

Correct Answers

B:

Review notebook execution identity, effective IAM roles, dataset access policies and audit records for protected tables. This inspects evidence relevant to colab enterprise notebook data access scope. Collaborative notebooks execute with real identities; editor convenience does not justify unrestricted production-data access. After identifying the cause, the matching correction is: Use a narrowly scoped service identity or approved user access, least-privilege dataset views and separated development data.

E:

Use a narrowly scoped service identity or approved user access, least-privilege dataset views and separated development data. This is the targeted corrective response for colab enterprise notebook data access scope. Collaborative notebooks execute with real identities; editor convenience does not justify unrestricted production-data access. Verify the diagnosis using: Review notebook execution identity, effective IAM roles, dataset access policies and audit records for protected tables. Confirm success using: The notebook still trains on approved sample tables while restricted production datasets deny unauthorized reads.

Incorrect Answers

A:

Inspect feature quantiles, physical validity bounds, missingness and training-only fit statistics against independent validation data. This is an action or diagnostic relevant to outlier handling before feature standardization, not one of the required two steps. In this scenario verify: Review notebook execution identity, effective IAM roles, dataset access policies and audit records for protected tables. Then correct: Use a narrowly scoped service identity or approved user access, least-privilege dataset views and separated development data.

C:

Refactor hidden state into explicit inputs and functions and add a clean-kernel end-to-end execution gate. This is an action or diagnostic relevant to notebook transient state and execution order, not one of the required two steps. In this scenario verify: Review notebook execution identity, effective IAM roles, dataset access policies and audit records for protected tables. Then correct: Use a narrowly scoped service identity or approved user access, least-privilege dataset views and separated development data.

D:

Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts. This is an action or diagnostic relevant to managed spark join-key skew repair, not one of the required two steps. In this scenario verify: Review notebook execution identity, effective IAM roles, dataset access policies and audit records for protected tables. Then correct: Use a narrowly scoped service identity or approved user access, least-privilege dataset views and separated development data.

Question 165

During a staged restoration test at a secondary serving deployment, the following condition occurs: A multi-class model returns numeric class indices, but an API gateway uses a stale alphabetical mapping and mislabels predictions. The team must prove an actual user-visible improvement without weakening access controls. What should the engineer inspect before selecting a correction?

  1. Compare Artifact Registry image digest, build provenance, runtime dependency inventory and release manifests.
  2. Inspect trained class-to-index metadata, endpoint output tensors and gateway mapping version.
  3. Measure bandwidth, network availability, latency deadline, edge hardware limits and model compression compatibility.
  4. Inspect feature-view sync status, latest source timestamps, entity ID and online lookup freshness.

Explanation

Correct Answer

B:

Inspect trained class-to-index metadata, endpoint output tensors and gateway mapping version. This inspects evidence relevant to custom postprocessing label mapping drift. Index ordering is part of the model contract; separate stale label dictionaries can silently corrupt inference. After identifying the cause, the matching correction is: Ship the class vocabulary with the model artifact and version or validate the output adapter against it.

Incorrect Answers

A:

Compare Artifact Registry image digest, build provenance, runtime dependency inventory and release manifests. This examines model artifact image digest reproducibility rather than the specific mechanism reported here. It is not the decisive first check for custom postprocessing label mapping drift. The relevant evidence is: Inspect trained class-to-index metadata, endpoint output tensors and gateway mapping version.

C:

Measure bandwidth, network availability, latency deadline, edge hardware limits and model compression compatibility. This examines edge versus cloud inference network constraints rather than the specific mechanism reported here. It is not the decisive first check for custom postprocessing label mapping drift. The relevant evidence is: Inspect trained class-to-index metadata, endpoint output tensors and gateway mapping version.

D:

Inspect feature-view sync status, latest source timestamps, entity ID and online lookup freshness. This examines feature store freshness and online sync rather than the specific mechanism reported here. It is not the decisive first check for custom postprocessing label mapping drift. The relevant evidence is: Inspect trained class-to-index metadata, endpoint output tensors and gateway mapping version.

Question 166

At a Google Cloud analytics team preparing a governed pilot, the following condition occurs: A team chooses the largest available foundation model by parameter count without checking whether its license allows commercial use or whether it handles the required input modality. The team must satisfy a reproducible low-code AI assessment. Which outcome most directly demonstrates a successful, measurable fix?

  1. The chosen version meets task quality, inference cost and license rules on a documented representative evaluation set.
  2. A controlled raw record yields the same transformed feature representation for evaluation and production SQL inference.
  3. A held-out invoice batch produces correct structured fields with measurable per-field precision and reject handling.
  4. Classification F1 remains above the acceptance threshold while end-to-end latency and cost per thousand requests fall.

Explanation

Correct Answer

A:

The chosen version meets task quality, inference cost and license rules on a documented representative evaluation set. This is specific acceptance evidence for model garden task and license selection. Model size alone does not ensure suitable task support, usage rights or production economics. It confirms the controlled correction: Select a permitted task-compatible Gemini or other supported foundation model and benchmark it against simpler candidates.

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 model garden task and license selection issue. The direct test is: The chosen version meets task quality, inference cost and license rules on a documented representative evaluation set.

C:

A held-out invoice batch produces correct structured fields with measurable per-field precision and reject handling. This result could demonstrate success for document ai structured invoice extraction but not for the stated model garden task and license selection issue. The direct test is: The chosen version meets task quality, inference cost and license rules on a documented representative evaluation set.

D:

Classification F1 remains above the acceptance threshold while end-to-end latency and cost per thousand requests fall. This result could demonstrate success for gemini model choice for latency versus complexity but not for the stated model garden task and license selection issue. The direct test is: The chosen version meets task quality, inference cost and license rules on a documented representative evaluation set.

Question 167

At a Google Cloud analytics team preparing a governed pilot, the following condition occurs: A commerce analyst uses a binary classifier to predict exact revenue per order even though labels are continuous currency amounts. The team must satisfy a reproducible low-code AI assessment. Which underlying engineering principle explains why the original approach fails?

  1. A label-derived future field leaks the outcome into input features and makes offline metrics deceptively strong.
  2. K-means discovers unlabeled similarity groups; fabricating labels would make supervised accuracy meaningless.
  3. Frequently changing external knowledge is better supplied through current context than repeatedly embedded into model weights.
  4. Classification labels cannot directly represent unrestricted continuous outcomes; SQL regression models match numeric targets.

Explanation

Correct Answer

D:

Classification labels cannot directly represent unrestricted continuous outcomes; SQL regression models match numeric targets. This explains the mechanism behind bigquery ml linear regression for continuous value and why the described failure is possible. A discriminating investigation is: Inspect the target column type, business loss metric, and sample prediction schema alongside model_type in the BigQuery model metadata. The corresponding repair is: Use a BigQuery ML LINEAR_REG or suitable regression model with a numeric target and evaluate continuous-error metrics on held-out records. Here, the relevant situation is: the following condition occurs: A commerce analyst uses a binary classifier to predict exact revenue per order even….

Incorrect Answers

A:

A label-derived future field leaks the outcome into input features and makes offline metrics deceptively strong. This principle describes bigquery ml ml.evaluate leakage detection, which is not the cause of the observed bigquery ml linear regression for continuous value failure. The controlling explanation is: Classification labels cannot directly represent unrestricted continuous outcomes; SQL regression models match numeric targets.

B:

K-means discovers unlabeled similarity groups; fabricating labels would make supervised accuracy meaningless. This principle describes bigquery ml kmeans customer segmentation, which is not the cause of the observed bigquery ml linear regression for continuous value failure. The controlling explanation is: Classification labels cannot directly represent unrestricted continuous outcomes; SQL regression models match numeric targets.

C:

Frequently changing external knowledge is better supplied through current context than repeatedly embedded into model weights. This principle describes foundation model tuning versus retrieval update, which is not the cause of the observed bigquery ml linear regression for continuous value failure. The controlling explanation is: Classification labels cannot directly represent unrestricted continuous outcomes; SQL regression models match numeric targets.

Question 168

During a production ML inference release on Google Cloud, the following condition occurs: A model server scales down to zero expensive workers overnight but cannot meet the first morning burst because loading weights takes several minutes. The service must meet its agreed quality and latency requirements. Which TWO selections represent the correct investigation and remediation together? Select TWO.

  1. Deploy a supported private endpoint or constrained private network path with least-privilege caller authorization.
  2. Compare baseline model size, supported precision, target hardware instructions and accuracy on representative samples.
  3. Set a justified warm minimum or scheduled capacity and balance initialization overhead against idle cost.
  4. Preserve stable canonical identifier types end-to-end and backfill only the affected feature records.
  5. Inspect idle cost, model initialization time, min replicas, burst arrival, queueing and request deadlines.

Explanation

Correct Answers

C:

Set a justified warm minimum or scheduled capacity and balance initialization overhead against idle cost. This is the targeted corrective response for autoscaling minimum capacity versus cold load. Reactive scaling cannot instantly serve requests when cold model initialization is long. Verify the diagnosis using: Inspect idle cost, model initialization time, min replicas, burst arrival, queueing and request deadlines. Confirm success using: The morning surge meets availability and p95 latency objectives while off-peak cost remains documented.

E:

Inspect idle cost, model initialization time, min replicas, burst arrival, queueing and request deadlines. This inspects evidence relevant to autoscaling minimum capacity versus cold load. Reactive scaling cannot instantly serve requests when cold model initialization is long. After identifying the cause, the matching correction is: Set a justified warm minimum or scheduled capacity and balance initialization overhead against idle cost.

Incorrect Answers

A:

Deploy a supported private endpoint or constrained private network path with least-privilege caller authorization. This is an action or diagnostic relevant to private endpoint for regulated inference traffic, not one of the required two steps. In this scenario verify: Inspect idle cost, model initialization time, min replicas, burst arrival, queueing and request deadlines. Then correct: Set a justified warm minimum or scheduled capacity and balance initialization overhead against idle cost.

B:

Compare baseline model size, supported precision, target hardware instructions and accuracy on representative samples. This is an action or diagnostic relevant to inference optimization using quantization, not one of the required two steps. In this scenario verify: Inspect idle cost, model initialization time, min replicas, burst arrival, queueing and request deadlines. Then correct: Set a justified warm minimum or scheduled capacity and balance initialization overhead against idle cost.

D:

Preserve stable canonical identifier types end-to-end and backfill only the affected feature records. This is an action or diagnostic relevant to feature online entity key mismatch, not one of the required two steps. In this scenario verify: Inspect idle cost, model initialization time, min replicas, burst arrival, queueing and request deadlines. Then correct: Set a justified warm minimum or scheduled capacity and balance initialization overhead against idle cost.

Question 169

Within a jointly maintained Google Cloud data science workspace, the following condition occurs: A project declares model B superior even though A was evaluated on last quarter and B on a deliberately easier random sample. Collaborators must avoid expanding data access or breaking experiment reproducibility. Which TWO complementary choices jointly establish the evidence and appropriate correction? Select TWO.

  1. Inspect dataset and split fingerprints, label definitions, metric versions and evaluation timestamps for both experiment runs.
  2. Rebuild offline training data with point-in-time eligible joins and remove features available only after each prediction moment.
  3. Record input dataset versions, training runs, code revisions and output artifact links in the managed metadata and registry workflow.
  4. Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates.
  5. Inspect pipeline execution IDs, experiment tracking records, artifact URIs and the link between metrics and saved models.

Explanation

Correct Answers

A:

Inspect dataset and split fingerprints, label definitions, metric versions and evaluation timestamps for both experiment runs. This inspects evidence relevant to experiment metric comparison with mismatched splits. Metrics from different data distributions are not directly comparable evidence of model improvement. After identifying the cause, the matching correction is: Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A project declares….

D:

Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates. This is the targeted corrective response for experiment metric comparison with mismatched splits. Metrics from different data distributions are not directly comparable evidence of model improvement. Verify the diagnosis using: Inspect dataset and split fingerprints, label definitions, metric versions and evaluation timestamps for both experiment runs. Confirm success using: Candidate scores can be reproduced on the same held-out data and their differences are attributable to model changes. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A project declares….

Incorrect Answers

B:

Rebuild offline training data with point-in-time eligible joins and remove features available only after each prediction moment. This is an action or diagnostic relevant to point-in-time feature leakage prevention, not one of the required two steps. In this scenario verify: Inspect dataset and split fingerprints, label definitions, metric versions and evaluation timestamps for both experiment runs. Then correct: Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates.

C:

Record input dataset versions, training runs, code revisions and output artifact links in the managed metadata and registry workflow. This is an action or diagnostic relevant to ml metadata lineage for production model, not one of the required two steps. In this scenario verify: Inspect dataset and split fingerprints, label definitions, metric versions and evaluation timestamps for both experiment runs. Then correct: Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A project declares….

E:

Inspect pipeline execution IDs, experiment tracking records, artifact URIs and the link between metrics and saved models. This is an action or diagnostic relevant to pipeline experiment versus notebook-only tracking, not one of the required two steps. In this scenario verify: Inspect dataset and split fingerprints, label definitions, metric versions and evaluation timestamps for both experiment runs. Then correct: Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates.

Question 170

During a production ML inference release on Google Cloud, the following condition occurs: A public prediction API queues unbounded client retries during a traffic spike, creating a cascading latency and memory outage. The service must meet its agreed quality and latency requirements. What acceptance result verifies the intended behavior after remediation?

  1. The running endpoint resolves to a traceable evaluated package and cannot silently switch weights when an alias moves.
  2. Peak traffic is rate-limited predictably and the serving fleet recovers without an unbounded request backlog.
  3. Regional clients experience lower p95 end-to-end latency without changes to model compute quality.
  4. Latency and memory decline on target hardware while validation degradation stays within the approved threshold.

Explanation

Correct Answer

B:

Peak traffic is rate-limited predictably and the serving fleet recovers without an unbounded request backlog. This is specific acceptance evidence for predictive serving rate limit and backpressure. Unlimited retries amplify overload; backpressure and controlled concurrency are needed along with scaling. It confirms the controlled correction: Apply bounded concurrency, idempotent retries with exponential backoff and explicit overload responses.

Incorrect Answers

A:

The running endpoint resolves to a traceable evaluated package and cannot silently switch weights when an alias moves. This result could demonstrate success for model registry version provenance but not for the stated predictive serving rate limit and backpressure issue. The direct test is: Peak traffic is rate-limited predictably and the serving fleet recovers without an unbounded request backlog.

C:

Regional clients experience lower p95 end-to-end latency without changes to model compute quality. This result could demonstrate success for serving region proximity versus model compute but not for the stated predictive serving rate limit and backpressure issue. The direct test is: Peak traffic is rate-limited predictably and the serving fleet recovers without an unbounded request backlog.

D:

Latency and memory decline on target hardware while validation degradation stays within the approved threshold. This result could demonstrate success for inference optimization using quantization but not for the stated predictive serving rate limit and backpressure issue. The direct test is: Peak traffic is rate-limited predictably and the serving fleet recovers without an unbounded request backlog.

Professional Machine Learning Engineer Practice Tests