Google Cloud Professional Cloud Architect · Free practice question 3 of 12
AlloyDB read pools for read scaling
Pevensey Insurance runs AlloyDB for PostgreSQL for its policy platform. Reporting queries during business hours slow down transactional writes on the primary instance. The deciding constraint is to scale reads with minimal application change and no separate replication to manage. What should the architect recommend?
- A.An AlloyDB read pool instance, with reporting connections sent to its endpoint
- B.More vCPUs for the primary instance, added until reporting no longer affects transactional writes
- C.A second AlloyDB cluster kept in sync by a custom replication script
- D.Hourly CSV exports of the tables, queried from Cloud Storage
Show answer and explanation
Correct answer: A. An AlloyDB read pool instance, with reporting connections sent to its endpoint
Why: AlloyDB read pools provide one or more read-only nodes behind a single endpoint that share the cluster's storage, offloading reads from the primary with no replication to operate. Scaling the primary up raises cost and still mixes workloads. Hourly CSV exports and custom replication add staleness and maintenance.
More free Google Cloud Professional Cloud Architect questions
- Config Sync GitOps across a cluster fleet
- Chirp speech model for call transcription
- VM Manager OS patch management
- BigQuery long-term storage pricing
- Feature Store against training-serving skew
- Autoclass for unpredictable object access
- Workflows orchestrating serverless steps
- Managed Service for Apache Airflow for complex DAGs
- Cloud DNS failover routing policy
- Datastream change data capture into BigQuery
- Cloud Asset Inventory IAM policy analysis