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 is securing its software supply chain across Google Kubernetes Engine (GKE) clusters and Cloud Run services using Binary Authorization.
The security architecture requires:
prod-attestor that verifies cryptographic signatures generated by the CI/CD pipeline using a Cloud KMS asymmetric key pair.prod-attestor before container deployment across all production GKE clusters and Cloud Run services.us-central1-a.staging-cluster) configured to log policy violations without blocking non-compliant container deployments.Which configuration should the security engineer implement to satisfy these requirements?
us-central1-a.staging-cluster set to Deny All Images.--binauthz-evaluation-mode=POLICY_BINDINGS.This option attempts to store attestation metadata inside a Cloud Storage bucket using Cloud KMS HMAC signing keys, configures the default policy to allow all images, and blocks deployments in staging with a Deny All Images rule.
Allow All Images fails to enforce attestations on production GKE and Cloud Run services. Furthermore, configuring the staging cluster with Deny All Images actively blocks staging deployments rather than auditing them in dry-run mode.--binauthz-evaluation-mode=POLICY_BINDINGS requires continuous validation platform policies instead of evaluating the standard project singleton policy rules.Allow All Images negates software supply chain enforcement across production workloads.The organization intended to bypass Binary Authorization entirely and manage custom deployment auditing scripts against Cloud Storage.
prod-attestor.--binauthz-evaluation-mode=DISABLED.This option suggests using a Cloud KMS symmetric encryption key for the Binary Authorization attestor, overriding policy behavior with a Kubernetes Service Account rule, and setting --binauthz-evaluation-mode=DISABLED on the cluster.
GOOGLE_SYMMETRIC_ENCRYPTION) cannot perform digital signature creation and public verification.--binauthz-evaluation-mode=DISABLED deactivates the Binary Authorization admission controller on GKE clusters, preventing any policy evaluation or deployment blocking.us-central1-a.staging-cluster.A cluster did not require any Binary Authorization enforcement and the workload relied solely on application-layer symmetric envelope encryption.
prod-attestor with enforcement mode enabled.us-central1-a.staging-cluster set to Dry Run mode.--binauthz-evaluation-mode=PROJECT_SINGLETON_POLICY_ENFORCE.Binary Authorization is a deploy-time security control for Google Kubernetes Engine (GKE) and Cloud Run that ensures only trusted container images are deployed. An attestor is a named Google Cloud resource that verifies cryptographic signatures (attestations) associated with a container image digest. The attestor links an Artifact Analysis note—which serves as the metadata anchor for storing attestation occurrences—to public keys or asymmetric Cloud Key Management Service (Cloud KMS) cryptographic keys used to verify those signatures.
defaultAdmissionRule to REQUIRE_ATTESTATION with requireAttestationsBy: [projects/PROJECT_ID/attestors/prod-attestor] ensures all GKE and Cloud Run deployments enforce signature validation across standard workloads.clusterAdmissionRules for us-central1-a.staging-cluster with Dry Run Mode (DRYRUN_AUDIT_LOG_ONLY) evaluates the policy against incoming deployments and emits audit logs in Cloud Logging without rejecting unverified containers.--binauthz-evaluation-mode=PROJECT_SINGLETON_POLICY_ENFORCE activates the admission controller to query the project's singleton policy at deploy time.This solution follows Google Cloud recommended security practices by leveraging built-in Artifact Analysis metadata management, Cloud KMS cryptographic key protection, and native project singleton policy evaluation flags on GKE.
default namespace set to Require Attestations.--binauthz-evaluation-mode=PROJECT_SINGLETON_POLICY_ENFORCE.This option attempts to create an attestor without linking it to an Artifact Analysis note, sets the default policy to dry-run globally, and applies a namespace-scoped rule to enforce attestations.
default namespace fails to enforce attestations across other production namespaces, and does not provide a cluster-level dry-run audit configuration for staging-cluster.The goal was only to test Binary Authorization in audit-only mode across an entire project during an initial migration phase.
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