QuestionQ261

Analyzing and optimizing technical and business processes

You use Cloud SQL as the database backend for a large CRM deployment. As usage grows, you need to scale while ensuring that storage does not run out, CPU utilization stays at 75%, and replication lag remains below 60 seconds. What steps should you take to meet these requirements?

  • A
    1. Enable automatic storage increase for the instance. 2. Create a Stackdriver alert when CPU usage exceeds 75%, and change the instance type to reduce CPU usage. 3. Create a Stackdriver alert for replication lag, and shard the database to reduce replication time.
  • B
    1. Enable automatic storage increase for the instance. 2. Change the instance type to a 32-core machine type to keep CPU usage below 75%. 3. Create a Stackdriver alert for replication lag, and deploy memcache to reduce load on the master.
  • C
    1. Create a Stackdriver alert when storage exceeds 75%, and increase the available storage on the instance to create more space. 2. Deploy memcached to reduce CPU load. 3. Change the instance type to a 32-core machine type to reduce replication lag.
  • D
    1. Create a Stackdriver alert when storage exceeds 75%, and increase the available storage on the instance to create more space. 2. Deploy memcached to reduce CPU load. 3. Create a Stackdriver alert for replication lag, and change the instance type to a 32-core machine type to reduce replication lag.
Explanation

Cloud SQL automatic storage increase adds capacity when available storage falls below its threshold, helping prevent an instance from running out of disk space. Increasing the machine type to 32 cores provides additional CPU capacity to keep utilization below the target. Monitoring replication lag with an alert and using a cache to reduce load on the primary database helps keep replicas from falling behind.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!