Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Cloud Architect Topic 11 Question 84 Discussion

Actual exam question for Google's Professional Cloud Architect exam
Question #: 84
Topic #: 11
[All Professional Cloud Architect Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: A

The Data Transfer appliance is a Google-provided hardware device that can be used to transfer large amounts of data from on-premises environments to Cloud Storage. It is suitable for scenarios where the bandwidth between the on-premises environment and Google Cloud is low or insufficient, and the data size is large. The Data Transfer appliance can minimize the time it takes to complete the migration, the overall cost and database load, by avoiding network bottlenecks and reducing bandwidth consumption. The Data Transfer appliance also encrypts the data at rest and in transit, ensuring data security and privacy. The other options are not optimal for this scenario, because they either require a high-bandwidth network connection (B, C, D), or incur additional costs and complexity (B, C). Reference:

https://cloud.google.com/data-transfer-appliance/docs/overview

https://cloud.google.com/blog/products/storage-data-transfer/introducing-storage-transfer-service-for-on-premises-data


Contribute your Thoughts:

Lorrine
3 days ago
I'm a bit skeptical of Option C - deploying memcached might not be the best solution for reducing CPU load on a database. And changing the instance type to reduce replication lag seems like an odd approach.
upvoted 0 times
...
Shanda
6 days ago
I like the simplicity of Option B. Increasing the instance type to a 32-core machine should handle the CPU and replication lag requirements. No need to overcomplicate things.
upvoted 0 times
...
Devorah
9 days ago
Option A seems to cover all the bases - automatic storage increase, CPU usage monitoring, and replication lag monitoring. Sharding the database is a nice touch to reduce replication time.
upvoted 0 times
...
Alberto
18 days ago
I'm not sure, I think option C could also work. It addresses storage and CPU load.
upvoted 0 times
...
Kara
21 days ago
I agree with Cristen. Option D seems to cover all the requirements.
upvoted 0 times
...
Cristen
22 days ago
I think the correct steps are in option D.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77