Google Updated Professional-Cloud-DevOps-Engineer Exam Questions and Answers by fern

The best option for giving developers the ability to test the latest revisions of the service before the service is exposed to customers is to run the gcloud run deploy booking-engine --no-traffic --tag devcommand and use the https://dev----booking-engine-abcdef.a.run.app URL for testing. The gcloud run deploy command is a command that deploys a new revision of your service or updates an existing service. By using the --no-traffic flag, you can prevent any traffic from being sent to the new revision. By using the --tag flag, you can assign a tag to the new revision, such as dev. This way, you can create a new revision of your service without affecting your customers. You can also use the tag-based URL (e.g., https://dev----booking-engine-abcdef.a.run.app) to access and test the new revision.

https://cloud.google.com/kubernetes-engine/docs/tutorials/autoscaling-metrics

The Google Cloud HTTP Load Balancer (GCLB) provides metrics on the number of requests and the response latency for each backend service. These metrics can be used as custom metrics for the horizontal pod autoscaler (HPA) to scale the deployment based on the load. This is the correct solution to use an appropriate SLI for scaling.

Cloud Build is a service that executes your builds on Google Cloud Platform infrastructure1. Cloud Build can be used as a pipeline runner for your CI pipeline, which is a process that automates the integration and testing of your code2. Cloud Build private pools are private, dedicated pools of workers that offer greater customization over the build environment, including the ability to access resources in a private VPC network3. A VPC network is a virtual network that provides connectivity for your Google Cloud resources and services. By using Cloud Build private pools, you can implement a solution that minimizesmanagement overhead, as Cloud Build private pools are hosted and fully-managed by Cloud Build and scale up and down to zero, with no infrastructure to set up, upgrade, or scale3. You can also implement a solution that meets your security requirement, as Cloud Build private pools use network peering to connect into your private VPC network and do not expose API traffic publicly.

Comprehensive and Detailed Explanation:

When using Managed Service for Prometheus, metrics may not appear in Cloud Monitoring if PodMonitoring is misconfigured. The most likely issue is that the PodMonitoring configuration does not reference a valid port.

PodMonitoring is required to collect metrics from workloads in GKE.

If the port is incorrect or missing, metrics won’t be scraped.

????Why not other options?

A (Check quota limits)❌→ If quotas were exceeded, you’d see explicit errors, but the question states no errors were encountered.

B (Grafana installation check)❌→ Grafana is not required for Prometheus metric collection.

C (monitoring.servicesViewer IAM role issue)❌→ This role allows viewing metrics, but does not affect metric collection.

????Official Reference:

Managed Service for Prometheus - PodMonitoring

GKE Monitoring Troubleshooting