Google Professional Machine Learning Engineer Practice Test 72
Question 710
During model-training validation on a Google Cloud experimental project, 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. The change should preserve a meaningful independent model-quality comparison. What implementation change resolves the specific issue without substituting an unrelated fix?
- Evaluate supported tensor or pipeline model parallelism to split the model across compatible accelerators.
- Split raw records first and resample only inside training folds, leaving validation cohorts untouched.
- Adapt the training program to the managed data input contract or stage files to an explicit configurable path.
- 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.
Incorrect Answers
A:Evaluate supported tensor or pipeline model parallelism to split the model across compatible accelerators. This action addresses model parallelism for memory-bound transformer, 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:Split raw records first and resample only inside training folds, leaving validation cohorts untouched. This action addresses training class imbalance fold leakage, 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:Adapt the training program to the managed data input contract or stage files to an explicit configurable path. This action addresses custom training input schema mismatch, 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 711
At a Google Cloud analytics team preparing a governed pilot, the following condition occurs: A retailer has no trustworthy segment labels but attempts a supervised classifier with synthetic classes supplied by the sales team. The team must satisfy a reproducible low-code AI assessment. Which configuration or procedure is the most appropriate correction?
- Exclude post-outcome fields, create point-in-time valid training and evaluation partitions, and rerun ML.EVALUATE.
- Train a supervised BigQuery ML LOGISTIC_REG or supported classifier with the churn label and evaluate precision-recall behavior.
- Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability.
- Use Cloud Translation API for supported text translation, then separately validate downstream classification against localized content.
Explanation
Correct Answer
C:Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability. This is the targeted corrective response for bigquery ml kmeans customer segmentation. K-means discovers unlabeled similarity groups; fabricating labels would make supervised accuracy meaningless. Verify the diagnosis using: Check whether real class labels exist and examine the standardized input distributions and cluster stability under different seeds. Confirm success using: Stable clusters reveal coherent customer behavior without pretending an unsupervised assignment is known supervised ground truth. Here, the relevant situation is: the following condition occurs: A retailer has no trustworthy segment labels but attempts a supervised classifier….
Incorrect Answers
A:Exclude post-outcome fields, create point-in-time valid training and evaluation partitions, and rerun ML.EVALUATE. This action addresses bigquery ml ml.evaluate leakage detection, not the failure in the described bigquery ml kmeans customer segmentation case. The targeted correction is: Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability.
B:Train a supervised BigQuery ML LOGISTIC_REG or supported classifier with the churn label and evaluate precision-recall behavior. This action addresses bigquery ml logistic model for conversion probability, not the failure in the described bigquery ml kmeans customer segmentation case. The targeted correction is: Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability.
D: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 bigquery ml kmeans customer segmentation case. The targeted correction is: Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability.
Question 712
During a regulated MLOps pipeline deployment, the following condition occurs: A data ingestion pipeline changes a numeric feature into a string, but the model-serving path accepts it and silently substitutes missing values. The workflow must be repeatable and protect the last approved production model. What should the engineer inspect before selecting a correction?
- Inspect incoming schema versions, validation logs, casting rules and downstream prediction anomalies.
- Inspect ML Metadata execution links, table snapshots, transformations and model version lineage.
- Inspect task execution states, failed-job logs, alert routing, pipeline-age metrics and owner escalation settings.
- Inspect task lineage, retries, durable checkpoints, object-store pressure and failed worker logs.
Explanation
Correct Answer
A:Inspect incoming schema versions, validation logs, casting rules and downstream prediction anomalies. This inspects evidence relevant to serving schema validation component. Silent casting can hide producer errors and produce invalid model inputs across pipeline boundaries. After identifying the cause, the matching correction is: Enforce a shared typed schema contract and reject incompatible feature versions before training or inference. This matters here because a data ingestion pipeline changes a numeric feature into a string, but the model-serving path accepts it and….
Incorrect Answers
B: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 serving schema validation component. The relevant evidence is: Inspect incoming schema versions, validation logs, casting rules and downstream prediction anomalies.
C:Inspect task execution states, failed-job logs, alert routing, pipeline-age metrics and owner escalation settings. This examines pipeline notification alert on silent failure rather than the specific mechanism reported here. It is not the decisive first check for serving schema validation component. The relevant evidence is: Inspect incoming schema versions, validation logs, casting rules and downstream prediction anomalies. This matters here because a data ingestion pipeline changes a numeric feature into a string, but the model-serving path accepts it and….
D: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 serving schema validation component. The relevant evidence is: Inspect incoming schema versions, validation logs, casting rules and downstream prediction anomalies.
Question 713
Within a jointly maintained Google Cloud data science workspace, the following condition occurs: A Colab Enterprise notebook crashes when an engineer loads a multi-terabyte BigQuery table into one pandas DataFrame to compute simple counts. Collaborators must avoid expanding data access or breaking experiment reproducibility. Which statement identifies the primary reason for this failure?
- Arrival time and event time are different; event-time windows with lateness rules preserve business-time meaning.
- Notebook execution can retain stale objects; a clean deterministic run detects hidden state dependencies.
- Framework-native checkpoints and runtime APIs are not automatically interchangeable across ML libraries.
- Single-machine notebook memory is limited; warehouse operations should execute near large warehouse-resident data.
Explanation
Correct Answer
D:Single-machine notebook memory is limited; warehouse operations should execute near large warehouse-resident data. This explains the mechanism behind notebook memory exhaustion on full data extraction and why the described failure is possible. A discriminating investigation is: Inspect query result sizes, runtime memory, pandas allocations and which aggregations can run in BigQuery SQL. The corresponding repair is: Push aggregations into BigQuery or stream bounded samples to the notebook rather than materializing the whole table. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A Colab Enterprise….
Incorrect Answers
A:Arrival time and event time are different; event-time windows with lateness rules preserve business-time meaning. This principle describes dataflow event-time window correctness, which is not the cause of the observed notebook memory exhaustion on full data extraction failure. The controlling explanation is: Single-machine notebook memory is limited; warehouse operations should execute near large warehouse-resident data.
B:Notebook execution can retain stale objects; a clean deterministic run detects hidden state dependencies. This principle describes notebook transient state and execution order, which is not the cause of the observed notebook memory exhaustion on full data extraction failure. The controlling explanation is: Single-machine notebook memory is limited; warehouse operations should execute near large warehouse-resident data. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A Colab Enterprise….
C:Framework-native checkpoints and runtime APIs are not automatically interchangeable across ML libraries. This principle describes model garden jax accelerator compatibility, which is not the cause of the observed notebook memory exhaustion on full data extraction failure. The controlling explanation is: Single-machine notebook memory is limited; warehouse operations should execute near large warehouse-resident data. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A Colab Enterprise….
Question 714
Within a jointly maintained Google Cloud data science workspace, the following condition occurs: An auditor cannot identify which training dataset and code commit produced a deployed model because the model archive has only a human-readable name. Collaborators must avoid expanding data access or breaking experiment reproducibility. Which underlying engineering principle explains why the original approach fails?
- MLOps provenance requires a recorded chain from code and data to model and deployment, not merely a friendly name.
- Arrival time and event time are different; event-time windows with lateness rules preserve business-time meaning.
- LLM-based scoring can be sensitive to phrasing, order and model preferences; evaluation needs explicit calibration.
- Trial metrics and artifact provenance must be linked to support valid experiment selection and release audits.
Explanation
Correct Answer
A:MLOps provenance requires a recorded chain from code and data to model and deployment, not merely a friendly name. This explains the mechanism behind ml metadata lineage for production model and why the described failure is possible. A discriminating investigation is: Inspect Agent Platform ML Metadata artifacts, pipeline executions, dataset fingerprints and deployment revisions. The corresponding repair is: Record input dataset versions, training runs, code revisions and output artifact links in the managed metadata and registry workflow.
Incorrect Answers
B:Arrival time and event time are different; event-time windows with lateness rules preserve business-time meaning. This principle describes dataflow event-time window correctness, which is not the cause of the observed ml metadata lineage for production model failure. The controlling explanation is: MLOps provenance requires a recorded chain from code and data to model and deployment, not merely a friendly name.
C:LLM-based scoring can be sensitive to phrasing, order and model preferences; evaluation needs explicit calibration. This principle describes llm-as-a-judge rubric reliability, which is not the cause of the observed ml metadata lineage for production model failure. The controlling explanation is: MLOps provenance requires a recorded chain from code and data to model and deployment, not merely a friendly name.
D:Trial metrics and artifact provenance must be linked to support valid experiment selection and release audits. This principle describes pipeline experiment versus notebook-only tracking, which is not the cause of the observed ml metadata lineage for production model failure. The controlling explanation is: MLOps provenance requires a recorded chain from code and data to model and deployment, not merely a friendly name.
Question 715
As the team tests a new governed AI release against adversarial and normal data, the following condition occurs: An online classifier uses a 24-hour account activity total while training created a seven-day total with the same column name. The fix must retain legitimate model usefulness and appropriate controls. Which diagnostic check should be performed FIRST to isolate the described cause?
- Inspect cohort conversion metrics, assignment validity, minimum sample requirements and the release guardrail configuration.
- Compare live and offline feature SQL, window definitions, sample entity values and prediction-time cutoffs.
- Examine alert history, day-of-week distributions, false-positive cost and baseline segmentation.
- Inspect explanation method assumptions, correlated input features, counterfactual evidence and the model's actual causal validity.
Explanation
Correct Answer
B:Compare live and offline feature SQL, window definitions, sample entity values and prediction-time cutoffs. This inspects evidence relevant to training-serving feature skew detection. Identical feature names do not guarantee identical semantics; mismatched windows create training-serving skew. After identifying the cause, the matching correction is: Version a single feature contract and add automated parity tests to the preprocessing pipeline and serving workflow.
Incorrect Answers
A:Inspect cohort conversion metrics, assignment validity, minimum sample requirements and the release guardrail configuration. This examines production incident rollback based on metrics rather than the specific mechanism reported here. It is not the decisive first check for training-serving feature skew detection. The relevant evidence is: Compare live and offline feature SQL, window definitions, sample entity values and prediction-time cutoffs.
C:Examine alert history, day-of-week distributions, false-positive cost and baseline segmentation. This examines model monitoring false-alert seasonality rather than the specific mechanism reported here. It is not the decisive first check for training-serving feature skew detection. The relevant evidence is: Compare live and offline feature SQL, window definitions, sample entity values and prediction-time cutoffs.
D:Inspect explanation method assumptions, correlated input features, counterfactual evidence and the model's actual causal validity. This examines explainability versus causal claim rather than the specific mechanism reported here. It is not the decisive first check for training-serving feature skew detection. The relevant evidence is: Compare live and offline feature SQL, window definitions, sample entity values and prediction-time cutoffs.
Question 716
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 technical explanation best accounts for the reported behavior?
- Container readiness checks alone do not guarantee successful predictions under real traffic and data distributions.
- Containerized CPU inference can be appropriate on serverless compute; specialized ML endpoints are not required for every model.
- Network exposure and IAM controls are complementary; a public endpoint adds attack surface even with authentication.
- Online feature serving requires an up-to-date synchronized view; source-table changes need not appear instantly.
Explanation
Correct Answer
C:Network exposure and IAM controls are complementary; a public endpoint adds attack surface even with authentication. This explains the mechanism behind private endpoint for regulated inference traffic and why the described failure is possible. A discriminating investigation is: Examine endpoint exposure settings, caller IAM, VPC routes, private connectivity and data egress requirements. The corresponding repair is: Deploy a supported private endpoint or constrained private network path with least-privilege caller authorization. This matters here because an internal fraud scorer sends sensitive feature vectors to a publicly accessible prediction endpoint even though….
Incorrect Answers
A:Container readiness checks alone do not guarantee successful predictions under real traffic and data distributions. This principle describes model traffic rollback on high error rate, which is not the cause of the observed private endpoint for regulated inference traffic failure. The controlling explanation is: Network exposure and IAM controls are complementary; a public endpoint adds attack surface even with authentication.
B:Containerized CPU inference can be appropriate on serverless compute; specialized ML endpoints are not required for every model. This principle describes cloud run versus managed inference endpoint, which is not the cause of the observed private endpoint for regulated inference traffic failure. The controlling explanation is: Network exposure and IAM controls are complementary; a public endpoint adds attack surface even with authentication.
D:Online feature serving requires an up-to-date synchronized view; source-table changes need not appear instantly. This principle describes feature store freshness and online sync, which is not the cause of the observed private endpoint for regulated inference traffic failure. The controlling explanation is: Network exposure and IAM controls are complementary; a public endpoint adds attack surface even with authentication.
Question 717
During a regulated MLOps pipeline deployment, the following condition occurs: A pipeline retrains after every minor quality fluctuation and immediately promotes each candidate, causing frequent unstable production swaps. The workflow must be repeatable and protect the last approved production model. Which statement identifies the primary reason for this failure?
- Continuous training needs statistically and operationally justified policy thresholds rather than reactive promotion of noise.
- Storage event notifications require business-level readiness and deduplication before training begins.
- Security scanning provides protection only if the CI/CD pipeline enforces its result before release.
- Continuous training should not imply uncontrolled continuous deployment of every new model.
Explanation
Correct Answer
A:Continuous training needs statistically and operationally justified policy thresholds rather than reactive promotion of noise. This explains the mechanism behind canary failure feedback into ct policy and why the described failure is possible. A discriminating investigation is: Inspect promotion history, drift thresholds, confidence intervals, model quality guardrails and rollback records. The corresponding repair is: Use a retraining policy with significant trigger thresholds, independent evaluation and staged deployment approval.
Incorrect Answers
B:Storage event notifications require business-level readiness and deduplication before training begins. This principle describes eventbridge equivalent event trigger on storage, which is not the cause of the observed canary failure feedback into ct policy failure. The controlling explanation is: Continuous training needs statistically and operationally justified policy thresholds rather than reactive promotion of noise.
C: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 canary failure feedback into ct policy failure. The controlling explanation is: Continuous training needs statistically and operationally justified policy thresholds rather than reactive promotion of noise.
D:Continuous training should not imply uncontrolled continuous deployment of every new model. This principle describes continuous training rollback protection, which is not the cause of the observed canary failure feedback into ct policy failure. The controlling explanation is: Continuous training needs statistically and operationally justified policy thresholds rather than reactive promotion of noise.
Question 718
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. Which result is the strongest postchange evidence of success?
- Representative photographs return the needed detections at acceptable precision, latency and per-image cost.
- Stable clusters reveal coherent customer behavior without pretending an unsupervised assignment is known supervised ground truth.
- A held-out invoice batch produces correct structured fields with measurable per-field precision and reject handling.
- On held-out questions, answers remain grounded while input tokens and p95 response latency decline.
Explanation
Correct Answer
D:On held-out questions, answers remain grounded while input tokens and p95 response latency decline. This is specific acceptance evidence for gemini prompt context token budget. Unfocused context consumes tokens and can distract generation; targeted retrieval can reduce cost without discarding needed facts. It confirms the controlled correction: 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….
Incorrect Answers
A: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 gemini prompt context token budget issue. The direct test is: 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….
B:Stable clusters reveal coherent customer behavior without pretending an unsupervised assignment is known supervised ground truth. This result could demonstrate success for bigquery ml kmeans customer segmentation but not for the stated gemini prompt context token budget issue. The direct test is: On held-out questions, answers remain grounded while input tokens and p95 response latency decline.
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 gemini prompt context token budget issue. The direct test is: On held-out questions, answers remain grounded while input tokens and p95 response latency decline.
Question 719
During a staged restoration test at a secondary serving deployment, 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 team must prove an actual user-visible improvement without weakening access controls. Which configuration or procedure is the most appropriate correction?
- Use stable cohort-level assignment and record model identity on requests and measured outcomes.
- Deploy a supported private endpoint or constrained private network path with least-privilege caller authorization.
- Preserve stable canonical identifier types end-to-end and backfill only the affected feature records.
- Ship the class vocabulary with the model artifact and version or validate the output adapter against it.
Explanation
Correct Answer
B: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.
Incorrect Answers
A:Use stable cohort-level assignment and record model identity on requests and measured outcomes. This action addresses a/b assignment consistency for user journeys, 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:Preserve stable canonical identifier types end-to-end and backfill only the affected feature records. This action addresses feature online entity key mismatch, 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:Ship the class vocabulary with the model artifact and version or validate the output adapter against it. This action addresses custom postprocessing label mapping drift, 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 720
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A custom training image expects a local CSV under the developer's home directory but managed training supplies data through configured Cloud Storage paths. Engineers need an auditable, resource-aware correction to the issue. Which TWO selections form an appropriate before-and-after verification pair? Select TWO.
- The training manifest contains traceable permitted sources and safety tests detect known prohibited outputs.
- A clean managed training run reads the intended versioned dataset without notebook-local path assumptions.
- The chosen threshold detects clinically relevant positives while the false-alarm rate is documented for deployment review.
- Inspect gradient ranges, loss-scaling logs, overflow events and the affected operations with test batches.
- Inspect task input configuration, container logs, expected file patterns and staged object paths.
Explanation
Correct Answers
B:A clean managed training run reads the intended versioned dataset without notebook-local path assumptions. This is specific acceptance evidence for custom training input schema mismatch. Notebook filesystem locations are not portable contracts for managed container training jobs. It confirms the controlled correction: Adapt the training program to the managed data input contract or stage files to an explicit configurable path.
E:Inspect task input configuration, container logs, expected file patterns and staged object paths. This inspects evidence relevant to custom training input schema mismatch. Notebook filesystem locations are not portable contracts for managed container training jobs. After identifying the cause, the matching correction is: Adapt the training program to the managed data input contract or stage files to an explicit configurable path.
Incorrect Answers
A:The training manifest contains traceable permitted sources and safety tests detect known prohibited outputs. This relates to fine-tuning image generator data rights but does not establish the requested before-and-after evidence. The actual diagnostic is: Inspect task input configuration, container logs, expected file patterns and staged object paths. The specific acceptance result is: A clean managed training run reads the intended versioned dataset without notebook-local path assumptions.
C:The chosen threshold detects clinically relevant positives while the false-alarm rate is documented for deployment review. This relates to cost-sensitive threshold for rare positives but does not establish the requested before-and-after evidence. The actual diagnostic is: Inspect task input configuration, container logs, expected file patterns and staged object paths. The specific acceptance result is: A clean managed training run reads the intended versioned dataset without notebook-local path assumptions.
D:Inspect gradient ranges, loss-scaling logs, overflow events and the affected operations with test batches. This relates to mixed precision overflow diagnosis but does not establish the requested before-and-after evidence. The actual diagnostic is: Inspect task input configuration, container logs, expected file patterns and staged object paths. The specific acceptance result is: A clean managed training run reads the intended versioned dataset without notebook-local path assumptions.