Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
An enterprise organization is establishing automated security gating mechanisms within their Google Cloud CI/CD pipeline. The security policy mandates that container images deployed to production Google Kubernetes Engine (GKE) clusters must satisfy the following criteria:
MEDIUM severity or unfixable vulnerabilities above HIGH severity must be blocked from progressing to production.Which architecture should the security team implement to enforce these gating requirements?
The built-by-cloud-build attestor is a Google-managed attestation mechanism that verifies whether a container image was produced and signed by Cloud Build. It validates build provenance and source integrity.
built-by-cloud-build attestor only confirms that Cloud Build completed an image build; it does not evaluate vulnerability scan results or inspect CVE severity levels against organizational thresholds.evaluationMode to ALWAYS_ALLOW allows all container images to deploy without validating attestations or security criteria.DRYRUN_AUDIT_LOG_ONLY enforcement mode records policy evaluation events to Cloud Audit Logs but allows non-conforming images to run, directly failing the requirement to block vulnerable artifacts.The objective were merely to verify build provenance from Cloud Build in an audit-only testing phase without enforcing vulnerability gating or blocking deployments.
Security Health Analytics is a built-in detector within Security Command Center (SCC) that discovers misconfigurations and compliance violations across Google Cloud infrastructure resources such as IAM policies, storage buckets, and firewall rules.
evaluationMode of ALWAYS_DENY blocks all deployments indiscriminately without providing a mechanism to verify passing scan criteria.The goal were to continuously monitor Google Cloud environment resources for configuration drift and compliance misconfigurations.
Continuous Validation (CV) is a background feature of Binary Authorization that periodically monitors already-running Pods on GKE clusters to detect if running container images have developed newly discovered vulnerabilities or drifted from platform policy requirements.
ALWAYS_ALLOW permits vulnerable artifacts containing high-severity CVEs to be scheduled and executed on production nodes before CV logs any findings.kubectl deployment requests.The requirement called for background post-deployment monitoring to identify newly published zero-day CVEs affecting containers that are already running in production.
Binary Authorization provides deploy-time policy enforcement for containerized workloads deployed across Google Kubernetes Engine (GKE). It works symbiotically with Artifact Analysis and Cloud Key Management Service (Cloud KMS) to cryptographically attest that specific quality, security, and vulnerability checks have been completed before an image descriptor is admitted to a runtime cluster.
maximumFixableSeverity: MEDIUM and maximumUnfixableSeverity: HIGH).evaluationMode: REQUIRE_ATTESTATION referencing the vulnerability attestor, and sets enforcementMode: ENFORCED_BLOCK_AND_AUDIT_LOG to block non-compliant deployments while logging events to Cloud Audit Logs.This solution prevents non-compliant or unscanned artifacts from entering production environments by enforcing a cryptographically signed gate that GKE validates before runtime pod creation.
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