What are the correct steps to meet your requirements?

You are using Cloud SQL as the database backend for a large CRM deployment. You want to scale as usage increases and ensure that you don’t run out of storage, maintain 75% CPU usage cores, and keep replication lag below 60 seconds. What are the correct steps to meet your 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 shard the database to reduce replication time.
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.

Download Printable PDF. VALID exam to help you PASS.

5 thoughts on “What are the correct steps to meet your requirements?

  1. Correct Answer A
    Cloud SQL instances support MySQL 8.0, 5.7 (default), and 5.6, and provide up to 416 GB of RAM and 30 TB of data storage, with the option to automatically increase the storage size, as needed.
    Between A & B : A seems better choice as we don’t know the CPU utilization.

  2. Change the instance type to a 32-core machine type –> this doesn’t guarantee to fix the cpu usage issue so this can’t be the ans

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.