Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Professional Cloud Database Engineer practice bank has an additional 769 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An e-commerce company manages a Cloud SQL for PostgreSQL primary instance in us-central1 with two cross-region read replicas. The instance uses a Sunday 2:00 AM maintenance window with Week 1 timing, and its maintenance version is four months old.
You receive a notification for maintenance scheduled in 10 days, overlapping an upcoming 45-day holiday freeze. Your requirements are:
Which action should you take?
When you define a deny maintenance period with explicit four-digit years in the start and end date parameters, Cloud SQL treats the exclusion as a one-time block that applies solely to that specified calendar year.
Including the specific year in a deny maintenance period is appropriate when protecting a non-recurring, one-time event—such as a major corporate acquisition cutover or a single-year regulatory audit—where you do not want the freeze to repeat on those dates in subsequent years.
Week 5.A maintenance window defines the preferred day of the week and one-hour slot when automatic updates may begin, while maintenance timing (Any, Week 1, Week 2, or Week 5) determines which rollout wave an instance belongs to relative to when the maintenance notification is issued.
Week 5 timing cannot enforce a 45-day freeze: Selecting Week 5 schedules future updates 35 to 42 days after a rollout notification is sent. This is shorter than 45 days and does not create a blocked calendar period or cancel an already-scheduled rollout in 10 days.Week 5 timing prevent rare, time-sensitive security patches.Changing maintenance timing to Week 5 while keeping a custom maintenance window is useful when you want maximum testing lead time in lower environments (Week 1 or Week 2) before production instances receive updates five weeks later.
A deny maintenance period is a defined block of days—ranging from 1 to 90 days—during which Cloud SQL is prevented from scheduling or executing routine automatic maintenance updates. It acts as a protective exclusion window that overrides any configured maintenance window.
Unlike one-time rescheduling—which is restricted by rollout timing limits and does not repeat—or modifying maintenance windows, a recurring deny maintenance period on the primary instance provides comprehensive, low-overhead protection for the entire database topology year after year.
Rescheduling planned maintenance allows administrators to postpone a specific, already-scheduled maintenance event either to the next available weekly window or to a custom date and time within a bounded deferral window.
Week 1 timing, maintenance can only be deferred up to 28 days from the original schedule—falling well short of clearing a 45-day holiday freeze.Rescheduling is the right choice when an unexpected, one-time business event (such as a major product launch or one-off migration) conflicts with a single scheduled maintenance window and only needs a short postponement of a few days to a couple of weeks.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated