cert
cert-1
cert-2

Pass Google Professional Machine Learning Engineer Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
Professional Machine Learning Engineer Exam - Verified By Experts
Professional Machine Learning Engineer Premium Bundle
$29.98

Professional Machine Learning Engineer Premium Bundle

$79.99
$109.97
  • Premium File 402 Questions & Answers. Last update: Nov 13, 2026
  • Training Course 69 Video Lectures
  • Study Guide 376 Pages
 
$109.97
$79.99
accept 47 downloads in last 7 days
block-screenshots
Purchase Google Professional Machine Learning Engineer Exam Training Products Individually
Google Professional Machine Learning Engineer Premium File
Premium File 402 Q&A
$76.99$69.99
Google Professional Machine Learning Engineer Video Training Course
Training Course 69 Lectures
$21.99 $19.99
Google Professional Machine Learning Engineer PDF Study Guide
Study Guide 376 Pages
$21.99 $19.99
Google Professional Machine Learning Engineer Practice Test 109

Question 1080

During a production ML inference release on Google Cloud, the following condition occurs: A document classification service sends huge media files through synchronous prediction calls whose processing exceeds clients' timeout limits. The service must meet its agreed quality and latency requirements. What should the engineer inspect before selecting a correction?

  1. Inspect traffic-splitting capabilities, release guardrails, rollback triggers and representative online metrics.
  2. Compare request rate, queue depth, GPU utilization, per-instance concurrency and p95 response latency.
  3. Examine endpoint exposure settings, caller IAM, VPC routes, private connectivity and data egress requirements.
  4. Review payload size distributions, request duration, response timeout policies and tolerance for deferred completion.

Explanation

Correct Answer

D:

Review payload size distributions, request duration, response timeout policies and tolerance for deferred completion. This inspects evidence relevant to online prediction timeout and batch fallback. Synchronous request limits cannot be solved merely by expanding the model context or retrying indefinitely. After identifying the cause, the matching correction is: Use asynchronous or batch processing with durable job status for oversized workloads, reserving online calls for bounded requests. This matters here because a document classification service sends huge media files through synchronous prediction calls whose processing….

Incorrect Answers

A:

Inspect traffic-splitting capabilities, release guardrails, rollback triggers and representative online metrics. This examines canary gradual traffic rollout rather than the specific mechanism reported here. It is not the decisive first check for online prediction timeout and batch fallback. The relevant evidence is: Review payload size distributions, request duration, response timeout policies and tolerance for deferred completion.

B:

Compare request rate, queue depth, GPU utilization, per-instance concurrency and p95 response latency. This examines throughput-based autoscaling versus cpu metric rather than the specific mechanism reported here. It is not the decisive first check for online prediction timeout and batch fallback. The relevant evidence is: Review payload size distributions, request duration, response timeout policies and tolerance for deferred completion.

C:

Examine endpoint exposure settings, caller IAM, VPC routes, private connectivity and data egress requirements. This examines private endpoint for regulated inference traffic rather than the specific mechanism reported here. It is not the decisive first check for online prediction timeout and batch fallback. The relevant evidence is: Review payload size distributions, request duration, response timeout policies and tolerance for deferred completion.

Question 1081

During a staged restoration test at a secondary serving deployment, the following condition occurs: A text classifier was trained with a specific subword vocabulary, but production preprocessors use a newer incompatible tokenizer. The team must prove an actual user-visible improvement without weakening access controls. Select TWO: the most relevant root-cause check and the specific observation that proves the fix worked.

  1. Only a limited portion initially uses the candidate and a simulated regression triggers a tested rollback.
  2. Identical sample text yields matching token IDs and model outputs in offline and online environments.
  3. Compare tokenizer hash, normalization rules, token IDs and inference schema against the trained model artifacts.
  4. The model loads at target concurrency without OOM and meets latency and cost targets.
  5. Inspect startup logs, HTTP listening port, health-check expectations and request and response schema.

Explanation

Correct Answers

B:

Identical sample text yields matching token IDs and model outputs in offline and online environments. This is specific acceptance evidence for inference preprocessing tokenization mismatch. Embedding matrices interpret token IDs according to one vocabulary; mismatched preprocessing changes input meaning. It confirms the controlled correction: Package and version the exact trained preprocessing pipeline with the served model and run equivalence tests.

C:

Compare tokenizer hash, normalization rules, token IDs and inference schema against the trained model artifacts. This inspects evidence relevant to inference preprocessing tokenization mismatch. Embedding matrices interpret token IDs according to one vocabulary; mismatched preprocessing changes input meaning. After identifying the cause, the matching correction is: Package and version the exact trained preprocessing pipeline with the served model and run equivalence tests.

Incorrect Answers

A:

Only a limited portion initially uses the candidate and a simulated regression triggers a tested rollback. This relates to canary gradual traffic rollout but does not establish the requested before-and-after evidence. The actual diagnostic is: Compare tokenizer hash, normalization rules, token IDs and inference schema against the trained model artifacts. The specific acceptance result is: Identical sample text yields matching token IDs and model outputs in offline and online environments.

D:

The model loads at target concurrency without OOM and meets latency and cost targets. This relates to gpu cost and memory fit for large embedding model but does not establish the requested before-and-after evidence. The actual diagnostic is: Compare tokenizer hash, normalization rules, token IDs and inference schema against the trained model artifacts. The specific acceptance result is: Identical sample text yields matching token IDs and model outputs in offline and online environments.

E:

Inspect startup logs, HTTP listening port, health-check expectations and request and response schema. This relates to inference container health interface mismatch but does not establish the requested before-and-after evidence. The actual diagnostic is: Compare tokenizer hash, normalization rules, token IDs and inference schema against the trained model artifacts. The specific acceptance result is: Identical sample text yields matching token IDs and model outputs in offline and online environments.

Question 1082

While reproducing a training orchestration incident in isolated staging, the following condition occurs: A Kubeflow preprocessing task is evicted repeatedly because it requests little memory despite materializing large embeddings inside the container. The team requires an idempotent pipeline behavior and traceable evidence. Which TWO selections form an appropriate before-and-after verification pair? Select TWO.

  1. Inspect Kubernetes task events, memory usage, component resource requests and container data-loading behavior.
  2. Staging and production runs report the same component digests and only documented configuration values differ.
  3. Training manifests exclude unlabeled recent transactions and measured metrics use verified ground truth.
  4. The task completes within approved resources with predictable cost and produces the same number of embeddings.
  5. Inspect Airflow retries, write mode, batch IDs, target partitions and commit logs.

Explanation

Correct Answers

A:

Inspect Kubernetes task events, memory usage, component resource requests and container data-loading behavior. This inspects evidence relevant to custom kfp component resource limits. Kubernetes resource limits constrain component runtime even when the model's training job itself has spare capacity. After identifying the cause, the matching correction is: Tune component resource requests/limits and stream or partition embeddings rather than materializing every vector at once.

D:

The task completes within approved resources with predictable cost and produces the same number of embeddings. This is specific acceptance evidence for custom kfp component resource limits. Kubernetes resource limits constrain component runtime even when the model's training job itself has spare capacity. It confirms the controlled correction: Tune component resource requests/limits and stream or partition embeddings rather than materializing every vector at once.

Incorrect Answers

B:

Staging and production runs report the same component digests and only documented configuration values differ. This relates to pipeline environment parameter promotion but does not establish the requested before-and-after evidence. The actual diagnostic is: Inspect Kubernetes task events, memory usage, component resource requests and container data-loading behavior. The specific acceptance result is: The task completes within approved resources with predictable cost and produces the same number of embeddings.

C:

Training manifests exclude unlabeled recent transactions and measured metrics use verified ground truth. This relates to scheduled retraining on delayed ground truth but does not establish the requested before-and-after evidence. The actual diagnostic is: Inspect Kubernetes task events, memory usage, component resource requests and container data-loading behavior. The specific acceptance result is: The task completes within approved resources with predictable cost and produces the same number of embeddings.

E:

Inspect Airflow retries, write mode, batch IDs, target partitions and commit logs. This relates to airflow task idempotency on retry but does not establish the requested before-and-after evidence. The actual diagnostic is: Inspect Kubernetes task events, memory usage, component resource requests and container data-loading behavior. The specific acceptance result is: The task completes within approved resources with predictable cost and produces the same number of embeddings.

Question 1083

During a controlled replay of the data and model handoff to a second engineering team, the following condition occurs: Two experiments use the same model configuration but show different accuracy due to untracked data shuffling and nondeterministic seeds. The handoff must preserve privacy, lineage and testable behavior. Which configuration or procedure is the most appropriate correction?

  1. Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates.
  2. Build a constrained judge rubric with blind repeated comparisons and human-adjudicated calibration on representative examples.
  3. Log reproducibility settings and rerun comparable trials with fixed split and controlled randomness before attributing changes.
  4. Configure event-time windowing with an appropriate watermark and explicit late-data correction policy in the Dataflow pipeline.

Explanation

Correct Answer

C:

Log reproducibility settings and rerun comparable trials with fixed split and controlled randomness before attributing changes. This is the targeted corrective response for experiment random seed and data order variance. A single stochastic training run is not sufficient to distinguish algorithm improvement from sampling variation. Verify the diagnosis using: Inspect random seeds, sample ordering, framework determinism settings and environment versions recorded per run. Confirm success using: Repeated controlled runs show bounded expected variance and any real improvement exceeds run-to-run noise. 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:

Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates. This action addresses experiment metric comparison with mismatched splits, not the failure in the described experiment random seed and data order variance case. The targeted correction is: Log reproducibility settings and rerun comparable trials with fixed split and controlled randomness before attributing changes. This matters here because during a controlled replay of the data and model handoff to a second engineering team, the following condition….

B:

Build a constrained judge rubric with blind repeated comparisons and human-adjudicated calibration on representative examples. This action addresses llm-as-a-judge rubric reliability, not the failure in the described experiment random seed and data order variance case. The targeted correction is: Log reproducibility settings and rerun comparable trials with fixed split and controlled randomness before attributing changes.

D:

Configure event-time windowing with an appropriate watermark and explicit late-data correction policy in the Dataflow pipeline. This action addresses dataflow event-time window correctness, not the failure in the described experiment random seed and data order variance case. The targeted correction is: Log reproducibility settings and rerun comparable trials with fixed split and controlled randomness before attributing changes.

Question 1084

During a regulated MLOps pipeline deployment, the following condition occurs: An endpoint calculates categorical encodings in application code while the training pipeline uses a separate mapping, creating drift after a feature update. The workflow must be repeatable and protect the last approved production model. Which result is the strongest postchange evidence of success?

  1. Representative raw records produce equal feature vectors offline and online, including unseen-category behavior.
  2. An incompatible payload fails visibly while compatible older versions follow documented conversion rules.
  3. A deliberately incompatible payload prevents the release and a compatible fixture completes an end-to-end prediction.
  4. A controlled worker loss resumes from saved progress and produces consistent output counts.

Explanation

Correct Answer

A:

Representative raw records produce equal feature vectors offline and online, including unseen-category behavior. This is specific acceptance evidence for training serving preprocessing artifact sharing. Two independent preprocessing implementations can diverge even when their initial training metrics look correct. It confirms the controlled correction: Package the fitted preprocessing component with the model and apply the same validated transform in both paths. This matters here because an endpoint calculates categorical encodings in application code while the training pipeline uses a separate….

Incorrect Answers

B:

An incompatible payload fails visibly while compatible older versions follow documented conversion rules. This result could demonstrate success for serving schema validation component but not for the stated training serving preprocessing artifact sharing issue. The direct test is: Representative raw records produce equal feature vectors offline and online, including unseen-category behavior.

C:

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 training serving preprocessing artifact sharing issue. The direct test is: Representative raw records produce equal feature vectors offline and online, including unseen-category behavior.

D:

A controlled worker loss resumes from saved progress and produces consistent output counts. This result could demonstrate success for ray distributed task failure isolation but not for the stated training serving preprocessing artifact sharing issue. The direct test is: Representative raw records produce equal feature vectors offline and online, including unseen-category behavior. This matters here because an endpoint calculates categorical encodings in application code while the training pipeline uses a separate….

Question 1085

At a Google Cloud analytics team preparing a governed pilot, the following condition occurs: A team chooses the largest available foundation model by parameter count without checking whether its license allows commercial use or whether it handles the required input modality. The team must satisfy a reproducible low-code AI assessment. Which diagnostic check should be performed FIRST to isolate the described cause?

  1. Inspect class definitions, sample error costs, throughput, p95 latency, pricing and published model capability constraints.
  2. Check whether real class labels exist and examine the standardized input distributions and cluster stability under different seeds.
  3. Review Model Garden model cards, permitted terms, input and output modalities, context limits and evaluation results on the target task.
  4. Inspect representative invoices, desired structured fields, supported processor output and field-level extraction errors.

Explanation

Correct Answer

C:

Review Model Garden model cards, permitted terms, input and output modalities, context limits and evaluation results on the target task. This inspects evidence relevant to model garden task and license selection. Model size alone does not ensure suitable task support, usage rights or production economics. After identifying the cause, the matching correction is: Select a permitted task-compatible Gemini or other supported foundation model and benchmark it against simpler candidates. Here, the relevant situation is: the following condition occurs: A team chooses the largest available foundation model by parameter count without….

Incorrect Answers

A:

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 model garden task and license selection. The relevant evidence is: Review Model Garden model cards, permitted terms, input and output modalities, context limits and evaluation results on the target task.

B:

Check whether real class labels exist and examine the standardized input distributions and cluster stability under different seeds. This examines bigquery ml kmeans customer segmentation rather than the specific mechanism reported here. It is not the decisive first check for model garden task and license selection. The relevant evidence is: Review Model Garden model cards, permitted terms, input and output modalities, context limits and evaluation results on the target task.

D:

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 model garden task and license selection. The relevant evidence is: Review Model Garden model cards, permitted terms, input and output modalities, context limits and evaluation results on the target task. Here, the relevant situation is: the following condition occurs: A team chooses the largest available foundation model by parameter count without….

Question 1086

During a staged restoration test at a secondary serving deployment, the following condition occurs: A new model revision passes deployment health checks but produces many application-level 5xx errors after traffic increases; rollback was never configured. The team must prove an actual user-visible improvement without weakening access controls. Which diagnostic check should be performed FIRST to isolate the described cause?

  1. Inspect trained class-to-index metadata, endpoint output tensors and gateway mapping version.
  2. Inspect endpoint revision metrics, release alarms, traffic fractions and availability of the prior known-good model.
  3. Compare tokenizer hash, normalization rules, token IDs and inference schema against the trained model artifacts.
  4. Examine effective IAM bindings, invocation audit logs and the intended partner service account identity.

Explanation

Correct Answer

B:

Inspect endpoint revision metrics, release alarms, traffic fractions and availability of the prior known-good model. This inspects evidence relevant to model traffic rollback on high error rate. Container readiness checks alone do not guarantee successful predictions under real traffic and data distributions. After identifying the cause, the matching correction is: Add guarded traffic shifts and automatic rollback to the retained healthy revision when threshold alarms trip. This matters here because during a staged restoration test at a secondary serving deployment, the following condition occurs: A new model….

Incorrect Answers

A:

Inspect trained class-to-index metadata, endpoint output tensors and gateway mapping version. This examines custom postprocessing label mapping drift rather than the specific mechanism reported here. It is not the decisive first check for model traffic rollback on high error rate. The relevant evidence is: Inspect endpoint revision metrics, release alarms, traffic fractions and availability of the prior known-good model.

C:

Compare tokenizer hash, normalization rules, token IDs and inference schema against the trained model artifacts. This examines inference preprocessing tokenization mismatch rather than the specific mechanism reported here. It is not the decisive first check for model traffic rollback on high error rate. The relevant evidence is: Inspect endpoint revision metrics, release alarms, traffic fractions and availability of the prior known-good model.

D:

Examine effective IAM bindings, invocation audit logs and the intended partner service account identity. This examines public endpoint iam oversharing rather than the specific mechanism reported here. It is not the decisive first check for model traffic rollback on high error rate. The relevant evidence is: Inspect endpoint revision metrics, release alarms, traffic fractions and availability of the prior known-good model.

Question 1087

During a production ML inference release on Google Cloud, the following condition occurs: A text classifier was trained with a specific subword vocabulary, but production preprocessors use a newer incompatible tokenizer. The service must meet its agreed quality and latency requirements. Which targeted engineering change most directly addresses the failure?

  1. Deploy a verified edge-compatible model for required offline decisions and sync summarized results when connectivity returns.
  2. Pin releases to reviewed immutable image digests and record image plus model artifact versions.
  3. Apply bounded concurrency, idempotent retries with exponential backoff and explicit overload responses.
  4. Package and version the exact trained preprocessing pipeline with the served model and run equivalence tests.

Explanation

Correct Answer

D:

Package and version the exact trained preprocessing pipeline with the served model and run equivalence tests. This is the targeted corrective response for inference preprocessing tokenization mismatch. Embedding matrices interpret token IDs according to one vocabulary; mismatched preprocessing changes input meaning. Verify the diagnosis using: Compare tokenizer hash, normalization rules, token IDs and inference schema against the trained model artifacts. Confirm success using: Identical sample text yields matching token IDs and model outputs in offline and online environments. This matters here because a text classifier was trained with a specific subword vocabulary, but production preprocessors use a newer….

Incorrect Answers

A:

Deploy a verified edge-compatible model for required offline decisions and sync summarized results when connectivity returns. This action addresses edge versus cloud inference network constraints, not the failure in the described inference preprocessing tokenization mismatch case. The targeted correction is: Package and version the exact trained preprocessing pipeline with the served model and run equivalence tests.

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 inference preprocessing tokenization mismatch case. The targeted correction is: Package and version the exact trained preprocessing pipeline with the served model and run equivalence tests.

C:

Apply bounded concurrency, idempotent retries with exponential backoff and explicit overload responses. This action addresses predictive serving rate limit and backpressure, not the failure in the described inference preprocessing tokenization mismatch case. The targeted correction is: Package and version the exact trained preprocessing pipeline with the served model and run equivalence tests.

Question 1088

Within a jointly maintained Google Cloud data science workspace, the following condition occurs: Two experiments use the same model configuration but show different accuracy due to untracked data shuffling and nondeterministic seeds. Collaborators must avoid expanding data access or breaking experiment reproducibility. Which diagnostic check should be performed FIRST to isolate the described cause?

  1. Inspect pipeline execution IDs, experiment tracking records, artifact URIs and the link between metrics and saved models.
  2. Inspect judge rubric prompts, evaluation dataset balance, repeated ratings, human benchmark and uncertainty in pairwise preferences.
  3. Inspect random seeds, sample ordering, framework determinism settings and environment versions recorded per run.
  4. Inspect the labeling payload schema, data classification, annotator roles and fields needed to complete the labeling task.

Explanation

Correct Answer

C:

Inspect random seeds, sample ordering, framework determinism settings and environment versions recorded per run. This inspects evidence relevant to experiment random seed and data order variance. A single stochastic training run is not sufficient to distinguish algorithm improvement from sampling variation. After identifying the cause, the matching correction is: Log reproducibility settings and rerun comparable trials with fixed split and controlled randomness before attributing changes. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: Two experiments use….

Incorrect Answers

A:

Inspect pipeline execution IDs, experiment tracking records, artifact URIs and the link between metrics and saved models. This examines pipeline experiment versus notebook-only tracking rather than the specific mechanism reported here. It is not the decisive first check for experiment random seed and data order variance. The relevant evidence is: Inspect random seeds, sample ordering, framework determinism settings and environment versions recorded per run. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: Two experiments use….

B:

Inspect judge rubric prompts, evaluation dataset balance, repeated ratings, human benchmark and uncertainty in pairwise preferences. This examines llm-as-a-judge rubric reliability rather than the specific mechanism reported here. It is not the decisive first check for experiment random seed and data order variance. The relevant evidence is: Inspect random seeds, sample ordering, framework determinism settings and environment versions recorded per run.

D:

Inspect the labeling payload schema, data classification, annotator roles and fields needed to complete the labeling task. This examines data minimization for labeling inputs rather than the specific mechanism reported here. It is not the decisive first check for experiment random seed and data order variance. The relevant evidence is: Inspect random seeds, sample ordering, framework determinism settings and environment versions recorded per run.

Question 1089

During a controlled replay of the data and model handoff to a second engineering team, the following condition occurs: A team uses manual spreadsheet rows for hyperparameter results and loses connections between training metrics and produced checkpoint artifacts. The handoff must preserve privacy, lineage and testable behavior. What implementation change resolves the specific issue without substituting an unrelated fix?

  1. Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates.
  2. Build a constrained judge rubric with blind repeated comparisons and human-adjudicated calibration on representative examples.
  3. Rebuild offline training data with point-in-time eligible joins and remove features available only after each prediction moment.
  4. Use Agent Platform Experiments and pipeline metadata to track each trial's parameters, measurements and output artifacts.

Explanation

Correct Answer

D:

Use Agent Platform Experiments and pipeline metadata to track each trial's parameters, measurements and output artifacts. This is the targeted corrective response for pipeline experiment versus notebook-only tracking. Trial metrics and artifact provenance must be linked to support valid experiment selection and release audits. Verify the diagnosis using: Inspect pipeline execution IDs, experiment tracking records, artifact URIs and the link between metrics and saved models. Confirm success using: Each candidate's reported metrics resolve to its actual artifact and replayable configuration without manual lookups. 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:

Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates. This action addresses experiment metric comparison with mismatched splits, not the failure in the described pipeline experiment versus notebook-only tracking case. The targeted correction is: Use Agent Platform Experiments and pipeline metadata to track each trial's parameters, measurements and output artifacts. This matters here because during a controlled replay of the data and model handoff to a second engineering team, the following condition….

B:

Build a constrained judge rubric with blind repeated comparisons and human-adjudicated calibration on representative examples. This action addresses llm-as-a-judge rubric reliability, not the failure in the described pipeline experiment versus notebook-only tracking case. The targeted correction is: Use Agent Platform Experiments and pipeline metadata to track each trial's parameters, measurements and output artifacts.

C:

Rebuild offline training data with point-in-time eligible joins and remove features available only after each prediction moment. This action addresses point-in-time feature leakage prevention, not the failure in the described pipeline experiment versus notebook-only tracking case. The targeted correction is: Use Agent Platform Experiments and pipeline metadata to track each trial's parameters, measurements and output artifacts.

Question 1090

As the team tests a new governed AI release against adversarial and normal data, 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 fix must retain legitimate model usefulness and appropriate controls. Select TWO: the decisive diagnostic step and the targeted repair for this specific issue.

  1. Restrict dataset and bucket access by principal and resource; enforce approved egress controls and audit sensitive reads.
  2. Investigate attribution drift, remove invalid proxy features if warranted and retrain with appropriate validation.
  3. Inspect retrieved document boundaries, instruction hierarchy, malicious test prompts and the application's output actions.
  4. Configure Agent Platform Model Monitoring on relevant features with representative baseline and actionable drift alerts.
  5. Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers.

Explanation

Correct Answers

A:

Restrict dataset and bucket access by principal and resource; enforce approved egress controls and audit sensitive reads. This is the targeted corrective response for training data exfiltration through broad access. Least-privilege access and destination controls reduce unauthorized model-data disclosure risk. Verify the diagnosis using: Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers. Confirm success using: The authorized pipeline still reads its intended data while attempts to export to unapproved destinations are denied. This matters here because as the team tests a new governed AI release against adversarial and normal data, the following condition occurs: A….

E:

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 as the team tests a new governed AI release against adversarial and normal data, the following condition occurs: A….

Incorrect Answers

B:

Investigate attribution drift, remove invalid proxy features if warranted and retrain with appropriate validation. This is an action or diagnostic relevant to feature attribution drift after deployment, not one of the required two steps. In this scenario verify: Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers. Then correct: Restrict dataset and bucket access by principal and resource; enforce approved egress controls and audit sensitive reads.

C:

Inspect retrieved document boundaries, instruction hierarchy, malicious test prompts and the application's output actions. This is an action or diagnostic relevant to prompt injection through retrieved documents, not one of the required two steps. In this scenario verify: Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers. Then correct: Restrict dataset and bucket access by principal and resource; enforce approved egress controls and audit sensitive reads.

D:

Configure Agent Platform Model Monitoring on relevant features with representative baseline and actionable drift alerts. This is an action or diagnostic relevant to input data distribution drift alarm, not one of the required two steps. In this scenario verify: Review IAM resource bindings, bucket access policies, egress paths and audit records for unauthorized data transfers. Then correct: Restrict dataset and bucket access by principal and resource; enforce approved egress controls and audit sensitive reads.

Professional Machine Learning Engineer Practice Tests