Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your enterprise is establishing an end-to-end software supply chain security architecture for containerized microservices deployed to Google Kubernetes Engine (GKE).
Your design must satisfy the following requirements:
Which strategy should you implement?
This approach uses a self-managed instance of the open-source Harbor registry running on Compute Engine configured to run vulnerability scans upon receiving image pushes, alongside custom admission webhooks in Kubernetes.
The organization operated within a completely disconnected, on-premises air-gapped environment where managed Google Cloud services like Artifact Registry and Binary Authorization were entirely unavailable.
This architecture establishes a complete, automated software supply chain security framework across Google Cloud by combining Artifact Analysis, Cloud Build, and Binary Authorization with Continuous Validation (CV).
This design provides a unified, cloud-native control plane across Google Cloud managed services, meeting all compliance and security requirements without adding third-party operational burdens or complex self-managed tooling.
This strategy uses Config Sync to implement GitOps synchronization, pulling OCI packages and Kubernetes manifests from Artifact Registry into GKE clusters while using signed Git commits to guarantee source configuration integrity.
The primary objective was to enforce declarative GitOps workflows, prevent configuration drift on cluster resources, and ensure all cluster configuration files originated from verified repository commits.
This approach relies on developers manually invoking the On-Demand Scanning API via the command-line interface on their local workstations before pushing code, coupled with GKE Network Policies to restrict traffic.
A developer needed to quickly inspect a local development container image for known OS-level vulnerabilities before submitting code to a centralized CI pipeline.
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