How should I use these Automating and orchestrating ML pipelines practice questions?

Read each scenario carefully and choose your answer before revealing the explanation. Then check why your choice was right or wrong. Repeat until the reasoning feels automatic.

PMLE · topic practice

Automating and orchestrating ML pipelines practice questions

Q: Can I practise just Automating and orchestrating ML pipelines questions in a focused session?

Yes — use the session launcher on this page to start a 10-, 20-, 30- or 50-question session drawn entirely from the Automating and orchestrating ML pipelines domain.

Practise Google Professional Machine Learning Engineer Automating and orchestrating ML pipelines practice questions — original exam-style scenarios with answer choices, explanations, and analysis of common mistakes.

Courseiva uses original exam-style practice questions designed for learning and revision. The goal is to understand the concepts, recognise exam patterns, and improve through explanations — not memorise copied exam dumps.

Reviewed byJohnson Ajibi· MSc IT Security

20 questionsDomain: Automating and orchestrating ML pipelines

Practice 10 questions Browse domain →

What the exam tests

What to know about Automating and orchestrating ML pipelines

Automating and orchestrating ML pipelines 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.

Watch out for

Common Automating and orchestrating ML pipelines exam traps

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Practice set

Automating and orchestrating ML pipelines questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

An MLOps team is implementing a CI/CD pipeline for a TensorFlow model on Vertex AI. The model training job takes 2 hours and produces a SavedModel. The team wants to automatically trigger a new pipeline run whenever a change is pushed to the 'main' branch of their source repository. The pipeline should include training, evaluation, and if metrics exceed a threshold, deploy the model to a Vertex AI endpoint. Which trigger configuration should they use?

Trap 1: Use Eventarc to listen for Cloud Source Repository push events and…

This is possible but not the simplest; Cloud Build is more straightforward for CI/CD.

Trap 2: Use an Artifact Registry trigger to detect new model images and…

Artifact Registry triggers are for container images, not source code changes.

Trap 3: Set up a Cloud Scheduler job that runs every 2 hours and triggers a…

Cloud Scheduler is for scheduled, not event-driven triggers.

Study all Automating and orchestrating ML pipelines common traps →

A
Use Eventarc to listen for Cloud Source Repository push events and invoke a Cloud Run service that starts the pipeline.
Why wrong: This is possible but not the simplest; Cloud Build is more straightforward for CI/CD.
B
Use an Artifact Registry trigger to detect new model images and then start the pipeline.
Why wrong: Artifact Registry triggers are for container images, not source code changes.
C
Set up a Cloud Scheduler job that runs every 2 hours and triggers a Vertex AI Pipeline run.
Why wrong: Cloud Scheduler is for scheduled, not event-driven triggers.
D
Configure a Cloud Build trigger that watches the 'main' branch of Cloud Source Repositories; in the build config, use steps to run the pipeline via the Vertex AI API.
Cloud Build triggers are designed for source code events and can orchestrate ML pipelines.

Full breakdown with real-world context →

Question 2hardmultiple choice

Study the full Python automation breakdown →

A data science team is deploying a PyTorch model for real-time inference using Vertex AI Endpoints. The model requires a custom container with specific CUDA drivers and Python packages. They have created a Docker image and pushed it to Artifact Registry. The pipeline should automatically retrain the model every week and deploy the new version if it passes validation. However, the deployment step fails intermittently with the error 'The container image is not compatible with the machine type.' What is the most likely cause?

Trap 1: The service account does not have permission to pull the container…

Permission issues cause unauthorized errors, not compatibility errors.

Trap 2: The container's health check endpoint is not responding correctly.

Health check failures produce different errors.

Trap 3: The model artifact size exceeds the maximum allowed for the machine…

Size issues cause timeout or memory errors, not compatibility errors.

Study all Automating and orchestrating ML pipelines common traps →

A
The service account does not have permission to pull the container from Artifact Registry.
Why wrong: Permission issues cause unauthorized errors, not compatibility errors.
B
The container image requires GPU support but the machine type specified in the endpoint is a CPU-only machine.
CUDA drivers require GPU machines; using a CPU machine causes compatibility error.
C
The container's health check endpoint is not responding correctly.
Why wrong: Health check failures produce different errors.
D
The model artifact size exceeds the maximum allowed for the machine type.
Why wrong: Size issues cause timeout or memory errors, not compatibility errors.

Full breakdown with real-world context →

Question 3easymultiple choice

Study the full Python automation breakdown →

An ML engineer is using Vertex AI Pipelines with Kubeflow Pipelines SDK (KFP) to orchestrate a training and deployment workflow. They want to reuse a custom component across multiple pipelines. The component is defined in a Python file 'preprocess.py' that includes a function decorated with @kfp.components.create_component_from_func. How should they package this component for reuse?

Trap 1: Save the component as a YAML file using…

ComponentStore is not a standard KFP feature.

Trap 2: Compile the pipeline that uses the component into a JSON file and…

Compilation is for the pipeline, not the component.

Trap 3: Build a custom container image with the function and use it as a…

Overkill; the KFP SDK handles component reuse without containers.

Study all Automating and orchestrating ML pipelines common traps →

A
Import the preprocess module and call create_component_from_func on the function, then use the resulting component in pipeline definitions.
This allows the component to be defined once and reused.
B
Save the component as a YAML file using kfp.components.ComponentStore and load it in other pipelines.
Why wrong: ComponentStore is not a standard KFP feature.
C
Compile the pipeline that uses the component into a JSON file and upload it to Vertex AI.
Why wrong: Compilation is for the pipeline, not the component.
D
Build a custom container image with the function and use it as a base image in other pipelines.
Why wrong: Overkill; the KFP SDK handles component reuse without containers.

Full breakdown with real-world context →

Question 4hardmultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

A company has a Vertex AI pipeline that trains a model on streaming data from Pub/Sub. The pipeline is triggered by a Cloud Function when new data arrives. Recently, jobs have been failing with 'ResourceExhausted: Quota limit exceeded for regional CPUs in us-central1.' The team needs to ensure successful job execution while minimizing changes. Which approach should they take?

Trap 1: Request a quota increase from Google Cloud Support.

This is a valid long-term fix but not minimal; it requires intervention.

Trap 2: Change the pipeline to run in a different region with available…

This may require data movement and is not minimal change.

Trap 3: Reduce the number of parallel pipeline runs by using a Cloud Tasks…

This doesn't help if quota is already exhausted; it just slows down.

Study all Automating and orchestrating ML pipelines common traps →

A
Request a quota increase from Google Cloud Support.
Why wrong: This is a valid long-term fix but not minimal; it requires intervention.
B
Change the pipeline to run in a different region with available quota.
Why wrong: This may require data movement and is not minimal change.
C
Reduce the number of parallel pipeline runs by using a Cloud Tasks queue with rate limiting.
Why wrong: This doesn't help if quota is already exhausted; it just slows down.
D
Configure the pipeline's training job to use preemptible VMs (which count toward a separate, usually higher quota).
Preemptible VMs have a separate quota and are cheaper.

Full breakdown with real-world context →

Question 5mediummulti select

Read the full Automating and orchestrating ML pipelines explanation →

An ML team is designing an automated pipeline to retrain a recommendation model every day using new user interaction data stored in BigQuery. The pipeline must be cost-efficient, scalable, and require minimal manual intervention. Which two approaches should they consider?

Trap 1: Deploy a custom Kubernetes cron job on GKE to run the training…

This adds cluster management overhead.

Trap 2: Use Cloud Composer (Airflow) to schedule the pipeline with a DAG.

Overkill for a simple daily schedule; adds complexity.

Trap 3: Use Dataflow to continuously read from BigQuery and trigger…

Dataflow is for streaming, but the requirement is daily batch.

Study all Automating and orchestrating ML pipelines common traps →

A
Deploy a custom Kubernetes cron job on GKE to run the training script directly.
Why wrong: This adds cluster management overhead.
B
Use Cloud Composer (Airflow) to schedule the pipeline with a DAG.
Why wrong: Overkill for a simple daily schedule; adds complexity.
C
Use Cloud Scheduler to publish a Pub/Sub message daily, which triggers a Cloud Function that starts the Vertex AI Pipeline.
This provides automated daily triggering with minimal overhead.
D
Use Dataflow to continuously read from BigQuery and trigger training when new data arrives.
Why wrong: Dataflow is for streaming, but the requirement is daily batch.
E
Use Vertex AI Pipelines to define the workflow and preemptible VMs for training to reduce cost.
Preemptible VMs are cost-effective and Vertex AI Pipelines orchestrates the workflow.

Full breakdown with real-world context →

Question 6hardmultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

You are an ML engineer at a large e-commerce company. Your team has developed a product recommendation model using TensorFlow and deployed it on Vertex AI Endpoints for real-time inference. The model is retrained weekly using a Vertex AI Pipeline that reads new user interaction data from BigQuery, trains the model, evaluates it, and deploys the new version to the endpoint with a traffic split: 10% to the new model and 90% to the previous champion model. Recently, the team noticed that the new model's online prediction latency has increased significantly (from 50ms to 200ms) after deployment, causing timeouts for some requests. The training code has not changed, and the model size is similar. The pipeline uses a custom container with the same TensorFlow Serving image as before. The deployment step uses the same machine type (n1-standard-4) for the endpoint. What is the most likely cause of the latency increase?

Trap 1: The endpoint is using a machine type that is not optimized for the…

The machine type is the same as before.

Trap 2: The new model has a significantly different architecture that…

The training code hasn't changed, so architecture is likely similar.

Trap 3: The new model is experiencing data skew because the training data…

Data skew affects model accuracy, not latency.

Study all Automating and orchestrating ML pipelines common traps →

A
The endpoint is using a machine type that is not optimized for the new model's computation.
Why wrong: The machine type is the same as before.
B
The new model has a significantly different architecture that requires more computation.
Why wrong: The training code hasn't changed, so architecture is likely similar.
C
The pipeline now includes a data validation step that modifies the SavedModel's serving signature, adding an extra preprocessing operation.
A data validation step might have inadvertently added preprocessing ops, increasing latency.
D
The new model is experiencing data skew because the training data distribution has changed.
Why wrong: Data skew affects model accuracy, not latency.

Full breakdown with real-world context →

Question 7hardmulti select

Read the full Automating and orchestrating ML pipelines explanation →

You are designing an ML pipeline for a large-scale recommendation system that runs weekly retraining on historical user interaction data. The pipeline uses TensorFlow and is deployed on Google Cloud. The pipeline must be orchestrated and automated with minimal manual intervention. Which THREE options should you include in your design? (Choose three.)

Trap 1: Use BigQuery scheduled queries to run the training script on a…

BigQuery scheduled queries are for SQL queries, not running ML training jobs.

Trap 2: Use AI Platform Notebooks to schedule the training job on a…

Notebooks are for interactive development, not scheduling production pipelines.

Study all Automating and orchestrating ML pipelines common traps →

A
Use BigQuery scheduled queries to run the training script on a schedule.
Why wrong: BigQuery scheduled queries are for SQL queries, not running ML training jobs.
B
Use Vertex AI Pipelines to define the ML pipeline as a Directed Acyclic Graph (DAG) of components.
Vertex AI Pipelines is purpose-built for ML pipelines.
C
Use AI Platform Notebooks to schedule the training job on a recurring basis.
Why wrong: Notebooks are for interactive development, not scheduling production pipelines.
D
Use Cloud Build and Cloud Functions to trigger the pipeline when new training data arrives in Cloud Storage.
Event-driven triggers automate pipeline execution on data arrival.
E
Use Cloud Composer to orchestrate the pipeline steps, including data extraction, preprocessing, training, and deployment.
Cloud Composer (Airflow) is designed for orchestrating complex workflows with dependencies.

Full breakdown with real-world context →

Question 8easymultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

A developer creates a Cloud Build trigger that runs a training pipeline whenever code is pushed to the main branch of the repository. The trigger is configured to use a source archive stored in Cloud Storage. After pushing code to main, the build fails with the error shown. What is the most likely cause of this failure?

Exhibit

Refer to the exhibit.

```
symptom: Cloud Build trigger fails with: Build failed: could not resolve source: fetching source: fetching storage object: object not found

trigger configuration:
  event: push to branch main
  repository: my-repo
  included files: 'train/**'
  excluded files: 'test/**'
  source: gs://my-bucket/source.tar.gz
```

Trap 1: The build configuration file is missing from the source archive.

The error occurs during source fetching, before the build configuration is read.

Trap 2: The included files filter 'train/**' excludes all files outside the…

The included files filter controls which files trigger the build, not the source content.

Trap 3: The service account does not have storage.objectViewer permission…

The error message says 'object not found', not permission denied.

Study all Automating and orchestrating ML pipelines common traps →

A
The build configuration file is missing from the source archive.
Why wrong: The error occurs during source fetching, before the build configuration is read.
B
The included files filter 'train/**' excludes all files outside the train directory, causing the build to have no source.
Why wrong: The included files filter controls which files trigger the build, not the source content.
C
The source archive is not being updated when code is pushed, so the trigger tries to fetch an old or nonexistent object.
The trigger points to a static archive; pushing new code does not update the archive, leading to missing source.
D
The service account does not have storage.objectViewer permission on the bucket.
Why wrong: The error message says 'object not found', not permission denied.

Full breakdown with real-world context →

Question 9mediummultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

Your team manages a production ML pipeline on Google Cloud that trains a fraud detection model every 6 hours using new transaction data. The pipeline steps are: (1) Cloud Function triggered by new files in Cloud Storage to validate data, (2) Dataflow job for feature engineering, (3) Vertex AI CustomJob for training, (4) Cloud Function to deploy the model to a Vertex AI endpoint after evaluation. You notice that the pipeline sometimes fails during the Dataflow job step with an error: 'Workflow failed. Causes: The job encountered a system error. Please try again later.' The error occurs sporadically, and retrying the pipeline manually usually succeeds. The team needs a reliable automated solution. What should you do?

Trap 1: Schedule the pipeline to run less frequently to reduce load on the…

Reducing frequency does not fix the sporadic errors and reduces model freshness.

Trap 2: Use Cloud Tasks to queue the Dataflow job and retry on failure.

Cloud Tasks is for asynchronous task execution, not orchestrating a multi-step pipeline with dependencies.

Trap 3: Increase the number of Dataflow workers and use flexRS to handle…

Transient system errors are not resolved by scaling resources; the job still may fail.

Study all Automating and orchestrating ML pipelines common traps →

A
Schedule the pipeline to run less frequently to reduce load on the Dataflow service.
Why wrong: Reducing frequency does not fix the sporadic errors and reduces model freshness.
B
Use Cloud Tasks to queue the Dataflow job and retry on failure.
Why wrong: Cloud Tasks is for asynchronous task execution, not orchestrating a multi-step pipeline with dependencies.
C
Increase the number of Dataflow workers and use flexRS to handle transient errors.
Why wrong: Transient system errors are not resolved by scaling resources; the job still may fail.
D
Orchestrate the pipeline using Cloud Composer with retry policies on the Dataflow operator.
Cloud Composer (Airflow) can manage the pipeline DAG with automatic retries and dependencies.

Full breakdown with real-world context →

Question 10mediumdrag order

Read the full Automating and orchestrating ML pipelines explanation →

Drag and drop the steps to set up a BigQuery ML linear regression model for forecasting in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 11mediumdrag order

Read the full Automating and orchestrating ML pipelines explanation →

Drag and drop the steps to set up a batch prediction job using Vertex AI in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

5Step 5

Question 12mediummatching

Read the full Automating and orchestrating ML pipelines explanation →

Match each Google Cloud AI/ML service to its primary purpose.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

End-to-end ML platform for building, deploying, and managing models

Train high-quality custom ML models with minimal effort

Managed service for distributed training of ML models

Custom ASIC for accelerating ML training workloads

Create and execute ML models using SQL queries

Question 13mediummatching

Read the full Automating and orchestrating ML pipelines explanation →

Match each MLOps practice to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Continuous integration and deployment for ML pipelines

Track and manage different model iterations

Monitor for changes in data or model performance over time

Schedule or trigger model retraining based on conditions

Compare model versions in production with traffic splitting

Question 14easymultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

An MLOps team wants to automate the retraining of a model each time new data arrives in a BigQuery table. What is the most efficient Google Cloud service to orchestrate this pipeline?

Trap 1: Cloud Composer with an Airflow DAG

Cloud Composer is a managed Airflow environment, but for simpler ML retraining, Vertex AI Pipelines is more streamlined and purpose-built.

Trap 2: Dataflow pipeline with a periodic trigger

Dataflow is for data processing, not for orchestrating ML training and deployment steps.

Trap 3: Cloud Functions triggered by BigQuery events

Cloud Functions can trigger on BigQuery events, but managing pipeline steps becomes cumbersome without a dedicated orchestration service.

Study all Automating and orchestrating ML pipelines common traps →

A
Cloud Composer with an Airflow DAG
Why wrong: Cloud Composer is a managed Airflow environment, but for simpler ML retraining, Vertex AI Pipelines is more streamlined and purpose-built.
B
Dataflow pipeline with a periodic trigger
Why wrong: Dataflow is for data processing, not for orchestrating ML training and deployment steps.
C
Cloud Functions triggered by BigQuery events
Why wrong: Cloud Functions can trigger on BigQuery events, but managing pipeline steps becomes cumbersome without a dedicated orchestration service.
D
Vertex AI Pipelines with a schedule trigger
Vertex AI Pipelines natively supports scheduled triggers and is the recommended service for ML pipeline orchestration.

Full breakdown with real-world context →

Question 15easymultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

A data scientist has trained a model using Vertex AI Training and wants to deploy it to a Vertex AI Endpoint for online predictions. Which orchestration service should be used to automate the deployment step after training completes?

Trap 1: App Engine

App Engine is a hosting service, not for ML pipeline orchestration.

Trap 2: Cloud Functions

Cloud Functions can be used but requires manual setup to coordinate steps; Vertex AI Pipelines is purpose-built for this.

Trap 3: Cloud Build

Cloud Build is for building and testing code, not for orchestrating ML model deployment.

Study all Automating and orchestrating ML pipelines common traps →

A
Vertex AI Pipelines
Vertex AI Pipelines allows you to define a pipeline with training and deployment components, automating the workflow.
B
App Engine
Why wrong: App Engine is a hosting service, not for ML pipeline orchestration.
C
Cloud Functions
Why wrong: Cloud Functions can be used but requires manual setup to coordinate steps; Vertex AI Pipelines is purpose-built for this.
D
Cloud Build
Why wrong: Cloud Build is for building and testing code, not for orchestrating ML model deployment.

Full breakdown with real-world context →

Question 16easymultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

A company uses Cloud Composer to orchestrate their ML pipelines. They notice that tasks are being queued but not executed, causing delays. What is the most likely cause?

Trap 1: The Airflow web server is down

The web server is for UI; the scheduler and workers handle execution.

Trap 2: The DAG file is corrupted

A corrupted DAG would typically cause a parse error and the DAG would not appear, not queue tasks.

Trap 3: The Cloud Storage bucket containing DAGs is not accessible

Inaccessible DAGs would prevent the DAG from being loaded, not cause queued tasks.

Study all Automating and orchestrating ML pipelines common traps →

A
The Airflow web server is down
Why wrong: The web server is for UI; the scheduler and workers handle execution.
B
The DAG file is corrupted
Why wrong: A corrupted DAG would typically cause a parse error and the DAG would not appear, not queue tasks.
C
The Cloud Storage bucket containing DAGs is not accessible
Why wrong: Inaccessible DAGs would prevent the DAG from being loaded, not cause queued tasks.
D
The Airflow worker resources are exhausted
If workers are busy or the cluster is under-provisioned, tasks will be queued.

Full breakdown with real-world context →

Question 17mediummultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

An ML engineer is using Vertex AI Pipelines and wants to reuse a trained model across multiple pipeline runs without retraining each time. Which artifact management strategy should be used?

Trap 1: Store the model in BigQuery as a ML model

BigQuery ML models are for BigQuery, not for arbitrary model artifacts.

Trap 2: Use Cloud Functions to cache the model

Cloud Functions is not designed for artifact storage.

Trap 3: Save the model to a Cloud Storage bucket and reference by path

This works but without metadata tracking, it's hard to manage versions and dependencies; ML Metadata is recommended.

Study all Automating and orchestrating ML pipelines common traps →

A
Store the model in BigQuery as a ML model
Why wrong: BigQuery ML models are for BigQuery, not for arbitrary model artifacts.
B
Use Cloud Functions to cache the model
Why wrong: Cloud Functions is not designed for artifact storage.
C
Save the model to a Cloud Storage bucket and reference by path
Why wrong: This works but without metadata tracking, it's hard to manage versions and dependencies; ML Metadata is recommended.
D
Use Vertex AI ML Metadata to track and retrieve model artifacts
ML Metadata provides lineage and artifact tracking, enabling efficient reuse across pipelines.

Full breakdown with real-world context →

Question 18mediummultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

A team wants to implement CI/CD for their ML models using Cloud Build. They have a pipeline that trains a model and deploys it. What is the best practice for triggering the pipeline when a new commit is pushed to the source repository?

Trap 1: Set up a Cloud Scheduler job to poll the repository periodically

Scheduling is not event-driven and is inefficient.

Trap 2: Deploy a custom web service on App Engine to call Cloud Build API

Overly complex; Cloud Build triggers are simpler.

Trap 3: Use Pub/Sub to notify Cloud Build of new commits

While possible, it's not the most direct; Cloud Build triggers natively integrate with repositories.

Study all Automating and orchestrating ML pipelines common traps →

A
Set up a Cloud Scheduler job to poll the repository periodically
Why wrong: Scheduling is not event-driven and is inefficient.
B
Deploy a custom web service on App Engine to call Cloud Build API
Why wrong: Overly complex; Cloud Build triggers are simpler.
C
Use Pub/Sub to notify Cloud Build of new commits
Why wrong: While possible, it's not the most direct; Cloud Build triggers natively integrate with repositories.
D
Configure a Cloud Build trigger on the source repository (e.g., Cloud Source Repositories, GitHub)
Cloud Build supports triggers that automatically start a build upon a push to the repository.

Full breakdown with real-world context →

Question 19mediummultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

A data-processing pipeline using Dataflow needs to incorporate a custom ML prediction step. The team wants to maintain fast processing and minimize latency. What is the optimal approach?

Trap 1: Write the data to Cloud Storage, trigger a Cloud Function to call…

This adds latency and extra components.

Trap 2: Send data to a Pub/Sub topic and have a separate subscriber that…

Adds complexity and latency; DoFn is simpler.

Trap 3: Stream data through Cloud Functions that serve predictions and…

Cloud Functions have time and concurrency limits, not ideal for streaming.

Study all Automating and orchestrating ML pipelines common traps →

A
Write the data to Cloud Storage, trigger a Cloud Function to call the model, and write results back
Why wrong: This adds latency and extra components.
B
Use a custom ParDo transform in Dataflow that calls Vertex AI Prediction API directly
Inline calls within Dataflow are efficient and keep the pipeline linear.
C
Send data to a Pub/Sub topic and have a separate subscriber that runs predictions
Why wrong: Adds complexity and latency; DoFn is simpler.
D
Stream data through Cloud Functions that serve predictions and write to BigQuery
Why wrong: Cloud Functions have time and concurrency limits, not ideal for streaming.

Full breakdown with real-world context →

Question 20hardmultiple choice

Read the full Automating and orchestrating ML pipelines explanation →

A company is using Vertex AI Pipelines with reusable components. They observe that a component that performs hyperparameter tuning is failing intermittently with a 'ResourceExhausted' error. The component is configured with a small custom service account. What is the most likely cause?

Trap 1: The component code has a bug causing infinite recursion

Infinite recursion would cause stack overflow or timeout, not ResourceExhausted typically.

Trap 2: The KFP executor is not properly configured

KFP executor handles component execution; the error is from the AI Platform resource creation.

Trap 3: The pipeline system memory is insufficient for the component

Memory is allocated per component; tuning jobs use separate resources.

Study all Automating and orchestrating ML pipelines common traps →

A
The component code has a bug causing infinite recursion
Why wrong: Infinite recursion would cause stack overflow or timeout, not ResourceExhausted typically.
B
The KFP executor is not properly configured
Why wrong: KFP executor handles component execution; the error is from the AI Platform resource creation.
C
The service account does not have sufficient quotas or permissions to create the required number of trials or workers
Hyperparameter tuning often spawns multiple trial jobs; quota limits on AI Platform training jobs or compute resources can cause this error.
D
The pipeline system memory is insufficient for the component
Why wrong: Memory is allocated per component; tuning jobs use separate resources.

Full breakdown with real-world context →

Continue with 20-question session →

Free account

Track your progress over time

Create a free account to save your results and see which topics improve across sessions.

Focused Automating and orchestrating ML pipelines sessions

Start a Automating and orchestrating ML pipelines only practice session

Every question in these sessions is drawn from the Automating and orchestrating ML pipelines domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Automating and orchestrating ML pipelines questions →Mixed PMLE session

Frequently asked questions

What does the PMLE exam test about Automating and orchestrating ML pipelines?: Automating and orchestrating ML pipelines questions test whether you can apply the concept in context, not just recognise a definition.
How should I use these practice questions?: Select your answer before revealing the explanation. Then read why each option is right or wrong — this active recall approach builds retention far faster than re-reading notes.
Can I practise just Automating and orchestrating ML pipelines questions in a focused session?: Yes — the session launcher on this page draws every question from the Automating and orchestrating ML pipelines domain. Use a 10-question session first to gauge your baseline, then move to 20 or 30 once the weak spots are clear.
Where can I practise other PMLE topics?: Use the topic links above to move to related areas, or go back to the PMLE question bank to see all topics.
Are these real exam questions or dumps?: These are original practice questions written to test the same concepts the PMLE exam covers. They are not copied from any real exam or dump site.

Automating and orchestrating ML pipelines only

10 questions 20 questions 30 questions 50 questions

Mixed PMLE session

Track your progress

A free account saves results across sessions and highlights which topics need work.

Study resources

All PMLE questions Automating and orchestrating ML pipelines domain overview PMLE exam guide

Exam traps to avoid

▸Answering from memory before reading the full scenario.
▸Missing a constraint such as cost, availability, security, scope or command context.
▸Choosing a broad answer when the question asks for the most specific fix.
▸Ignoring why the wrong options are tempting.

Automating and orchestrating ML pipelines practice questions

What to know about Automating and orchestrating ML pipelines

Common Automating and orchestrating ML pipelines exam traps

Automating and orchestrating ML pipelines questions

An ML team is designing an automated pipeline to retrain a recommendation model every day using new user interaction data stored in BigQuery. The pipeline must be cost-efficient, scalable, and require minimal manual intervention. Which two approaches should they consider?

Exhibit

Drag and drop the steps to set up a BigQuery ML linear regression model for forecasting in the correct order.

Drag and drop the steps to set up a batch prediction job using Vertex AI in the correct order.

Match each Google Cloud AI/ML service to its primary purpose.

Match each MLOps practice to its description.

An MLOps team wants to automate the retraining of a model each time new data arrives in a BigQuery table. What is the most efficient Google Cloud service to orchestrate this pipeline?

A data scientist has trained a model using Vertex AI Training and wants to deploy it to a Vertex AI Endpoint for online predictions. Which orchestration service should be used to automate the deployment step after training completes?

A company uses Cloud Composer to orchestrate their ML pipelines. They notice that tasks are being queued but not executed, causing delays. What is the most likely cause?

An ML engineer is using Vertex AI Pipelines and wants to reuse a trained model across multiple pipeline runs without retraining each time. Which artifact management strategy should be used?

A team wants to implement CI/CD for their ML models using Cloud Build. They have a pipeline that trains a model and deploys it. What is the best practice for triggering the pipeline when a new commit is pushed to the source repository?

A data-processing pipeline using Dataflow needs to incorporate a custom ML prediction step. The team wants to maintain fast processing and minimize latency. What is the optimal approach?

A company is using Vertex AI Pipelines with reusable components. They observe that a component that performs hyperparameter tuning is failing intermittently with a 'ResourceExhausted' error. The component is configured with a small custom service account. What is the most likely cause?

Track your progress over time

Start a Automating and orchestrating ML pipelines only practice session

Related PMLE topic practice pages

Scaling prototypes into ML models practice questions