Your application uses Cloud SQL for MySQL. Your users run reports on data that relies on near-real time; however, the additional analytics caused excessive load on the primary database. You created a read replica for the analytics workloads, but now your users are complaining about the lag in data changes and that their reports are still slow. You need to improve the report performance and shorten the lag in data replication without making changes to the current reports. Which two approaches should you implement? (Choose two.)

• A.Disable replication on the primary instance, and set the flag for parallel replication on the primary instance. Re-enable replication and optimize performance by setting flags on the read replica.
• B.Move your analytics workloads to BigQuery, and set up a streaming pipeline to move data and update BigQuery.
• C.Create additional read replicas, and partition your analytics users to use different read replicas.
• D.Disable replication on the read replica, and set the flag for parallel replication on the read replica. Re-enable replication and optimize performance by setting flags on the primary instance.
• E.Create secondary indexes on the replica.

Comment: *

Name: *

Email: *

Verification: *

You are running a large, highly transactional application on Oracle Real Application Cluster (RAC) that is multi-tenant and uses shared storage. You need a solution that ensures high-performance throughput and a low-latency connection between applications and databases. The solution must also support existing Oracle features and provide ease of migration to Google Cloud. What should you do?

• A.Migrate to Compute Engine.
• B.Migrate to Google Kubernetes Engine (GKE)
• C.Migrate to Bare Metal Solution for Oracle.
• D.Migrate to Google Cloud VMware Engine

Comment: *

Name: *

Email: *

Verification: *

You are troubleshooting a connection issue with a newly deployed Cloud SQL instance on Google Cloud. While investigating the Cloud SQL Proxy logs, you see the message Error 403: Access Not Configured. What should you do?

• A.Ensure that you are using an external (public) IP address interface.
• B.Check the app.yaml value cloud_sql_instances for a misspelled or incorrect instance connection name.
• C.Check whether your service account has cloudsql.instances.connect permission.
• D.Enable the Cloud SQL Admin API.

Comment: *

Name: *

Email: *

Verification: *

You are evaluating Cloud SQL for PostgreSQL as a possible destination for your on-premises PostgreSQL instances. Geography is becoming increasingly relevant to customer privacy worldwide. Your solution must support data residency requirements and include a strategy to:
configure where data is stored
control where the encryption keys are stored
govern the access to data
What should you do?

• A.Use features like customer-managed encryption keys (CMEK), VPC Service Controls, and Identity and Access Management (IAM) policies.
• B.Allow application access to data only if the users are in the same region as the Google Cloud region for the Cloud SQL for PostgreSQL database.
• C.Create a Cloud SQL for PostgreSQL instance on Google Cloud for the data that does not need to adhere to data residency requirements. Keep the data that must adhere to data residency requirements on-premises. Make application changes to support both databases.
• D.Replicate Cloud SQL databases across different zones.

Comment: *

Name: *

Email: *

Verification: *

Your company is developing a global ecommerce website on Google Cloud. Your development team is working on a shopping cart service that is durable and elastically scalable with live traffic. Business disruptions from unplanned downtime are expected to be less than 5 minutes per month. In addition, the application needs to have very low latency writes. You need a data storage solution that has high write throughput and provides 99.99% uptime. What should you do?

• A.Use Cloud Spanner for data storage.
• B.Use Cloud SQL for data storage.
• C.Use Memorystore for data storage.
• D.Use Bigtable for data storage.

Comment: *

Name: *

Email: *

Verification: *