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.
An organization is deploying a transaction processing database on a Google Cloud Compute Engine virtual machine (VM). The workload has the following architectural requirements:
The engineering team wants to meet the performance targets cost-effectively without provisioning unneeded storage capacity.
Which storage type should the team select?
Google Cloud Hyperdisk Balanced is Google Cloud's next-generation block storage service designed for cloud workloads requiring flexible performance tuning. Unlike traditional persistent disks where input/output operations per second (IOPS) and throughput scale strictly in proportion to disk capacity, Hyperdisk decouples performance from disk size.

Hyperdisk Balanced is the optimal architectural choice because it directly solves the mismatch between storage capacity and performance demands, allowing direct provisioning of 30,000 IOPS and 500 MiB/s on a compact 100 GB disk.
Balanced Persistent Disk (pd-balanced) is an SSD-backed Persistent Disk offering that balances price and performance for general-purpose workloads, web servers, and container boot disks.
pd-balanced, IOPS and throughput scale proportionally with disk size (up to 6 IOPS per GB and 0.28 MiB/s per GB).pd-balanced disk delivers approximately 600 baseline IOPS and 28 MiB/s throughput, far below the required 30,000 IOPS and 500 MiB/s.pd-balanced, the organization would need to provision thousands of gigabytes of disk space that the database does not need, significantly increasing monthly costs.The application had standard general-purpose computing requirements where disk capacity naturally aligned with the proportional IOPS and throughput baselines provided by default SSDs.
While pd-balanced shares the term "Balanced" with Hyperdisk Balanced, only Hyperdisk provides independent scaling of IOPS and throughput metrics.
SSD Persistent Disk (pd-ssd) is a high-performance, traditional block storage type in Compute Engine designed for enterprise applications and databases that require low latency and high IOPS.
pd-ssd, performance limits scale directly with provisioned capacity (typically 30 IOPS per GB and 0.48 MiB/s per GB).pd-ssd volume delivers roughly 3,000 IOPS and 48 MiB/s throughput. It cannot reach 30,000 IOPS or 500 MiB/s without overprovisioning the disk size to at least 1 TB or more.pd-ssd does not support explicit custom IOPS and throughput provisioning independent of disk volume size.The dataset size was naturally large (e.g., several terabytes) such that the proportional IOPS scaling inherently satisfied the 30,000 IOPS requirement without paying for empty storage.
pd-ssd represents the previous-generation performance architecture in GCP, which has now been superseded by Google Cloud Hyperdisk for fine-grained performance tuning.
Standard Persistent Disk (pd-standard) is a standard hard disk drive (HDD) based block storage solution offered in Compute Engine, primarily optimized for large-capacity, sequential I/O workloads such as log processing and cold data archiving.
pd-standard, performance scales strictly per gigabyte of provisioned space and offers very low baseline performance per GB (typically 0.75 read IOPS and 1.5 write IOPS per GB).pd-standard disk provides only a few hundred IOPS and single-digit MiB/s throughput, falling drastically short of the required 30,000 IOPS and 500 MiB/s throughput.The workload consisted of sequential data pipelines, batch backup files, or cold log storage where low storage cost per gigabyte is the priority and high IOPS is not required.
Using HDD-backed storage for transactional databases leads to severe I/O bottlenecks and unacceptable request latency.
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