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 enterprise organization requires a secure CI/CD pipeline on Google Cloud for containerized microservices deployed to Google Kubernetes Engine (GKE). You need to implement a comprehensive supply chain security strategy that satisfies the following requirements:
CRITICAL or HIGH vulnerabilities are found.Which combination of actions should you implement?
This configuration sets up a scheduled Cloud Scheduler job to re-tag images, uses legacy gcloud container images commands to export scan results into BigQuery, and deploys an in-house custom mutating webhook to reject unapproved image tags on GKE.
gcloud container images command is intended for legacy Container Registry, whereas Artifact Registry utilizes gcloud artifacts docker. Rejecting pods by tag rather than digest or signed attestation leaves workloads vulnerable to tag mutation attacks.You were maintaining a legacy Container Registry (gcr.io) environment and building a custom analytics reporting pipeline in BigQuery without native admission control integrations.
This approach relies on pushing container images directly to Artifact Registry, triggering an asynchronous post-push Cloud Function via Pub/Sub to inspect scan occurrences and delete images exceeding vulnerability thresholds, while attempting to use IAM condition bindings to prevent deployment.
You needed a lightweight cleanup script to purge outdated image tags across non-production repositories where pre-build scanning and admission control were not mandated.
This architecture integrates Cloud Build, Artifact Analysis On-Demand Scanning, Artifact Registry continuous vulnerability scanning, and Binary Authorization to deliver an end-to-end secure software supply chain.
By integrating the On-Demand Scanning API directly into cloudbuild.yaml, the pipeline runs gcloud artifacts docker images scan on the locally built image and inspects the output with gcloud artifacts docker images list-vulnerabilities. If CRITICAL or HIGH vulnerabilities are detected, the build step returns a non-zero exit code, immediately halting the pipeline before executing docker push.
Enabling automatic scanning (containerscanning.googleapis.com) in Artifact Registry ensures that once an approved image is uploaded, Artifact Analysis continuously matches its package metadata against external CVE sources updated multiple times per day throughout the 30-day active monitoring window.
Binary Authorization acts as a Kubernetes admission controller on GKE. It enforces signature verification and attestations (such as vulnerability scan compliance and build provenance) before allowing container pods to deploy to the cluster.
This proposal attempts to use Web Security Scanner during CI to inspect container binaries, disables the Container Scanning API in Artifact Registry, and uses manual approval gates inside Cloud Deploy before rolling out to GKE.
You were performing dynamic application security testing (DAST) on an already deployed staging web service to audit OWASP Top 10 vulnerabilities prior to public production launch.
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