Google Professional Machine Learning Engineer Practice Test 102
Question 1010
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: Distributed training validation counts the final padded examples twice because the evaluation sampler duplicates data to balance worker batches. Engineers need an auditable, resource-aware correction to the issue. Which diagnostic check should be performed FIRST to isolate the described cause?
- Inspect feature computation cutoffs, window frame bounds, label timestamps and time-aware evaluation splits.
- Inspect gradient ranges, loss-scaling logs, overflow events and the affected operations with test batches.
- Compare sampler configuration, example IDs, per-worker output counts and the global metric-reduction step.
- Inspect feature modality, example counts, training cost, validation scores and latency requirements.
Explanation
Correct Answer
C:Compare sampler configuration, example IDs, per-worker output counts and the global metric-reduction step. This inspects evidence relevant to data-parallel evaluation duplicate samples. Distributed sampling can pad replicas; uncorrected metric aggregation may bias evaluation results. After identifying the cause, the matching correction is: Deduplicate or correctly weight validation samples when aggregating distributed metrics across workers. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….
Incorrect Answers
A:Inspect feature computation cutoffs, window frame bounds, label timestamps and time-aware evaluation splits. This examines temporal training label leakage in rolling windows rather than the specific mechanism reported here. It is not the decisive first check for data-parallel evaluation duplicate samples. The relevant evidence is: Compare sampler configuration, example IDs, per-worker output counts and the global metric-reduction step.
B:Inspect gradient ranges, loss-scaling logs, overflow events and the affected operations with test batches. This examines mixed precision overflow diagnosis rather than the specific mechanism reported here. It is not the decisive first check for data-parallel evaluation duplicate samples. The relevant evidence is: Compare sampler configuration, example IDs, per-worker output counts and the global metric-reduction step. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….
D:Inspect feature modality, example counts, training cost, validation scores and latency requirements. This examines deep model versus gradient boosted trees on tabular rather than the specific mechanism reported here. It is not the decisive first check for data-parallel evaluation duplicate samples. The relevant evidence is: Compare sampler configuration, example IDs, per-worker output counts and the global metric-reduction step. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….
Question 1011
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A hospital alert model achieves 99% accuracy by predicting every patient is negative when the positive condition occurs in 1% of cases. Engineers need an auditable, resource-aware correction to the issue. What acceptance result verifies the intended behavior after remediation?
- The chosen threshold detects clinically relevant positives while the false-alarm rate is documented for deployment review.
- Relevant articles rank highly for unseen paraphrased queries and retrieval hit rate is measured against judgments.
- New warranty rules appear correctly after the index update without unnecessary retraining and sources remain traceable.
- Trials stay within the approved compute budget and a winner improves the specified independent metric.
Explanation
Correct Answer
A:The chosen threshold detects clinically relevant positives while the false-alarm rate is documented for deployment review. This is specific acceptance evidence for cost-sensitive threshold for rare positives. Accuracy on highly imbalanced labels can hide severe minority-class recall failures. It confirms the controlled correction: Choose a decision threshold using acceptable recall and alert burden with a validated independent cohort. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….
Incorrect Answers
B:Relevant articles rank highly for unseen paraphrased queries and retrieval hit rate is measured against judgments. This result could demonstrate success for embedding retrieval versus text classifier but not for the stated cost-sensitive threshold for rare positives issue. The direct test is: The chosen threshold detects clinically relevant positives while the false-alarm rate is documented for deployment review.
C:New warranty rules appear correctly after the index update without unnecessary retraining and sources remain traceable. This result could demonstrate success for foundation model prompt versus fine-tuning but not for the stated cost-sensitive threshold for rare positives issue. The direct test is: The chosen threshold detects clinically relevant positives while the false-alarm rate is documented for deployment review.
D:Trials stay within the approved compute budget and a winner improves the specified independent metric. This result could demonstrate success for hyperparameter search budget limit but not for the stated cost-sensitive threshold for rare positives issue. The direct test is: The chosen threshold detects clinically relevant positives while the false-alarm rate is documented for deployment review.
Question 1012
During a staged restoration test at a secondary serving deployment, the following condition occurs: A team deploys a model using a mutable storage path named production-latest and cannot reconstruct which evaluation approved its weights. The team must prove an actual user-visible improvement without weakening access controls. What acceptance result verifies the intended behavior after remediation?
- Previously missed customer IDs retrieve the intended feature values without collapsing distinct leading-zero identifiers.
- Only a limited portion initially uses the candidate and a simulated regression triggers a tested rollback.
- The running endpoint resolves to a traceable evaluated package and cannot silently switch weights when an alias moves.
- Repeated requests from the same test user stay on one variant and conversion comparisons preserve randomized balance.
Explanation
Correct Answer
C:The running endpoint resolves to a traceable evaluated package and cannot silently switch weights when an alias moves. This is specific acceptance evidence for model registry version provenance. Mutable nicknames do not establish immutable model provenance for controlled production releases. It confirms the controlled correction: Promote an explicitly approved model version from Agent Platform Model Registry and record deployment lineage. This matters here because during a staged restoration test at a secondary serving deployment, the following condition occurs: A team deploys a….
Incorrect Answers
A:Previously missed customer IDs retrieve the intended feature values without collapsing distinct leading-zero identifiers. This result could demonstrate success for feature online entity key mismatch but not for the stated model registry version provenance issue. The direct test is: The running endpoint resolves to a traceable evaluated package and cannot silently switch weights when an alias moves.
B:Only a limited portion initially uses the candidate and a simulated regression triggers a tested rollback. This result could demonstrate success for canary gradual traffic rollout but not for the stated model registry version provenance issue. The direct test is: The running endpoint resolves to a traceable evaluated package and cannot silently switch weights when an alias moves.
D:Repeated requests from the same test user stay on one variant and conversion comparisons preserve randomized balance. This result could demonstrate success for a/b assignment consistency for user journeys but not for the stated model registry version provenance issue. The direct test is: The running endpoint resolves to a traceable evaluated package and cannot silently switch weights when an alias moves. This matters here because during a staged restoration test at a secondary serving deployment, the following condition occurs: A team deploys a….
Question 1013
Within a jointly maintained Google Cloud data science workspace, the following condition occurs: A numeric risk feature contains occasional physically impossible sensor spikes that inflate its fitted scale and degrade otherwise normal predictions. Collaborators must avoid expanding data access or breaking experiment reproducibility. What implementation change resolves the specific issue without substituting an unrelated fix?
- Redact or tokenize unnecessary identifying fields before labeling and limit access to approved mappings.
- Quarantine invalid spikes and fit a robust transformation using training data only, then apply it consistently at inference.
- Rebuild offline training data with point-in-time eligible joins and remove features available only after each prediction moment.
- Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates.
Explanation
Correct Answer
B:Quarantine invalid spikes and fit a robust transformation using training data only, then apply it consistently at inference. This is the targeted corrective response for outlier handling before feature standardization. A scaler learned from corrupted or held-out values can distort typical feature magnitudes and leak evaluation information. Verify the diagnosis using: Inspect feature quantiles, physical validity bounds, missingness and training-only fit statistics against independent validation data. Confirm success using: A held-out clean sample preserves meaningful ranges while invalid spikes trigger visible data-quality exceptions. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A numeric risk….
Incorrect Answers
A:Redact or tokenize unnecessary identifying fields before labeling and limit access to approved mappings. This action addresses data minimization for labeling inputs, not the failure in the described outlier handling before feature standardization case. The targeted correction is: Quarantine invalid spikes and fit a robust transformation using training data only, then apply it consistently at inference.
C:Rebuild offline training data with point-in-time eligible joins and remove features available only after each prediction moment. This action addresses point-in-time feature leakage prevention, not the failure in the described outlier handling before feature standardization case. The targeted correction is: Quarantine invalid spikes and fit a robust transformation using training data only, then apply it consistently at inference.
D:Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates. This action addresses experiment metric comparison with mismatched splits, not the failure in the described outlier handling before feature standardization case. The targeted correction is: Quarantine invalid spikes and fit a robust transformation using training data only, then apply it consistently at inference.
Question 1014
During an independent acceptance rehearsal of a customer-facing AI capability, 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 owners require measurable quality and controlled operating cost. Which outcome most directly demonstrates a successful, measurable fix?
- The scheduled report processes the full authorized partition and stores traceable predictions without a local export.
- An unseen labeled cohort receives probabilities for the intended positive class with a calibrated operating threshold.
- A controlled raw record yields the same transformed feature representation for evaluation and production SQL inference.
- A bilingual reviewer confirms meaning and formatting for representative descriptions without retraining a translation model.
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. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….
Incorrect Answers
A:The scheduled report processes the full authorized partition and stores traceable predictions without a local export. This result could demonstrate success for bigquery ml sql batch prediction integration 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:A controlled raw record yields the same transformed feature representation for evaluation and production SQL inference. This result could demonstrate success for bigquery ml transform serving parity but not for the stated bigquery ml 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: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 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 1015
Within a jointly maintained Google Cloud data science workspace, the following condition occurs: A prototype notebook commits a service-account JSON private key beside its feature code so colleagues can open Cloud Storage directly. Collaborators must avoid expanding data access or breaking experiment reproducibility. Which TWO complementary choices jointly establish the evidence and appropriate correction? Select TWO.
- Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project.
- Inspect saved artifact format, framework versions, device placement requirements and the model card's supported execution paths.
- Revoke and rotate the exposed key and use managed workload identity or approved short-lived credentials with least privilege.
- Build a constrained judge rubric with blind repeated comparisons and human-adjudicated calibration on representative examples.
- Push aggregations into BigQuery or stream bounded samples to the notebook rather than materializing the whole table.
Explanation
Correct Answers
A:Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project. This inspects evidence relevant to workbench credentials embedded in repository. Long-lived secrets copied into notebooks or Git can be reused outside intended workloads and must be rotated. After identifying the cause, the matching correction is: Revoke and rotate the exposed key and use managed workload identity or approved short-lived credentials with least privilege. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A prototype….
C:Revoke and rotate the exposed key and use managed workload identity or approved short-lived credentials with least privilege. This is the targeted corrective response for workbench credentials embedded in repository. Long-lived secrets copied into notebooks or Git can be reused outside intended workloads and must be rotated. Verify the diagnosis using: Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project. Confirm success using: The notebook can access allowed buckets without a stored private key and the old key no longer authenticates. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A prototype….
Incorrect Answers
B:Inspect saved artifact format, framework versions, device placement requirements and the model card's supported execution paths. This is an action or diagnostic relevant to model garden jax accelerator compatibility, not one of the required two steps. In this scenario verify: Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project. Then correct: Revoke and rotate the exposed key and use managed workload identity or approved short-lived credentials with least privilege.
D:Build a constrained judge rubric with blind repeated comparisons and human-adjudicated calibration on representative examples. This is an action or diagnostic relevant to llm-as-a-judge rubric reliability, not one of the required two steps. In this scenario verify: Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project. Then correct: Revoke and rotate the exposed key and use managed workload identity or approved short-lived credentials with least privilege.
E:Push aggregations into BigQuery or stream bounded samples to the notebook rather than materializing the whole table. This is an action or diagnostic relevant to notebook memory exhaustion on full data extraction, not one of the required two steps. In this scenario verify: Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project. Then correct: Revoke and rotate the exposed key and use managed workload identity or approved short-lived credentials with least privilege.
Question 1016
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A regulated loan approval team chooses a large neural network despite needing explanations for which borrower attributes affected decisions. Engineers need an auditable, resource-aware correction to the issue. Which outcome most directly demonstrates a successful, measurable fix?
- The chosen threshold detects clinically relevant positives while the false-alarm rate is documented for deployment review.
- Trials stay within the approved compute budget and a winner improves the specified independent metric.
- Auditors can reproduce feature influence evidence while holdout quality remains within the approved threshold.
- A batch of representative requests yields valid schema-conforming objects and rejects invalid types explicitly.
Explanation
Correct Answer
C:Auditors can reproduce feature influence evidence while holdout quality remains within the approved threshold. This is specific acceptance evidence for interpretability-constrained model baseline. Interpretability is an engineering requirement that must be considered with predictive power, not appended as a label. It confirms the controlled correction: Compare an interpretable model or validated feature attribution approach with the black box and document decision tradeoffs. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….
Incorrect Answers
A:The chosen threshold detects clinically relevant positives while the false-alarm rate is documented for deployment review. This result could demonstrate success for cost-sensitive threshold for rare positives but not for the stated interpretability-constrained model baseline issue. The direct test is: Auditors can reproduce feature influence evidence while holdout quality remains within the approved threshold.
B:Trials stay within the approved compute budget and a winner improves the specified independent metric. This result could demonstrate success for hyperparameter search budget limit but not for the stated interpretability-constrained model baseline issue. The direct test is: Auditors can reproduce feature influence evidence while holdout quality remains within the approved threshold.
D:A batch of representative requests yields valid schema-conforming objects and rejects invalid types explicitly. This result could demonstrate success for constrained generative json outputs but not for the stated interpretability-constrained model baseline issue. The direct test is: Auditors can reproduce feature influence evidence while holdout quality remains within the approved threshold.
Question 1017
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A training job remains pending for hours because its requested high-end GPU count exceeds project quota in the chosen region. Engineers need an auditable, resource-aware correction to the issue. What implementation change resolves the specific issue without substituting an unrelated fix?
- Use appropriately sharded data, parallel decode, caching or prefetching within memory limits to feed the accelerator.
- Request justified quota or select an available compatible accelerator and region without compromising data residency controls.
- Benchmark compatible TPU and GPU configurations and select hardware based on measured throughput and target budget.
- Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping.
Explanation
Correct Answer
B:Request justified quota or select an available compatible accelerator and region without compromising data residency controls. This is the targeted corrective response for accelerator quota and regional availability. Cloud accelerators have regional quota and stock limits distinct from an application's logical training configuration. Verify the diagnosis using: Inspect region-zone capacity, quota limits, accelerator requirements and scheduling error events. Confirm success using: The job schedules successfully with the approved hardware and remains inside budget and residency constraints. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….
Incorrect Answers
A:Use appropriately sharded data, parallel decode, caching or prefetching within memory limits to feed the accelerator. This action addresses accelerator starvation from slow input pipeline, not the failure in the described accelerator quota and regional availability case. The targeted correction is: Request justified quota or select an available compatible accelerator and region without compromising data residency controls.
C:Benchmark compatible TPU and GPU configurations and select hardware based on measured throughput and target budget. This action addresses tpu versus gpu for tensorflow workload, not the failure in the described accelerator quota and regional availability case. The targeted correction is: Request justified quota or select an available compatible accelerator and region without compromising data residency controls.
D:Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping. This action addresses hyperparameter search budget limit, not the failure in the described accelerator quota and regional availability case. The targeted correction is: Request justified quota or select an available compatible accelerator and region without compromising data residency controls.
Question 1018
During model-training validation on a Google Cloud experimental project, the following condition occurs: A team wants to tune an image-generation foundation model using scraped brand imagery without verifying usage rights or consent. The change should preserve a meaningful independent model-quality comparison. Which technical explanation best accounts for the reported behavior?
- Preemptible execution can end abruptly; local-only state is not a durable recovery mechanism.
- Fine-tuning technical feasibility does not confer rights to reuse restricted training images or ignore model safety.
- External reference updates need fresh context; changing foundation weights for every factual revision is inefficient.
- Distributed sampling can pad replicas; uncorrected metric aggregation may bias evaluation results.
Explanation
Correct Answer
B:Fine-tuning technical feasibility does not confer rights to reuse restricted training images or ignore model safety. This explains the mechanism behind fine-tuning image generator data rights and why the described failure is possible. A discriminating investigation is: Check dataset licenses, provenance, consent policies, safety requirements and the model's supported tuning route. The corresponding repair is: Use licensed and permitted training images with appropriate governance reviews before any supported tuning job. This matters here because during model-training validation on a Google Cloud experimental project, the following condition occurs: A team….
Incorrect Answers
A:Preemptible execution can end abruptly; local-only state is not a durable recovery mechanism. This principle describes training checkpoint persistence across interruptions, which is not the cause of the observed fine-tuning image generator data rights failure. The controlling explanation is: Fine-tuning technical feasibility does not confer rights to reuse restricted training images or ignore model safety.
C:External reference updates need fresh context; changing foundation weights for every factual revision is inefficient. This principle describes foundation model prompt versus fine-tuning, which is not the cause of the observed fine-tuning image generator data rights failure. The controlling explanation is: Fine-tuning technical feasibility does not confer rights to reuse restricted training images or ignore model safety.
D: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 fine-tuning image generator data rights failure. The controlling explanation is: Fine-tuning technical feasibility does not confer rights to reuse restricted training images or ignore model safety.
Question 1019
During an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A demand team needs a 21-day rolling forecast but creates a classification model on randomly shuffled dates and never defines the forecast horizon. The owners require measurable quality and controlled operating cost. Which configuration or procedure is the most appropriate correction?
- Evaluate Cloud Vision API for supported generic image detection and use custom training only for missing domain-specific classes.
- Evaluate Agent Platform AutoML tabular training against a simple baseline and select it if quality and operating cost justify the managed path.
- Use a suitable ARIMA_PLUS time-series model with timestamp and data columns and evaluate ML.FORECAST on rolling historical cutoffs.
- Use ML.PREDICT on the appropriate BigQuery ML model within a controlled SQL batch job, writing results to governed tables.
Explanation
Correct Answer
C:Use a suitable ARIMA_PLUS time-series model with timestamp and data columns and evaluate ML.FORECAST on rolling historical cutoffs. This is the targeted corrective response for bigquery arima_plus forecast horizon. Forecasting requires time-ordered histories and explicitly defined future steps, not shuffled categorical labels. Verify the diagnosis using: Inspect the timestamp ordering, seasonal patterns, horizon requirement, and the BigQuery ML model_type and time-series options. Confirm success using: Twenty-one future daily estimates are produced with reported prediction intervals and error is scored on forward dates. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….
Incorrect Answers
A:Evaluate Cloud Vision API for supported generic image detection and use custom training only for missing domain-specific classes. This action addresses vision api pretrained image labels versus custom detection, not the failure in the described bigquery arima_plus forecast horizon case. The targeted correction is: Use a suitable ARIMA_PLUS time-series model with timestamp and data columns and evaluate ML.FORECAST on rolling historical cutoffs. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….
B:Evaluate Agent Platform AutoML tabular training against a simple baseline and select it if quality and operating cost justify the managed path. This action addresses automl tabular supervised model selection, not the failure in the described bigquery arima_plus forecast horizon case. The targeted correction is: Use a suitable ARIMA_PLUS time-series model with timestamp and data columns and evaluate ML.FORECAST on rolling historical cutoffs.
D:Use ML.PREDICT on the appropriate BigQuery ML model within a controlled SQL batch job, writing results to governed tables. This action addresses bigquery ml sql batch prediction integration, not the failure in the described bigquery arima_plus forecast horizon case. The targeted correction is: Use a suitable ARIMA_PLUS time-series model with timestamp and data columns and evaluate ML.FORECAST on rolling historical cutoffs. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….
Question 1020
As the team tests a new governed AI release against adversarial and normal data, the following condition occurs: A product demand model raises a drift alert every weekend because the baseline ignores known weekly seasonality and monitoring thresholds are overly narrow. The fix must retain legitimate model usefulness and appropriate controls. Which outcome most directly demonstrates a successful, measurable fix?
- For controlled entities the online and offline features match at equivalent cutoffs and quality recovers.
- Expected weekend patterns no longer page operators while injected abnormal changes still alert.
- Test prompts preserve support utility without exposing real account identifiers to unauthorized model requests.
- Precision and recall recover on new labeled periods and monitoring distinguishes performance change from mere input shift.
Explanation
Correct Answer
B:Expected weekend patterns no longer page operators while injected abnormal changes still alert. This is specific acceptance evidence for model monitoring false-alert seasonality. Normal recurring seasonality can resemble drift against an unsegmented static baseline. It confirms the controlled correction: Adopt justified seasonal baselines or cohorts and tune alert thresholds without suppressing severe shifts. This matters here because as the team tests a new governed AI release against adversarial and normal data, the following condition occurs: A….
Incorrect Answers
A:For controlled entities the online and offline features match at equivalent cutoffs and quality recovers. This result could demonstrate success for training-serving feature skew detection but not for the stated model monitoring false-alert seasonality issue. The direct test is: Expected weekend patterns no longer page operators while injected abnormal changes still alert.
C:Test prompts preserve support utility without exposing real account identifiers to unauthorized model requests. This result could demonstrate success for sensitive identifiers leaked to llm prompts but not for the stated model monitoring false-alert seasonality issue. The direct test is: Expected weekend patterns no longer page operators while injected abnormal changes still alert.
D:Precision and recall recover on new labeled periods and monitoring distinguishes performance change from mere input shift. This result could demonstrate success for concept drift with stable feature statistics but not for the stated model monitoring false-alert seasonality issue. The direct test is: Expected weekend patterns no longer page operators while injected abnormal changes still alert.