Google Professional Machine Learning Engineer Practice Test 86
Question 850
At a Google Cloud analytics team preparing a governed pilot, the following condition occurs: A customer churn dataset has yes/no labels but an analyst trains unsupervised k-means clusters and treats cluster IDs as churn probabilities. The team must satisfy a reproducible low-code AI assessment. Which result is the strongest postchange evidence of success?
- Twenty-one future daily estimates are produced with reported prediction intervals and error is scored on forward dates.
- An unseen labeled cohort receives probabilities for the intended positive class with a calibrated operating threshold.
- Held-out metrics reflect only features available before the prediction timestamp and remain credible on later periods.
- Representative photographs return the needed detections at acceptable precision, latency and per-image cost.
Explanation
Correct Answer
B:An unseen labeled cohort receives probabilities for the intended positive class with a calibrated operating threshold. This is specific acceptance evidence for bigquery ml logistic model for conversion probability. Clustering segments observations without learning their known outcomes, while supervised classification predicts those outcomes. It confirms the controlled correction: Train a supervised BigQuery ML LOGISTIC_REG or supported classifier with the churn label and evaluate precision-recall behavior.
Incorrect Answers
A:Twenty-one future daily estimates are produced with reported prediction intervals and error is scored on forward dates. This result could demonstrate success for bigquery arima_plus forecast horizon but not for the stated bigquery ml logistic model for conversion probability issue. The direct test is: An unseen labeled cohort receives probabilities for the intended positive class with a calibrated operating threshold.
C:Held-out metrics reflect only features available before the prediction timestamp and remain credible on later periods. This result could demonstrate success for bigquery ml ml.evaluate leakage detection but not for the stated bigquery ml logistic model for conversion probability issue. The direct test is: An unseen labeled cohort receives probabilities for the intended positive class with a calibrated operating threshold.
D:Representative photographs return the needed detections at acceptable precision, latency and per-image cost. This result could demonstrate success for vision api pretrained image labels versus custom detection but not for the stated bigquery ml logistic model for conversion probability issue. The direct test is: An unseen labeled cohort receives probabilities for the intended positive class with a calibrated operating threshold.
Question 851
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A retailer asks for next-week order value as a dollar amount, but the prototype returns yes/no purchase classes without estimated magnitude. Engineers need an auditable, resource-aware correction to the issue. Which TWO complementary choices jointly establish the evidence and appropriate correction? Select TWO.
- Inspect required output type, business loss, sample labels, and the configured model objective and metric.
- Determine whether failures arise from changing reference knowledge, stable behavior patterns or inadequate retrieval coverage.
- Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision.
- Recompute lagged windows using only prior observations and validate with rolling-origin splits.
- Select a regression architecture and matching numeric loss rather than using a binary classifier for amounts.
Explanation
Correct Answers
A:Inspect required output type, business loss, sample labels, and the configured model objective and metric. This inspects evidence relevant to regression versus classification product choice. Categorical classification is not an estimator of an unrestricted continuous order value. After identifying the cause, the matching correction is: Select a regression architecture and matching numeric loss rather than using a binary classifier for amounts. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….
E:Select a regression architecture and matching numeric loss rather than using a binary classifier for amounts. This is the targeted corrective response for regression versus classification product choice. Categorical classification is not an estimator of an unrestricted continuous order value. Verify the diagnosis using: Inspect required output type, business loss, sample labels, and the configured model objective and metric. Confirm success using: Held-out predictions are currency-valued and their absolute or squared errors match the financial evaluation contract. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….
Incorrect Answers
B:Determine whether failures arise from changing reference knowledge, stable behavior patterns or inadequate retrieval coverage. This is an action or diagnostic relevant to foundation model prompt versus fine-tuning, not one of the required two steps. In this scenario verify: Inspect required output type, business loss, sample labels, and the configured model objective and metric. Then correct: Select a regression architecture and matching numeric loss rather than using a binary classifier for amounts.
C:Use suitable text embeddings with vector similarity search and reranking rather than a binary spam decision. This is an action or diagnostic relevant to embedding retrieval versus text classifier, not one of the required two steps. In this scenario verify: Inspect required output type, business loss, sample labels, and the configured model objective and metric. Then correct: Select a regression architecture and matching numeric loss rather than using a binary classifier for amounts.
D:Recompute lagged windows using only prior observations and validate with rolling-origin splits. This is an action or diagnostic relevant to temporal training label leakage in rolling windows, not one of the required two steps. In this scenario verify: Inspect required output type, business loss, sample labels, and the configured model objective and metric. Then correct: Select a regression architecture and matching numeric loss rather than using a binary classifier for amounts.
Question 852
During a controlled replay of the data and model handoff to a second engineering team, the following condition occurs: A team uses manual spreadsheet rows for hyperparameter results and loses connections between training metrics and produced checkpoint artifacts. The handoff must preserve privacy, lineage and testable behavior. Which result is the strongest postchange evidence of success?
- Each candidate's reported metrics resolve to its actual artifact and replayable configuration without manual lookups.
- A production model identifier resolves to its training execution, immutable artifacts, approvals and input dataset.
- Candidate scores can be reproduced on the same held-out data and their differences are attributable to model changes.
- A newly started Workbench or Colab Enterprise runtime reproduces the complete experiment without undocumented manual cell order.
Explanation
Correct Answer
A:Each candidate's reported metrics resolve to its actual artifact and replayable configuration without manual lookups. This is specific acceptance evidence for pipeline experiment versus notebook-only tracking. Trial metrics and artifact provenance must be linked to support valid experiment selection and release audits. It confirms the controlled correction: Use Agent Platform Experiments and pipeline metadata to track each trial's parameters, measurements and output artifacts. 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: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 pipeline experiment versus notebook-only tracking issue. The direct test is: Each candidate's reported metrics resolve to its actual artifact and replayable configuration without manual lookups. This matters here because during a controlled replay of the data and model handoff to a second engineering team, the following condition….
C:Candidate scores can be reproduced on the same held-out data and their differences are attributable to model changes. This result could demonstrate success for experiment metric comparison with mismatched splits but not for the stated pipeline experiment versus notebook-only tracking issue. The direct test is: Each candidate's reported metrics resolve to its actual artifact and replayable configuration without manual lookups. This matters here because during a controlled replay of the data and model handoff to a second engineering team, the following condition….
D: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 pipeline experiment versus notebook-only tracking issue. The direct test is: Each candidate's reported metrics resolve to its actual artifact and replayable configuration without manual lookups.
Question 853
During a staged restoration test at a secondary serving deployment, the following condition occurs: A model receives empty features for existing customers because online requests use string IDs with leading zeros while the source feature view cast them to integers. The team must prove an actual user-visible improvement without weakening access controls. Which configuration or procedure is the most appropriate correction?
- Test a supported post-training quantization or optimization path and release only if target quality remains acceptable.
- Choose a managed batch inference or scheduled container batch workflow instead of an always-on online endpoint.
- Preserve stable canonical identifier types end-to-end and backfill only the affected feature records.
- Schedule and monitor approved Feature Store synchronization at the needed frequency, with stale-feature handling.
Explanation
Correct Answer
C:Preserve stable canonical identifier types end-to-end and backfill only the affected feature records. This is the targeted corrective response for feature online entity key mismatch. Coercing identifier types can change keys, particularly when numeric-looking strings have meaningful leading zeros. Verify the diagnosis using: Compare requested entity key bytes, stored feature-group schema, casting rules and online lookup failures. Confirm success using: Previously missed customer IDs retrieve the intended feature values without collapsing distinct leading-zero identifiers. This matters here because during a staged restoration test at a secondary serving deployment, the following condition occurs: A model receives….
Incorrect Answers
A: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 feature online entity key mismatch case. The targeted correction is: Preserve stable canonical identifier types end-to-end and backfill only the affected feature records.
B:Choose a managed batch inference or scheduled container batch workflow instead of an always-on online endpoint. This action addresses batch versus online inference schedule, not the failure in the described feature online entity key mismatch case. The targeted correction is: Preserve stable canonical identifier types end-to-end and backfill only the affected feature records.
D:Schedule and monitor approved Feature Store synchronization at the needed frequency, with stale-feature handling. This action addresses feature store freshness and online sync, not the failure in the described feature online entity key mismatch case. The targeted correction is: Preserve stable canonical identifier types end-to-end and backfill only the affected feature records.
Question 854
During model-training validation on a Google Cloud experimental project, 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. The change should preserve a meaningful independent model-quality comparison. Which statement identifies the primary reason for this failure?
- When a model fits on each worker, partitioning training data is often more suitable than splitting the model itself.
- Distributed sampling can pad replicas; uncorrected metric aggregation may bias evaluation results.
- Search quality depends on comparable objectives and resource limits, not exhaustive combinations at any cost.
- Structured numeric forecasting relies on temporal evidence; a conversational model is not automatically the best forecaster.
Explanation
Correct Answer
A:When a model fits on each worker, partitioning training data is often more suitable than splitting the model itself. This explains the mechanism behind distributed data parallel gradient synchronization and why the described failure is possible. A discriminating investigation is: Measure model footprint, per-device utilization, communication cost and batch throughput on one and multiple accelerators. The corresponding repair is: Prefer suitable data parallel replicas with synchronized gradient aggregation, then benchmark scale efficiency. This matters here because during model-training validation on a Google Cloud experimental project, the following condition occurs: A model….
Incorrect Answers
B:Distributed sampling can pad replicas; uncorrected metric aggregation may bias evaluation results. This principle describes data-parallel evaluation duplicate samples, which is not the cause of the observed distributed data parallel gradient synchronization failure. The controlling explanation is: When a model fits on each worker, partitioning training data is often more suitable than splitting the model itself. This matters here because during model-training validation on a Google Cloud experimental project, the following condition occurs: A model….
C:Search quality depends on comparable objectives and resource limits, not exhaustive combinations at any cost. This principle describes hyperparameter search budget limit, which is not the cause of the observed distributed data parallel gradient synchronization failure. The controlling explanation is: When a model fits on each worker, partitioning training data is often more suitable than splitting the model itself.
D:Structured numeric forecasting relies on temporal evidence; a conversational model is not automatically the best forecaster. This principle describes forecast trend and seasonality versus llm, which is not the cause of the observed distributed data parallel gradient synchronization failure. The controlling explanation is: When a model fits on each worker, partitioning training data is often more suitable than splitting the model itself.
Question 855
While reproducing a training orchestration incident in isolated staging, the following condition occurs: A monthly CSV feed begins omitting account IDs, but the pipeline trains and publishes a model without examining null-rate changes. The team requires an idempotent pipeline behavior and traceable evidence. Which TWO selections represent the correct investigation and remediation together? Select TWO.
- Add a data-validation component that quarantines nonconforming inputs and fails downstream training until reviewed.
- Inspect Cloud Build stage status propagation, vulnerability findings, policy thresholds and deployment triggers.
- Tune component resource requests/limits and stream or partition embeddings rather than materializing every vector at once.
- Require inference contract and integration tests with representative requests before promoting each candidate artifact.
- Review schema tests, null-rate distributions, validation thresholds and which pipeline stages respond to failures.
Explanation
Correct Answers
A:Add a data-validation component that quarantines nonconforming inputs and fails downstream training until reviewed. This is the targeted corrective response for data validation threshold gate. A schema existing does not imply data quality; pipeline gates must enforce business completeness rules. Verify the diagnosis using: Review schema tests, null-rate distributions, validation thresholds and which pipeline stages respond to failures. Confirm success using: A deliberately malformed dataset is rejected before training while healthy fixtures proceed successfully. This matters here because while reproducing a training orchestration incident in isolated staging, the following condition occurs: A monthly….
E:Review schema tests, null-rate distributions, validation thresholds and which pipeline stages respond to failures. This inspects evidence relevant to data validation threshold gate. A schema existing does not imply data quality; pipeline gates must enforce business completeness rules. After identifying the cause, the matching correction is: Add a data-validation component that quarantines nonconforming inputs and fails downstream training until reviewed. This matters here because while reproducing a training orchestration incident in isolated staging, the following condition occurs: A monthly….
Incorrect Answers
B:Inspect Cloud Build stage status propagation, vulnerability findings, policy thresholds and deployment triggers. This is an action or diagnostic relevant to cloud build container security gate, not one of the required two steps. In this scenario verify: Review schema tests, null-rate distributions, validation thresholds and which pipeline stages respond to failures. Then correct: Add a data-validation component that quarantines nonconforming inputs and fails downstream training until reviewed.
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: Review schema tests, null-rate distributions, validation thresholds and which pipeline stages respond to failures. Then correct: Add a data-validation component that quarantines nonconforming inputs and fails downstream training until reviewed.
D: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: Review schema tests, null-rate distributions, validation thresholds and which pipeline stages respond to failures. Then correct: Add a data-validation component that quarantines nonconforming inputs and fails downstream training until reviewed.
Question 856
At a Google Cloud analytics team preparing a governed pilot, the following condition occurs: A content moderation team needs generic objects detected in product photographs but starts training a custom network without checking pretrained image analysis. The team must satisfy a reproducible low-code AI assessment. What acceptance result verifies the intended behavior after remediation?
- A bilingual reviewer confirms meaning and formatting for representative descriptions without retraining a translation model.
- Representative photographs return the needed detections at acceptable precision, latency and per-image cost.
- A held-out invoice batch produces correct structured fields with measurable per-field precision and reject handling.
- Twenty-one future daily estimates are produced with reported prediction intervals and error is scored on forward dates.
Explanation
Correct Answer
B:Representative photographs return the needed detections at acceptable precision, latency and per-image cost. This is specific acceptance evidence for vision api pretrained image labels versus custom detection. A pretrained vision API may cover general image concepts, while specialized categories may need a custom model. It confirms the controlled correction: Evaluate Cloud Vision API for supported generic image detection and use custom training only for missing domain-specific classes. Here, the relevant situation is: the following condition occurs: A content moderation team needs generic objects detected in product photographs but….
Incorrect Answers
A:A bilingual reviewer confirms meaning and formatting for representative descriptions without retraining a translation model. This result could demonstrate success for translate api for multilingual product descriptions but not for the stated vision api pretrained image labels versus custom detection issue. The direct test is: Representative photographs return the needed detections at acceptable precision, latency and per-image cost. Here, the relevant situation is: the following condition occurs: A content moderation team needs generic objects detected in product photographs but….
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 vision api pretrained image labels versus custom detection issue. The direct test is: Representative photographs return the needed detections at acceptable precision, latency and per-image cost.
D:Twenty-one future daily estimates are produced with reported prediction intervals and error is scored on forward dates. This result could demonstrate success for bigquery arima_plus forecast horizon but not for the stated vision api pretrained image labels versus custom detection issue. The direct test is: Representative photographs return the needed detections at acceptable precision, latency and per-image cost.
Question 857
Within a jointly maintained Google Cloud data science workspace, the following condition occurs: An analyst runs a long-lived custom Apache Beam streaming service to compute a simple daily SQL join and aggregate over tables already in BigQuery. Collaborators must avoid expanding data access or breaking experiment reproducibility. Which evidence most directly establishes what is wrong with this AI or ML workflow?
- Inspect join-key frequency distributions, per-task runtime, shuffle spill and the output cardinality before optimization.
- Inspect the labeling payload schema, data classification, annotator roles and fields needed to complete the labeling task.
- Examine source locations, batch cadence, SQL transform complexity, streaming latency requirements and operational burden.
- Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project.
Explanation
Correct Answer
C:Examine source locations, batch cadence, SQL transform complexity, streaming latency requirements and operational burden. This inspects evidence relevant to bigquery versus dataflow preparation selection. Choosing a managed SQL engine for warehouse-resident batch joins avoids unnecessary always-on stream processing. After identifying the cause, the matching correction is: Implement the batch aggregate in scheduled BigQuery SQL when the required transformation is expressible and fits its SLA. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: An analyst runs a….
Incorrect Answers
A:Inspect join-key frequency distributions, per-task runtime, shuffle spill and the output cardinality before optimization. This examines managed spark join-key skew repair rather than the specific mechanism reported here. It is not the decisive first check for bigquery versus dataflow preparation selection. The relevant evidence is: Examine source locations, batch cadence, SQL transform complexity, streaming latency requirements and operational burden.
B:Inspect the labeling payload schema, data classification, annotator roles and fields needed to complete the labeling task. This examines data minimization for labeling inputs rather than the specific mechanism reported here. It is not the decisive first check for bigquery versus dataflow preparation selection. The relevant evidence is: Examine source locations, batch cadence, SQL transform complexity, streaming latency requirements and operational burden. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: An analyst runs a….
D:Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project. This examines workbench credentials embedded in repository rather than the specific mechanism reported here. It is not the decisive first check for bigquery versus dataflow preparation selection. The relevant evidence is: Examine source locations, batch cadence, SQL transform complexity, streaming latency requirements and operational burden.
Question 858
During a regulated MLOps pipeline deployment, the following condition occurs: A Kubeflow preprocessing task is evicted repeatedly because it requests little memory despite materializing large embeddings inside the container. The workflow must be repeatable and protect the last approved production model. Which underlying engineering principle explains why the original approach fails?
- Security scanning provides protection only if the CI/CD pipeline enforces its result before release.
- Unobserved outcomes cannot serve as reliable supervised labels regardless of the desired retraining schedule.
- Distributed in-memory object stores are not durable archival storage; failure recovery needs explicit design.
- Kubernetes resource limits constrain component runtime even when the model's training job itself has spare capacity.
Explanation
Correct Answer
D:Kubernetes resource limits constrain component runtime even when the model's training job itself has spare capacity. This explains the mechanism behind custom kfp component resource limits and why the described failure is possible. A discriminating investigation is: Inspect Kubernetes task events, memory usage, component resource requests and container data-loading behavior. The corresponding repair is: Tune component resource requests/limits and stream or partition embeddings rather than materializing every vector at once.
Incorrect Answers
A:Security scanning provides protection only if the CI/CD pipeline enforces its result before release. This principle describes cloud build container security gate, which is not the cause of the observed custom kfp component resource limits failure. The controlling explanation is: Kubernetes resource limits constrain component runtime even when the model's training job itself has spare capacity.
B:Unobserved outcomes cannot serve as reliable supervised labels regardless of the desired retraining schedule. This principle describes scheduled retraining on delayed ground truth, which is not the cause of the observed custom kfp component resource limits failure. The controlling explanation is: Kubernetes resource limits constrain component runtime even when the model's training job itself has spare capacity.
C:Distributed in-memory object stores are not durable archival storage; failure recovery needs explicit design. This principle describes ray distributed task failure isolation, which is not the cause of the observed custom kfp component resource limits failure. The controlling explanation is: Kubernetes resource limits constrain component runtime even when the model's training job itself has spare capacity.
Question 859
While reproducing a training orchestration incident in isolated staging, the following condition occurs: A Kubeflow preprocessing task is evicted repeatedly because it requests little memory despite materializing large embeddings inside the container. The team requires an idempotent pipeline behavior and traceable evidence. Which result is the strongest postchange evidence of success?
- Running the same task twice produces one logical batch and preserves prior validated partitions.
- The deployed model and container can be traced to a particular approved commit and evaluation result.
- The task completes within approved resources with predictable cost and produces the same number of embeddings.
- Changing the dataset version forces a rebuild while identical inputs may reuse validated cached results.
Explanation
Correct Answer
C:The task completes within approved resources with predictable cost and produces the same number of embeddings. This is specific acceptance evidence for custom kfp component resource limits. Kubernetes resource limits constrain component runtime even when the model's training job itself has spare capacity. It confirms the controlled correction: Tune component resource requests/limits and stream or partition embeddings rather than materializing every vector at once. This matters here because while reproducing a training orchestration incident in isolated staging, the following condition occurs: A Kubeflow….
Incorrect Answers
A:Running the same task twice produces one logical batch and preserves prior validated partitions. This result could demonstrate success for airflow task idempotency on retry but not for the stated custom kfp component resource limits issue. The direct test is: The task completes within approved resources with predictable cost and produces the same number of embeddings.
B:The deployed model and container can be traced to a particular approved commit and evaluation result. This result could demonstrate success for cloud build release version promotion but not for the stated custom kfp component resource limits issue. The direct test is: The task completes within approved resources with predictable cost and produces the same number of embeddings.
D:Changing the dataset version forces a rebuild while identical inputs may reuse validated cached results. This result could demonstrate success for kubeflow component cache invalidation but not for the stated custom kfp component resource limits issue. The direct test is: The task completes within approved resources with predictable cost and produces the same number of embeddings.
Question 860
While reproducing a training orchestration incident in isolated staging, the following condition occurs: An endpoint calculates categorical encodings in application code while the training pipeline uses a separate mapping, creating drift after a feature update. The team requires an idempotent pipeline behavior and traceable evidence. Which diagnostic check should be performed FIRST to isolate the described cause?
- Inspect ML Metadata execution links, table snapshots, transformations and model version lineage.
- Inspect task lineage, retries, durable checkpoints, object-store pressure and failed worker logs.
- Inspect snapshot identifiers, SQL filters, table partitions and the model version's recorded input manifest.
- Compare serialized preprocessing artifacts, schema versions, train-time transformations and live request feature IDs.
Explanation
Correct Answer
D:Compare serialized preprocessing artifacts, schema versions, train-time transformations and live request feature IDs. This inspects evidence relevant to training serving preprocessing artifact sharing. Two independent preprocessing implementations can diverge even when their initial training metrics look correct. After identifying the cause, the matching correction is: Package the fitted preprocessing component with the model and apply the same validated transform in both paths. This matters here because while reproducing a training orchestration incident in isolated staging, the following condition occurs: An endpoint….
Incorrect Answers
A:Inspect ML Metadata execution links, table snapshots, transformations and model version lineage. This examines model feature lineage for audit rather than the specific mechanism reported here. It is not the decisive first check for training serving preprocessing artifact sharing. The relevant evidence is: Compare serialized preprocessing artifacts, schema versions, train-time transformations and live request feature IDs.
B:Inspect task lineage, retries, durable checkpoints, object-store pressure and failed worker logs. This examines ray distributed task failure isolation rather than the specific mechanism reported here. It is not the decisive first check for training serving preprocessing artifact sharing. The relevant evidence is: Compare serialized preprocessing artifacts, schema versions, train-time transformations and live request feature IDs.
C:Inspect snapshot identifiers, SQL filters, table partitions and the model version's recorded input manifest. This examines data version reproducibility in ct jobs rather than the specific mechanism reported here. It is not the decisive first check for training serving preprocessing artifact sharing. The relevant evidence is: Compare serialized preprocessing artifacts, schema versions, train-time transformations and live request feature IDs.