Question 750
The original database complaint was: An application launches an AlloyDB read pool but leaves every reporting connection pointed at the primary endpoint. Which observed result best verifies the repair?
Explanation
Correct Answer
Read traffic visibly shifts from the primary while writes remain correctly directed. This is the intended effect of: Configure and verify read-eligible client connections to the appropriate read pool endpoint. The original defect was read scaling infrastructure exists but application routing still targets the writer.
Incorrect Answers
Even if this observation were recorded, it would support a case where a new AlloyDB deployment reports healthy virtual resources while its application user cannot commit a simple transaction. It would not verify that read traffic visibly shifts from the primary while writes remain correctly directed.
Even if this observation were recorded, it would support a case where a new database instance goes live before an accountable team is assigned its alerts, backups and upgrade decisions. It would not verify that read traffic visibly shifts from the primary while writes remain correctly directed.
Even if this observation were recorded, it would support a case where Cloud SQL for MySQL is configured with public addressing while the application design specifies database access only through a private VPC. It would not verify that read traffic visibly shifts from the primary while writes remain correctly directed.