How many Troubleshooting Scenario Questions questions are on this page?

This page has 6 Troubleshooting Scenario Questions scenario questions for the PMLE exam, each with detailed explanations and wrong-answer analysis.

How should I approach PMLE scenario questions?

Read the full scenario before looking at the answer options. Identify the constraint or requirement in the scenario, then eliminate options that are generally true but wrong for this specific case. Scenario questions reward careful reading over pattern matching.

← Back to Google Professional Machine Learning Engineer questions

Scenario-based practice

Troubleshooting Scenario Questions

Practise Google Professional Machine Learning Engineer practice questions — original exam-style scenarios covering every exam domain, with detailed explanations, wrong-answer analysis, and common exam traps.

Start full practice test Read exam guide

scenario questions

PMLE

exam code

Google Cloud

vendor

Scenario guide

How to approach troubleshooting scenario questions

These questions describe a network symptom and ask you to identify the root cause or the correct fix. They appear across all certification exams and reward systematic thinking over memorisation. The best candidates follow a consistent troubleshooting framework even under time pressure.

Quick answer

Troubleshooting Scenario Questions questions test whether you can apply the concept in context, not just recognise a definition.

How the topic appears in realistic exam-style scenarios.

Which detail in the question changes the correct answer.

How to eliminate plausible but wrong options.

How to connect the question back to the wider exam objective.

Practice scenarios

Question 1easymultiple choice

Full question →

You have an online prediction model that is showing increasing prediction latency. You have already verified that the request rate and input data size are unchanged. Which of the following should you investigate next?

A
Check if the model was recently updated to a larger version
Larger model increases inference latency.
B
Check the monitoring dashboard configuration
Why wrong: Dashboard does not affect latency.
C
Check if the feature engineering logic was changed
Why wrong: Feature engineering change would be part of model update.
D
Check the geographic location of the endpoint
Why wrong: Location affects network latency, not compute latency.

Full breakdown with real-world context →

Question 2mediummultiple choice

Full question →

A data scientist trains an XGBoost model on Vertex AI with a custom container. The model performs well on a held-out test set but fails to generalize in production. They suspect data leakage between training and validation. What is the best practice to prevent this?

A
Store and serve features using Vertex AI Feature Store with point-in-time correctness
Feature Store provides consistent feature values for each timestamp, preventing leakage.
B
Implement feature engineering in Vertex AI Pipelines to ensure temporal ordering
Why wrong: Pipelines orchestrate but don't enforce feature consistency by themselves.
C
Store all features in BigQuery and join on timestamp during training and serving
Why wrong: Manual joins are error-prone and may still introduce leakage.
D
Use Vertex AI AutoML instead of custom training
Why wrong: AutoML may not solve custom feature engineering leakage.

Full breakdown with real-world context →

Question 3hardmulti select

Full question →

A team is troubleshooting a Vertex AI Pipelines run that keeps failing at the model evaluation step. The pipeline includes steps: data preprocessing, training, evaluation, and deployment. Which THREE actions should they take to diagnose the issue?

A
Verify that the training step output is correctly linked as input to evaluation.
Mismatched outputs are a common pipeline failure cause.
B
Run the evaluation code locally with the same input data.
Reproducing locally helps isolate environment-specific issues.
C
Increase the memory of the evaluation step's machine.
Why wrong: Premature fix without knowing if memory is the issue.
D
Check the logs of the evaluation step in Cloud Logging.
Logs provide error details essential for diagnosis.
E
Replace the evaluation step with a Vertex AI Model Evaluation service.
Why wrong: Changes the process instead of diagnosing the current failure.

Full breakdown with real-world context →

Question 4hardmulti select

Full question →

An ML engineer is troubleshooting why a Vertex AI Endpoint is returning high prediction latency. They have enabled request/response logging and see that some requests take >1 second while most are fast. Which THREE actions should they take to diagnose the issue?

A
Check CPU and GPU utilisation metrics on the endpoint.
High utilisation can indicate resource bottleneck.
B
Review the request/response logs in BigQuery to identify if large payloads correlate with high latency.
Logs can show payload size and latency per request.
C
Disable Vertex AI Model Monitoring to reduce overhead.
Why wrong: Monitoring overhead is minimal and not the cause of high latency.
D
Check the p99 latency metric in Cloud Monitoring.
Essential to confirm the latency issue.
E
Increase the number of replicas to resolve the issue immediately.
Why wrong: Scaling without diagnosis may not address root cause; should diagnose first.

Full breakdown with real-world context →

Question 5hardmultiple choice

Full question →

A data science team has trained a TensorFlow model on-premises using a large dataset. When they try to deploy the model to Vertex AI for online predictions, the deployed model fails to start with a ‘MemoryError’. The model artifact is 2 GB, and the machine type is n1-standard-4 (15 GB RAM). What is the most likely cause?

A
The model is stored in a regional bucket and the Vertex AI endpoint is in a different region.
Why wrong: Cross-region access is allowed, though not optimal; it would not cause MemoryError.
B
The machine type does not support TensorFlow models larger than 1 GB.
Why wrong: No such limitation exists; TensorFlow can load larger models given sufficient memory.
C
The model is too large for the machine's memory, causing an out-of-memory (OOM) error during loading.
The 2 GB model may require more than 15 GB RAM during loading due to overhead and intermediate structures.
D
The model file is corrupted or missing dependencies, causing a crash.
Why wrong: Corruption typically causes import errors, not MemoryError.

Full breakdown with real-world context →

Question 6hardmultiple choice

Full question →

You are troubleshooting a Vertex AI endpoint for a customer. The exhibit shows the endpoint configuration. The customer reports that Model A is experiencing high latency during peaks. Model B runs fine. What is the most likely cause?

Exhibit

Refer to the exhibit.

{
  "name": "projects/my-project/locations/us-central1/endpoints/1234",
  "displayName": "my-endpoint",
  "dedicatedEndpointEnabled": false,
  "deployedModels": [
    {
      "id": "model-a-1",
      "displayName": "model-a",
      "model": "projects/my-project/locations/us-central1/models/456",
      "dedicatedResources": {
        "minReplicaCount": 1,
        "maxReplicaCount": 5,
        "machineSpec": {
          "machineType": "n1-standard-4",
          "acceleratorType": "NVIDIA_TESLA_T4",
          "acceleratorCount": 1
        }
      }
    },
    {
      "id": "model-b-1",
      "displayName": "model-b",
      "model": "projects/my-project/locations/us-central1/models/789",
      "dedicatedResources": {
        "minReplicaCount": 1,
        "maxReplicaCount": 5,
        "machineSpec": {
          "machineType": "n1-standard-8",
          "acceleratorType": "NVIDIA_TESLA_T4",
          "acceleratorCount": 2
        }
      }
    }
  ],
  "trafficSplit": {
    "model-a-1": 50,
    "model-b-1": 50
  }
}

A
Model A is not autoscaling properly due to minReplicaCount=1.
Why wrong: Autoscaling is based on max; min=1 doesn't prevent scaling up.
B
Model A's machine type has insufficient CPU and GPU for the load.
Model A uses n1-standard-4 with 1 GPU, while Model B uses n1-standard-8 with 2 GPUs.
C
Dedicated endpoint is disabled, causing resource sharing between models.
Why wrong: Even with shared endpoint, resources are per deployed model.
D
The traffic split is unevenly balanced, causing Model A to receive more requests.
Why wrong: Split is 50-50, so even.

Full breakdown with real-world context →

These PMLE practice questions are part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style PMLE questions with detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics.

Troubleshooting Scenario Questions

How to approach troubleshooting scenario questions

Quick answer

Related PMLE topic practice pages

Automating and Orchestrating ML Pipelines practice questions

Collaborating Within and Across Teams to Manage Data and Models practice questions

Serving and Scaling Models practice questions

Monitoring ML Solutions practice questions

Architecting Low-Code ML Solutions practice questions

Scaling Prototypes into ML Models practice questions

Collaborating to manage data and models practice questions

PMLE fundamentals practice questions

PMLE scenario practice questions

PMLE troubleshooting practice questions

Practice scenarios

You have an online prediction model that is showing increasing prediction latency. You have already verified that the request rate and input data size are unchanged. Which of the following should you investigate next?

A data scientist trains an XGBoost model on Vertex AI with a custom container. The model performs well on a held-out test set but fails to generalize in production. They suspect data leakage between training and validation. What is the best practice to prevent this?

A team is troubleshooting a Vertex AI Pipelines run that keeps failing at the model evaluation step. The pipeline includes steps: data preprocessing, training, evaluation, and deployment. Which THREE actions should they take to diagnose the issue?

An ML engineer is troubleshooting why a Vertex AI Endpoint is returning high prediction latency. They have enabled request/response logging and see that some requests take >1 second while most are fast. Which THREE actions should they take to diagnose the issue?

You are troubleshooting a Vertex AI endpoint for a customer. The exhibit shows the endpoint configuration. The customer reports that Model A is experiencing high latency during peaks. Model B runs fine. What is the most likely cause?

Exhibit