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 118

Question 1170

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 targeted engineering change most directly addresses the failure?

  1. Index versioned policy sources and use retrieval-grounded Gemini responses for changing facts, reserving tuning for justified behavior adaptation.
  2. Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability.
  3. Retrieve only relevant passages with provenance and use a concise structured prompt with measured token limits.
  4. Select a permitted task-compatible Gemini or other supported foundation model and benchmark it against simpler candidates.

Explanation

Correct Answer

D:

Select a permitted task-compatible Gemini or other supported foundation model and benchmark it against simpler candidates. This is the targeted corrective response for model garden task and license selection. Model size alone does not ensure suitable task support, usage rights or production economics. Verify the diagnosis using: Review Model Garden model cards, permitted terms, input and output modalities, context limits and evaluation results on the target task. Confirm success using: The chosen version meets task quality, inference cost and license rules on a documented representative evaluation set. Here, the relevant situation is: the following condition occurs: A team chooses the largest available foundation model by parameter count without….

Incorrect Answers

A:

Index versioned policy sources and use retrieval-grounded Gemini responses for changing facts, reserving tuning for justified behavior adaptation. This action addresses foundation model tuning versus retrieval update, not the failure in the described model garden task and license selection case. The targeted correction is: Select a permitted task-compatible Gemini or other supported foundation model and benchmark it against simpler candidates.

B:

Train an appropriately scaled BigQuery ML KMEANS model and assess cluster cohesion, size and business interpretability. This action addresses bigquery ml kmeans customer segmentation, not the failure in the described model garden task and license selection case. The targeted correction is: Select a permitted task-compatible Gemini or other supported foundation model and benchmark it against simpler candidates.

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 model garden task and license selection case. The targeted correction is: Select a permitted task-compatible Gemini or other supported foundation model and benchmark it against simpler candidates.

Question 1171

Within a jointly maintained Google Cloud data science workspace, the following condition occurs: A project declares model B superior even though A was evaluated on last quarter and B on a deliberately easier random sample. 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 the labeling payload schema, data classification, annotator roles and fields needed to complete the labeling task.
  4. Inspect dataset and split fingerprints, label definitions, metric versions and evaluation timestamps for both experiment runs.

Explanation

Correct Answer

D:

Inspect dataset and split fingerprints, label definitions, metric versions and evaluation timestamps for both experiment runs. This inspects evidence relevant to experiment metric comparison with mismatched splits. Metrics from different data distributions are not directly comparable evidence of model improvement. After identifying the cause, the matching correction is: Register a common versioned holdout and comparable metrics in Agent Platform Experiments before ranking candidates. This matters here because within a jointly maintained Google Cloud data science workspace, the following condition occurs: A project declares….

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 metric comparison with mismatched splits. The relevant evidence is: Inspect dataset and split fingerprints, label definitions, metric versions and evaluation timestamps for both experiment runs.

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 metric comparison with mismatched splits. The relevant evidence is: Inspect dataset and split fingerprints, label definitions, metric versions and evaluation timestamps for both experiment runs.

C:

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 metric comparison with mismatched splits. The relevant evidence is: Inspect dataset and split fingerprints, label definitions, metric versions and evaluation timestamps for both experiment runs.

Question 1172

While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A model fits in one GPU but a huge dataset takes too long to process, and engineers propose splitting its layers between devices without memory pressure. Engineers need an auditable, resource-aware correction to the issue. Which outcome most directly demonstrates a successful, measurable fix?

  1. Every evaluation feature is available at its simulated prediction time and later-period scores remain stable.
  2. More replicas shorten epoch time without materially changing convergence or causing network communication to dominate.
  3. Trials stay within the approved compute budget and a winner improves the specified independent metric.
  4. The chosen accelerator meets throughput and convergence expectations without unsupported operations or unstable retracing.

Explanation

Correct Answer

B:

More replicas shorten epoch time without materially changing convergence or causing network communication to dominate. This is specific acceptance evidence for distributed data parallel gradient synchronization. When a model fits on each worker, partitioning training data is often more suitable than splitting the model itself. It confirms the controlled correction: Prefer suitable data parallel replicas with synchronized gradient aggregation, then benchmark scale efficiency. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….

Incorrect Answers

A:

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 distributed data parallel gradient synchronization issue. The direct test is: More replicas shorten epoch time without materially changing convergence or causing network communication to dominate. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….

C:

Trials stay within the approved compute budget and a winner improves the specified independent metric. This result could demonstrate success for hyperparameter search budget limit but not for the stated distributed data parallel gradient synchronization issue. The direct test is: More replicas shorten epoch time without materially changing convergence or causing network communication to dominate. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….

D:

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 distributed data parallel gradient synchronization issue. The direct test is: More replicas shorten epoch time without materially changing convergence or causing network communication to dominate.

Question 1173

During a regulated MLOps pipeline deployment, the following condition occurs: The same pipeline is manually edited between staging and production, so a critical feature filter differs across environments without a code review. The workflow must be repeatable and protect the last approved production model. Which configuration or procedure is the most appropriate correction?

  1. Require candidate evaluation against a governed baseline with an enforced acceptance threshold before promotion.
  2. Filter validated completed-dataset events and enforce an idempotent manifest-based training trigger.
  3. Publish one versioned pipeline package and promote it with reviewed environment-specific parameters.
  4. Tune component resource requests/limits and stream or partition embeddings rather than materializing every vector at once.

Explanation

Correct Answer

C:

Publish one versioned pipeline package and promote it with reviewed environment-specific parameters. This is the targeted corrective response for pipeline environment parameter promotion. Promoting immutable pipeline definitions prevents untracked hand edits from changing processing semantics. Verify the diagnosis using: Inspect component definitions, pipeline package versions, parameters and source revisions used in both environments. Confirm success using: Staging and production runs report the same component digests and only documented configuration values differ. This matters here because the same pipeline is manually edited between staging and production, so a critical feature filter differs across….

Incorrect Answers

A:

Require candidate evaluation against a governed baseline with an enforced acceptance threshold before promotion. This action addresses model evaluation gate before deployment, not the failure in the described pipeline environment parameter promotion case. The targeted correction is: Publish one versioned pipeline package and promote it with reviewed environment-specific parameters.

B:

Filter validated completed-dataset events and enforce an idempotent manifest-based training trigger. This action addresses eventbridge equivalent event trigger on storage, not the failure in the described pipeline environment parameter promotion case. The targeted correction is: Publish one versioned pipeline package and promote it with reviewed environment-specific parameters.

D:

Tune component resource requests/limits and stream or partition embeddings rather than materializing every vector at once. This action addresses custom kfp component resource limits, not the failure in the described pipeline environment parameter promotion case. The targeted correction is: Publish one versioned pipeline package and promote it with reviewed environment-specific parameters.

Question 1174

During a regulated MLOps pipeline deployment, the following condition occurs: The same pipeline is manually edited between staging and production, so a critical feature filter differs across environments without a code review. The workflow must be repeatable and protect the last approved production model. Select TWO: the decisive diagnostic step and the targeted repair for this specific issue.

  1. Inspect component definitions, pipeline package versions, parameters and source revisions used in both environments.
  2. Inspect Airflow retries, write mode, batch IDs, target partitions and commit logs.
  3. Publish one versioned pipeline package and promote it with reviewed environment-specific parameters.
  4. Fail protected build or release stages when prohibited vulnerabilities exist and require documented exceptions for approved deviations.
  5. Promote explicit immutable model and image versions with versioned release manifests and review gates.

Explanation

Correct Answers

A:

Inspect component definitions, pipeline package versions, parameters and source revisions used in both environments. This inspects evidence relevant to pipeline environment parameter promotion. Promoting immutable pipeline definitions prevents untracked hand edits from changing processing semantics. After identifying the cause, the matching correction is: Publish one versioned pipeline package and promote it with reviewed environment-specific parameters. This matters here because the same pipeline is manually edited between staging and production, so a critical feature filter differs across….

C:

Publish one versioned pipeline package and promote it with reviewed environment-specific parameters. This is the targeted corrective response for pipeline environment parameter promotion. Promoting immutable pipeline definitions prevents untracked hand edits from changing processing semantics. Verify the diagnosis using: Inspect component definitions, pipeline package versions, parameters and source revisions used in both environments. Confirm success using: Staging and production runs report the same component digests and only documented configuration values differ. This matters here because the same pipeline is manually edited between staging and production, so a critical feature filter differs across….

Incorrect Answers

B:

Inspect Airflow retries, write mode, batch IDs, target partitions and commit logs. This is an action or diagnostic relevant to airflow task idempotency on retry, not one of the required two steps. In this scenario verify: Inspect component definitions, pipeline package versions, parameters and source revisions used in both environments. Then correct: Publish one versioned pipeline package and promote it with reviewed environment-specific parameters.

D:

Fail protected build or release stages when prohibited vulnerabilities exist and require documented exceptions for approved deviations. This is an action or diagnostic relevant to cloud build container security gate, not one of the required two steps. In this scenario verify: Inspect component definitions, pipeline package versions, parameters and source revisions used in both environments. Then correct: Publish one versioned pipeline package and promote it with reviewed environment-specific parameters.

E:

Promote explicit immutable model and image versions with versioned release manifests and review gates. This is an action or diagnostic relevant to cloud build release version promotion, not one of the required two steps. In this scenario verify: Inspect component definitions, pipeline package versions, parameters and source revisions used in both environments. Then correct: Publish one versioned pipeline package and promote it with reviewed environment-specific parameters.

Question 1175

During a regulated MLOps pipeline deployment, the following condition occurs: A build pipeline deploys an arbitrary model tag without tying it to the source revision and the approved evaluation report. The workflow must be repeatable and protect the last approved production model. Which TWO selections represent the correct investigation and remediation together? Select TWO.

  1. Inspect snapshot identifiers, SQL filters, table partitions and the model version's recorded input manifest.
  2. Inspect Cloud Build substitutions, commit SHAs, model registry versions, signed image digests and approval records.
  3. Require inference contract and integration tests with representative requests before promoting each candidate artifact.
  4. Publish one versioned pipeline package and promote it with reviewed environment-specific parameters.
  5. Promote explicit immutable model and image versions with versioned release manifests and review gates.

Explanation

Correct Answers

B:

Inspect Cloud Build substitutions, commit SHAs, model registry versions, signed image digests and approval records. This inspects evidence relevant to cloud build release version promotion. Unpinned tags do not establish a trustworthy relationship between code, model artifacts and production rollout. After identifying the cause, the matching correction is: Promote explicit immutable model and image versions with versioned release manifests and review gates. This matters here because a build pipeline deploys an arbitrary model tag without tying it to the source revision and the approved evaluation….

E:

Promote explicit immutable model and image versions with versioned release manifests and review gates. This is the targeted corrective response for cloud build release version promotion. Unpinned tags do not establish a trustworthy relationship between code, model artifacts and production rollout. Verify the diagnosis using: Inspect Cloud Build substitutions, commit SHAs, model registry versions, signed image digests and approval records. Confirm success using: The deployed model and container can be traced to a particular approved commit and evaluation result. This matters here because a build pipeline deploys an arbitrary model tag without tying it to the source revision and the approved evaluation….

Incorrect Answers

A:

Inspect snapshot identifiers, SQL filters, table partitions and the model version's recorded input manifest. This is an action or diagnostic relevant to data version reproducibility in ct jobs, not one of the required two steps. In this scenario verify: Inspect Cloud Build substitutions, commit SHAs, model registry versions, signed image digests and approval records. Then correct: Promote explicit immutable model and image versions with versioned release manifests and review gates.

C:

Require inference contract and integration tests with representative requests before promoting each candidate artifact. This is an action or diagnostic relevant to continuous delivery integration contract tests, not one of the required two steps. In this scenario verify: Inspect Cloud Build substitutions, commit SHAs, model registry versions, signed image digests and approval records. Then correct: Promote explicit immutable model and image versions with versioned release manifests and review gates.

D:

Publish one versioned pipeline package and promote it with reviewed environment-specific parameters. This is an action or diagnostic relevant to pipeline environment parameter promotion, not one of the required two steps. In this scenario verify: Inspect Cloud Build substitutions, commit SHAs, model registry versions, signed image digests and approval records. Then correct: Promote explicit immutable model and image versions with versioned release manifests and review gates.

Question 1176

While reproducing a training orchestration incident in isolated staging, the following condition occurs: A freshly trained PyTorch model deploys but rejects the production client's JSON keys because only training unit tests ran in CI. The team requires an idempotent pipeline behavior and traceable evidence. What should the engineer inspect before selecting a correction?

  1. Inspect ML Metadata execution links, table snapshots, transformations and model version lineage.
  2. Inspect promotion history, drift thresholds, confidence intervals, model quality guardrails and rollback records.
  3. Review champion model retention, candidate metrics, change approvals and automatic rollback triggers.
  4. Inspect request schema, container route behavior, test fixtures and CI stage dependency graph.

Explanation

Correct Answer

D:

Inspect request schema, container route behavior, test fixtures and CI stage dependency graph. This inspects evidence relevant to continuous delivery integration contract tests. Training success does not guarantee compatibility with the deployed model's consumer API. After identifying the cause, the matching correction is: Require inference contract and integration tests with representative requests before promoting each candidate artifact. This matters here because while reproducing a training orchestration incident in isolated staging, the following condition occurs: A freshly….

Incorrect Answers

A:

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 continuous delivery integration contract tests. The relevant evidence is: Inspect request schema, container route behavior, test fixtures and CI stage dependency graph.

B:

Inspect promotion history, drift thresholds, confidence intervals, model quality guardrails and rollback records. This examines canary failure feedback into ct policy rather than the specific mechanism reported here. It is not the decisive first check for continuous delivery integration contract tests. The relevant evidence is: Inspect request schema, container route behavior, test fixtures and CI stage dependency graph. This matters here because while reproducing a training orchestration incident in isolated staging, the following condition occurs: A freshly….

C:

Review champion model retention, candidate metrics, change approvals and automatic rollback triggers. This examines continuous training rollback protection rather than the specific mechanism reported here. It is not the decisive first check for continuous delivery integration contract tests. The relevant evidence is: Inspect request schema, container route behavior, test fixtures and CI stage dependency graph. This matters here because while reproducing a training orchestration incident in isolated staging, the following condition occurs: A freshly….

Question 1177

During a postdeployment AI safety and reliability review, the following condition occurs: A model keeps similar average scores after an upstream data migration, but feature importance shifts from stable signals toward a suspicious proxy variable. The model owner must provide repeatable evidence rather than a cosmetic dashboard change. What implementation change resolves the specific issue without substituting an unrelated fix?

  1. Minimize or tokenize personal fields before generation and enforce access and retention controls on any necessary context.
  2. Treat retrieved text as untrusted data, isolate instructions, restrict tool actions and apply appropriate Model Armor screening.
  3. Investigate attribution drift, remove invalid proxy features if warranted and retrain with appropriate validation.
  4. Reduce unnecessary few-shot context or use targeted retrieval and evaluate an appropriate lower-latency model where safe.

Explanation

Correct Answer

C:

Investigate attribution drift, remove invalid proxy features if warranted and retrain with appropriate validation. This is the targeted corrective response for feature attribution drift after deployment. Feature attribution drift can indicate changing model reliance even when overall score distributions remain stable. Verify the diagnosis using: Examine explanation distributions, feature generation changes, protected attribute proxies and prediction outcomes by cohort. Confirm success using: Attribution changes are explained or remediated and decision drivers remain stable on known reference cases. This matters here because a model keeps similar average scores after an upstream data migration, but feature importance shifts from stable….

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 feature attribution drift after deployment case. The targeted correction is: Investigate attribution drift, remove invalid proxy features if warranted and retrain with appropriate validation.

B:

Treat retrieved text as untrusted data, isolate instructions, restrict tool actions and apply appropriate Model Armor screening. This action addresses prompt injection through retrieved documents, not the failure in the described feature attribution drift after deployment case. The targeted correction is: Investigate attribution drift, remove invalid proxy features if warranted and retrain with appropriate validation.

D:

Reduce unnecessary few-shot context or use targeted retrieval and evaluate an appropriate lower-latency model where safe. This action addresses llm latency and cost token regression, not the failure in the described feature attribution drift after deployment case. The targeted correction is: Investigate attribution drift, remove invalid proxy features if warranted and retrain with appropriate validation.

Question 1178

While preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs: A neural network's training loss continues falling for fifty epochs while validation loss starts rising after epoch ten. Engineers need an auditable, resource-aware correction to the issue. Which outcome most directly demonstrates a successful, measurable fix?

  1. Every evaluation feature is available at its simulated prediction time and later-period scores remain stable.
  2. New warranty rules appear correctly after the index update without unnecessary retraining and sources remain traceable.
  3. The deployed artifact corresponds to the best held-out epoch rather than the final overfit epoch.
  4. A clean managed training run reads the intended versioned dataset without notebook-local path assumptions.

Explanation

Correct Answer

C:

The deployed artifact corresponds to the best held-out epoch rather than the final overfit epoch. This is specific acceptance evidence for early stopping on validation divergence. More training steps can increase overfitting even when training-set loss keeps improving. It confirms the controlled correction: Configure early stopping with a justified patience window and restore the best validated checkpoint. This matters here because while preparing a production training workflow on Gemini Enterprise Agent Platform, the following condition occurs:….

Incorrect Answers

A:

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 early stopping on validation divergence issue. The direct test is: The deployed artifact corresponds to the best held-out epoch rather than the final overfit epoch.

B:

New warranty rules appear correctly after the index update without unnecessary retraining and sources remain traceable. This result could demonstrate success for foundation model prompt versus fine-tuning but not for the stated early stopping on validation divergence issue. The direct test is: The deployed artifact corresponds to the best held-out epoch rather than the final overfit epoch.

D:

A clean managed training run reads the intended versioned dataset without notebook-local path assumptions. This result could demonstrate success for custom training input schema mismatch but not for the stated early stopping on validation divergence issue. The direct test is: The deployed artifact corresponds to the best held-out epoch rather than the final overfit epoch.

Question 1179

During a staged restoration test at a secondary serving deployment, the following condition occurs: A model receives empty features for existing customers because online requests use string IDs with leading zeros while the source feature view cast them to integers. 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. The morning surge meets availability and p95 latency objectives while off-peak cost remains documented.
  2. The nightly job completes within the agreed SLA without idle real-time serving charges.
  3. Previously missed customer IDs retrieve the intended feature values without collapsing distinct leading-zero identifiers.
  4. Compare requested entity key bytes, stored feature-group schema, casting rules and online lookup failures.
  5. Inspect feature-view sync status, latest source timestamps, entity ID and online lookup freshness.

Explanation

Correct Answers

C:

Previously missed customer IDs retrieve the intended feature values without collapsing distinct leading-zero identifiers. This is specific acceptance evidence for feature online entity key mismatch. Coercing identifier types can change keys, particularly when numeric-looking strings have meaningful leading zeros. It confirms the controlled correction: Preserve stable canonical identifier types end-to-end and backfill only the affected feature records.

D:

Compare requested entity key bytes, stored feature-group schema, casting rules and online lookup failures. This inspects evidence relevant to feature online entity key mismatch. Coercing identifier types can change keys, particularly when numeric-looking strings have meaningful leading zeros. After identifying the cause, the matching correction is: Preserve stable canonical identifier types end-to-end and backfill only the affected feature records.

Incorrect Answers

A:

The morning surge meets availability and p95 latency objectives while off-peak cost remains documented. This relates to autoscaling minimum capacity versus cold load but does not establish the requested before-and-after evidence. The actual diagnostic is: Compare requested entity key bytes, stored feature-group schema, casting rules and online lookup failures. The specific acceptance result is: Previously missed customer IDs retrieve the intended feature values without collapsing distinct leading-zero identifiers.

B:

The nightly job completes within the agreed SLA without idle real-time serving charges. This relates to batch versus online inference schedule but does not establish the requested before-and-after evidence. The actual diagnostic is: Compare requested entity key bytes, stored feature-group schema, casting rules and online lookup failures. The specific acceptance result is: Previously missed customer IDs retrieve the intended feature values without collapsing distinct leading-zero identifiers.

E:

Inspect feature-view sync status, latest source timestamps, entity ID and online lookup freshness. This relates to feature store freshness and online sync but does not establish the requested before-and-after evidence. The actual diagnostic is: Compare requested entity key bytes, stored feature-group schema, casting rules and online lookup failures. The specific acceptance result is: Previously missed customer IDs retrieve the intended feature values without collapsing distinct leading-zero identifiers.

Question 1180

During a controlled replay of the data and model handoff to a second engineering team, the following condition occurs: A prototype notebook commits a service-account JSON private key beside its feature code so colleagues can open Cloud Storage directly. The handoff must preserve privacy, lineage and testable behavior. Which evidence most directly establishes what is wrong with this AI or ML workflow?

  1. Inspect query result sizes, runtime memory, pandas allocations and which aggregations can run in BigQuery SQL.
  2. Examine the partitioning column, query plan, bytes scanned and predicate form against the table's partition definition.
  3. Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project.
  4. Restart the runtime, run the notebook top to bottom and compare variable initialization with committed source revision.

Explanation

Correct Answer

C:

Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project. This inspects evidence relevant to workbench credentials embedded in repository. Long-lived secrets copied into notebooks or Git can be reused outside intended workloads and must be rotated. After identifying the cause, the matching correction is: Revoke and rotate the exposed key and use managed workload identity or approved short-lived credentials with least privilege. This matters here because during a controlled replay of the data and model handoff to a second engineering team, the following condition….

Incorrect Answers

A:

Inspect query result sizes, runtime memory, pandas allocations and which aggregations can run in BigQuery SQL. This examines notebook memory exhaustion on full data extraction rather than the specific mechanism reported here. It is not the decisive first check for workbench credentials embedded in repository. The relevant evidence is: Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project.

B:

Examine the partitioning column, query plan, bytes scanned and predicate form against the table's partition definition. This examines bigquery partition filter cost optimization rather than the specific mechanism reported here. It is not the decisive first check for workbench credentials embedded in repository. The relevant evidence is: Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project.

D:

Restart the runtime, run the notebook top to bottom and compare variable initialization with committed source revision. This examines notebook transient state and execution order rather than the specific mechanism reported here. It is not the decisive first check for workbench credentials embedded in repository. The relevant evidence is: Inspect repository history, mounted credentials, authorized identities and any logs of secret access from the shared project. This matters here because during a controlled replay of the data and model handoff to a second engineering team, the following condition….

Professional Machine Learning Engineer Practice Tests