nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #191

Your company has an application deployed on Google Kubernetes Engine (GKE) consisting of 12 microservices. Multiple teams are working concurrently on various features across three environments: Dev…

The correct answer is A. Automate CI pipelines by using Cloud Build for container image creation and Kubernetes manifest. This approach ensures cost-effectiveness by utilizing dynamically created namespaces within the existing Dev GKE cluster rather than provisioning entire clusters for each feature branch. It allows developers to test their microservices in isolated namespaces while autoscaling…

Submitted by joshua94· Apr 18, 2026Building and implementing CI/CD pipelines for a service

Question

Your company has an application deployed on Google Kubernetes Engine (GKE) consisting of 12 microservices. Multiple teams are working concurrently on various features across three environments: Dev, Staging, and Prod. Developers report dependency test failures and delayed releases due to deployments from multiple feature branches in the shared Dev GKE cluster. You need to implement a cost-effective solution for developers to test their microservice features in a stable development environment isolated from other development activities. What should you do?

Options

  • AAutomate CI pipelines by using Cloud Build for container image creation and Kubernetes manifest
  • BAutomate CI pipelines by using Cloud Build to create container images and update Kubernetes
  • CUse Cloud Build to automate CI pipelines and update Kubernetes manifest files from feature
  • DUse Cloud Build to automate CI pipelines and update Kubernetes manifest files from feature

How the community answered

(45 responses)
  • A
    76% (34)
  • B
    9% (4)
  • C
    13% (6)
  • D
    2% (1)

Explanation

This approach ensures cost-effectiveness by utilizing dynamically created namespaces within the existing Dev GKE cluster rather than provisioning entire clusters for each feature branch. It allows developers to test their microservices in isolated namespaces while autoscaling ensures efficient resource utilization. The post-test cleanup routine ensures that unused resources are removed, maintaining cluster efficiency.

Topics

#CI/CD#Cloud Build#Kubernetes#Ephemeral Environments

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice