PCDOE Drag & Drop — 10 Questions

Question 1

Arrange the steps to recover a Google Cloud SQL instance from a point-in-time backup.

Accepted Answer

Identify time, then Clone, then Verify, then Promote, then Update connections. The correct sequence for recovering a Google Cloud SQL instance from a point-in-time backup is: first, identify the exact point-in-time to recover; second, clone the instance to that time; third, verify the cloned instance's data; fourth, promote the clone to become the primary instance; and fifth, update application connections to use the new primary. This order ensures a consistent and verifiable recovery process.

Answer

Clone, then Identify time, then Verify, then Promote, then Update connections

Answer

Identify time, then Clone, then Promote, then Verify, then Update connections

Answer

Clone, then Identify time, then Promote, then Verify, then Update connections

Question 2

Order the steps to set up a CI/CD pipeline using Cloud Build and Cloud Deploy for a Cloud Run service.

Accepted Answer

Step 1: Create build config → Step 2: Set trigger → Step 3: Define delivery pipeline → Step 4: Push code → Step 5: Promote. The correct order for setting up a CI/CD pipeline using Cloud Build and Cloud Deploy for a Cloud Run service begins with creating a build configuration file (cloudbuild.yaml) that specifies how to build and test the application. Next, you set a trigger (e.g., on push to a branch) in Cloud Build to automatically start builds. Then, you define a delivery pipeline in Cloud Deploy with targets (e.g., staging, production) and approval gates. After that, you push code to the repository, which triggers the build and, if successful, creates a release in the delivery pipeline. Finally, you promote the release through the stages (e.g., from staging to production) either automatically or after manual approval. This order ensures each prerequisite is in place before the next step, enabling a seamless automated workflow.

Answer

Step 1: Create build config → Step 2: Set trigger → Step 3: Push code → Step 4: Define delivery pipeline → Step 5: Promote

Answer

Step 1: Define delivery pipeline → Step 2: Create build config → Step 3: Set trigger → Step 4: Push code → Step 5: Promote

Answer

Step 1: Push code → Step 2: Create build config → Step 3: Set trigger → Step 4: Define delivery pipeline → Step 5: Promote

Question 3

Arrange the steps to troubleshoot a high latency issue on a Google Cloud HTTP(S) Load Balancer.

Accepted Answer

Check health checks, then review load balancer logs, then analyze metrics, then identify the problematic backend, then take corrective action.. Start with health checks, then logs, metrics, identify culprit, and take action.

Answer

Analyze metrics, then review logs, then check health checks, then identify the problematic backend, then take corrective action.

Answer

Check health checks, then identify the problematic backend from logs, then take corrective action, then analyze metrics, then verify.

Answer

Review logs, then analyze metrics, then identify the problematic backend, then take corrective action.

Question 4

Arrange the steps to set up a Google Cloud Monitoring alerting policy for a Compute Engine instance.

Accepted Answer

Create notification channel, then define condition, set evaluation parameters, attach the channel, then save.. First create a notification channel, then define the condition, set evaluation parameters, attach the channel, and save.

Answer

Save, then attach the channel, set evaluation parameters, define condition, then create notification channel.

Answer

Define condition, then create notification channel, attach the channel, set evaluation parameters, then save.

Answer

Create notification channel, set evaluation parameters, define condition, attach the channel, then save.

Question 5

Order the steps to set up a log-based metric in Cloud Logging for error tracking.

Accepted Answer

Filter logs -> Create metric -> Set alert -> Test -> Verify. The correct sequence to set up a log-based metric in Cloud Logging for error tracking is: first, filter logs to isolate relevant entries; second, create a metric based on that filter; third, set an alert to trigger on metric conditions; fourth, test the alert to ensure it works; and finally, verify the setup. This order ensures each step builds logically on the previous one.

Answer

Create metric -> Filter logs -> Set alert -> Test -> Verify

Answer

Filter logs -> Set alert -> Create metric -> Test -> Verify

Answer

Filter logs -> Create metric -> Test -> Set alert -> Verify

Question 6

Order the steps to respond to a Google Cloud security incident involving a compromised service account key.

Accepted Answer

Revoke key, then rotate key, then audit logs, then assess impact, then update policies.. The correct order for responding to a compromised service account key is: first revoke the key to stop unauthorized use, then rotate (reissue) a new key to restore legitimate access, then audit logs to understand the scope, then assess the impact on resources, and finally update security policies to prevent future incidents. This sequence balances containment, recovery, investigation, and improvement.

Answer

Audit logs, then revoke key, then rotate key, then assess impact, then update policies.

Answer

Rotate key, then revoke key, then audit logs, then assess impact, then update policies.

Answer

Revoke key, then audit logs, then rotate key, then assess impact, then update policies.

Question 7

Order the steps to configure a VPC Network Peering between two projects.

Accepted Answer

Create VPC networks in both projects, then configure firewall rules to allow traffic between the VPCs, then create a peering connection from Project A to Project B, then create a peering connection from Project B to Project A, then verify the peering connection.. The correct sequence for configuring VPC Network Peering is to first create the VPC networks in both projects, then configure firewall rules to allow traffic, then create the peering connection in both directions (from Project A to Project B and from Project B to Project A), and finally verify connectivity. Common mistakes include performing steps out of order or omitting the reverse peering.

Answer

Create VPC networks in both projects, then create peering from A to B, then create peering from B to A, then configure firewall rules, then verify.

Answer

Create VPC networks in both projects, then create peering from A to B, then configure firewall rules, then verify.

Answer

Configure firewall rules, then create VPC networks in both projects, then create peering from A to B, then create peering from B to A, then verify.

Question 8

Order the steps to deploy a new version of a microservice to Google Kubernetes Engine using a rolling update.

Accepted Answer

Update the manifest, then apply the manifest using kubectl apply, then monitor the rollout status, then verify the deployment, then roll back if needed.. The correct sequence for a rolling update in GKE is: update the manifest, apply it with kubectl apply, monitor the rollout status, verify the deployment, and roll back if needed. This ensures the new version is properly deployed and validated before considering it successful, with a safety net for issues.

Answer

Update the manifest, then apply the manifest using kubectl apply, then verify the deployment, then monitor the rollout status, then roll back if needed.

Answer

Apply the manifest using kubectl apply, then update the manifest, then monitor the rollout status, then verify the deployment, then roll back if needed.

Answer

Update the manifest, then monitor the rollout status, then apply the manifest using kubectl apply, then verify the deployment, then roll back if needed.

Question 9

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.

Question 10

Arrange the steps to migrate a monolithic application to microservices on Google Kubernetes Engine.

Accepted Answer

Identify contexts, then containerize, then deploy, then set up communication between microservices, then redirect traffic.. Identify contexts, containerize, deploy, set up communication, redirect traffic.

Answer

Containerize, then identify contexts, then deploy, then set up communication between microservices, then redirect traffic.

Answer

Identify contexts, then deploy, then containerize, then set up communication between microservices, then redirect traffic.

Answer

Identify contexts, then containerize, then set up communication between microservices, then deploy, then redirect traffic.