Question 1
An engineer investigates this database issue: A ticketing service running on Cloud SQL for PostgreSQL rejects new sessions during a marketing event while CPU remains moderate. Which remediation addresses the underlying problem?
Explanation
Correct Answer
Introduce bounded application connection pooling and right-size connection capacity against measured concurrency. The root issue is: The application creates a separate database connection per request and exhausts the instance connection limit. A successful change should produce this result: Peak requests complete without connection exhaustion while active session counts remain within tested limits.
Incorrect Answers
This would reschedule or isolate heavy batch work and size compute for the remaining peak concurrency. It applies when a Cloud SQL order database runs out of CPU each afternoon while overnight processing is nearly idle. Here, the issue arises because the application creates a separate database connection per request and exhausts the instance connection limit.
It would measure index-build and temporary-space requirements and provide safe storage headroom before retrying; that targets the issue where a Cloud SQL database runs out of free storage during a large index build even though the indexed table itself fits. The key issue here is that the application creates a separate database connection per request and exhausts the instance connection limit.
It would measure replica lag and define a recovery decision based on observed data freshness; that targets the issue where a Bigtable team claims replication ensures data protection but never measures how late changes reach the alternate cluster. The key issue here is that the application creates a separate database connection per request and exhausts the instance connection limit.