Free Access Google.Professional-Cloud-DevOps-Engineer.v2026-09-16.q209 Practice Test (Page 9)

Question 36

You manage a critical, user-facing application and have configured a service level objective (SLO) in Cloud Monitoring to track 99% availability over a 30-day rolling window. Recently, a series of minor issues have increased latency, causing the error budget to be consumed at an accelerated rate. You need to be proactively notified when the service is at risk of violating its SLO before the error budget is fully depleted. What should you do?

A.In Cloud Monitoring, create an alerting policy based on the SLO's error budget burn rate. Configure the alert to trigger when the current consumption rate is projected to exhaust the budget before the end of the 30-day compliance period.

B.Create a custom dashboard in Cloud Monitoring that visualizes the SLO compliance percentage and the remaining error budget. Configure the dashboard to send a scheduled daily report through email.

C.Configure a log-based metric in Cloud Monitoring that tracks the rate of application error logs. Create an alerting policy on this metric that triggers when the error rate shows a significant anomalous deviation from its historical baseline.

D.In Metrics Explorer, create an alerting policy based on the average request latency for the application's load balancer. Configure the alert to trigger if latency exceeds a predefined threshold.

Question 37

Your product is currently deployed in three Google Cloud Platform (GCP) zones with your users divided between the zones. You can fail over from one zone to another, but it causes a 10-minute service disruption for the affected users. You typically experience a database failure once per quarter and can detect it within five minutes. You are cataloging the reliability risks of a new real-time chat feature for your product. You catalog the following information for each risk:
* Mean Time to Detect (MUD} in minutes
* Mean Time to Repair (MTTR) in minutes
* Mean Time Between Failure (MTBF) in days
* User Impact Percentage
The chat feature requires a new database system that takes twice as long to successfully fail over between zones. You want to account for the risk of the new database failing in one zone. What would be the values for the risk of database failover with the new system?

A.MTTD: 5MTTR: 10MTBF: 90Impact: 33%

B.MTTD:5MTTR: 20MTBF: 90Impact: 33%

C.MTTD:5MTTR: 10MTBF: 90Impact 50%

D.MTTD:5MTTR: 20MTBF: 90Impact: 50%

Question 38

You support a trading application written in Python and hosted on App Engine flexible environment. You want to customize the error information being sent to Stackdriver Error Reporting. What should you do?

A.Install the Stackdriver Error Reporting library for Python, and then run your code on a Compute Engine VM.

B.Install the Stackdriver Error Reporting library for Python, and then run your code on Google Kubernetes Engine.

C.Install the Stackdriver Error Reporting library for Python, and then run your code on App Engine flexible environment.

D.Use the Stackdriver Error Reporting API to write errors from your application to ReportedErrorEvent, and then generate log entries with properly formatted error messages in Stackdriver Logging.

Question 39

You are configuring Cloud Logging for a new application that runs on a Compute Engine instance with a public IP address. A user-managed service account is attached to the instance. You confirmed that the necessary agents are running on the instance but you cannot see any log entries from the instance in Cloud Logging. You want to resolve the issue by following Google-recommended practices. What should you do?

A.Enable Private Google Access on the subnet that the instance is in.

B.Export the service account key and configure the agents to use the key.

C.Update the instance to use the default Compute Engine service account.

D.Add the Logs Writer role to the service account.

Question 40

Your company follows Site Reliability Engineering principles. You are writing a postmortem for an incident, triggered by a software change, that severely affected users. You want to prevent severe incidents from happening in the future. What should you do?

A.Identify engineers responsible for the incident and escalate to their senior management.

B.Ensure that test cases that catch errors of this type are run successfully before new software releases.

C.Follow up with the employees who reviewed the changes and prescribe practices they should follow in the future.

D.Design a policy that will require on-call teams to immediately call engineers and management to discuss a plan of action if an incident occurs.

Other Version: 982Google.Professional-Cloud-DevOps-Engineer.v2026-03-30.q189; 2955Google.Professional-Cloud-DevOps-Engineer.v2025-09-27.q141; 1261Google.Professional-Cloud-DevOps-Engineer.v2023-01-21.q29; 2521Google.Professional-Cloud-DevOps-Engineer.v2022-06-30.q61; 2689Google.Professional-Cloud-DevOps-Engineer.v2022-04-13.q62; 65Google.Pass4surecert.Professional-Cloud-DevOps-Engineer.v2021-09-22.by.horace.37q.pdf

Latest Upload: 156Google.Professional-Cloud-DevOps-Engineer.v2026-09-16.q209; 135AAPC.CPC.v2026-09-16.q132; 116HP.HPE0-J82.v2026-09-16.q26; 165F5.303.v2026-09-16.q147; 158PaloAltoNetworks.NGFW-Engineer.v2026-09-16.q105; 127Workday.Workday-Pro-Recruiting.v2026-09-15.q19; 140ACAMS.CAMS-FCI.v2026-09-15.q36; 157VMware.250-614.v2026-09-15.q42; 183IAPP.CIPM.v2026-09-15.q217; 170VMware.2V0-13.25.v2026-09-14.q122

Question 36

Question 37

Question 38

Question 39

Question 40

Download PDF File