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.
A DevOps team uses Google Cloud Build to run automated tests and build container images for a critical application. The organization's security policy requires shifting security left by validating that container images do not contain severe vulnerabilities before they are stored in the artifact repository.
The team has the following requirements:
CRITICAL or HIGH severity vulnerabilities are detected.Which strategy should the team implement in their Cloud Build configuration?
Binary Authorization is a deploy-time security control that ensures only trusted container images are deployed to Google Cloud runtime environments, such as Google Kubernetes Engine (GKE) and Cloud Run. It enforces signature validation against predefined policies by verifying attestations created by trusted authorities.
docker push step in a CI build pipeline.The objective was to prevent GKE clusters from running container images that lack a valid cryptographic attestation confirming compliance with organizational vulnerability policies.
This architecture relies on Artifact Analysis automatic scanning, which triggers an asynchronous vulnerability scan only after a container image has already been pushed to an Artifact Registry repository. When scan results are available, Artifact Analysis publishes notifications to a Pub/Sub topic, which can trigger an event-driven Cloud Function to delete non-compliant images.
The requirement was to continuously monitor images already deployed or stored in Artifact Registry for newly discovered Common Vulnerabilities and Exposures (CVEs) over time.
cloudbuild.yaml to execute gcloud artifacts docker images scan on the local image, evaluate the results using gcloud artifacts docker images list-vulnerabilities, and fail the pipeline prior to executing docker push if matching severity levels are found.Artifact Analysis On-Demand Scanning allows developers and CI/CD pipelines to initiate vulnerability scans on container images stored locally or in Artifact Registry. By leveraging the Google Cloud SDK within Cloud Build, organizations can scan images as a build step immediately after compilation and containerization.
gcloud artifacts docker images scan followed by gcloud artifacts docker images list-vulnerabilities, the build pipeline can parse the effective severity levels. If vulnerabilities matching CRITICAL or HIGH are discovered, the script exits with a non-zero code, failing the build and preventing subsequent docker push execution.
This approach directly prevents vulnerable images from reaching the repository, saving storage and network overhead while establishing a clean separation between validated release candidates and failed builds.
cloudbuild.yaml to scan the local container image filesystem for CVEs and halt the build upon detection of high-risk vulnerabilities.Web Security Scanner is a security tool within Security Command Center designed to scan public-facing web applications for common web application vulnerabilities such as Cross-Site Scripting (XSS), Flash content, mixed content, and cleartext passwords in web endpoints.
dpkg or rpm), or language lockfiles.The goal was to run automated Dynamic Application Security Testing (DAST) against a deployed staging URL to detect OWASP Top 10 security risks prior to production release.
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