Google Professional Cloud DevOps Engineer
Get started today
Ultimate access to all questions.
Comments
Loading comments...
Ultimate access to all questions.
Your company has a 12-microservice application running on Google Kubernetes Engine (GKE) with multiple teams working on features across Dev, Staging, and Production environments. Developers experience dependency test failures and release delays due to concurrent deployments from multiple feature branches in the shared Dev GKE cluster.
What cost-effective solution should you implement to provide developers with isolated, stable environments for testing microservice features without interference from other development activities?
A
Automate CI pipelines by using Cloud Build for container image creation and Kubernetes manifest updates from main branch merge requests. Integrate with Config Sync to test new images in dynamically created namespaces on the Dev GKE cluster with autoscaling enabled. Implement a post-test namespace cleanup routine.
B
Automate CI pipelines by using Cloud Build to create container images and update Kubernetes manifests for each commit. Use Cloud Deploy for progressive delivery to Dev, Staging, and Prod GKE clusters. Enable Config Sync for consistent Kubernetes configurations across environments.
C
Use Cloud Build to automate CI pipelines and update Kubernetes manifest files from feature branch commits. Integrate with Config Sync to test new images in dynamically created namespaces on the Dev GKE cluster with autoscaling enabled. Implement a post-test namespace cleanup routine.
D
Use Cloud Build to automate CI pipelines and update Kubernetes manifest files from feature branch commits. Integrate with Config Sync to test new images in dynamically created GKE Dev clusters for each feature branch, which are deleted upon merge request.