easyMultiple Choice
PMLE Practice Question: Refer to the exhibit
Network Topology
Refer to the exhibit. A team runs the command above and sees only two models. They know there is a model 'model-v3' created three days ago. What is the most likely reason it is not listed?
⚠ Common exam trap
Google Cloud often tests the regional scope of Vertex AI resources, trapping candidates who assume model listing is global or project-wide, when in fact it is region-specific and requires the correct `--region` flag.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The model was created in a different region.
The `gcloud ai models list` command lists models within a specific region, as Vertex AI models are regional resources. If 'model-v3' was created in a different region, it would not appear in the output unless the `--region` flag is set to that region. This is the most likely reason the model is missing from the list.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The model was created in a different region.
Why this is correct
A model registered in another region is stored in that region's registry, so listing commands scoped to the current region will not return it. This directly satisfies the stem's constraint: the team queries one region while 'model-v3' resides elsewhere, hence only two models appear.
- ✗
The model is in a different project.
Why it's wrong here
The CLI lists models scoped to the currently active project, so a model registered elsewhere will not appear. It is tempting because project isolation is a genuine cause of missing resources, and switching projects with the --project flag would be the right fix if the model truly lived in another workspace.
- ✗
The model is not deployed to an endpoint.
Why it's wrong here
Deployment to an endpoint governs serving, not listing; an undeployed model still appears in the registry. The listing command enumerates registered models regardless of endpoint state. Deployment is tempting because it is required before predictions, but it does not control whether the model is returned by a registry query.
- ✗
The model's display name contains a hyphen.
Why it's wrong here
Hyphens are valid characters in model names and display names, so 'model-v3' is listed normally. The listing command filters by project scope, not naming syntax. Hyphens are tempting because they look unusual, but they cause no exclusion; the actual filter is the project context.
- ✗
The model was created by a different user.
Why it's wrong here
The listing command filters by the caller's own user ID, so models created by other accounts are hidden regardless of age. It is tempting because per-user scoping is a genuine feature, and would be the correct choice when isolating one engineer's registered models in a shared workspace.
Go deeper
Related to this question
About these practice questions
This PMLE question is part of Courseiva's 775-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.