Google Professional Machine Learning Engineer Practice Test 111
Question 1100
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A GPU training job reports 10% utilization while CPU workers spend most time decoding tiny images from scattered Cloud Storage objects. Engineers need an auditable, resource-aware correction to the issue. Which result is the strongest postchange evidence of success?
- The chosen accelerator meets throughput and convergence expectations without unsupported operations or unstable retracing.
- The model fits and trains across devices with controlled synchronization overhead and reproducible checkpoints.
- A controlled interruption resumes near the saved step without restarting training from zero.
- GPU utilization and examples per second rise without changing model accuracy or violating data-order requirements.
Explanation
Correct Answer
D:GPU utilization and examples per second rise without changing model accuracy or violating data-order requirements. This is specific acceptance evidence for accelerator starvation from slow input pipeline. An accelerator can sit idle waiting for input even when its own memory and compute capacity are sufficient. It confirms the controlled correction: Use appropriately sharded data, parallel decode, caching or prefetching within memory limits to feed the accelerator. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….
Incorrect Answers
A:The chosen accelerator meets throughput and convergence expectations without unsupported operations or unstable retracing. This result could demonstrate success for tpu versus gpu for tensorflow workload but not for the stated accelerator starvation from slow input pipeline issue. The direct test is: GPU utilization and examples per second rise without changing model accuracy or violating data-order requirements. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….
B:The model fits and trains across devices with controlled synchronization overhead and reproducible checkpoints. This result could demonstrate success for model parallelism for memory-bound transformer but not for the stated accelerator starvation from slow input pipeline issue. The direct test is: GPU utilization and examples per second rise without changing model accuracy or violating data-order requirements.
C: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 accelerator starvation from slow input pipeline issue. The direct test is: GPU utilization and examples per second rise without changing model accuracy or violating data-order requirements.
Question 1101
During model-training validation on a Google Cloud experimental project, 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. The change should preserve a meaningful independent model-quality comparison. Which evidence most directly establishes what is wrong with this AI or ML workflow?
- Inspect task requirements for retrieval ranking, available query-document pairs, embedding similarity and labeled relevance examples.
- Inspect gradient ranges, loss-scaling logs, overflow events and the affected operations with test batches.
- Inspect feature modality, example counts, training cost, validation scores and latency requirements.
- 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. This matters here because during model-training validation on a Google Cloud experimental project, the following condition occurs: An LLM….
Incorrect Answers
A: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. This matters here because during model-training validation on a Google Cloud experimental project, the following condition occurs: An LLM….
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 constrained generative json outputs. The relevant evidence is: Inspect output schema, decoding configuration, structured-output support and malformed samples under representative prompts.
C: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 constrained generative json outputs. The relevant evidence is: Inspect output schema, decoding configuration, structured-output support and malformed samples under representative prompts.
Question 1102
During an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: An accounts-payable team needs supplier names, invoice totals and line items but uses image classification to decide whether an invoice is present. The owners require measurable quality and controlled operating cost. Which configuration or procedure is the most appropriate correction?
- Select a permitted task-compatible Gemini or other supported foundation model and benchmark it against simpler candidates.
- Use a BigQuery ML LINEAR_REG or suitable regression model with a numeric target and evaluate continuous-error metrics on held-out records.
- Retrieve only relevant passages with provenance and use a concise structured prompt with measured token limits.
- Use an appropriate Document AI processor for form or invoice extraction and validate required fields before downstream posting.
Explanation
Correct Answer
D:Use an appropriate Document AI processor for form or invoice extraction and validate required fields before downstream posting. This is the targeted corrective response for document ai structured invoice extraction. Object or image classification only identifies image categories; document understanding targets structured text fields. Verify the diagnosis using: Inspect representative invoices, desired structured fields, supported processor output and field-level extraction errors. Confirm success using: A held-out invoice batch produces correct structured fields with measurable per-field precision and reject handling. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: An….
Incorrect Answers
A:Select a permitted task-compatible Gemini or other supported foundation model and benchmark it against simpler candidates. This action addresses model garden task and license selection, not the failure in the described document ai structured invoice extraction case. The targeted correction is: Use an appropriate Document AI processor for form or invoice extraction and validate required fields before downstream posting. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: An….
B:Use a BigQuery ML LINEAR_REG or suitable regression model with a numeric target and evaluate continuous-error metrics on held-out records. This action addresses bigquery ml linear regression for continuous value, not the failure in the described document ai structured invoice extraction case. The targeted correction is: Use an appropriate Document AI processor for form or invoice extraction and validate required fields before downstream posting.
C:Retrieve only relevant passages with provenance and use a concise structured prompt with measured token limits. This action addresses gemini prompt context token budget, not the failure in the described document ai structured invoice extraction case. The targeted correction is: Use an appropriate Document AI processor for form or invoice extraction and validate required fields before downstream posting.
Question 1103
During model-training validation on a Google Cloud experimental project, the following condition occurs: A customer-service model correctly follows general instructions but lacks newly updated internal warranty details, so developers schedule daily weight fine-tuning. The change should preserve a meaningful independent model-quality comparison. Which technical explanation best accounts for the reported behavior?
- Structured tabular datasets often have competitive simple baselines; architectural complexity is not inherently better.
- Structured numeric forecasting relies on temporal evidence; a conversational model is not automatically the best forecaster.
- Distributed sampling can pad replicas; uncorrected metric aggregation may bias evaluation results.
- External reference updates need fresh context; changing foundation weights for every factual revision is inefficient.
Explanation
Correct Answer
D:External reference updates need fresh context; changing foundation weights for every factual revision is inefficient. This explains the mechanism behind foundation model prompt versus fine-tuning and why the described failure is possible. A discriminating investigation is: Determine whether failures arise from changing reference knowledge, stable behavior patterns or inadequate retrieval coverage. The corresponding repair is: Use grounded retrieval for frequently changing policy facts and reserve fine-tuning for measured durable behavior adaptation. This matters here because during model-training validation on a Google Cloud experimental project, the following condition occurs: A….
Incorrect Answers
A:Structured tabular datasets often have competitive simple baselines; architectural complexity is not inherently better. This principle describes deep model versus gradient boosted trees on tabular, which is not the cause of the observed foundation model prompt versus fine-tuning failure. The controlling explanation is: External reference updates need fresh context; changing foundation weights for every factual revision is inefficient. This matters here because during model-training validation on a Google Cloud experimental project, the following condition occurs: A….
B:Structured numeric forecasting relies on temporal evidence; a conversational model is not automatically the best forecaster. This principle describes forecast trend and seasonality versus llm, which is not the cause of the observed foundation model prompt versus fine-tuning failure. The controlling explanation is: External reference updates need fresh context; changing foundation weights for every factual revision is inefficient.
C: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 foundation model prompt versus fine-tuning failure. The controlling explanation is: External reference updates need fresh context; changing foundation weights for every factual revision is inefficient.
Question 1104
During a production ML inference release on Google Cloud, the following condition occurs: A PyTorch model container builds successfully but the serving platform marks its deployed revision unhealthy due to a missing health-check route and incorrect listener port. The service must meet its agreed quality and latency requirements. What implementation change resolves the specific issue without substituting an unrelated fix?
- Package and version the exact trained preprocessing pipeline with the served model and run equivalence tests.
- Enable compatible dynamic batching with a bounded wait time and benchmark throughput against p95 latency.
- Use asynchronous or batch processing with durable job status for oversized workloads, reserving online calls for bounded requests.
- Implement the required serving contract and make the container report readiness only after loading model assets.
Explanation
Correct Answer
D:Implement the required serving contract and make the container report readiness only after loading model assets. This is the targeted corrective response for inference container health interface mismatch. A valid container image is not necessarily compatible with an inference service's HTTP startup and health contract. Verify the diagnosis using: Inspect startup logs, HTTP listening port, health-check expectations and request and response schema. Confirm success using: A known prediction request succeeds through the deployed endpoint and readiness reflects successful initialization. This matters here because a PyTorch model container builds successfully but the serving platform marks its deployed revision unhealthy due to….
Incorrect Answers
A:Package and version the exact trained preprocessing pipeline with the served model and run equivalence tests. This action addresses inference preprocessing tokenization mismatch, not the failure in the described inference container health interface mismatch case. The targeted correction is: Implement the required serving contract and make the container report readiness only after loading model assets. This matters here because a PyTorch model container builds successfully but the serving platform marks its deployed revision unhealthy due to….
B:Enable compatible dynamic batching with a bounded wait time and benchmark throughput against p95 latency. This action addresses dynamic batch serving for gpu saturation, not the failure in the described inference container health interface mismatch case. The targeted correction is: Implement the required serving contract and make the container report readiness only after loading model assets.
C:Use asynchronous or batch processing with durable job status for oversized workloads, reserving online calls for bounded requests. This action addresses online prediction timeout and batch fallback, not the failure in the described inference container health interface mismatch case. The targeted correction is: Implement the required serving contract and make the container report readiness only after loading model assets.
Question 1105
Within a jointly maintained Google Cloud data science workspace, the following condition occurs: A distributed preprocessing job joins two huge feature tables, but one NULL-like customer category contains most rows and one reducer becomes the bottleneck. Collaborators must avoid expanding data access or breaking experiment reproducibility. Which TWO complementary choices jointly establish the evidence and appropriate correction? Select TWO.
- Pin compatible dependency versions in a reproducible environment specification and validate fresh builds on clean runtimes.
- Implement the batch aggregate in scheduled BigQuery SQL when the required transformation is expressible and fits its SLA.
- Inspect feature event timestamps, prediction cutoffs, feature joins and any post-cancellation administrative flags.
- Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts.
- Inspect join-key frequency distributions, per-task runtime, shuffle spill and the output cardinality before optimization.
Explanation
Correct Answers
D:Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts. This is the targeted corrective response for managed spark join-key skew repair. Skew concentrates otherwise distributed work on a single hot key, which extra workers alone may not resolve. Verify the diagnosis using: Inspect join-key frequency distributions, per-task runtime, shuffle spill and the output cardinality before optimization. Confirm success using: Long-tail shuffle tasks shorten and the normalized output row count matches a reference implementation. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A distributed….
E:Inspect join-key frequency distributions, per-task runtime, shuffle spill and the output cardinality before optimization. This inspects evidence relevant to managed spark join-key skew repair. Skew concentrates otherwise distributed work on a single hot key, which extra workers alone may not resolve. After identifying the cause, the matching correction is: Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A distributed….
Incorrect Answers
A:Pin compatible dependency versions in a reproducible environment specification and validate fresh builds on clean runtimes. This is an action or diagnostic relevant to notebook dependency lock reproducibility, not one of the required two steps. In this scenario verify: Inspect join-key frequency distributions, per-task runtime, shuffle spill and the output cardinality before optimization. Then correct: Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts.
B:Implement the batch aggregate in scheduled BigQuery SQL when the required transformation is expressible and fits its SLA. This is an action or diagnostic relevant to bigquery versus dataflow preparation selection, not one of the required two steps. In this scenario verify: Inspect join-key frequency distributions, per-task runtime, shuffle spill and the output cardinality before optimization. Then correct: Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts.
C:Inspect feature event timestamps, prediction cutoffs, feature joins and any post-cancellation administrative flags. This is an action or diagnostic relevant to point-in-time feature leakage prevention, not one of the required two steps. In this scenario verify: Inspect join-key frequency distributions, per-task runtime, shuffle spill and the output cardinality before optimization. Then correct: Handle the dominant key separately or repartition and salt the skewed join while validating join semantics and counts.
Question 1106
During model-training validation on a Google Cloud experimental project, the following condition occurs: A retailer asks for next-week order value as a dollar amount, but the prototype returns yes/no purchase classes without estimated magnitude. The change should preserve a meaningful independent model-quality comparison. Which statement identifies the primary reason for this failure?
- Interpretability is an engineering requirement that must be considered with predictive power, not appended as a label.
- Categorical classification is not an estimator of an unrestricted continuous order value.
- Prompt-only requests for JSON may not guarantee type validity; interface contracts need machine-verifiable constraints.
- Notebook filesystem locations are not portable contracts for managed container training jobs.
Explanation
Correct Answer
B:Categorical classification is not an estimator of an unrestricted continuous order value. This explains the mechanism behind regression versus classification product choice and why the described failure is possible. A discriminating investigation is: Inspect required output type, business loss, sample labels, and the configured model objective and metric. The corresponding repair is: Select a regression architecture and matching numeric loss rather than using a binary classifier for amounts.
Incorrect Answers
A:Interpretability is an engineering requirement that must be considered with predictive power, not appended as a label. This principle describes interpretability-constrained model baseline, which is not the cause of the observed regression versus classification product choice failure. The controlling explanation is: Categorical classification is not an estimator of an unrestricted continuous order value.
C:Prompt-only requests for JSON may not guarantee type validity; interface contracts need machine-verifiable constraints. This principle describes constrained generative json outputs, which is not the cause of the observed regression versus classification product choice failure. The controlling explanation is: Categorical classification is not an estimator of an unrestricted continuous order value.
D:Notebook filesystem locations are not portable contracts for managed container training jobs. This principle describes custom training input schema mismatch, which is not the cause of the observed regression versus classification product choice failure. The controlling explanation is: Categorical classification is not an estimator of an unrestricted continuous order value.
Question 1107
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 targeted engineering change most directly addresses the failure?
- Deploy a verified edge-compatible model for required offline decisions and sync summarized results when connectivity returns.
- Configure the supported private DNS, network route and endpoint access path without granting public ingress.
- Promote an explicitly approved model version from Agent Platform Model Registry and record deployment lineage.
- Roll out a small canary percentage first, monitor error and quality guardrails and expand only after acceptance.
Explanation
Correct Answer
A:Deploy a verified edge-compatible model for required offline decisions and sync summarized results when connectivity returns. This is the targeted corrective response for edge versus cloud inference network constraints. A cloud-only inference architecture cannot satisfy hard offline and low-latency edge requirements. Verify the diagnosis using: Measure bandwidth, network availability, latency deadline, edge hardware limits and model compression compatibility. Confirm success using: The camera processes representative frames inside its latency budget during an intentional network outage. This matters here because an industrial camera must classify frames while offline for hours, but its prototype requires every frame to reach a….
Incorrect Answers
B:Configure the supported private DNS, network route and endpoint access path without granting public ingress. This action addresses private vpc routing failure for serving, not the failure in the described edge versus cloud inference network constraints case. The targeted correction is: Deploy a verified edge-compatible model for required offline decisions and sync summarized results when connectivity returns.
C:Promote an explicitly approved model version from Agent Platform Model Registry and record deployment lineage. This action addresses model registry version provenance, not the failure in the described edge versus cloud inference network constraints case. The targeted correction is: Deploy a verified edge-compatible model for required offline decisions and sync summarized results when connectivity returns. This matters here because an industrial camera must classify frames while offline for hours, but its prototype requires every frame to reach a….
D:Roll out a small canary percentage first, monitor error and quality guardrails and expand only after acceptance. This action addresses canary gradual traffic rollout, not the failure in the described edge versus cloud inference network constraints case. The targeted correction is: Deploy a verified edge-compatible model for required offline decisions and sync summarized results when connectivity returns.
Question 1108
As the team tests a new governed AI release against adversarial and normal data, the following condition occurs: An assistant summarizes third-party documents and malicious attachments can contain hidden exfiltration instructions, with no content screening before model invocation. The fix must retain legitimate model usefulness and appropriate controls. Which configuration or procedure is the most appropriate correction?
- Add groundedness and factual correctness checks to a representative gen AI evaluation suite and tune retrieval or prompting accordingly.
- Investigate attribution drift, remove invalid proxy features if warranted and retrain with appropriate validation.
- Add appropriate Model Armor screening to untrusted inputs and outputs and reject or quarantine policy-violating content.
- Evaluate and address documented subgroup disparities using appropriate fairness metrics and approved data/model changes.
Explanation
Correct Answer
C:Add appropriate Model Armor screening to untrusted inputs and outputs and reject or quarantine policy-violating content. This is the targeted corrective response for model armor untrusted content screening. Screening helps detect malicious instructions or sensitive content crossing the model trust boundary. Verify the diagnosis using: Inspect attachment ingestion, trust boundaries, malicious prompt examples and deployed Model Armor filter results. Confirm success using: A controlled prompt-injection fixture is blocked or neutralized without disrupting ordinary allowed documents. This matters here because as the team tests a new governed AI release against adversarial and normal data, the following condition occurs: An….
Incorrect Answers
A:Add groundedness and factual correctness checks to a representative gen AI evaluation suite and tune retrieval or prompting accordingly. This action addresses generative ai factual grounding evaluation, not the failure in the described model armor untrusted content screening case. The targeted correction is: Add appropriate Model Armor screening to untrusted inputs and outputs and reject or quarantine policy-violating content.
B:Investigate attribution drift, remove invalid proxy features if warranted and retrain with appropriate validation. This action addresses feature attribution drift after deployment, not the failure in the described model armor untrusted content screening case. The targeted correction is: Add appropriate Model Armor screening to untrusted inputs and outputs and reject or quarantine policy-violating content.
D:Evaluate and address documented subgroup disparities using appropriate fairness metrics and approved data/model changes. This action addresses model feature bias by subgroup, not the failure in the described model armor untrusted content screening case. The targeted correction is: Add appropriate Model Armor screening to untrusted inputs and outputs and reject or quarantine policy-violating content.
Question 1109
During an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: An international retailer manually sends each product description to an English-only classifier although the business first needs translated content in several supported languages. The owners require measurable quality and controlled operating cost. Which diagnostic check should be performed FIRST to isolate the described cause?
- Inspect representative invoices, desired structured fields, supported processor output and field-level extraction errors.
- Inspect source languages, target locale requirements, formatting preservation and translation quality on a multilingual sample.
- Inspect whether errors come from changing factual reference documents or from stable task/style behavior, and examine retrieval accuracy.
- Inspect the target column type, business loss metric, and sample prediction schema alongside model_type in the BigQuery model metadata.
Explanation
Correct Answer
B:Inspect source languages, target locale requirements, formatting preservation and translation quality on a multilingual sample. This inspects evidence relevant to translate api for multilingual product descriptions. Translation and classification are different tasks; an industry language API directly addresses supported cross-language conversion. After identifying the cause, the matching correction is: Use Cloud Translation API for supported text translation, then separately validate downstream classification against localized content. This matters here because during an independent acceptance rehearsal of a customer-facing AI capability, the following condition occurs: An….
Incorrect Answers
A:Inspect representative invoices, desired structured fields, supported processor output and field-level extraction errors. This examines document ai structured invoice extraction rather than the specific mechanism reported here. It is not the decisive first check for translate api for multilingual product descriptions. The relevant evidence is: Inspect source languages, target locale requirements, formatting preservation and translation quality on a multilingual sample.
C:Inspect whether errors come from changing factual reference documents or from stable task/style behavior, and examine retrieval accuracy. This examines foundation model tuning versus retrieval update rather than the specific mechanism reported here. It is not the decisive first check for translate api for multilingual product descriptions. The relevant evidence is: Inspect source languages, target locale requirements, formatting preservation and translation quality on a multilingual sample.
D:Inspect the target column type, business loss metric, and sample prediction schema alongside model_type in the BigQuery model metadata. This examines bigquery ml linear regression for continuous value rather than the specific mechanism reported here. It is not the decisive first check for translate api for multilingual product descriptions. The relevant evidence is: Inspect source languages, target locale requirements, formatting preservation and translation quality on a multilingual sample.
Question 1110
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 targeted engineering change most directly addresses the failure?
- Minimize or tokenize personal fields before generation and enforce access and retention controls on any necessary context.
- Capture immutable prediction identifiers and join verified outcome records to the corresponding earlier inference request.
- Monitor outcome-based quality metrics on matured cohorts and retrain when verified concept drift is significant.
- Version a single feature contract and add automated parity tests to the preprocessing pipeline and serving workflow.
Explanation
Correct Answer
D:Version a single feature contract and add automated parity tests to the preprocessing pipeline and serving workflow. This is the targeted corrective response for training-serving feature skew detection. Identical feature names do not guarantee identical semantics; mismatched windows create training-serving skew. Verify the diagnosis using: Compare live and offline feature SQL, window definitions, sample entity values and prediction-time cutoffs. Confirm success using: For controlled entities the online and offline features match at equivalent cutoffs and quality recovers. This matters here because as the team tests a new governed AI release against adversarial and normal data, the following condition occurs: An….
Incorrect Answers
A:Minimize or tokenize personal fields before generation and enforce access and retention controls on any necessary context. This action addresses sensitive identifiers leaked to llm prompts, not the failure in the described training-serving feature skew detection case. The targeted correction is: Version a single feature contract and add automated parity tests to the preprocessing pipeline and serving workflow.
B:Capture immutable prediction identifiers and join verified outcome records to the corresponding earlier inference request. This action addresses ground truth association for quality monitoring, not the failure in the described training-serving feature skew detection case. The targeted correction is: Version a single feature contract and add automated parity tests to the preprocessing pipeline and serving workflow. This matters here because as the team tests a new governed AI release against adversarial and normal data, the following condition occurs: An….
C:Monitor outcome-based quality metrics on matured cohorts and retrain when verified concept drift is significant. This action addresses concept drift with stable feature statistics, not the failure in the described training-serving feature skew detection case. The targeted correction is: Version a single feature contract and add automated parity tests to the preprocessing pipeline and serving workflow.