Google PCA Manage implementation of cloud architecture Practice Question

Exhibit

Refer to the exhibit.

gcloud deployment-manager deployments describe my-deployment
---
id: '12345'
name: my-deployment
manifest: manifest-123
state: DEPLOYED
resources:
- name: my-vm
  type: compute.v1.instance
  properties:
    machineType: zones/us-central1-a/machineTypes/n1-standard-1
    networkInterfaces:
    - network: global/networks/default
  currentStatus: FAILED
- name: my-disk
  type: compute.v1.disk
  properties:
    zone: us-central1-a
    sizeGb: 10
  currentStatus: SUCCESS

Why did the VM resource fail while the disk succeeded?

⚠ Common exam trap

Google Cloud often tests the subtle dependency that a boot disk must have an explicit `source` reference in the VM definition, and candidates mistakenly think the disk creation implies the VM will also succeed, or they confuse zone constraints with missing required fields.

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 VM definition is missing a boot disk source reference.

When you define a VM instance in Google Cloud, you must include a reference to a boot disk source. If the `source` field under `disks` is missing or empty, the API will reject the VM creation but may still succeed in creating the disk resource separately, since the disk creation does not depend on the VM. This explains why the disk succeeded while the VM failed.

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 disk and VM must be in the same zone; us-central1-a is consistent.
Why it's wrong here
They are same zone.
✓
The VM definition is missing a boot disk source reference.
Why this is correct
A VM instance typically requires a boot disk; the disk resource exists but VM doesn't reference it as boot disk.
✗
The VM's machine type is not available in us-central1-a.
Why it's wrong here
n1-standard-1 is available.
✗
The VM's network is misspelled as 'global/networks/default' instead of 'global/networks/default' (correct).
Why it's wrong here
Spelling is correct.

Go deeper

Google PCA Manage implementation of cloud architecture Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question