You need to issue a new server certificate because your old one is expiring. You need to avoid a restart of your Cloud SQL for MySQL instance. What should you do in your Cloud SQL instance?
You are managing a Cloud SQL for PostgreSQL instance in Google Cloud. You have a primary instance in region 1 and a read replica in region 2. After a failure of region 1, you need to make the Cloud SQL instance available again. You want to minimize data loss and follow Google-recommended practices. What should you do?
You want to migrate an on-premises mission-critical PostgreSQL database to Cloud SQL. The database must be able to withstand a zonal failure with less than five minutes of downtime and still not lose any transactions. You want to follow Google-recommended practices for the migration. What should you do?
You are managing a Cloud SQL for PostgreSQL instance in Google Cloud. You have a primary instance in region 1 and a read replica in region 2. After a failure of region 1, you need to make the Cloud SQL instance available again. You want to minimize data loss and follow Google-recommended practices. What should you do?
You are designing for a write-heavy application. During testing, you discover that the write workloads are performant in a regional Cloud Spanner instance but slow down by an order of magnitude in a multi-regional instance. You want to make the write workloads faster in a multi-regional instance. What should you do?
https://cloud.google.com/spanner/docs/instance-configurations#multi-region-best-practices Best practices For optimal performance, follow these best practices: Design a schema that prevents hotspots and other performance issues. For optimal write latency, place compute resources for write-heavy workloads within or close to the default leader region. For optimal read performance outside of the default leader region, use staleness of at least 15 seconds. To avoid single-region dependency for your workloads, place critical compute resources in at least two regions. A good option is to place them next to the two different read-write regions so that any single region outage will not impact all of your application. Provision enough compute capacity to keep high priority total CPU utilization under 45% in each region.
Alaine
5 days agoDottie
11 days agoJame
19 days agoRebecka
23 days agoKeena
1 months agoRhea
1 months agoLinsey
2 months agoAlex
2 months agoJame
2 months agoGracie
2 months agoFelicitas
2 months agoDana
3 months agoTiara
3 months agoGerman
3 months agoBerry
3 months agoMaybelle
3 months agoLinn
4 months agoShayne
4 months agoDenise
4 months agoAntione
4 months agoJulie
4 months agoNathan
5 months agoKati
5 months agoLynelle
5 months agoStephen
5 months agoMelina
5 months agoPete
6 months agoSabine
7 months agoJamal
7 months agoLai
8 months agoAlpha
8 months agoDesiree
8 months agoReyes
8 months agoHelga
8 months agoAnnmarie
8 months ago