Google Professional Machine Learning Engineer Practice Test 42
Question 410
Within a jointly maintained Google Cloud data science workspace, the following condition occurs: A team uses manual spreadsheet rows for hyperparameter results and loses connections between training metrics and produced checkpoint artifacts. Collaborators must avoid expanding data access or breaking experiment reproducibility. What acceptance result verifies the intended behavior after remediation?
- Candidate scores can be reproduced on the same held-out data and their differences are attributable to model changes.
- For every row the feature version predates its prediction cutoff and prospective holdout quality is realistic.
- A production model identifier resolves to its training execution, immutable artifacts, approvals and input dataset.
- Each candidate's reported metrics resolve to its actual artifact and replayable configuration without manual lookups.
Explanation
Correct Answer
D: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.
Incorrect Answers
A: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.
B:For every row the feature version predates its prediction cutoff and prospective holdout quality is realistic. This result could demonstrate success for point-in-time feature leakage prevention 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.
C: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.
Question 411
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. Which configuration or procedure is the most appropriate correction?
- Implement the required serving contract and make the container report readiness only after loading model assets.
- Pin releases to reviewed immutable image digests and record image plus model artifact versions.
- Promote an explicitly approved model version from Agent Platform Model Registry and record deployment lineage.
- Test a supported post-training quantization or optimization path and release only if target quality remains acceptable.
Explanation
Correct Answer
C:Promote an explicitly approved model version from Agent Platform Model Registry and record deployment lineage. This is the targeted corrective response for model registry version provenance. Mutable nicknames do not establish immutable model provenance for controlled production releases. Verify the diagnosis using: Review immutable artifact IDs, Model Registry versions, evaluation reports, approvals and deployed revision metadata. Confirm success using: The running endpoint resolves to a traceable evaluated package and cannot silently switch weights when an alias moves.
Incorrect Answers
A:Implement the required serving contract and make the container report readiness only after loading model assets. This action addresses inference container health interface mismatch, not the failure in the described model registry version provenance case. The targeted correction is: Promote an explicitly approved model version from Agent Platform Model Registry and record deployment lineage.
B:Pin releases to reviewed immutable image digests and record image plus model artifact versions. This action addresses model artifact image digest reproducibility, not the failure in the described model registry version provenance case. The targeted correction is: Promote an explicitly approved model version from Agent Platform Model Registry and record deployment lineage.
D: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 model registry version provenance case. The targeted correction is: Promote an explicitly approved model version from Agent Platform Model Registry and record deployment lineage.
Question 412
During a production ML inference release on Google Cloud, the following condition occurs: An industrial camera must classify frames while offline for hours, but its prototype requires every frame to reach a remote cloud endpoint. The service must meet its agreed quality and latency requirements. Which outcome most directly demonstrates a successful, measurable fix?
- The camera processes representative frames inside its latency budget during an intentional network outage.
- Identical release manifests resolve to identical image bytes across reproducible deployments.
- Repeated requests from the same test user stay on one variant and conversion comparisons preserve randomized balance.
- Authorized lookups return expected recent values and freshness alarms fire when synchronization falls behind.
Explanation
Correct Answer
A:The camera processes representative frames inside its latency budget during an intentional network outage. This is specific acceptance evidence for edge versus cloud inference network constraints. A cloud-only inference architecture cannot satisfy hard offline and low-latency edge requirements. It confirms the controlled correction: Deploy a verified edge-compatible model for required offline decisions and sync summarized results when connectivity returns.
Incorrect Answers
B:Identical release manifests resolve to identical image bytes across reproducible deployments. This result could demonstrate success for model artifact image digest reproducibility but not for the stated edge versus cloud inference network constraints issue. The direct test is: The camera processes representative frames inside its latency budget during an intentional network outage.
C: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 edge versus cloud inference network constraints issue. The direct test is: The camera processes representative frames inside its latency budget during an intentional network outage.
D:Authorized lookups return expected recent values and freshness alarms fire when synchronization falls behind. This result could demonstrate success for feature store freshness and online sync but not for the stated edge versus cloud inference network constraints issue. The direct test is: The camera processes representative frames inside its latency budget during an intentional network outage.
Question 413
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: An LLM occasionally emits natural-language introductions before an API-required JSON object, causing strict parsers to reject otherwise correct answers. Engineers need an auditable, resource-aware correction to the issue. What should the engineer inspect before selecting a correction?
- Inspect prevalence, confusion matrix, false-negative harm, calibration and precision-recall curves at candidate thresholds.
- Inspect task requirements for retrieval ranking, available query-document pairs, embedding similarity and labeled relevance examples.
- Inspect model framework, accelerator kernel support, batch sizes, input pipeline speed and per-step cost.
- Inspect output schema, decoding configuration, structured-output support and malformed samples under representative prompts.
Explanation
Correct Answer
D:Inspect output schema, decoding configuration, structured-output support and malformed samples under representative prompts. This inspects evidence relevant to constrained generative json outputs. Prompt-only requests for JSON may not guarantee type validity; interface contracts need machine-verifiable constraints. After identifying the cause, the matching correction is: Use supported structured output and schema validation with graceful retry or rejection for nonconforming responses.
Incorrect Answers
A:Inspect prevalence, confusion matrix, false-negative harm, calibration and precision-recall curves at candidate thresholds. This examines cost-sensitive threshold for rare positives rather than the specific mechanism reported here. It is not the decisive first check for constrained generative json outputs. The relevant evidence is: Inspect output schema, decoding configuration, structured-output support and malformed samples under representative prompts.
B:Inspect task requirements for retrieval ranking, available query-document pairs, embedding similarity and labeled relevance examples. This examines embedding retrieval versus text classifier rather than the specific mechanism reported here. It is not the decisive first check for constrained generative json outputs. The relevant evidence is: Inspect output schema, decoding configuration, structured-output support and malformed samples under representative prompts.
C:Inspect model framework, accelerator kernel support, batch sizes, input pipeline speed and per-step cost. This examines tpu versus gpu for tensorflow workload rather than the specific mechanism reported here. It is not the decisive first check for constrained generative json outputs. The relevant evidence is: Inspect output schema, decoding configuration, structured-output support and malformed samples under representative prompts.
Question 414
During a postdeployment AI safety and reliability review, the following condition occurs: A service account running an AI workload can read all analytics datasets and copy confidential training data to an unrelated storage bucket. The model owner must provide repeatable evidence rather than a cosmetic dashboard change. Which diagnostic check should be performed FIRST to isolate the described cause?
- Inspect subgroup confusion matrices, sample sizes, training representation and evaluation slices over time.
- Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers.
- Inspect input logs, sensitivity classifications, prompt assembly and approved data-processing boundaries.
- Review prompt token counts, output length, cache behavior, p95 model latency and cost per successful task.
Explanation
Correct Answer
B:Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers. This inspects evidence relevant to training data exfiltration through broad access. Least-privilege access and destination controls reduce unauthorized model-data disclosure risk. After identifying the cause, the matching correction is: Restrict dataset and bucket access by principal and resource; enforce approved egress controls and audit sensitive reads. This matters here because a service account running an AI workload can read all analytics datasets and copy confidential training data to an….
Incorrect Answers
A:Inspect subgroup confusion matrices, sample sizes, training representation and evaluation slices over time. This examines model feature bias by subgroup rather than the specific mechanism reported here. It is not the decisive first check for training data exfiltration through broad access. The relevant evidence is: Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers. This matters here because a service account running an AI workload can read all analytics datasets and copy confidential training data to an….
C:Inspect input logs, sensitivity classifications, prompt assembly and approved data-processing boundaries. This examines sensitive identifiers leaked to llm prompts rather than the specific mechanism reported here. It is not the decisive first check for training data exfiltration through broad access. The relevant evidence is: Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers.
D:Review prompt token counts, output length, cache behavior, p95 model latency and cost per successful task. This examines llm latency and cost token regression rather than the specific mechanism reported here. It is not the decisive first check for training data exfiltration through broad access. The relevant evidence is: Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers.
Question 415
During an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A reporting team exports millions of BigQuery rows to a laptop for daily scoring although a trained BigQuery ML model already exists in the dataset. The owners require measurable quality and controlled operating cost. Which diagnostic check should be performed FIRST to isolate the described cause?
- Inspect requested labels or bounding boxes, sample image quality, supported Vision API capabilities and required detection thresholds.
- Inspect label availability, feature types, tuning needs, governance requirements, and supported AutoML model interfaces.
- Inspect the training preprocessing SQL, TRANSFORM clause, model input schema, and the inference query's feature values.
- Review row volume, model location, permissions and the current SQL report dependency on the local scoring script.
Explanation
Correct Answer
D:Review row volume, model location, permissions and the current SQL report dependency on the local scoring script. This inspects evidence relevant to bigquery ml sql batch prediction integration. In-database prediction avoids unnecessary bulk data transfer when model and features are already in BigQuery. After identifying the cause, the matching correction is: Use ML.PREDICT on the appropriate BigQuery ML model within a controlled SQL batch job, writing results to governed tables. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….
Incorrect Answers
A:Inspect requested labels or bounding boxes, sample image quality, supported Vision API capabilities and required detection thresholds. This examines vision api pretrained image labels versus custom detection rather than the specific mechanism reported here. It is not the decisive first check for bigquery ml sql batch prediction integration. The relevant evidence is: Review row volume, model location, permissions and the current SQL report dependency on the local scoring script.
B:Inspect label availability, feature types, tuning needs, governance requirements, and supported AutoML model interfaces. This examines automl tabular supervised model selection rather than the specific mechanism reported here. It is not the decisive first check for bigquery ml sql batch prediction integration. The relevant evidence is: Review row volume, model location, permissions and the current SQL report dependency on the local scoring script.
C:Inspect the training preprocessing SQL, TRANSFORM clause, model input schema, and the inference query's feature values. This examines bigquery ml transform serving parity rather than the specific mechanism reported here. It is not the decisive first check for bigquery ml sql batch prediction integration. The relevant evidence is: Review row volume, model location, permissions and the current SQL report dependency on the local scoring script. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: A….
Question 416
During a production ML inference release on Google Cloud, the following condition occurs: A marketing model scores ten million customers every midnight, but engineers keep a low-latency online endpoint running continuously for the once-daily batch. The service must meet its agreed quality and latency requirements. Which outcome most directly demonstrates a successful, measurable fix?
- The approved integration continues to work while unrelated accounts receive permission denied on inference calls.
- The nightly job completes within the agreed SLA without idle real-time serving charges.
- Identical release manifests resolve to identical image bytes across reproducible deployments.
- Every controlled sample's returned label matches the model's trained class index with no misordered classes.
Explanation
Correct Answer
B:The nightly job completes within the agreed SLA without idle real-time serving charges. This is specific acceptance evidence for batch versus online inference schedule. Batch workloads need throughput and scheduling guarantees, whereas real-time endpoints serve interactive low-latency calls. It confirms the controlled correction: Choose a managed batch inference or scheduled container batch workflow instead of an always-on online endpoint. This matters here because a marketing model scores ten million customers every midnight, but engineers keep a low-latency online endpoint….
Incorrect Answers
A:The approved integration continues to work while unrelated accounts receive permission denied on inference calls. This result could demonstrate success for public endpoint iam oversharing but not for the stated batch versus online inference schedule issue. The direct test is: The nightly job completes within the agreed SLA without idle real-time serving charges.
C:Identical release manifests resolve to identical image bytes across reproducible deployments. This result could demonstrate success for model artifact image digest reproducibility but not for the stated batch versus online inference schedule issue. The direct test is: The nightly job completes within the agreed SLA without idle real-time serving charges.
D:Every controlled sample's returned label matches the model's trained class index with no misordered classes. This result could demonstrate success for custom postprocessing label mapping drift but not for the stated batch versus online inference schedule issue. The direct test is: The nightly job completes within the agreed SLA without idle real-time serving charges.
Question 417
Within a jointly maintained Google Cloud data science workspace, the following condition occurs: A streaming feature pipeline aggregates transactions by processing arrival time, causing delayed events to land in the wrong customer-hour bucket. Collaborators must avoid expanding data access or breaking experiment reproducibility. Which evidence most directly establishes what is wrong with this AI or ML workflow?
- Compare source event timestamps, processing timestamps, watermark settings, allowed lateness and actual window outputs from a replay.
- Inspect join-key frequency distributions, per-task runtime, shuffle spill and the output cardinality before optimization.
- Inspect saved artifact format, framework versions, device placement requirements and the model card's supported execution paths.
- Compare entity IDs, key types, online feature-view definitions, offline joins and records for the same verified customer.
Explanation
Correct Answer
A:Compare source event timestamps, processing timestamps, watermark settings, allowed lateness and actual window outputs from a replay. This inspects evidence relevant to dataflow event-time window correctness. Arrival time and event time are different; event-time windows with lateness rules preserve business-time meaning. After identifying the cause, the matching correction is: Configure event-time windowing with an appropriate watermark and explicit late-data correction policy in the Dataflow pipeline.
Incorrect Answers
B: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 dataflow event-time window correctness. The relevant evidence is: Compare source event timestamps, processing timestamps, watermark settings, allowed lateness and actual window outputs from a replay.
C:Inspect saved artifact format, framework versions, device placement requirements and the model card's supported execution paths. This examines model garden jax accelerator compatibility rather than the specific mechanism reported here. It is not the decisive first check for dataflow event-time window correctness. The relevant evidence is: Compare source event timestamps, processing timestamps, watermark settings, allowed lateness and actual window outputs from a replay.
D:Compare entity IDs, key types, online feature-view definitions, offline joins and records for the same verified customer. This examines feature store online and offline entity alignment rather than the specific mechanism reported here. It is not the decisive first check for dataflow event-time window correctness. The relevant evidence is: Compare source event timestamps, processing timestamps, watermark settings, allowed lateness and actual window outputs from a replay.
Question 418
During a controlled replay of the data and model handoff to a second engineering team, 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. The handoff must preserve privacy, lineage and testable behavior. Which TWO selections represent the correct investigation and remediation together? Select TWO.
- Log reproducibility settings and rerun comparable trials with fixed split and controlled randomness before attributing changes.
- Examine source locations, batch cadence, SQL transform complexity, streaming latency requirements and operational burden.
- Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts.
- Implement the batch aggregate in scheduled BigQuery SQL when the required transformation is expressible and fits its SLA.
- Inspect the labeling payload schema, data classification, annotator roles and fields needed to complete the labeling task.
Explanation
Correct Answers
B: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 during a controlled replay of the data and model handoff to a second engineering team, the following condition….
D:Implement the batch aggregate in scheduled BigQuery SQL when the required transformation is expressible and fits its SLA. This is the targeted corrective response for bigquery versus dataflow preparation selection. Choosing a managed SQL engine for warehouse-resident batch joins avoids unnecessary always-on stream processing. Verify the diagnosis using: Examine source locations, batch cadence, SQL transform complexity, streaming latency requirements and operational burden. Confirm success using: The scheduled query produces equivalent daily features with less service orchestration and within the run window. This matters here because during a controlled replay of the data and model handoff to a second engineering team, the following condition….
Incorrect Answers
A:Log reproducibility settings and rerun comparable trials with fixed split and controlled randomness before attributing changes. This is an action or diagnostic relevant to experiment random seed and data order variance, not one of the required two steps. In this scenario verify: Examine source locations, batch cadence, SQL transform complexity, streaming latency requirements and operational burden. Then correct: Implement the batch aggregate in scheduled BigQuery SQL when the required transformation is expressible and fits its SLA.
C:Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts. This is an action or diagnostic relevant to managed spark join-key skew repair, not one of the required two steps. In this scenario verify: Examine source locations, batch cadence, SQL transform complexity, streaming latency requirements and operational burden. Then correct: Implement the batch aggregate in scheduled BigQuery SQL when the required transformation is expressible and fits its SLA.
E:Inspect the labeling payload schema, data classification, annotator roles and fields needed to complete the labeling task. This is an action or diagnostic relevant to data minimization for labeling inputs, not one of the required two steps. In this scenario verify: Examine source locations, batch cadence, SQL transform complexity, streaming latency requirements and operational burden. Then correct: Implement the batch aggregate in scheduled BigQuery SQL when the required transformation is expressible and fits its SLA.
Question 419
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A pretrained multilingual text model loses common-language understanding after engineers fine-tune every layer at an aggressive learning rate on a tiny legal dataset. Engineers need an auditable, resource-aware correction to the issue. What acceptance result verifies the intended behavior after remediation?
- The job completes representative epochs without OOM and convergence remains within the approved tolerance.
- A controlled interruption resumes near the saved step without restarting training from zero.
- A batch of representative requests yields valid schema-conforming objects and rejects invalid types explicitly.
- Domain accuracy improves while broad language capability remains within the agreed retention threshold.
Explanation
Correct Answer
D:Domain accuracy improves while broad language capability remains within the agreed retention threshold. This is specific acceptance evidence for fine-tuning catastrophic forgetting. Large unconstrained parameter updates on small data can overwrite useful pretrained representations. It confirms the controlled correction: Reduce the learning rate and use justified parameter-efficient tuning or partial freezing with a controlled evaluation set.
Incorrect Answers
A:The job completes representative epochs without OOM and convergence remains within the approved tolerance. This result could demonstrate success for gpu out-of-memory batch control but not for the stated fine-tuning catastrophic forgetting issue. The direct test is: Domain accuracy improves while broad language capability remains within the agreed retention threshold.
B:A controlled interruption resumes near the saved step without restarting training from zero. This result could demonstrate success for training checkpoint persistence across interruptions but not for the stated fine-tuning catastrophic forgetting issue. The direct test is: Domain accuracy improves while broad language capability remains within the agreed retention threshold.
C: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 fine-tuning catastrophic forgetting issue. The direct test is: Domain accuracy improves while broad language capability remains within the agreed retention threshold.
Question 420
During a staged restoration test at a secondary serving deployment, the following condition occurs: A multi-class model returns numeric class indices, but an API gateway uses a stale alphabetical mapping and mislabels predictions. The team must prove an actual user-visible improvement without weakening access controls. Which result is the strongest postchange evidence of success?
- Identical sample text yields matching token IDs and model outputs in offline and online environments.
- Identical release manifests resolve to identical image bytes across reproducible deployments.
- Every controlled sample's returned label matches the model's trained class index with no misordered classes.
- Previously missed customer IDs retrieve the intended feature values without collapsing distinct leading-zero identifiers.
Explanation
Correct Answer
C:Every controlled sample's returned label matches the model's trained class index with no misordered classes. This is specific acceptance evidence for custom postprocessing label mapping drift. Index ordering is part of the model contract; separate stale label dictionaries can silently corrupt inference. It confirms the controlled correction: Ship the class vocabulary with the model artifact and version or validate the output adapter against it.
Incorrect Answers
A:Identical sample text yields matching token IDs and model outputs in offline and online environments. This result could demonstrate success for inference preprocessing tokenization mismatch but not for the stated custom postprocessing label mapping drift issue. The direct test is: Every controlled sample's returned label matches the model's trained class index with no misordered classes.
B:Identical release manifests resolve to identical image bytes across reproducible deployments. This result could demonstrate success for model artifact image digest reproducibility but not for the stated custom postprocessing label mapping drift issue. The direct test is: Every controlled sample's returned label matches the model's trained class index with no misordered classes.
D: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 custom postprocessing label mapping drift issue. The direct test is: Every controlled sample's returned label matches the model's trained class index with no misordered classes.