Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  2. Home
  3. Exams
  4. Google
  5. PROFESSIONAL-CLOUD-DEVOPS-ENGINEER

Google PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Exam
Professional Cloud DevOps Engineer (Page 17 )

Updated On: 1-Feb-2026
Page 7 of 37
PDF with 201 Questions

You have a CI/CD pipeline that uses Cloud Build to build new Docker images and push them to Docker Hub. You use Git for code versioning. After making a change in the Cloud Build YAML configuration, you notice that no new artifacts are being built by the pipeline. You need to resolve the issue following Site Reliability Engineering practices.
What should you do?

  1. Disable the CI pipeline and revert to manually building and pushing the artifacts.
  2. Change the CI pipeline to push the artifacts to Container Registry instead of Docker Hub.
  3. Upload the configuration YAML file to Cloud Storage and use Error Reporting to identify and fix the issue.
  4. Run a Git compare between the previous and current Cloud Build Configuration files to find and fix the bug.

Answer(s): D

Explanation:

"After making a change in the Cloud Build YAML configuration, you notice that no new artifacts are being built by the pipeline"- means something wrong on the recent change not with the image registry.



You support an application that stores product information in cached memory. For every cache miss, an entry is logged in Stackdriver Logging. You want to visualize how often a cache miss happens over time.
What should you do?

  1. Link Stackdriver Logging as a source in Google Data Studio. Filler (he logs on the cache misses.
  2. Configure Stackdriver Profiler to identify and visualize when the cache misses occur based on the logs.
  3. Create a logs-based metric in Stackdriver Logging and a dashboard for that metric in Stackdriver Monitoring.
  4. Configure BigOuery as a sink for Stackdriver Logging. Create a scheduled query to filter the cache miss logs and write them to a separate table

Answer(s): C

Explanation:

https://cloud.google.com/logging/docs/logs-based-metrics#counter-metric



You are part of an organization that follows SRE practices and principles. You are taking over the management of a new service from the Development Team, and you conduct a Production Readiness Review (PRR). After the PRR analysis phase, you determine that the service cannot currently meet its Service Level Objectives (SLOs). You want to ensure that the service can meet its SLOs in production.
What should you do next?

  1. Adjust the SLO targets to be achievable by the service so you can bring it into production.
  2. Notify the development team that they will have to provide production support for the service.
  3. Identify recommended reliability improvements to the service to be completed before handover.
  4. Bring the service into production with no SLOs and build them when you have collected operational data.

Answer(s): C



You support a multi-region web service running on Google Kubernetes Engine (GKE) behind a Global HTTP'S Cloud Load Balancer (CLB). For legacy reasons, user requests first go through a third-party Content Delivery Network (CDN). which then routes traffic to the CLB. You have already implemented an availability Service Level Indicator (SLI) at the CLB level. However, you want to increase coverage in case of a potential load balancer misconfiguration. CDN failure, or other global networking catastrophe.
Where should you measure this new SLI?

Choose 2 answers

  1. Your application servers' logs
  2. Instrumentation coded directly in the client
  3. Metrics exported from the application servers
  4. GKE health checks for your application servers
  5. A synthetic client that periodically sends simulated user requests

Answer(s): B,E



Your application images are built using Cloud Build and pushed to Google Container Registry (GCR). You want to be able to specify a particular version of your application for deployment based on the release version tagged in source control.
What should you do when you push the image?

  1. Reference the image digest in the source control tag.
  2. Supply the source control tag as a parameter within the image name.
  3. Use Cloud Build to include the release version tag in the application image.
  4. Use GCR digest versioning to match the image to the tag in source control.

Answer(s): B

Explanation:

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



Viewing page 17 of 37
Viewing questions 81 - 85 out of 201 questions



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

Join the PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Discussion