ScenarioCert
GCP PCA ยท Designing and planning a cloud solution architecture (25-25%)

Designing network, storage, and compute resources

Practice questions and explanations for the "Designing network, storage, and compute resources" objective of the Google Cloud Professional Cloud Architect exam. Skills measured as of 2026-10-22.

Skills in this objective

  • Integration with on-premises/multicloud environments
  • Google Cloud AI and machine learning solutions (e.g., Gemini LLMs, Agent Builder, Model Garden, Gemini models, and AI Hypercomputer)
  • Cloud-native networking (e.g., virtual private cloud [VPC], peering, firewalls, load balancers, routing, container networking, shared VPC, and Private Service Connect)
  • Choosing data processing solutions
  • Choosing appropriate storage types (e.g., object, file, and databases)
  • Mapping compute needs to platform products (e.g., Google Kubernetes Engine [GKE], Cloud Run, and Cloud Run functions)
  • Choosing compute resources (e.g., spot VMs, custom machine types, and specialized workload)

Test yourself on this domain

Take the free 15-question test, or unlock all 150 questions and practice this domain on its own.

Sample questions

4 of the 11 questions we have for this objective, shown with the answer and the reasoning.

Designing network, storage, and compute resources

Harlow Group has eight application teams, each with its own Google Cloud project. The central network team must own all subnets, firewall rules, routes, and the Cloud Interconnect attachments, while application teams must be able to deploy VMs and GKE clusters into subnets they are given. Workloads in different team projects must talk to each other using internal IP addresses without extra network hops.

Which network design should you recommend?

  1. ACreate a VPC network in each team project and connect them all with VPC Network PeeringSeparate peered networks leave each team owning its own subnets, routes, and firewall rules, which conflicts with the requirement that the central network team owns them.
  2. BCreate a Shared VPC in a host project owned by the network team, attach the eight team projects as service projects, and grant each team the Compute Network User role on its subnetsShared VPC keeps network control in the host project while service projects deploy into shared subnets, and all workloads share one VPC network for direct internal communication.
  3. CCreate a VPC network in each team project and connect them with HA VPN tunnelsVPN between VPC networks adds tunnels, cost, and bandwidth limits, and it still leaves network control with each team.
  4. DPut all eight teams' workloads into one project with a single VPC networkOne project removes the separation of billing, quotas, and IAM that per-team projects provide.
Why: Shared VPC is Google Cloud's pattern for central network administration with decentralized application ownership. The host project holds the VPC network, subnets, firewall rules, and hybrid connectivity; service projects are attached and their administrators receive the Compute Network User role at the subnet level to use only what they are given. Because everything is one VPC network, traffic between teams stays internal with no peering or VPN hops. Peering and VPN connect separately owned networks, which is the opposite of the stated ownership model.
Designing network, storage, and compute resources

Lumenrise Utilities is building a platform for 30 million smart meters that each report a reading every 15 seconds, which is about 2 million writes per second. The customer app looks up a single meter's readings for a time range with single-digit millisecond latency, and data scientists run occasional large analytical scans. The data has no need for joins or multi-row transactions.

Which database should you recommend for the meter readings?

  1. ABigtable with a row key that combines the meter ID and a timestampBigtable scales linearly to millions of writes per second, serves key and key-range lookups in single-digit milliseconds, and a meter ID plus timestamp row key makes time-range reads for one meter efficient.
  2. BBigQuery tables partitioned by dayBigQuery is excellent for the analytical scans, but it is not designed for single-digit millisecond lookups serving a customer app.
  3. CCloud SQL for PostgreSQL with read replicasCloud SQL is a single-primary relational database that cannot absorb 2 million writes per second.
  4. DFirestore in Native mode with one document per readingFirestore suits mobile and web application data, but sustained write rates of this size against sequential keys run into hotspotting and cost far more than Bigtable.
Why: Pick a database by access pattern and scale. Very high write throughput, key or key-range reads, low latency, and no relational needs describe a wide-column store, which is Bigtable. Row key design is the critical decision: putting the meter ID first spreads writes across nodes and keeps one meter's readings together for range scans, while a timestamp-first key would create hotspots. BigQuery remains useful for the data scientists, often fed from Bigtable or queried through an external table, but it is not the serving store.
Designing network, storage, and compute resources

Tidewell Software sells a fraud-scoring API that runs behind an internal passthrough Network Load Balancer in its own VPC network. Forty enterprise customers want to call the API privately from their own Google Cloud VPC networks. Many customers use the same 10.0.0.0/8 ranges that Tidewell uses, Tidewell must not gain any network access to customer networks, and each customer must be approved before it can connect.

Which design should you recommend?

  1. ASet up VPC Network Peering between Tidewell's network and each customer networkPeering fails when subnet ranges overlap, and it exposes whole networks to each other rather than a single service.
  2. BAdd every customer project as a service project of a Shared VPC hosted by TidewellShared VPC is for projects inside one organization's administrative control, not for separate customer companies, and it would give customers access to Tidewell's network.
  3. CPublish the service with a Private Service Connect service attachment that requires explicit project approval, and have each customer create a Private Service Connect endpoint in its own VPC networkPrivate Service Connect exposes only the service through an endpoint IP address in the consumer's own network, works with overlapping IP ranges, is unidirectional, and supports accept lists for approving consumers.
  4. DExpose the API through Cloud NAT so that customers reach it on a public IP addressCloud NAT provides outbound internet access for private resources; it does not publish inbound services, and the traffic would not be private.
Why: Private Service Connect is the producer-consumer pattern for exposing a service privately across organizations. The producer publishes a service attachment in front of an internal load balancer; consumers create an endpoint with an IP address from their own range, so overlapping address space does not matter and only the published service is reachable. Connection preferences such as accepting only approved projects give the producer control. VPC Network Peering is the trap: it is simple between networks you control with distinct ranges, but it breaks on overlap and exposes more than the service.
Designing network, storage, and compute resources

Fairhollow Press receives manuscript files from authors. Each time a file is uploaded to a Cloud Storage bucket, a short piece of Python code must extract metadata and write it to Firestore, which takes under 10 seconds. Uploads happen a few hundred times a day, and the team wants to pay nothing when there are no uploads and manage no servers or containers.

Which compute option should you recommend?

  1. AA GKE Autopilot cluster running a Deployment that polls the bucketAutopilot removes node management but still requires container images and Kubernetes manifests, and a polling Deployment runs even when there are no uploads.
  2. BA Cloud Run functions function triggered by the Cloud Storage object finalized event through EventarcCloud Run functions runs a single function from source code in response to events such as Cloud Storage uploads, scales to zero, and needs no container or server management.
  3. CA Compute Engine VM with a cron job that checks the bucket every minuteA VM bills while idle and leaves the team to patch the operating system, which the scenario rules out.
  4. DA Dataflow streaming pipeline that reads bucket notificationsDataflow is built for large-scale data processing and keeps workers running, which is costly and excessive for a few hundred small events a day.
Why: Map the shape of the workload to the platform. A short, event-triggered piece of code with low volume is the case Cloud Run functions is designed for: deploy source, attach an event trigger, and pay only while it runs. Cloud Run services fit containerized HTTP applications, GKE fits teams that need Kubernetes, and Compute Engine fits workloads that need control of the operating system. The scenario's phrases no servers or containers and pay nothing when idle point to functions.

Written from the public documentation. Not affiliated with Google Cloud. Official study guide.