Discuss Google Professional Cloud Architect (PR000213) Exam Topic 11 Question 84

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?

A1) 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.

B1) 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.

C1) 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.

D1) 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.

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

Get Premium Professional Cloud Architect (PR000213) Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

34 comments · newest first

Paz 11 months ago

I disagree, memcached isn't always the answer for CPU load.

Tess 11 months ago

Wait, why would you change to a 32-core machine?

Shawnee 11 months ago

Sharding the database? Sounds complicated!

Bernardine 11 months ago

I think option B is the best choice here.

Sharee 12 months ago

Automatic storage increase is a must!

Kati 12 months ago

I feel like deploying memcached could help with CPU load, but I’m not confident about the specifics of instance types and their impact on replication.

Margarett 1 year ago

Sharding the database seems familiar, but I’m uncertain if it directly affects replication lag like the question suggests.

Anastacia 1 year ago

I think we had a practice question about setting alerts for CPU usage, but I can't recall if changing the instance type was the right approach.

Rozella 1 year ago

I remember we talked about enabling automatic storage increase, but I'm not sure if that's enough for CPU management.

Art 1 year ago

The key is to focus on the specific requirements stated in the question. Option B seems to directly address the CPU and replication lag, so that might be the best approach.

Zoila 1 year ago

I'm a bit unsure about the memcached part in options C and D. Does that really help with the CPU usage and replication lag?

Rikki 1 year ago

I'm confident I can handle this. The steps in option A look like the right approach to meet all the requirements.

Wenona 1 year ago

Okay, let me think this through step-by-step. Enabling automatic storage increase, monitoring CPU usage, and monitoring replication lag seem like the key things to address.

Salena 1 year ago

This question seems straightforward, but I want to make sure I understand the requirements correctly before answering.

Catarina 1 year ago

I've got a good strategy for this. I'll focus on understanding the key terms like "DBA" and "GPON network", then try to match the bandwidth types listed in the answers.

Sherell 1 year ago

Okay, let me think this through. The question is asking about changing the fill pattern for walls in plan view, so it's probably related to the cut pattern or projection/surface pattern settings. I'll go with B to be safe.

Elbert 1 year ago

Okay, I've got this. The key is that the question is asking about valid reasons for aggregating the performance test results. So the answer has to be something about how aggregated data is useful for stakeholders, either business or technical. I'll go with C.

Louis 1 year 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!

Vesta 1 year 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.

Joanne 1 year ago

↳ replying to Vesta

That's a good point. Maybe just increasing storage and deploying memcached would be enough to handle the load.

Aliza 1 year ago

↳ replying to Vesta

True, but maybe changing the instance type for replication lag is a bit redundant if we're already monitoring it.

Kimberely 1 year ago

↳ replying to Vesta

I think option D covers all the bases for scaling and maintaining performance.

Lorrine 2 years 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.

Whitley 1 year ago

↳ replying to Lorrine

Yeah, changing the instance type to reduce replication lag in Option C does seem like an unusual approach. Option A seems more straightforward.

Leah 1 year ago

↳ replying to Lorrine

I'm not so sure about Option C either. Deploying memcached for reducing CPU load on a database does seem a bit unconventional.

Kenda 1 year ago

↳ replying to Lorrine

I agree, Option A seems like the most practical solution to meet the requirements for scaling and maintaining performance.

Georgiann 1 year ago

↳ replying to Lorrine

I think Option A is the best choice. Enabling automatic storage increase and setting up alerts for CPU and replication lag makes sense.

Shanda 2 years 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.

Devorah 2 years 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.

Ettie 1 year ago

↳ replying to Devorah

User 2

Blair 1 year ago

↳ replying to Devorah

User 1

Alberto 2 years ago

I'm not sure, I think option C could also work. It addresses storage and CPU load.

Kara 2 years ago

I agree with Cristen. Option D seems to cover all the requirements.

Cristen 2 years ago

I think the correct steps are in option D.

Google Professional Cloud Architect (PR000213) Exam - Topic 11 Question 84 Discussion