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 organization is establishing a secure CI/CD deployment pipeline for containerized microservices running on Google Kubernetes Engine (GKE). The security team has defined the following compliance requirements:
Which combination of steps should you implement to configure this deployment gate?
This option configures Binary Authorization in Audit-only mode with Continuous Validation (CV) and records a cryptographic signature of the Git commit SHA within Kubernetes deployment manifest metadata annotations.
Audit-only evaluation mode does not block non-compliant deployments at admission time; it only generates monitoring log entries in Cloud Logging when an image violates policy.Audit-only mode is designed for dry-run observation or monitoring active workloads, not preventing unauthorized deployments.The primary goal was non-blocking post-deployment monitoring or auditing of running workloads across clusters without disrupting active deployment operations.
This option configures a strict ALWAYS_DENY rule in Binary Authorization and uses the emergency breakglass workflow in the automated CI/CD pipeline to bypass policy enforcement when vulnerability scans pass.
ALWAYS_DENY blocks all normal admission paths.An on-call engineer needed to deploy an emergency mitigation during an active production outage when normal attestation authorities or pipeline components are temporarily unavailable.
Binary Authorization is a deploy-time security control that ensures only trusted and verified container images are deployed to Google Kubernetes Engine (GKE). It integrates directly with Artifact Analysis, which automatically scans container images stored in Artifact Registry for known vulnerabilities (Common Vulnerabilities and Exposures - CVEs) and records metadata notes and occurrences.
image@sha256:...) rather than mutable tags guarantees that the cryptographic signature matches the exact bits being executed, preventing tag-swapping or drift.This approach uses native Google Cloud security services to form an automated, end-to-end software supply chain security gate. It eliminates manual intervention while guaranteeing that only cryptographically signed, vulnerability-free container digests are admitted into the production GKE environment.
This option attempts to construct a custom Kubernetes admission controller webhook that queries vulnerability findings during pod creation while leaving Binary Authorization in an ALWAYS_ALLOW permissive state and deploying images using mutable container tags.
ALWAYS_ALLOW disables Binary Authorization enforcement, bypassing Google Cloud's managed supply-chain security gate.image:tag) rather than image digests allows container registries or unauthorized actors to overwrite tags with unvetted images after signing.You were operating in a non-GKE Kubernetes environment without access to Binary Authorization and were required to build a proprietary admission controller from scratch.
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