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 is modernizing its continuous integration and continuous delivery (CI/CD) pipeline on Google Cloud. The security team requires a shift-left approach to software delivery with the following constraints:
Which solution should you implement to meet these requirements?
This proposal suggests using GKE Workload Identity to create image signatures during the build phase and configuring Kubernetes Network Policies to isolate non-compliant workloads inside the cluster.
The requirement was to allow GKE microservices to securely access Cloud SQL or Cloud Storage using short-lived IAM credentials while restricting east-west network traffic between namespaces.
This approach relies on Artifact Registry automatic scanning (on-push scanning via Artifact Analysis) and configures Google Cloud Armor web application firewall (WAF) policies at the external HTTP(S) load balancer level.
The objective was to protect public-facing web applications running on GKE from Layer 7 OWASP Top 10 web injection attacks while monitoring pushed registry containers for newly disclosed zero-day vulnerabilities.
This architecture combines Cloud Build, the Artifact Analysis On-Demand Scanning API, and Binary Authorization to build a comprehensive end-to-end secure software supply chain on Google Cloud. It directly operationalizes the shift-left security paradigm by testing and enforcing compliance before images are stored in registries or deployed to runtime environments.
docker build step. If the scan identifies CVEs exceeding the defined severity threshold, Cloud Build fails the pipeline and blocks the upload to Artifact Registry.
This solution implements preventive controls across both the build and deployment phases of the SDLC. It prevents defective images from ever entering production environments without relying on manual approvals or post-deployment remediation.
This configuration uses Security Command Center (SCC) to centralize security posture monitoring and deploys VPC Service Controls to establish an isolation boundary around Google Cloud APIs and managed services.
The primary goal was to prevent sensitive container images and data inside an Artifact Registry repository from being exfiltrated to external Google Cloud projects or unauthorized networks.
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