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 65–72 (page: 10)

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

You need to define Service Level Objectives (SLOs) for a high-traffic multi-region web application. Customers expect the application to always be available and have fast response times. Customers are currently happy with the application performance and availability. Based on current measurement, you observe that the 90th percentile of latency is 120ms and the 95th percentile of latency is 275ms over a 28-day window. What latency SLO would you recommend to the team to publish?

  1. 90th percentile ­ 100ms
    95th percentile ­ 250ms
  2. 90th percentile ­ 120ms
    95th percentile ­ 275ms
  3. 90th percentile ­ 150ms
    95th percentile ­ 300ms
  4. 90th percentile ­ 250ms
    95th percentile ­ 400ms

Answer(s): C



You support a large service with a well-defined Service Level Objective (SLO). The development team deploys new releases of the service multiple times a week. If a major incident causes the service to miss its SLO, you want the development team to shift its focus from working on features to improving service reliability. What should you do before a major incident occurs?

  1. Develop an appropriate error budget policy in cooperation with all service stakeholders.
  2. Negotiate with the product team to always prioritize service reliability over releasing new features.
  3. Negotiate with the development team to reduce the release frequency to no more than once a week.
  4. Add a plugin to your Jenkins pipeline that prevents new releases whenever your service is out of SLO.

Answer(s): A



Your company is developing applications that are deployed on Google Kubernetes Engine (GKE). Each team manages a different application. You need to create the development and production environments for each team while you minimize costs. Different teams should not be able to access other teams' environments. You want to follow Google-recommended practices. What should you do?

  1. Create one Google Cloud Project per team. In each project, create a cluster for Development and one for Production. Grant the teams IAM access to their respective clusters.
  2. Create one Google Cloud Project per team. In each project, create a cluster with a Kubernetes namespace for Development and one for Production. Grant the teams IAM access to their respective clusters.
  3. Create a Development and a Production GKE cluster in separate projects. In each cluster, create a Kubernetes namespace per team, and then configure Identity Aware Proxy so that each team can only access its own namespace.
  4. Create a Development and a Production GKE cluster in separate projects. In each cluster, create a Kubernetes namespace per team, and then configure Kubernetes Role-based access control (RBAC) so that each team can only access its own namespace.

Answer(s): D


Reference:

https://kubernetes.io/docs/reference/access-authn-authz/rbac/



Some of your production services are running in Google Kubernetes Engine (GKE) in the eu-west-1 region. Your build system runs in the us-west-1 region. You want to push the container images from your build system to a scalable registry to maximize the bandwidth for transferring the images to the cluster. What should you do?

  1. Push the images to Artifact Registry using the us-docker.pkg.dev hostname.
  2. Push the images to Artifact Registry using the europe-docker.pkg.dev hostname.
  3. Push the images to Artifact Registry using the europe-west1-docker.pkg.dev hostname.
  4. Push the images to a private image registry running on a Compute Engine instance in the eu-west-1 region.

Answer(s): C


Reference:

https://cloud.google.com/container-registry/docs/pushing-and-pulling



You manage several production systems that run on Compute Engine in the same Google Cloud project. Each system has its own set of dedicated Compute Engine instances. You want to know how must it costs to run each of the systems. What should you do?

  1. In the Google Cloud Console, use the Cost Breakdown section to visualize the costs per system.
  2. Assign all instances a label specific to the system they run. Configure BigQuery billing export and query costs per label.
  3. Enrich all instances with metadata specific to the system they run. Configure Cloud Logging to export to BigQuery, and query costs based on the metadata.
  4. Name each virtual machine (VM) after the system it runs. Set up a usage report export to a Cloud Storage bucket. Configure the bucket as a source in BigQuery to query costs based on VM name.

Answer(s): B


Reference:

https://cloud.google.com/compute/docs/logging/usage-export



You use Cloud Build to build and deploy your application. You want to securely incorporate database credentials and other application secrets into the build pipeline. You also want to minimize the development effort. What should you do?

  1. Create a Cloud Storage bucket and use the built-in encryption at rest. Store the secrets in the bucket and grant Cloud Build access to the bucket.
  2. Encrypt the secrets and store them in the application repository. Store a decryption key in a separate repository and grant Cloud Build access to the repository.
  3. Use client-side encryption to encrypt the secrets and store them in a Cloud Storage bucket. Store a decryption key in the bucket and grant Cloud Build access to the bucket.
  4. Use Cloud Key Management Service (Cloud KMS) to encrypt the secrets and include them in your Cloud Build deployment configuration. Grant Cloud Build access to the KeyRing.

Answer(s): D


Reference:

https://cloud.google.com/build/docs/securing-builds/use-encrypted-credentials



You support a popular mobile game application deployed on Google Kubernetes Engine (GKE) across several Google Cloud regions. Each region has multiple Kubernetes clusters. You receive a report that none of the users in a specific region can connect to the application. You want to resolve the incident while following Site Reliability Engineering practices. What should you do first?

  1. Reroute the user traffic from the affected region to other regions that don't report issues.
  2. Use Cloud Monitoring to check for a spike in CPU or memory usage for the affected region.
  3. Add an extra node pool that consists of high memory and high CPU machine type instances to the cluster.
  4. Use Cloud Logging to filter on the clusters in the affected region, and inspect error messages in the logs.

Answer(s): A


Reference:

https://cloud.google.com/error-reporting/docs/viewing-errors



You are writing a postmortem for an incident that severely affected users. You want to prevent similar incidents in the future. Which two of the following sections should you include in the postmortem? (Choose two.)

  1. Metrics showing the impacted service's performance before, during, and after the incident.
  2. Copies of the design documents for all the services impacted by the incident.
  3. An explanation of the root cause of the incident.
  4. A Cloud Monitoring report showing the correlation of this incident to previous incidents.
  5. A list of action items to prevent a recurrence of the incident.

Answer(s): C,E



  PDF
Viewing page 10 of 31
Viewing questions 73 - 80 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!