PMLE · topic practice

Collaborating within and across teams to manage data and models practice questions

Q: How should I use these Collaborating within and across teams to manage data and models 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.

Q: Can I practise just Collaborating within and across teams to manage data and models 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 Collaborating within and across teams to manage data and models domain.

Practise Google Professional Machine Learning Engineer Collaborating within and across teams to manage data and models 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: Collaborating within and across teams to manage data and models

Practice 10 questions Browse domain →

What the exam tests

What to know about Collaborating within and across teams to manage data and models

Collaborating within and across teams to manage data and models 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 Collaborating within and across teams to manage data and models 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

Collaborating within and across teams to manage data and models questions

20 questions · select your answer, then reveal the explanation

Question 1mediummultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A data science team uses a shared Cloud Storage bucket to store training datasets. They notice that some team members accidentally overwrite existing datasets, causing issues with reproducibility. Which approach best prevents accidental overwrites while maintaining collaboration?

Trap 1: Use a single shared service account with strict IAM roles that…

Cloud Storage does not support append-only at object level.

Trap 2: Require team members to manually rename files before uploading.

Manual process is error-prone and not enforced.

Trap 3: Set bucket permissions to read-only for all team members except the…

This prevents any writes, hindering collaboration.

Study all Collaborating within and across teams to manage data and models common traps →

A
Use a single shared service account with strict IAM roles that allow only append operations.
Why wrong: Cloud Storage does not support append-only at object level.
B
Require team members to manually rename files before uploading.
Why wrong: Manual process is error-prone and not enforced.
C
Set bucket permissions to read-only for all team members except the data owner.
Why wrong: This prevents any writes, hindering collaboration.
D
Enable object versioning on the bucket and use lifecycle rules to manage versions.
Versioning allows recovery of previous versions if overwritten.

Full breakdown with real-world context →

Question 2hardmultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A machine learning engineer needs to share a trained model with the product team for integration. The model is stored in Cloud Storage, and the product team’s service account needs read access. The engineer wants to follow the principle of least privilege. Which IAM configuration should be used?

Trap 1: Generate a signed URL with read access and share it with the…

Signed URLs do not require IAM but may expire and are less secure for ongoing access.

Trap 2: Grant the product team's service account the…

Grants write/delete permissions, not least privilege.

Trap 3: Grant the product team's service account the…

Project-level grants access to all buckets in the project.

Study all Collaborating within and across teams to manage data and models common traps →

A
Generate a signed URL with read access and share it with the product team.
Why wrong: Signed URLs do not require IAM but may expire and are less secure for ongoing access.
B
Grant the product team's service account the roles/storage.objectViewer role at the bucket level.
Bucket-level grants read access to objects in that bucket only, following least privilege.
C
Grant the product team's service account the roles/storage.objectAdmin role at the bucket level.
Why wrong: Grants write/delete permissions, not least privilege.
D
Grant the product team's service account the roles/storage.objectViewer role at the project level.
Why wrong: Project-level grants access to all buckets in the project.

Full breakdown with real-world context →

Question 3easymultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A team is using Vertex AI Pipelines to automate their ML workflow. They want to ensure that pipeline runs are reproducible and that artifacts are tracked. Which feature should they use?

Trap 1: Vertex AI Feature Store

Feature store is for managing ML features.

Trap 2: Vertex AI Model Registry

Model registry tracks model versions but not the full pipeline run.

Trap 3: Vertex AI Endpoints

Endpoints are for serving predictions.

Study all Collaborating within and across teams to manage data and models common traps →

A
Vertex AI Feature Store
Why wrong: Feature store is for managing ML features.
B
Vertex AI Experiments
Experiments track parameters, metrics, and artifacts for each run.
C
Vertex AI Model Registry
Why wrong: Model registry tracks model versions but not the full pipeline run.
D
Vertex AI Endpoints
Why wrong: Endpoints are for serving predictions.

Full breakdown with real-world context →

Question 4mediummultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A team of data scientists and ML engineers is collaborating on a project using Vertex AI Workbench. They need to share notebooks and code, but want to avoid conflicts and maintain a history of changes. Which approach should they use?

Trap 1: Email notebook files to each other and manually merge changes.

Manual merging is error-prone and not scalable.

Trap 2: Store notebooks in a shared Cloud Storage bucket and access them…

No version control or conflict resolution.

Trap 3: Use Vertex AI Experiments to share notebook outputs.

Experiments track runs, not code collaboration.

Study all Collaborating within and across teams to manage data and models common traps →

A
Email notebook files to each other and manually merge changes.
Why wrong: Manual merging is error-prone and not scalable.
B
Store notebooks in a shared Cloud Storage bucket and access them simultaneously.
Why wrong: No version control or conflict resolution.
C
Use Vertex AI Experiments to share notebook outputs.
Why wrong: Experiments track runs, not code collaboration.
D
Use a git repository (e.g., Cloud Source Repositories) to manage code and notebooks.
Git provides branching, merging, and history.

Full breakdown with real-world context →

Question 5hardmulti select

Read the full Collaborating within and across teams to manage data and models explanation →

A machine learning team is deploying a model for real-time predictions using Vertex AI. They need to ensure that the deployment follows best practices for collaboration and governance. Which TWO actions should they take?

Trap 1: Store all model artifacts in a local file system to reduce latency.

Local storage is not scalable or collaborative.

Trap 2: Manually configure autoscaling parameters for the endpoint.

Vertex AI can auto-scale; manual tuning not required.

Trap 3: Allow any team member to deploy directly to production without…

Missing governance and testing.

Study all Collaborating within and across teams to manage data and models common traps →

A
Use a continuous integration/continuous deployment (CI/CD) pipeline to deploy model versions.
CI/CD ensures consistent, repeatable deployments.
B
Store all model artifacts in a local file system to reduce latency.
Why wrong: Local storage is not scalable or collaborative.
C
Enable model monitoring to detect data drift and performance degradation.
Monitoring is essential for ongoing model quality.
D
Manually configure autoscaling parameters for the endpoint.
Why wrong: Vertex AI can auto-scale; manual tuning not required.
E
Allow any team member to deploy directly to production without review.
Why wrong: Missing governance and testing.

Full breakdown with real-world context →

Question 6hardmultiple choice

Read the full NAT/PAT explanation →

A financial services company uses Vertex AI Pipelines to train and deploy models for fraud detection. The ML team consists of data scientists who develop models and ML engineers who deploy them. They use a CI/CD pipeline with Cloud Build to build and push Docker images to Artifact Registry, then trigger Vertex AI Pipelines. Recently, the team noticed that a model deployed to production was trained on a dataset that had not been approved by the data governance team. Upon investigation, they found that a data scientist accidentally used an unapproved version of the training data by specifying a Cloud Storage path that was not the latest approved dataset. The company needs to enforce that only approved datasets are used in training jobs. Which approach should they take?

Trap 1: Implement a manual approval process where data scientists request…

Manual process is slow and not enforceable at runtime.

Trap 2: After training, run a validation step that checks if the dataset…

This is reactive and still allows unapproved training to proceed initially.

Trap 3: Restrict all Cloud Storage buckets to be read-only for the data…

This blocks data scientists from accessing any data, preventing even approved experimentation.

Study all Collaborating within and across teams to manage data and models common traps →

A
Implement a manual approval process where data scientists request dataset paths from the data governance team before each training run.
Why wrong: Manual process is slow and not enforceable at runtime.
B
After training, run a validation step that checks if the dataset used matches the latest approved version, and roll back if not.
Why wrong: This is reactive and still allows unapproved training to proceed initially.
C
Use a curated dataset registry in BigQuery or Cloud Storage with IAM conditions that allow access only to datasets tagged as 'approved'. Modify the CI/CD pipeline to pass only approved dataset references to the training job.
This automates governance by restricting training to approved datasets via IAM and pipeline configuration.
D
Restrict all Cloud Storage buckets to be read-only for the data scientists, and have ML engineers copy approved datasets to a separate bucket.
Why wrong: This blocks data scientists from accessing any data, preventing even approved experimentation.

Full breakdown with real-world context →

Question 7easymultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A data science team is using a shared Cloud Storage bucket to store training data. Multiple team members are simultaneously uploading new data files, and occasionally the wrong version of a file is used in training, leading to inconsistent results. Which best practice should the team implement to ensure data version consistency?

Trap 1: Use Cloud Composer to schedule a daily snapshot of the Cloud…

Cloud Composer orchestrates workflows but does not automatically version files.

Trap 2: Migrate all training data to BigQuery and use time-travel queries…

BigQuery time travel is for querying historical table snapshots, not for versioning individual files.

Trap 3: Restrict write access to the bucket to only one team member using…

This creates a bottleneck and does not prevent version conflicts.

Study all Collaborating within and across teams to manage data and models common traps →

A
Use Cloud Composer to schedule a daily snapshot of the Cloud Storage bucket.
Why wrong: Cloud Composer orchestrates workflows but does not automatically version files.
B
Migrate all training data to BigQuery and use time-travel queries to access historical versions.
Why wrong: BigQuery time travel is for querying historical table snapshots, not for versioning individual files.
C
Enable object versioning on the Cloud Storage bucket and use the version ID when referencing data files.
Object versioning provides a way to keep multiple versions of an object, ensuring consistency.
D
Restrict write access to the bucket to only one team member using IAM roles.
Why wrong: This creates a bottleneck and does not prevent version conflicts.

Full breakdown with real-world context →

Question 8mediummulti select

Read the full Collaborating within and across teams to manage data and models explanation →

A machine learning team is collaborating on a project using Vertex AI Experiments to track model training runs. They want to ensure that all team members can reproduce any experiment by using the same code, data, and environment. Which THREE actions should the team take?

Trap 1: Share a service account key with all team members so they can…

Sharing keys is a security risk and not a standard reproducibility practice.

Trap 2: Use Vertex AI's hyperparameter tuning job to automatically find the…

Automatic tuning can change parameters between runs, making exact reproduction difficult.

Study all Collaborating within and across teams to manage data and models common traps →

A
Store the training code in a Cloud Source Repository and tag commits with the experiment ID.
This ensures the exact code version is tied to the experiment.
B
Build a custom container image for training and push it to Artifact Registry with a fixed tag.
A fixed container image ensures the same environment is used across runs.
C
Record the path and version of the training dataset in the experiment parameters.
This allows others to use the exact same data for reproduction.
D
Share a service account key with all team members so they can access the same resources.
Why wrong: Sharing keys is a security risk and not a standard reproducibility practice.
E
Use Vertex AI's hyperparameter tuning job to automatically find the best parameters.
Why wrong: Automatic tuning can change parameters between runs, making exact reproduction difficult.

Full breakdown with real-world context →

Question 9hardmultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A team has set up the IAM policy above on a Vertex AI project. Alice, a data scientist, reports that she cannot create a Vertex AI Training custom job using a pre-built container. Other data scientists in the group 'data-scientists@example.com' have the same issue. What is the most likely cause?

Exhibit

Refer to the exhibit.

```
{
  "bindings": [
    {
      "role": "roles/aiplatform.user",
      "members": [
        "user:alice@example.com",
        "group:data-scientists@example.com"
      ]
    },
    {
      "role": "roles/aiplatform.customCodeServiceAgent",
      "members": [
        "serviceAccount:vertex-ai@project.iam.gserviceaccount.com"
      ]
    }
  ],
  "etag": "BwXahRc1X3w="
}
```

Trap 1: The Vertex AI Custom Code Service Agent service account is missing…

The service account has a different role and does not affect user permissions.

Trap 2: Alice is not included in the 'data-scientists@example.com' group.

The exhibit shows the group is in the policy, and Alice is presumably a member; the issue is with the role, not group membership.

Trap 3: The service account 'vertex-ai@project.iam.gserviceaccount.com'…

The issue is about job creation, not data access.

Study all Collaborating within and across teams to manage data and models common traps →

A
The 'roles/aiplatform.user' role does not grant the permission to create custom training jobs.
Creating custom jobs requires 'aiplatform.customJobs.create', which is not in the aiplatform.user role.
B
The Vertex AI Custom Code Service Agent service account is missing the 'roles/aiplatform.user' role.
Why wrong: The service account has a different role and does not affect user permissions.
C
Alice is not included in the 'data-scientists@example.com' group.
Why wrong: The exhibit shows the group is in the policy, and Alice is presumably a member; the issue is with the role, not group membership.
D
The service account 'vertex-ai@project.iam.gserviceaccount.com' does not have permission to access the training data.
Why wrong: The issue is about job creation, not data access.

Full breakdown with real-world context →

Question 10mediumdrag order

Read the full Collaborating within and across teams to manage data and models explanation →

Drag and drop the steps to perform a hyperparameter tuning job on 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 11mediummatching

Read the full Collaborating within and across teams to manage data and models explanation →

Match each ML pipeline component to its description.

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

Concepts

Matches

Production ML pipeline framework by Google

ML toolkit for Kubernetes-based workflows

Unified stream and batch data processing service

Managed Apache Airflow workflow orchestration

Serverless ML pipeline orchestration on Vertex AI

Question 12mediummultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A company has multiple teams that need to access and manage ML models in Vertex AI. Different teams require different permission levels: the data science team should be able to create and update models, while the MLOps team should have full control. What is the recommended approach to manage access?

Trap 1: Grant the 'aiplatform.user' role to a Google Group containing all…

Giving all users the same role does not differentiate permissions between teams.

Trap 2: Use labels and tags on models to control access

Labels and tags are for metadata and billing, not IAM permissions.

Trap 3: Create a separate Google Cloud project for each team

Projects per team increase overhead and prevent easy sharing of models across teams.

Study all Collaborating within and across teams to manage data and models common traps →

A
Grant the 'aiplatform.user' role to a Google Group containing all users
Why wrong: Giving all users the same role does not differentiate permissions between teams.
B
Use folders in Google Cloud Resource Manager and assign IAM roles at the folder level
Folders allow hierarchical policy management, and IAM roles can be scoped appropriately for each team.
C
Use labels and tags on models to control access
Why wrong: Labels and tags are for metadata and billing, not IAM permissions.
D
Create a separate Google Cloud project for each team
Why wrong: Projects per team increase overhead and prevent easy sharing of models across teams.

Full breakdown with real-world context →

Question 13easymultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A data scientist needs to share a BigQuery dataset with a colleague in a different team so they can run queries. What is the simplest and most secure way to grant access?

Trap 1: Export the dataset to Cloud Storage and share the bucket

This creates a copy and requires additional permissions, and data becomes stale.

Trap 2: Share the service account key of a BigQuery job user with the…

Service account keys should be kept confidential and not shared.

Trap 3: Add the colleague's account as a Project Viewer on the entire…

Project Viewer grants access to all resources in the project, which is too broad.

Study all Collaborating within and across teams to manage data and models common traps →

A
Export the dataset to Cloud Storage and share the bucket
Why wrong: This creates a copy and requires additional permissions, and data becomes stale.
B
Add the colleague's account as a BigQuery Data Viewer on the dataset
Direct IAM binding on the dataset provides least-privilege access.
C
Share the service account key of a BigQuery job user with the colleague
Why wrong: Service account keys should be kept confidential and not shared.
D
Add the colleague's account as a Project Viewer on the entire project
Why wrong: Project Viewer grants access to all resources in the project, which is too broad.

Full breakdown with real-world context →

Question 14hardmultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A team is building a CI/CD pipeline for ML using Cloud Build. The pipeline trains a model and deploys it to Vertex AI. Recently, a change in the data processing step caused the model to be trained with a different data version, leading to a failed deployment because the model was invalid. How should the team prevent this in the future?

Trap 1: Add a manual review step before training

Manual reviews do not guarantee reproducibility and are not scalable.

Trap 2: Pin all library versions in the Docker image

Library versions are important but do not control data versioning.

Trap 3: Schedule a cron job to check for data changes

A cron job does not enforce that the training step uses the correct version.

Study all Collaborating within and across teams to manage data and models common traps →

A
Add a manual review step before training
Why wrong: Manual reviews do not guarantee reproducibility and are not scalable.
B
Pin all library versions in the Docker image
Why wrong: Library versions are important but do not control data versioning.
C
Use a data versioning tool (e.g., DVC) to track datasets and ensure the pipeline always uses the correct version
Data versioning ensures reproducibility and consistency across pipeline runs.
D
Schedule a cron job to check for data changes
Why wrong: A cron job does not enforce that the training step uses the correct version.

Full breakdown with real-world context →

Question 15mediummultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

Two teams are collaborating on a project and want to use a shared Feature Store in Vertex AI. They need to ensure that features are discoverable and that access is controlled. What is the best practice?

Trap 1: Export features to CSV files in Cloud Storage and share the bucket

CSV files are not a scalable or discoverable solution.

Trap 2: Build a custom feature pipeline using Dataflow and store in Cloud…

This adds maintenance overhead and lacks built-in feature store capabilities.

Trap 3: Each team stores features in their own BigQuery table and shares…

BigQuery tables lack feature store capabilities like monitoring and online serving.

Study all Collaborating within and across teams to manage data and models common traps →

A
Export features to CSV files in Cloud Storage and share the bucket
Why wrong: CSV files are not a scalable or discoverable solution.
B
Build a custom feature pipeline using Dataflow and store in Cloud SQL
Why wrong: This adds maintenance overhead and lacks built-in feature store capabilities.
C
Each team stores features in their own BigQuery table and shares the table
Why wrong: BigQuery tables lack feature store capabilities like monitoring and online serving.
D
Use Vertex AI Feature Store and grant appropriate IAM roles to each team
Vertex AI Feature Store provides a unified repository with access control and discovery.

Full breakdown with real-world context →

Question 16easymultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A team is using Cloud Composer to orchestrate ML workflows. They want to allow multiple data scientists to contribute DAGs without interfering with each other. What is the recommended approach?

Trap 1: Give each data scientist write access to the DAGs folder in Cloud…

Direct write access can lead to conflicts and disrupted workflows.

Trap 2: Use a complex naming convention for DAG files to avoid overwriting

Naming conventions do not prevent overwriting or conflicts.

Trap 3: Create a separate Cloud Composer environment for each data scientist

This is costly and leads to resource fragmentation.

Study all Collaborating within and across teams to manage data and models common traps →

A
Give each data scientist write access to the DAGs folder in Cloud Storage
Why wrong: Direct write access can lead to conflicts and disrupted workflows.
B
Use a complex naming convention for DAG files to avoid overwriting
Why wrong: Naming conventions do not prevent overwriting or conflicts.
C
Store DAGs in a source control repository and use CI/CD to deploy to Cloud Composer
Version control and CI/CD provide collaboration, testing, and safe deployment.
D
Create a separate Cloud Composer environment for each data scientist
Why wrong: This is costly and leads to resource fragmentation.

Full breakdown with real-world context →

Question 17hardmultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A company needs to maintain an audit trail of model changes for compliance. Multiple teams will be updating models. What is the best approach to track who created, modified, or deployed each model version?

Trap 1: Enable Cloud Storage audit logs and require all model files to be…

This does not capture model-specific actions like deployment or evaluation.

Trap 2: Use Cloud Logging to collect logs from all services and search for…

This is cumbersome and does not provide structured metadata.

Trap 3: Ask team members to maintain a shared spreadsheet of changes

Manual logging is unreliable and not auditable.

Study all Collaborating within and across teams to manage data and models common traps →

A
Enable Cloud Storage audit logs and require all model files to be stored in a bucket
Why wrong: This does not capture model-specific actions like deployment or evaluation.
B
Use Cloud Logging to collect logs from all services and search for model names
Why wrong: This is cumbersome and does not provide structured metadata.
C
Use Vertex AI Experiments and Metadata to track model lineage and audit logs
Vertex AI provides built-in audit capabilities with user attribution and metadata.
D
Ask team members to maintain a shared spreadsheet of changes
Why wrong: Manual logging is unreliable and not auditable.

Full breakdown with real-world context →

Question 18mediummultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

A team is using AI Platform Data Labeling Service to label data for a classification model. They want to allow a labeler from a different team to work on the same dataset. What is the correct way to grant access?

Trap 1: Add the labeler's account as a Project Editor on the project

Project Editor grants broad permissions beyond labeling.

Trap 2: Share the Cloud Storage bucket containing the data with the labeler

Bucket access does not grant access to labeling tasks.

Trap 3: Export the dataset and have the labeler create a new dataset

This creates duplicate work and does not allow collaboration on the same task.

Study all Collaborating within and across teams to manage data and models common traps →

A
Add the labeler's account as a Project Editor on the project
Why wrong: Project Editor grants broad permissions beyond labeling.
B
Share the Cloud Storage bucket containing the data with the labeler
Why wrong: Bucket access does not grant access to labeling tasks.
C
Export the dataset and have the labeler create a new dataset
Why wrong: This creates duplicate work and does not allow collaboration on the same task.
D
Add the labeler as a participant in the labeling task and assign IAM roles on the dataset
The Data Labeling Service allows adding participants to tasks, and IAM roles control access.

Full breakdown with real-world context →

Question 19easymultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

To enable collaboration on notebook-based experiments across teams, what is the recommended approach in Google Cloud?

Trap 1: Share Docker images containing the notebook environment

Docker images provide environment consistency but not collaborative editing.

Trap 2: Each team member works on their own local Jupyter notebook and…

This does not allow real-time collaboration or version control.

Trap 3: Store notebooks in a Cloud Storage bucket and open them with Vertex…

Storage alone does not provide concurrent editing and collaboration.

Study all Collaborating within and across teams to manage data and models common traps →

A
Use Colab Enterprise notebooks with shared runtimes and IAM permissions
Colab Enterprise enables collaborative editing and shared compute resources.
B
Share Docker images containing the notebook environment
Why wrong: Docker images provide environment consistency but not collaborative editing.
C
Each team member works on their own local Jupyter notebook and shares screenshots
Why wrong: This does not allow real-time collaboration or version control.
D
Store notebooks in a Cloud Storage bucket and open them with Vertex AI Workbench
Why wrong: Storage alone does not provide concurrent editing and collaboration.

Full breakdown with real-world context →

Question 20hardmultiple choice

Read the full Collaborating within and across teams to manage data and models explanation →

Two teams independently develop two different versions of a model for the same use case. They both deploy to the same Vertex AI endpoint, causing conflicts. What is the best way to manage multiple model versions and avoid conflicts in a collaborative environment?

Trap 1: Have each team work on a separate Google Cloud project

Separate projects make it difficult to share models and collaborate.

Trap 2: Use custom metadata to tag each version and rely on team…

Coordination alone is error-prone and does not prevent conflicts.

Trap 3: Deploy each team's model to a separate endpoint

Separate endpoints complicate traffic splitting and increase costs.

Study all Collaborating within and across teams to manage data and models common traps →

A
Have each team work on a separate Google Cloud project
Why wrong: Separate projects make it difficult to share models and collaborate.
B
Use custom metadata to tag each version and rely on team coordination
Why wrong: Coordination alone is error-prone and does not prevent conflicts.
C
Deploy each team's model to a separate endpoint
Why wrong: Separate endpoints complicate traffic splitting and increase costs.
D
Use Vertex AI Model Registry with staging and production channels, and implement CI/CD to control promotions
Model registry with staging/production allows controlled version management and rollback.

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 Collaborating within and across teams to manage data and models sessions

Start a Collaborating within and across teams to manage data and models only practice session

Every question in these sessions is drawn from the Collaborating within and across teams to manage data and models domain — nothing else.

10 questions 20 questions 30 questions 50 questions

Browse all Collaborating within and across teams to manage data and models questions →Mixed PMLE session

Frequently asked questions

What does the PMLE exam test about Collaborating within and across teams to manage data and models?: Collaborating within and across teams to manage data and models 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 Collaborating within and across teams to manage data and models questions in a focused session?: Yes — the session launcher on this page draws every question from the Collaborating within and across teams to manage data and models 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.

Collaborating within and across teams to manage data and models 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 Collaborating within and across teams to manage data and models 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.

Collaborating within and across teams to manage data and models practice questions

What to know about Collaborating within and across teams to manage data and models

Common Collaborating within and across teams to manage data and models exam traps

Collaborating within and across teams to manage data and models questions

A data science team uses a shared Cloud Storage bucket to store training datasets. They notice that some team members accidentally overwrite existing datasets, causing issues with reproducibility. Which approach best prevents accidental overwrites while maintaining collaboration?

A machine learning engineer needs to share a trained model with the product team for integration. The model is stored in Cloud Storage, and the product team’s service account needs read access. The engineer wants to follow the principle of least privilege. Which IAM configuration should be used?

A team is using Vertex AI Pipelines to automate their ML workflow. They want to ensure that pipeline runs are reproducible and that artifacts are tracked. Which feature should they use?

A team of data scientists and ML engineers is collaborating on a project using Vertex AI Workbench. They need to share notebooks and code, but want to avoid conflicts and maintain a history of changes. Which approach should they use?

A machine learning team is deploying a model for real-time predictions using Vertex AI. They need to ensure that the deployment follows best practices for collaboration and governance. Which TWO actions should they take?

A machine learning team is collaborating on a project using Vertex AI Experiments to track model training runs. They want to ensure that all team members can reproduce any experiment by using the same code, data, and environment. Which THREE actions should the team take?

A team has set up the IAM policy above on a Vertex AI project. Alice, a data scientist, reports that she cannot create a Vertex AI Training custom job using a pre-built container. Other data scientists in the group 'data-scientists@example.com' have the same issue. What is the most likely cause?

Exhibit

Drag and drop the steps to perform a hyperparameter tuning job on Vertex AI in the correct order.

Match each ML pipeline component to its description.

A company has multiple teams that need to access and manage ML models in Vertex AI. Different teams require different permission levels: the data science team should be able to create and update models, while the MLOps team should have full control. What is the recommended approach to manage access?

A data scientist needs to share a BigQuery dataset with a colleague in a different team so they can run queries. What is the simplest and most secure way to grant access?

Two teams are collaborating on a project and want to use a shared Feature Store in Vertex AI. They need to ensure that features are discoverable and that access is controlled. What is the best practice?

A team is using Cloud Composer to orchestrate ML workflows. They want to allow multiple data scientists to contribute DAGs without interfering with each other. What is the recommended approach?

A company needs to maintain an audit trail of model changes for compliance. Multiple teams will be updating models. What is the best approach to track who created, modified, or deployed each model version?

A team is using AI Platform Data Labeling Service to label data for a classification model. They want to allow a labeler from a different team to work on the same dataset. What is the correct way to grant access?

To enable collaboration on notebook-based experiments across teams, what is the recommended approach in Google Cloud?

Two teams independently develop two different versions of a model for the same use case. They both deploy to the same Vertex AI endpoint, causing conflicts. What is the best way to manage multiple model versions and avoid conflicts in a collaborative environment?

Track your progress over time

Start a Collaborating within and across teams to manage data and models only practice session

Related PMLE topic practice pages

Scaling prototypes into ML models practice questions

Automating and orchestrating ML pipelines practice questions