Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise runs containerized workloads across Google Kubernetes Engine (GKE) and Cloud Run. The security compliance team establishes a mandatory software supply chain policy:
Which solution should you implement to enforce this deployment control?
This configuration sets the admission rule to ALWAYS_DENY and uses admissionWhitelistPatterns (exempt image patterns) to allow containers whose repository path matches specified URL strings, such as us-docker.pkg.dev/my-project/**.
admissionWhitelistPatterns exempts matching image paths based purely on registry location and URL matching without evaluating digital signatures, PKI keys, or attestations.The goal was simply to restrict deployments to a specific trusted container registry folder or allowlist Google-managed system container images without requiring cryptographic signatures.
Binary Authorization is a Google Cloud deploy-time security service that ensures only trusted container images are deployed across platforms such as Google Kubernetes Engine (GKE) and Cloud Run. It uses a policy model where deployment admission is gated by verifiable cryptographic signatures called attestations.
evaluationMode to REQUIRE_ATTESTATION ensures that the admission controller requires digital signatures created by trusted signers before allowing execution.enforcementMode to ENFORCED_BLOCK_AND_AUDIT_LOG blocks any container deployment attempt that fails attestation verification and writes an audit event directly to Cloud Audit Logs.This approach directly satisfies the enterprise requirement for automated signature verification prior to container execution while leveraging native Google Cloud deploy-time enforcement and centralized logging without altering workload code.
This approach attempts to use Identity and Access Management (IAM) conditions and repository-level access controls to restrict image pull operations in Artifact Registry based on client authentication.
The requirement was strictly to enforce identity-based access control and network access levels for downloading images from Artifact Registry.
This configuration sets up attestation requirements but sets the enforcement mode to DRYRUN_AUDIT_LOG_ONLY. In dry-run mode, Binary Authorization evaluates images against the attestors and logs violations to Cloud Audit Logs, but allows non-compliant containers to deploy.
The security team wanted to test policy rules and monitor potential violations across active environments without disrupting ongoing application deployments.
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