Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
A retail organization runs its primary transactional database on Google Cloud using Cloud SQL for MySQL. During seasonal promotions, the application experiences sudden, unpredictable surges in transaction volume and data growth. In the past, unexpected data spikes caused on-premises database crashes due to disk space exhaustion.
The cloud architect needs to design a storage provisioning and capacity management strategy that satisfies the following requirements:
Which configuration strategy should the architect implement?
Cloud SQL automatic storage increase (storage auto-resize) is a managed feature that automatically detects when an instance is running low on available storage capacity and allocates additional disk space in real time. Configuring an automatic storage increase limit sets an upper threshold on how much storage the instance can automatically provision, providing cost governance alongside automated availability.
This approach directly leverages native Google Cloud database management features to eliminate operational toil and downtime risks, striking the optimal balance between continuous database availability and predictable financial control.
This approach keeps storage capacity static and attempts to trigger programmatic disk expansion via Cloud Monitoring alerts and Cloud Tasks only when the database disk reaches near-capacity (95% full).
The platform lacked native auto-resize capabilities and required custom governance workflows across non-managed storage volumes.
Local SSDs are ephemeral, physically attached solid-state drives used on Compute Engine instances for temporary scratch space and high-IOPS transient workloads. Instance group autoscalers dynamically adjust the number of VM instances in a managed instance group based on load.
You were designing a stateless web tier on Compute Engine VMs using local caching rather than provisioning storage for a managed Cloud SQL relational database.
This proposal relies on unbounded storage auto-resize during traffic surges and attempts to use an external automation script via Google Cloud Functions to shrink the database disk capacity back down after the promotional event ends.
The cloud database engine supported native online disk shrinking and dynamic storage contraction, which is not a feature of Cloud SQL managed storage.
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