PCDOE Practice Test 8 — 10 Questions

Question 1

After deploying a new version of a Cloud Run service, the team notices an increase in 5xx errors. They want to quickly revert to the previous version while minimizing user impact. What is the recommended approach?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Use Cloud Run's traffic management to set 100% of traffic to the previous revision.. Cloud Run supports traffic splitting between revisions, allowing you to instantly route 100% of traffic to the previous revision without redeploying. This minimizes user impact because the rollback is immediate and does not require rebuilding or re-pulling container images. Option D is correct because it leverages Cloud Run's built-in traffic management feature for zero-downtime rollbacks.

Answer

Set the minimum number of instances of the new revision to 0.

Answer

Redeploy the previous version from the container registry.

Answer

Modify the ingress settings to restrict traffic to the new revision.

Question 2

Refer to the exhibit. A DevOps engineer notices that instance-1 runs on older CPU platform. The application is sensitive to CPU features that are only available on Skylake or newer. Which action should be taken to optimize performance?

Accepted Answer

Stop instance-1 and update the minimum CPU platform to Skylake.. Stopping the instance and updating the minimum CPU platform to Skylake ensures that the instance is rescheduled onto a host that meets the required CPU feature set. This action directly addresses the application's sensitivity to CPU features available only on Skylake or newer, without requiring a full recreation or risking compatibility issues during live migration.

Answer

Live migrate instance-1 to a different host.

Answer

Use Terraform to add a lifecycle rule to ignore changes.

Answer

Terminate instance-1 and recreate it with a newer machine type.

Question 3

A DevOps team is setting up SLOs for a service with two critical metrics: availability and latency. They want to measure over a 30-day window. Which approach correctly defines an SLO?

Accepted Answer

Use Cloud Monitoring to create a custom SLI based on request latency metrics and set an SLO with a 30-day rolling window. It uses Cloud Monitoring to create a custom SLI based on request latency metrics, which is a valid SLI type, and sets an SLO with a 30-day rolling window, matching the requirement. Cloud Monitoring's SLO feature natively supports rolling windows, and latency is a standard metric for defining service-level objectives.

Answer

Use Cloud Monitoring to create a custom SLI based on logs and set an SLO with a 7-day rolling window

Answer

Use Cloud Tasks to schedule a cron job that calculates availability

Answer

Use Stackdriver Monitoring (deprecated) to set an SLO with a fixed 30-day window

Question 4

Refer to the exhibit. The output shows a recommendation from the Cloud Cost Optimization recommender for an instance in us-central1-a. The instance is a production web server that consistently runs at 25% CPU utilization during peak hours. What should the DevOps engineer do to implement this recommendation with minimal risk?

Accepted Answer

Stop the instance, change the machine type to n2-standard-4, and start it again.. The Cloud Cost Optimization recommender has identified that the current instance is over-provisioned for its actual workload (25% CPU utilization during peak hours). By stopping the instance, changing the machine type to n2-standard-4 (which has 4 vCPUs and 16 GB RAM, matching the recommended 4 vCPUs and 15 GB memory), and starting it again, the engineer rightsizes the instance without incurring downtime during the change itself. This approach minimizes risk because the instance is stopped only briefly for the machine type change, and the new machine type is a standard, well-tested configuration that aligns with the recommender's analysis.

Answer

Ignore the recommendation because the instance is production and any change might cause downtime.

Answer

Add a second n2-standard-4 instance behind a load balancer to distribute load.

Answer

Use a custom machine type with 4 vCPUs and 32 GB memory to ensure enough RAM.

Question 5

A DevOps team is using Cloud Build to build and push container images. The build times have increased significantly. They suspect that the build cache is not being used effectively. Which build configuration change would likely improve cache usage?

Accepted Answer

Use kaniko instead of Docker. Kaniko is a cache-aware container image builder that can leverage a remote image registry as a cache layer, unlike the default Docker builder which relies on a local Docker daemon and its local layer cache. By using Kaniko with a configured cache repository, the team can reuse previously built layers across builds, even when builds run on different Cloud Build workers, significantly reducing build times.

Answer

Increase the machine type

Answer

Use a private pool

Answer

Enable parallel builds

Question 6

Which TWO are best practices for implementing CI/CD on Google Cloud?

Accepted Answer

Use Artifact Registry for storing container images.. Artifact Registry is the recommended service for storing, managing, and securing container images and other artifacts in Google Cloud. It integrates natively with Cloud Build, Cloud Run, and Kubernetes, providing vulnerability scanning and IAM-based access control, which are essential for a secure CI/CD pipeline.

Answer

Use Cloud Run for all services.

Answer

Use Cloud Build for all deployments, including infrastructure changes.

Answer

Use GitHub Actions instead of Cloud Build.

Question 7

Refer to the exhibit. You are reviewing an alert policy for CPU utilization. What is a potential problem with this configuration?

Accepted Answer

The duration is too short, which may cause noise during spikes.. A short duration in a CPU utilization alert policy means the threshold must be breached for only a brief period before triggering an incident. This can cause noise during transient spikes that are not indicative of a sustained problem, leading to false positives and alert fatigue for operations teams.

Answer

The autoClose time is too long.

Answer

The threshold is set too low.

Answer

The combiner should be 'AND'.

Question 8

Which TWO are benefits of using Cloud Build triggers to implement CI/CD pipelines?

Accepted Answer

Start a build automatically when changes are pushed to a repository. Cloud Build triggers can be configured to automatically start a build in response to events such as a push to a repository branch or the creation of a pull request. This event-driven automation is the foundation of a CI/CD pipeline, eliminating the need for manual build initiation and ensuring that every code change is validated immediately.

Answer

Deploy to a specific Google Cloud region based on the trigger

Answer

Support only a single branch per trigger

Answer

Automatically provision infrastructure as part of the build

Question 9

A team uses Cloud Monitoring alerting policies with multiple conditions. They want an incident to fire only when both conditions are met simultaneously. What should they configure?

Accepted Answer

Set the alerting policy combiner to 'AND'. Cloud Monitoring alerting policies support a 'combiner' field that can be set to 'AND' to require that all conditions are met simultaneously before the incident fires. This ensures the alert triggers only when both conditions are true at the same evaluation window, rather than when either condition is met.

Answer

Create two separate alerting policies

Answer

Create a single condition with a ratio metric

Answer

Use a log-based metric condition

Question 10

Arrange the steps to implement a canary deployment for a Cloud Run service.

Accepted Answer

Deploy new revision with 0% traffic, then shift a small percentage of traffic to it, then monitor, then gradually increase traffic, then remove old revision.. In a canary deployment for Cloud Run, the correct sequence ensures minimal risk. First, deploy the new revision with 0% traffic. Then, route a small percentage (e.g., 1%) to it and monitor for errors or performance issues. If successful, gradually increase traffic while monitoring. Once the new revision is fully validated, point 100% traffic to it and remove the old revision. This incremental approach limits blast radius and allows rollback.

Answer

Shift a small percentage of traffic to the new revision, then deploy the new revision, then monitor, then gradually increase traffic, then remove old revision.

Answer

Deploy new revision with 0% traffic, then gradually increase traffic to 100%, then monitor, then remove old revision.

Answer

Deploy new revision with 0% traffic, then shift a small percentage of traffic, then remove old revision, then monitor, then gradually increase traffic.