Scale Your Cloud SQL Deployment for Optimal Performance and Storage Efficiency | PCA Exam Preparation

Steps to Meet Your Cloud SQL Scaling Requirements for CRM Deployment

Question

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?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

A.

The correct answer is D.

Explanation:

Cloud SQL is a fully-managed relational database service that provides scalability, availability, and durability without the need for infrastructure provisioning, setup, or maintenance. It is an excellent choice for large CRM deployments, and it provides automatic backups, automatic failover, and point-in-time recovery.

To meet the requirements, the following steps should be taken:

  1. Create a Stackdriver alert when storage exceeds 75%, and increase the available storage on the instance to create more space.

This step ensures that the database has enough storage to handle the increasing usage. When the storage usage reaches 75%, a Stackdriver alert is triggered, and the available storage on the instance should be increased to create more space.

  1. Deploy memcached to reduce CPU load.

Memcached is a distributed memory caching system that can be used to reduce the load on the database. It stores data in memory, which makes it faster to access than retrieving data from the database. This step reduces the CPU load on the database, ensuring that the CPU usage is maintained below 75%.

  1. Create a Stackdriver alert for replication lag, and change the instance type to a 32-core machine type to reduce replication lag.

Replication lag is the time it takes for changes to be replicated to all the replicas in the database. This step ensures that the replication lag is kept below 60 seconds. When the replication lag exceeds 60 seconds, a Stackdriver alert is triggered, and the instance type should be changed to a 32-core machine type to reduce the replication lag.

Therefore, option D is the correct answer. Options A, B, and C have incorrect or insufficient steps to meet the requirements.