Google PCA Ensure solution and operations reliability Practice Question
Network Topology
Refer to the exhibit. A Cloud Deploy pipeline has a release with two targets: staging and prod. The staging rollout succeeded, but the prod rollout failed with 'MANIFEST_INVALID'. What is the most likely cause of the failure?
⚠ Common exam trap
A common trap is confusing 'MANIFEST_INVALID' with permission or quota issues, which are separate failure modes in the deployment pipeline.
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 manifest for prod contains a syntax error or references a resource that does not exist in the prod cluster.
The 'MANIFEST_INVALID' error in Cloud Deploy indicates that the Kubernetes manifest provided for the prod target is syntactically incorrect or references a resource (e.g., a ConfigMap, Secret, or custom resource definition) that does not exist in the prod cluster. This is a validation failure that occurs before any deployment attempt, so it is not related to runtime issues like permissions or quotas.
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 manifest for prod contains a syntax error or references a resource that does not exist in the prod cluster.
Why this is correct
A manifest that parses cleanly against staging can still fail validation against prod, because MANIFEST_INVALID is raised when the rendered manifest is syntactically malformed or references resources absent from the target cluster. The prod target's differing namespace, CRDs or API versions therefore satisfy the stem's constraint that staging succeeded while prod alone failed.
- ✗
The prod target's applyManifest has a higher replica count than staging, which violates a cluster quota.
Why it's wrong here
A replica count exceeding cluster quota fails at apply time with a quota or admission error, not MANIFEST_INVALID, which indicates the manifest itself cannot be parsed or rendered. Quota limits are tempting because they do block rollouts, but they yield a distinct error.
- ✗
The prod cluster does not have the necessary permissions to pull the container image.
Why it's wrong here
MANIFEST_INVALID signals a malformed or unrenderable manifest, not an image-pull authorisation failure, which surfaces as ImagePullBackOff or a permission error. Image-pull permissions are tempting because they block deployments, but they produce a different failure signature.
- ✗
The release was not approved for the prod target.
Why it's wrong here
Approval gating blocks a rollout before it starts, producing a pending-approval state rather than MANIFEST_INVALID, which Cloud Deploy raises when the rendered manifest fails schema or API validation against the target cluster. Approval is the right control when you need a human gate between staging and prod.
Visual reference
Go deeper
Related to this question
Learn chapter
Google Kubernetes Engine (GKE)
Key term
Cloud Deploy
Cloud Deploy is the process of releasing software applications and updates from development to production environments that run on cloud infrastructure.
Key term
Anthos
Anthos is a Google Cloud platform that lets you run applications consistently across different computing environments, like on-premises data centers and multiple public clouds.
About these practice questions
One of 807 original PCA practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PCA 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 PCA exam.