Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your team needs to run complex analytical queries against a production Cloud SQL instance. These queries process large data joins and aggregate operations that generate substantial temporary tables, causing disk space usage to spike rapidly.
Which strategy should you implement to optimize query execution and prevent database outages during these operations?
Preemptive storage resizing is the proactive practice of manually increasing a Cloud SQL instance's provisioned disk capacity prior to executing workloads known to consume large amounts of disk space rapidly, such as complex queries creating substantial temporary tables or heavy batch imports.
out of disk space errors).While automatic storage increase is a critical safety feature for steady, predictable data growth, it is reactive. For scheduled, high-intensity operations that rapidly inflate disk usage, proactive manual resizing is the recommended operational standard to guarantee resource availability and avoid instance termination.
Storage shrinking in database management refers to reducing allocated underlying physical disk space after data or temporary objects are deleted.
The requirement was focused on post-migration disk cleanup or long-term storage reclamation after a one-time archiving of historical data.
Disabling automatic storage increase locks the provisioned disk capacity to a fixed size, preventing Cloud SQL from adding any disk space when thresholds are breached.
You had a strict cost cap and intentionally chose to fail non-critical test queries rather than allow disk size to expand permanently.
Automatic storage increase is a Cloud SQL setting that monitors disk capacity and provisions additional storage when free space falls below a defined threshold percentage.
This approach would be appropriate for gradual, organic application data growth over days or weeks where data consumption rates are steady and predictable.
Change the inputs and watch how the outcome changes.

Change the strategy and workload pattern to see how the Cloud SQL instance and its disk respond.
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