Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - 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:

Louis
1 months ago
Option E: Throw the whole thing in the cloud and let the cloud gods handle it. No need to worry about scaling or monitoring when you have a strong faith in the cloud!
upvoted 0 times
...
Vesta
1 months ago
Option D looks good, but I'm not sure why you'd need to change the instance type to reduce replication lag if you're already monitoring it and can take action accordingly.
upvoted 0 times
Joanne
4 days ago
That's a good point. Maybe just increasing storage and deploying memcached would be enough to handle the load.
upvoted 0 times
...
Aliza
11 days ago
True, but maybe changing the instance type for replication lag is a bit redundant if we're already monitoring it.
upvoted 0 times
...
Kimberely
19 days ago
I think option D covers all the bases for scaling and maintaining performance.
upvoted 0 times
...
...
Lorrine
2 months 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
Whitley
11 days ago
Yeah, changing the instance type to reduce replication lag in Option C does seem like an unusual approach. Option A seems more straightforward.
upvoted 0 times
...
Leah
16 days ago
I'm not so sure about Option C either. Deploying memcached for reducing CPU load on a database does seem a bit unconventional.
upvoted 0 times
...
Kenda
20 days ago
I agree, Option A seems like the most practical solution to meet the requirements for scaling and maintaining performance.
upvoted 0 times
...
Georgiann
26 days ago
I think Option A is the best choice. Enabling automatic storage increase and setting up alerts for CPU and replication lag makes sense.
upvoted 0 times
...
...
Shanda
2 months 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
2 months 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
Ettie
26 days ago
User 2
upvoted 0 times
...
Blair
29 days ago
User 1
upvoted 0 times
...
...
Alberto
2 months ago
I'm not sure, I think option C could also work. It addresses storage and CPU load.
upvoted 0 times
...
Kara
3 months ago
I agree with Cristen. Option D seems to cover all the requirements.
upvoted 0 times
...
Cristen
3 months 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