support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
CrowdStrike
Anthropic
All Vendors
  1. Home
  2. Exams
  3. Google
  4. PROFESSIONAL CLOUD DEVOPS ENGINEER

Free PROFESSIONAL CLOUD DEVOPS ENGINEER Exam Braindumps
Professional Cloud DevOps Engineer Questions 89–96 (page: 13)

Updated On: 4-Jun-2026
Page 13 of 31
PDF with 239 Questions

You recently deployed your application in Google Kubernetes Engine (GKE) and now need to release a new version of the application. You need the ability to instantly roll back to the previous version of the application in case there are issues with the new version. Which deployment model should you use?

  1. Perform a rolling deployment, and test your new application after the deployment is complete.
  2. Perform A/B testing, and test your application periodically after the deployment is complete.
  3. Perform a canary deployment, and test your new application periodically after the new version is deployed.
  4. Perform a blue/green deployment, and test your new application after the deployment is complete.

Answer(s): D



You are building and deploying a microservice on Cloud Run for your organization. Your service is used by many applications internally. You are deploying a new release, and you need to test the new version extensively in the staging and production environments. You must minimize user and developer impact. What should you do?

  1. Deploy the new version of the service to the staging environment. Split the traffic, and allow 1% of traffic through to the latest version. Test the latest version. If the test passes, gradually roll out the latest version to the staging and production environments.
  2. Deploy the new version of the service to the staging environment. Split the traffic, and allow 50% of traffic through to the latest version. Test the latest version. If the test passes, send all traffic to the latest version.
    Repeat for the production environment.
  3. Deploy the new version of the service to the staging environment with a new-release tag without serving traffic. Test the new-release version. If the test passes, gradually roll out this tagged version. Repeat for the production environment.
  4. Deploy a new environment with the green tag to use as the staging environment. Deploy the new version of the service to the green environment and test the new version. If the tests pass, send all traffic to the green environment and delete the existing staging environment. Repeat for the production environment.

Answer(s): C



You work for a global organization and run a service with an availability target of 99% with limited engineering resources.
For the current calendar month, you noticed that the service has 99.5% availability. You must ensure that your service meets the defined availability goals and can react to business changes, including the upcoming launch of new features.
You also need to reduce technical debt while minimizing operational costs. You want to follow Google- recommended practices. What should you do?

  1. Add N+1 redundancy to your service by adding additional compute resources to the service.
  2. Identify, measure, and eliminate toil by automating repetitive tasks.
  3. Define an error budget for your service level availability and minimize the remaining error budget.
  4. Allocate available engineers to the feature backlog while you ensure that the service remains within the availability target.

Answer(s): B



You are developing the deployment and testing strategies for your CI/CD pipeline in Google Cloud. You must be able to:
Reduce the complexity of release deployments and minimize the duration of deployment rollbacks.



Test real production traffic with a gradual increase in the number of affected users.



You want to select a deployment and testing strategy that meets your requirements. What should you do?

  1. Recreate deployment and canary testing
  2. Blue/green deployment and canary testing
  3. Rolling update deployment and A/B testing
  4. Rolling update deployment and shadow testing

Answer(s): B



You are creating a CI/CD pipeline to perform Terraform deployments of Google Cloud resources. Your CI/CD tooling is running in Google Kubernetes Engine (GKE) and uses an ephemeral Pod for each pipeline run. You must ensure that the pipelines that run in the Pods have the appropriate Identity and Access Management (IAM) permissions to perform the Terraform deployments. You want to follow Google-recommended practices for identity management. What should you do? (Choose two.)

  1. Create a new Kubernetes service account, and assign the service account to the Pods. Use Workload Identity to authenticate as the Google service account.
  2. Create a new JSON service account key for the Google service account, store the key as a Kubernetes secret, inject the key into the Pods, and set the GOOGLE_APPLICATION_CREDENTIALS environment variable.
  3. Create a new Google service account, and assign the appropriate IAM permissions.
  4. Create a new JSON service account key for the Google service account, store the key in the secret management store for the CI/CD tool, and configure Terraform to use this key for authentication.
  5. Assign the appropriate IAM permissions to the Google service account associated with the Compute Engine VM instances that run the Pods.

Answer(s): A,C



You are the on-call Site Reliability Engineer for a microservice that is deployed to a Google Kubernetes Engine (GKE) Autopilot cluster. Your company runs an online store that publishes order messages to Pub/Sub, and a microservice receives these messages and updates stock information in the warehousing system. A sales event caused an increase in orders, and the stock information is not being updated quickly enough. This is causing a large number of orders to be accepted for products that are out of stock. You check the metrics for the microservice and compare them to typical levels:



You need to ensure that the warehouse system accurately reflects product inventory at the time orders are placed and minimize the impact on customers. What should you do?

  1. Decrease the acknowledgment deadline on the subscription.
  2. Add a virtual queue to the online store that allows typical traffic levels.
  3. Increase the number of Pod replicas.
  4. Increase the Pod CPU and memory limits.

Answer(s): C



Your team deploys applications to three Google Kubernetes Engine (GKE) environments: development, staging, and production. You use GitHub repositories as your source of truth. You need to ensure that the three environments are consistent. You want to follow Google-recommended practices to enforce and install network policies and a logging DaemonSet on all the GKE clusters in those environments. What should you do?

  1. Use Google Cloud Deploy to deploy the network policies and the DaemonSet. Use Cloud Monitoring to trigger an alert if the network policies and DaemonSet drift from your source in the repository.
  2. Use Google Cloud Deploy to deploy the DaemonSet and use Policy Controller to configure the network policies. Use Cloud Monitoring to detect drifts from the source in the repository and Cloud Functions to correct the drifts.
  3. Use Cloud Build to render and deploy the network policies and the DaemonSet. Set up Config Sync to sync the configurations for the three environments.
  4. Use Cloud Build to render and deploy the network policies and the DaemonSet. Set up a Policy Controller to enforce the configurations for the three environments.

Answer(s): D



You are using Terraform to manage infrastructure as code within a CI/CD pipeline. You notice that multiple copies of the entire infrastructure stack exist in your Google Cloud project, and a new copy is created each time a change to the existing infrastructure is made. You need to optimize your cloud spend by ensuring that only a single instance of your infrastructure stack exists at a time. You want to follow Google-recommended practices.
What should you do?

  1. Create a new pipeline to delete old infrastructure stacks when they are no longer needed.
  2. Confirm that the pipeline is storing and retrieving the terraform.tfstate file from Cloud Storage with the Terraform gcs backend.
  3. Verify that the pipeline is storing and retrieving the terraform.tfstate file from a source control.
  4. Update the pipeline to remove any existing infrastructure before you apply the latest configuration.

Answer(s): B



  PDF
Viewing page 13 of 31
Viewing questions 97 - 104 out of 239 questions


Post your Comments and Discuss Google PROFESSIONAL CLOUD DEVOPS ENGINEER exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!