The answer is to implement Cloud Build triggers that run validation steps, then use Vertex AI Model Registry state to mark models as validated before allowing deployment to endpoints. This approach is correct because it enforces model validation before deployment Vertex AI by embedding governance directly into the CI/CD pipeline: Cloud Build executes unit tests, fairness checks, and performance benchmarks, and only upon success does it update the model’s state in the registry to “validated.” The deployment pipeline then checks this state as a gate, preventing any unvalidated model from being deployed to Vertex AI Endpoints. On the Google Professional Machine Learning Engineer exam, this scenario tests your understanding of combining Vertex AI Model Registry’s lifecycle states with Cloud Build’s approval steps—a common trap is assuming endpoint-level access controls alone suffice, but the registry state is the actual enforcement mechanism. Remember the mnemonic: “Build, Validate, Gate, Deploy” to recall that validation must occur in the build step before the registry gate allows deployment.
PMLE Collaborating to manage data and models Practice Question
This PMLE practice question tests your understanding of collaborating to manage data and models. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A large e-commerce company deploys multiple ML models on Vertex AI Endpoints. They use Vertex AI Model Registry to manage model versions. Recently, a team accidentally deployed an unvalidated model to production, causing a service outage. They want to implement a governance process where models must pass certain validation checks before deployment. The validation includes unit tests, fairness checks, and performance benchmarks. They use CI/CD pipelines (Cloud Build). They also need to allow manual approval for critical models. Which combination of Vertex AI features and Cloud Build steps would enforce the required governance?
Use Vertex AI Experiments to log validation results and require manual checks before deployment.
Why wrong: Manual checks are not automated and may be skipped or delayed.
B
Set up Cloud Armor to block deployment of unvalidated models.
Why wrong: Cloud Armor is a network security service, not a model governance tool.
C
Implement Cloud Build triggers that run validation steps, then use Vertex AI Model Registry 'state' to mark models as 'validated' before allowing deployment to endpoints.
This enforces a gate where only models with appropriate state can be deployed.
D
Use Vertex AI Continuous Monitoring to automatically detect issues and roll back deployments.
Why wrong: Monitoring detects issues after deployment, not prevent them.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement Cloud Build triggers that run validation steps, then use Vertex AI Model Registry 'state' to mark models as 'validated' before allowing deployment to endpoints.
Option C is correct because it combines Cloud Build triggers to run validation steps (unit tests, fairness checks, performance benchmarks) and uses Vertex AI Model Registry's 'state' field to mark models as 'validated' only after passing those checks. This state then acts as a gate in the deployment pipeline, ensuring that only validated models can be deployed to Vertex AI Endpoints. The manual approval for critical models can be integrated as a Cloud Build approval step before the state is set to 'validated'.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use Vertex AI Experiments to log validation results and require manual checks before deployment.
Why it's wrong here
Manual checks are not automated and may be skipped or delayed.
✗
Set up Cloud Armor to block deployment of unvalidated models.
Why it's wrong here
Cloud Armor is a network security service, not a model governance tool.
✓
Implement Cloud Build triggers that run validation steps, then use Vertex AI Model Registry 'state' to mark models as 'validated' before allowing deployment to endpoints.
Why this is correct
This enforces a gate where only models with appropriate state can be deployed.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use Vertex AI Continuous Monitoring to automatically detect issues and roll back deployments.
Why it's wrong here
Monitoring detects issues after deployment, not prevent them.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is confusing reactive monitoring (Continuous Monitoring) or unrelated security services (Cloud Armor) with proactive deployment governance, while overlooking that Vertex AI Model Registry's state field is the correct mechanism to enforce pre-deployment validation gates.
Detailed technical explanation
How to think about this question
Vertex AI Model Registry supports custom 'state' labels (e.g., 'validated', 'staging', 'production') that can be programmatically set via the Vertex AI API or Cloud Build steps. By integrating Cloud Build triggers to run validation scripts and then updating the model's state only on success, you create a deterministic deployment gate. This pattern aligns with CI/CD best practices where artifact promotion is controlled by pipeline success, and manual approval can be inserted as a Cloud Build 'approval' step before the state transition.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Collaborating to manage data and models — This question tests Collaborating to manage data and models — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Implement Cloud Build triggers that run validation steps, then use Vertex AI Model Registry 'state' to mark models as 'validated' before allowing deployment to endpoints. — Option C is correct because it combines Cloud Build triggers to run validation steps (unit tests, fairness checks, performance benchmarks) and uses Vertex AI Model Registry's 'state' field to mark models as 'validated' only after passing those checks. This state then acts as a gate in the deployment pipeline, ensuring that only validated models can be deployed to Vertex AI Endpoints. The manual approval for critical models can be integrated as a Cloud Build approval step before the state is set to 'validated'.
What should I do if I get this PMLE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A financial services company uses Vertex AI to deploy multiple models for fraud detection. The ML team has set up a CI/CD pipeline using Cloud Build and Cloud Deploy. The pipeline builds a custom container with the trained model, pushes it to Artifact Registry, and deploys it to a Vertex AI Endpoint. Recently, a new regulation requires that all model deployments be audited and approved by the compliance team before going live. The compliance team wants to review the model's evaluation metrics and approve the deployment via a ticketing system. Currently, the CI/CD pipeline automatically deploys after the container is built. The team needs to implement a gating process without slowing down the development cycle. What should they do?
hard
A.Use Cloud Composer to orchestrate the deployment and add a sensor that waits for approval from the ticketing system via a custom operator.
B.Use Cloud Build's built-in approval gate feature to require compliance team sign-off before deployment.
✓ C.Modify the CI/CD pipeline to use Cloud Deploy's approval gate feature, requiring a manual approval from the compliance team before the deployment step.
D.Store the model artifacts in Cloud Storage and have the compliance team deploy manually using the gcloud command.
Why C: Option C is correct because Cloud Deploy provides a native approval gate feature that can be inserted into a delivery pipeline to require manual sign-off before a deployment proceeds. This allows the compliance team to review model evaluation metrics and approve via a ticketing system without modifying the CI/CD pipeline's build process, thus maintaining development velocity. The approval gate pauses the deployment at a specific stage, waiting for an external approval signal, which integrates seamlessly with Cloud Deploy's rollout management.
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PMLE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PMLE exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.