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.
You are building a data warehouse on BigQuery. Sources of data include several MySQL databases located on-premises.
You need to transfer data from these databases into BigQuery for analytics. You want to use a managed solution that has low latency and is easy to set up. What should you do?
A. Create extracts from your on-premises databases periodically, and push these extracts to Cloud Storage. Upload the changes into BigQuery, and merge them with existing tables.
Rebecka
3 days agoKeena
14 days agoRhea
19 days agoLinsey
28 days agoAlex
29 days agoJame
1 months agoGracie
1 months agoFelicitas
2 months agoDana
2 months agoTiara
2 months agoGerman
2 months agoBerry
2 months agoMaybelle
3 months agoLinn
3 months agoShayne
3 months agoDenise
3 months agoAntione
3 months agoJulie
4 months agoNathan
4 months agoKati
4 months agoLynelle
4 months agoStephen
4 months agoMelina
5 months agoPete
5 months agoSabine
6 months agoJamal
6 months agoLai
7 months agoAlpha
7 months agoDesiree
7 months agoReyes
7 months agoHelga
7 months agoAnnmarie
8 months ago