Google Professional Machine Learning Engineer Practice Test 31
Question 300
While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: An engineer runs an unbounded grid across learning rates, depths and regularization values, using expensive accelerators without a metric-driven stopping rule. Engineers need an auditable, resource-aware correction to the issue. What acceptance result verifies the intended behavior after remediation?
- Held-out predictions are currency-valued and their absolute or squared errors match the financial evaluation contract.
- Trials stay within the approved compute budget and a winner improves the specified independent metric.
- Every evaluation feature is available at its simulated prediction time and later-period scores remain stable.
- A controlled interruption resumes near the saved step without restarting training from zero.
Explanation
Correct Answer
B:Trials stay within the approved compute budget and a winner improves the specified independent metric. This is specific acceptance evidence for hyperparameter search budget limit. Search quality depends on comparable objectives and resource limits, not exhaustive combinations at any cost. It confirms the controlled correction: Use bounded hyperparameter tuning with an explicit objective metric, search space, concurrency and early stopping.
Incorrect Answers
A:Held-out predictions are currency-valued and their absolute or squared errors match the financial evaluation contract. This result could demonstrate success for regression versus classification product choice but not for the stated hyperparameter search budget limit issue. The direct test is: Trials stay within the approved compute budget and a winner improves the specified independent metric.
C:Every evaluation feature is available at its simulated prediction time and later-period scores remain stable. This result could demonstrate success for temporal training label leakage in rolling windows but not for the stated hyperparameter search budget limit issue. The direct test is: Trials stay within the approved compute budget and a winner improves the specified independent metric.
D: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 hyperparameter search budget limit issue. The direct test is: Trials stay within the approved compute budget and a winner improves the specified independent metric.
Question 301
During a production ML inference release on Google Cloud, the following condition occurs: A real-time scoring service reads a managed feature view that has not synchronized since yesterday while the source BigQuery table contains recent transaction updates. The service must meet its agreed quality and latency requirements. Which evidence most directly establishes what is wrong with this AI or ML workflow?
- Inspect idle cost, model initialization time, min replicas, burst arrival, queueing and request deadlines.
- Decompose client network, TLS, request transport, model compute and response times by user geography.
- Compare Artifact Registry image digest, build provenance, runtime dependency inventory and release manifests.
- Inspect feature-view sync status, latest source timestamps, entity ID and online lookup freshness.
Explanation
Correct Answer
D:Inspect feature-view sync status, latest source timestamps, entity ID and online lookup freshness. This inspects evidence relevant to feature store freshness and online sync. Online feature serving requires an up-to-date synchronized view; source-table changes need not appear instantly. After identifying the cause, the matching correction is: Schedule and monitor approved Feature Store synchronization at the needed frequency, with stale-feature handling. This matters here because a real-time scoring service reads a managed feature view that has not synchronized since yesterday while the sourceā¦.
Incorrect Answers
A:Inspect idle cost, model initialization time, min replicas, burst arrival, queueing and request deadlines. This examines autoscaling minimum capacity versus cold load rather than the specific mechanism reported here. It is not the decisive first check for feature store freshness and online sync. The relevant evidence is: Inspect feature-view sync status, latest source timestamps, entity ID and online lookup freshness.
B:Decompose client network, TLS, request transport, model compute and response times by user geography. This examines serving region proximity versus model compute rather than the specific mechanism reported here. It is not the decisive first check for feature store freshness and online sync. The relevant evidence is: Inspect feature-view sync status, latest source timestamps, entity ID and online lookup freshness.
C:Compare Artifact Registry image digest, build provenance, runtime dependency inventory and release manifests. This examines model artifact image digest reproducibility rather than the specific mechanism reported here. It is not the decisive first check for feature store freshness and online sync. The relevant evidence is: Inspect feature-view sync status, latest source timestamps, entity ID and online lookup freshness.
Question 302
While reproducing a training orchestration incident in isolated staging, the following condition occurs: A monthly CSV feed begins omitting account IDs, but the pipeline trains and publishes a model without examining null-rate changes. The team requires an idempotent pipeline behavior and traceable evidence. What should the engineer inspect before selecting a correction?
- Review schema tests, null-rate distributions, validation thresholds and which pipeline stages respond to failures.
- Inspect Airflow retries, write mode, batch IDs, target partitions and commit logs.
- Inspect Kubernetes task events, memory usage, component resource requests and container data-loading behavior.
- Inspect label arrival times, cohort maturity, feedback collection coverage and effective training cutoffs.
Explanation
Correct Answer
A:Review schema tests, null-rate distributions, validation thresholds and which pipeline stages respond to failures. This inspects evidence relevant to data validation threshold gate. A schema existing does not imply data quality; pipeline gates must enforce business completeness rules. After identifying the cause, the matching correction is: Add a data-validation component that quarantines nonconforming inputs and fails downstream training until reviewed.
Incorrect Answers
B:Inspect Airflow retries, write mode, batch IDs, target partitions and commit logs. This examines airflow task idempotency on retry rather than the specific mechanism reported here. It is not the decisive first check for data validation threshold gate. The relevant evidence is: Review schema tests, null-rate distributions, validation thresholds and which pipeline stages respond to failures.
C:Inspect Kubernetes task events, memory usage, component resource requests and container data-loading behavior. This examines custom kfp component resource limits rather than the specific mechanism reported here. It is not the decisive first check for data validation threshold gate. The relevant evidence is: Review schema tests, null-rate distributions, validation thresholds and which pipeline stages respond to failures.
D:Inspect label arrival times, cohort maturity, feedback collection coverage and effective training cutoffs. This examines scheduled retraining on delayed ground truth rather than the specific mechanism reported here. It is not the decisive first check for data validation threshold gate. The relevant evidence is: Review schema tests, null-rate distributions, validation thresholds and which pipeline stages respond to failures.
Question 303
During a postdeployment AI safety and reliability review, 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 model owner must provide repeatable evidence rather than a cosmetic dashboard change. Which statement identifies the primary reason for this failure?
- Normal recurring seasonality can resemble drift against an unsegmented static baseline.
- External retrieval content can carry attacker instructions; data should not receive the authority of trusted application instructions.
- Supervised production quality requires reliable prediction-to-ground-truth linkage, not only unlabeled model outputs.
- Resource health cannot substitute for model outcome quality; release decisions need explicit relevant monitoring signals.
Explanation
Correct Answer
A:Normal recurring seasonality can resemble drift against an unsegmented static baseline. This explains the mechanism behind model monitoring false-alert seasonality and why the described failure is possible. A discriminating investigation is: Examine alert history, day-of-week distributions, false-positive cost and baseline segmentation. The corresponding repair is: Adopt justified seasonal baselines or cohorts and tune alert thresholds without suppressing severe shifts.
Incorrect Answers
B:External retrieval content can carry attacker instructions; data should not receive the authority of trusted application instructions. This principle describes prompt injection through retrieved documents, which is not the cause of the observed model monitoring false-alert seasonality failure. The controlling explanation is: Normal recurring seasonality can resemble drift against an unsegmented static baseline.
C:Supervised production quality requires reliable prediction-to-ground-truth linkage, not only unlabeled model outputs. This principle describes ground truth association for quality monitoring, which is not the cause of the observed model monitoring false-alert seasonality failure. The controlling explanation is: Normal recurring seasonality can resemble drift against an unsegmented static baseline.
D:Resource health cannot substitute for model outcome quality; release decisions need explicit relevant monitoring signals. This principle describes production incident rollback based on metrics, which is not the cause of the observed model monitoring false-alert seasonality failure. The controlling explanation is: Normal recurring seasonality can resemble drift against an unsegmented static baseline.
Question 304
While reproducing a training orchestration incident in isolated staging, the following condition occurs: A continuous-training pipeline reads a mutable all-data table each run and never logs which rows produced its newest artifact. The team requires an idempotent pipeline behavior and traceable evidence. Which diagnostic check should be performed FIRST to isolate the described cause?
- Inspect task execution states, failed-job logs, alert routing, pipeline-age metrics and owner escalation settings.
- Inspect snapshot identifiers, SQL filters, table partitions and the model version's recorded input manifest.
- Inspect request schema, container route behavior, test fixtures and CI stage dependency graph.
- Inspect ML Metadata execution links, table snapshots, transformations and model version lineage.
Explanation
Correct Answer
B:Inspect snapshot identifiers, SQL filters, table partitions and the model version's recorded input manifest. This inspects evidence relevant to data version reproducibility in ct jobs. Model retraining reproducibility requires stable inputs rather than unversioned reads of an evolving table. After identifying the cause, the matching correction is: Create immutable versioned input snapshots or partition manifests and record them in training metadata.
Incorrect Answers
A:Inspect task execution states, failed-job logs, alert routing, pipeline-age metrics and owner escalation settings. This examines pipeline notification alert on silent failure rather than the specific mechanism reported here. It is not the decisive first check for data version reproducibility in ct jobs. The relevant evidence is: Inspect snapshot identifiers, SQL filters, table partitions and the model version's recorded input manifest.
C:Inspect request schema, container route behavior, test fixtures and CI stage dependency graph. This examines continuous delivery integration contract tests rather than the specific mechanism reported here. It is not the decisive first check for data version reproducibility in ct jobs. The relevant evidence is: Inspect snapshot identifiers, SQL filters, table partitions and the model version's recorded input manifest.
D:Inspect ML Metadata execution links, table snapshots, transformations and model version lineage. This examines model feature lineage for audit rather than the specific mechanism reported here. It is not the decisive first check for data version reproducibility in ct jobs. The relevant evidence is: Inspect snapshot identifiers, SQL filters, table partitions and the model version's recorded input manifest.
Question 305
At a Google Cloud analytics team preparing a governed pilot, 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 team must satisfy a reproducible low-code AI assessment. 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 feature timestamps, label generation time, feature attributions, and whether the evaluation partition is independent.
- Inspect representative invoices, desired structured fields, supported processor output and field-level extraction errors.
- Inspect class definitions, sample error costs, throughput, p95 latency, pricing and published model capability constraints.
Explanation
Correct Answer
C:Inspect representative invoices, desired structured fields, supported processor output and field-level extraction errors. This inspects evidence relevant to document ai structured invoice extraction. Object or image classification only identifies image categories; document understanding targets structured text fields. After identifying the cause, the matching correction is: Use an appropriate Document AI processor for form or invoice extraction and validate required fields before downstream posting.
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 document ai structured invoice extraction. The relevant evidence is: Inspect representative invoices, desired structured fields, supported processor output and field-level extraction errors.
B:Inspect feature timestamps, label generation time, feature attributions, and whether the evaluation partition is independent. This examines bigquery ml ml.evaluate leakage detection rather than the specific mechanism reported here. It is not the decisive first check for document ai structured invoice extraction. The relevant evidence is: Inspect representative invoices, desired structured fields, supported processor output and field-level extraction errors.
D:Inspect class definitions, sample error costs, throughput, p95 latency, pricing and published model capability constraints. This examines gemini model choice for latency versus complexity rather than the specific mechanism reported here. It is not the decisive first check for document ai structured invoice extraction. The relevant evidence is: Inspect representative invoices, desired structured fields, supported processor output and field-level extraction errors.
Question 306
During a regulated MLOps pipeline deployment, the following condition occurs: An orchestrated data pipeline inserts training rows twice after transient failure because a retried task appends without a stable batch identifier. The workflow must be repeatable and protect the last approved production model. Which evidence most directly establishes what is wrong with this AI or ML workflow?
- Compare serialized preprocessing artifacts, schema versions, train-time transformations and live request feature IDs.
- Inspect label arrival times, cohort maturity, feedback collection coverage and effective training cutoffs.
- Inspect Airflow retries, write mode, batch IDs, target partitions and commit logs.
- Inspect Cloud Build stage status propagation, vulnerability findings, policy thresholds and deployment triggers.
Explanation
Correct Answer
C:Inspect Airflow retries, write mode, batch IDs, target partitions and commit logs. This inspects evidence relevant to airflow task idempotency on retry. Orchestrators often retry tasks; duplicate side effects are prevented by idempotent data operations. After identifying the cause, the matching correction is: Make the load idempotent with keyed merge or overwrite-per-version semantics and safe retry handling.
Incorrect Answers
A:Compare serialized preprocessing artifacts, schema versions, train-time transformations and live request feature IDs. This examines training serving preprocessing artifact sharing rather than the specific mechanism reported here. It is not the decisive first check for airflow task idempotency on retry. The relevant evidence is: Inspect Airflow retries, write mode, batch IDs, target partitions and commit logs.
B:Inspect label arrival times, cohort maturity, feedback collection coverage and effective training cutoffs. This examines scheduled retraining on delayed ground truth rather than the specific mechanism reported here. It is not the decisive first check for airflow task idempotency on retry. The relevant evidence is: Inspect Airflow retries, write mode, batch IDs, target partitions and commit logs.
D:Inspect Cloud Build stage status propagation, vulnerability findings, policy thresholds and deployment triggers. This examines cloud build container security gate rather than the specific mechanism reported here. It is not the decisive first check for airflow task idempotency on retry. The relevant evidence is: Inspect Airflow retries, write mode, batch IDs, target partitions and commit logs.
Question 307
At a Google Cloud analytics team preparing a governed pilot, the following condition occurs: A content moderation team needs generic objects detected in product photographs but starts training a custom network without checking pretrained image analysis. The team must satisfy a reproducible low-code AI assessment. Which configuration or procedure is the most appropriate correction?
- Use an appropriate Document AI processor for form or invoice extraction and validate required fields before downstream posting.
- Evaluate Cloud Vision API for supported generic image detection and use custom training only for missing domain-specific classes.
- Retrieve only relevant passages with provenance and use a concise structured prompt with measured token limits.
- Move deterministic feature transformations into the supported BigQuery ML TRANSFORM workflow and use the same model at inference.
Explanation
Correct Answer
B:Evaluate Cloud Vision API for supported generic image detection and use custom training only for missing domain-specific classes. This is the targeted corrective response for vision api pretrained image labels versus custom detection. A pretrained vision API may cover general image concepts, while specialized categories may need a custom model. Verify the diagnosis using: Inspect requested labels or bounding boxes, sample image quality, supported Vision API capabilities and required detection thresholds. Confirm success using: Representative photographs return the needed detections at acceptable precision, latency and per-image cost.
Incorrect Answers
A:Use an appropriate Document AI processor for form or invoice extraction and validate required fields before downstream posting. This action addresses document ai structured invoice extraction, not the failure in the described vision api pretrained image labels versus custom detection case. The targeted correction is: Evaluate Cloud Vision API for supported generic image detection and use custom training only for missing domain-specific classes.
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 vision api pretrained image labels versus custom detection case. The targeted correction is: Evaluate Cloud Vision API for supported generic image detection and use custom training only for missing domain-specific classes.
D:Move deterministic feature transformations into the supported BigQuery ML TRANSFORM workflow and use the same model at inference. This action addresses bigquery ml transform serving parity, not the failure in the described vision api pretrained image labels versus custom detection case. The targeted correction is: Evaluate Cloud Vision API for supported generic image detection and use custom training only for missing domain-specific classes.
Question 308
During a regulated MLOps pipeline deployment, the following condition occurs: A monthly CSV feed begins omitting account IDs, but the pipeline trains and publishes a model without examining null-rate changes. The workflow must be repeatable and protect the last approved production model. What acceptance result verifies the intended behavior after remediation?
- Every production model version traces to successfully completed validation and evaluation steps in that run.
- The task completes within approved resources with predictable cost and produces the same number of embeddings.
- A deliberately malformed dataset is rejected before training while healthy fixtures proceed successfully.
- A deliberately incompatible payload prevents the release and a compatible fixture completes an end-to-end prediction.
Explanation
Correct Answer
C:A deliberately malformed dataset is rejected before training while healthy fixtures proceed successfully. This is specific acceptance evidence for data validation threshold gate. A schema existing does not imply data quality; pipeline gates must enforce business completeness rules. It confirms the controlled correction: Add a data-validation component that quarantines nonconforming inputs and fails downstream training until reviewed.
Incorrect Answers
A:Every production model version traces to successfully completed validation and evaluation steps in that run. This result could demonstrate success for pipeline component dependency order but not for the stated data validation threshold gate issue. The direct test is: A deliberately malformed dataset is rejected before training while healthy fixtures proceed successfully.
B:The task completes within approved resources with predictable cost and produces the same number of embeddings. This result could demonstrate success for custom kfp component resource limits but not for the stated data validation threshold gate issue. The direct test is: A deliberately malformed dataset is rejected before training while healthy fixtures proceed successfully.
D:A deliberately incompatible payload prevents the release and a compatible fixture completes an end-to-end prediction. This result could demonstrate success for continuous delivery integration contract tests but not for the stated data validation threshold gate issue. The direct test is: A deliberately malformed dataset is rejected before training while healthy fixtures proceed successfully.
Question 309
At a Google Cloud analytics team preparing a governed pilot, 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 team must satisfy a reproducible low-code AI assessment. What should the engineer inspect before selecting a correction?
- Inspect the training preprocessing SQL, TRANSFORM clause, model input schema, and the inference query's feature values.
- Inspect whether errors come from changing factual reference documents or from stable task/style behavior, and examine retrieval accuracy.
- Review row volume, model location, permissions and the current SQL report dependency on the local scoring script.
- Inspect feature timestamps, label generation time, feature attributions, and whether the evaluation partition is independent.
Explanation
Correct Answer
C: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.
Incorrect Answers
A: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.
B: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 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.
D:Inspect feature timestamps, label generation time, feature attributions, and whether the evaluation partition is independent. This examines bigquery ml ml.evaluate leakage 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.
Question 310
While reproducing a training orchestration incident in isolated staging, the following condition occurs: A distributed batch preprocessing workflow launches thousands of Ray tasks but loses intermediate outputs after one worker fails because object references are not persisted appropriately. The team requires an idempotent pipeline behavior and traceable evidence. Which configuration or procedure is the most appropriate correction?
- Make the load idempotent with keyed merge or overwrite-per-version semantics and safe retry handling.
- Promote explicit immutable model and image versions with versioned release manifests and review gates.
- Enforce a shared typed schema contract and reject incompatible feature versions before training or inference.
- Use supported Ray retry policies and durable checkpoints at suitable stage boundaries instead of relying only on worker memory.
Explanation
Correct Answer
D:Use supported Ray retry policies and durable checkpoints at suitable stage boundaries instead of relying only on worker memory. This is the targeted corrective response for ray distributed task failure isolation. Distributed in-memory object stores are not durable archival storage; failure recovery needs explicit design. Verify the diagnosis using: Inspect task lineage, retries, durable checkpoints, object-store pressure and failed worker logs. Confirm success using: A controlled worker loss resumes from saved progress and produces consistent output counts.
Incorrect Answers
A:Make the load idempotent with keyed merge or overwrite-per-version semantics and safe retry handling. This action addresses airflow task idempotency on retry, not the failure in the described ray distributed task failure isolation case. The targeted correction is: Use supported Ray retry policies and durable checkpoints at suitable stage boundaries instead of relying only on worker memory.
B:Promote explicit immutable model and image versions with versioned release manifests and review gates. This action addresses cloud build release version promotion, not the failure in the described ray distributed task failure isolation case. The targeted correction is: Use supported Ray retry policies and durable checkpoints at suitable stage boundaries instead of relying only on worker memory.
C:Enforce a shared typed schema contract and reject incompatible feature versions before training or inference. This action addresses serving schema validation component, not the failure in the described ray distributed task failure isolation case. The targeted correction is: Use supported Ray retry policies and durable checkpoints at suitable stage boundaries instead of relying only on worker memory.