Google Exam Professional Cloud Database Engineer Topic 3 Question 54 Discussion

Actual exam question for Google's Professional Cloud Database Engineer exam

Question #: 54
Topic #: 3

[All Professional Cloud Database Engineer Questions]

You manage a meeting booking application that uses Cloud SQL. During an important launch, the Cloud SQL instance went through a maintenance event that resulted in a downtime of more than 5 minutes and adversely affected your production application. You need to immediately address the maintenance issue to prevent any unplanned events in the future. What should you do?

ASet your production instance's maintenance window to non-business hours.

BMigrate the Cloud SQL instance to Cloud Spanner to avoid any future disruptions due to maintenance.

CContact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.

DUse Cloud Scheduler to schedule a maintenance window of no longer than 5 minutes.

Show Suggested Answer

Suggested Answer: C

Cloud Scheduler triggers actions at regular fixed intervals, whereas Cloud Tasks triggers actions based on how the individual task object is configured. Reference: https://cloud.google.com/tasks/docs/comp-tasks-sched

by Marvel at Mar 20, 2025, 07:32 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Database Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Joaquin

1 months ago

Wait, so the Cloud SQL instance went down for more than 5 minutes? That's like trying to run a meeting booking app on a toaster oven. Might as well just use carrier pigeons!

upvoted 0 times

...

Mari

2 months ago

Using Cloud Scheduler to limit the maintenance window to 5 minutes? That's like trying to fit an elephant in a shoebox! Good luck with that one.

upvoted 0 times

Jackie

12 days ago

Using Cloud Scheduler to limit the maintenance window to 5 minutes? That's like trying to fit an elephant in a shoebox! Good luck with that one.

upvoted 0 times

...

Jess

14 days ago

C) Contact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.

upvoted 0 times

...

Ressie

17 days ago

A) Set your production instance's maintenance window to non-business hours.

upvoted 0 times

...

Malcolm

2 months ago

Contacting Support is definitely the way to go. They should be able to provide insights and help me address this issue.

upvoted 0 times

Tanja

2 months ago

C) Contact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.

upvoted 0 times

...

Georgiann

2 months ago

A) Set your production instance's maintenance window to non-business hours.

upvoted 0 times

...

Mertie

2 months ago

I'm not sure, maybe we should also contact Support to understand why it happened in the first place.

upvoted 0 times

...

Brett

2 months ago

Migrating to Cloud Spanner seems like an overkill. I'd rather just work with Support to understand the root cause and prevent future disruptions.

upvoted 0 times

...

Nan

2 months ago

I agree with Timmy, that seems like the best option to prevent future downtime.

upvoted 0 times

...

Mee

2 months ago

Setting the maintenance window to non-business hours is a great idea. That way, my users won't be affected by any downtime.

upvoted 0 times

Charlene

16 days ago

That's a good point. I should definitely reach out to Support to investigate the downtime issue.

upvoted 0 times

...

Loreta

18 days ago

C) Contact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.

upvoted 0 times

...

Jeannetta

19 days ago

Setting the maintenance window to non-business hours is a great idea. That way, my users won't be affected by any downtime.

upvoted 0 times

...

Sage

19 days ago

A) Set your production instance's maintenance window to non-business hours.

upvoted 0 times

...

Kizzy

21 days ago

Setting the maintenance window to non-business hours is a great idea. That way, my users won't be affected by any downtime.

upvoted 0 times

...

Lavonne

28 days ago

C) Contact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.

upvoted 0 times

...

Fletcher

2 months ago

A) Set your production instance's maintenance window to non-business hours.

upvoted 0 times

...

Timmy

3 months ago

I think we should set the maintenance window to non-business hours to avoid disruptions.

upvoted 0 times

...