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 designing a high-availability database architecture on Google Cloud using Compute Engine virtual machines and managed database services. The engineering team is preparing a monthly budget estimate and evaluating how storage pricing is calculated for standard and SSD Persistent Disks, as well as multi-zone configurations. They need to ensure that their financial projections account for idle periods and disaster recovery replication.
Which principle should the team use to accurately estimate their Persistent Disk storage costs?
Consumption-based or pay-as-you-go data billing charges users exclusively for the exact volume of data stored (such as raw bytes written), which is standard for object storage solutions like Cloud Storage or query storage in BigQuery. In those services, an empty bucket or table incurs zero storage fees, and costs increase dynamically only as files or rows are uploaded.
This pricing model would be accurate if the workload used Cloud Storage object buckets to hold backup files or export archives, where customers are billed solely for the gigabytes of data actually stored and where inactive compute infrastructure incurs no ongoing storage overhead.
Google Cloud Persistent Disk provides durable, network-attached block storage designed for virtual machines on Compute Engine and managed services such as Cloud SQL. Unlike object storage, block storage reserves a dedicated partition of virtualized disk space that is formatted and managed directly by the operating system or database engine. Pricing for Persistent Disk is calculated per gigabyte-month (GiB/month) based strictly on the provisioned capacity allocated at disk creation, rather than the volume of data actually written to the file system.

Understanding that Persistent Disk charges depend on provisioned capacity, persistent reservation, and cross-zone replication allows architects to forecast storage expenditures accurately, avoid surprise bills from idle stopped instances, and properly balance database availability against budget constraints.
Google Cloud offers multiple Persistent Disk types suited for different workload profiles, including Standard Persistent Disk (pd-standard using HDD), Balanced Persistent Disk (pd-balanced using SSD), and SSD Persistent Disk (pd-ssd). Each tier delivers distinct input/output operations per second (IOPS) and throughput limits, with higher tiers offering substantially lower latency for random read and write operations.
pd-balanced and pd-ssd) carry higher unit costs per provisioned gigabyte than magnetic hard disk drives (pd-standard) due to the higher underlying hardware and infrastructure expenses.pd-standard, pd-balanced, and pd-ssd, maximum IOPS and throughput increase proportionally with every gigabyte provisioned until instance vCPU limits are reached.pd-ssd offers high IOPS at a higher per-GiB price point, pd-standard offers budget sequential storage at the lowest per-GiB price, and pd-balanced provides an intermediate cost-to-performance compromise.pd-extreme), allow customers to provision and pay separately for target IOPS and throughput independent of disk volume.This logic would apply if the team were evaluating transactional NoSQL databases like Firestore in Datastore mode, or object storage retrieval APIs in Cloud Storage, where pricing incorporates discrete charges for read, write, and delete operations rather than relying purely on provisioned capacity scaling.
A Regional Persistent Disk is a durable block storage device that provides synchronous replication of data between two zones located within the same Google Cloud region. If an unexpected zonal failure or scheduled maintenance occurs in one zone, the attached workload or virtual machine can rapidly fail over to the secondary zone using the standby disk replica.
This assumption would only be valid if Google Cloud included multi-zone physical block replication at no additional cost as part of a basic zonal storage SLA, or if the workload relied on an application-level logical replication framework that handled cross-zone syncing across separate, independently billed compute and storage resources.
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