Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your team uses Google Cloud Deploy to deliver microservices to a production Google Kubernetes Engine (GKE) cluster using a canary deployment strategy. You recently updated the delivery pipeline YAML configuration to enable automated deployment verification by setting verify: true under the canaryDeployment strategy.
During the subsequent release rollout, the deployment phase succeeds, but the rollout immediately fails and halts during the verification phase before executing any test suites. Inspection of the clouddeploy-operations Pub/Sub notification logs confirms a JobRun failure with JobType: Verify.
What is the root cause of this pipeline failure, and what action should you take to resolve it?
predeploy and postdeploy lifecycle hooks in DeliveryPipeline; you must declare custom action hooks pointing to Skaffold lifecycle scripts.Deploy hooks (predeploy and postdeploy) in Cloud Deploy allow execution of custom actions before a deploy job runs or after a verify job finishes.
verify: true) and deploy hooks (predeploy/postdeploy) are completely independent configuration blocks. Hooks are not mandatory for deployment verification to succeed.customActions in skaffold.yaml and referenced under strategy.Verify JobRun failure.verify stanza.skaffold.yaml are ignored by Cloud Deploy.You needed to execute custom database schema migrations before applying manifests (predeploy) or run cache invalidation scripts following a successful rollout (postdeploy).
Workload vulnerability scanning is a security feature within Google Kubernetes Engine (GKE) and Artifact Analysis that detects Common Vulnerabilities and Exposures (CVEs) in container OS images and language packages.
JobRun verify jobs to fail.The objective was to detect application-level open-source package vulnerabilities on running GKE container workloads from the Google Cloud console.
skaffold.yaml configuration lacks a verify stanza with test container definitions; you must add the verify stanza and ensure the Skaffold apiVersion is skaffold/v3alpha1 or greater.Deployment verification in Google Cloud Deploy is a native pipeline feature that allows automated execution of verification jobs (such as end-to-end or integration tests) against a target environment following a deployment phase.
When verify: true is enabled on a target stage or canary strategy within DeliveryPipeline, Cloud Deploy orchestrates a separate VERIFY execution environment job. For this job to execute successfully:
verify stanza in the skaffold.yaml configuration (or within the relevant Skaffold profile) that specifies the container image and test execution commands.skaffold.yaml must use an apiVersion of skaffold/v3alpha1 or greater.verify: true is configured in the pipeline but the skaffold.yaml is missing the verify stanza, Cloud Deploy will automatically fail the Verify JobRun.dev, staging, and prod targets.Adding the verify stanza with appropriate test container definitions and a compliant apiVersion satisfies Cloud Deploy's validation requirements and allows the verification phase to run test suites directly against the deployed canary pods.
kubectl rendering instead of Helm; you must change the deployer stanza in skaffold.yaml to deploy.helm.Cloud Deploy uses Skaffold under the hood to manage manifest rendering and deployment. Skaffold can render manifests using Kustomize, Helm, or raw YAML.
kubectl as the deployer mechanism for Kubernetes targets. It does not support helm as a deployer (deploy.helm).manifests.helm stanza in skaffold.yaml, the deployment phase strictly uses deploy.kubectl.deploy.helm in skaffold.yaml for Cloud Deploy will result in pipeline configuration or execution errors.The scenario described manifest hydration failures during the release render step when trying to process Helm chart templates.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated