You need to migrate existing databases from Microsoft SQL Server 2016 Standard Edition on a single Windows Server 2019 Datacenter Edition to a single Cloud SQL for SQL Server instance. During the discovery phase of your project, you notice that your on-premises server peaks at around 25,000 read IOPS. You need to ensure that your Cloud SQL instance is sized appropriately to maximize read performance. What should you do?

1. A. Create a SQL Server 2019 Standard on Standard machine type with 4 vCPUs, 15 GB of RAM, and 800 GB of solid-state drive (SSD).
2. B. Create a SQL Server 2019 Standard on High Memory machine type with at least 16 vCPUs, 104 GB of RAM, and 200 GB of SSD.
3. C. Create a SQL Server 2019 Standard on High Memory machine type with 16 vCPUs, 104 GB of RAM, and 4 TB of SSD.
4. D. Create a SQL Server 2019 Enterprise on High Memory machine type with 16 vCPUs, 104 GB of RAM, and 500 GB of SSD.

Correct Answer: C
Given that Google SSD performance is related to the size of the disk in an order of 30 IOPS for each GB, ti would require at least 833 GB to handle 25000 IOPS, the only answer that exceeds this value is C. https://cloud.google.com/compute/docs/disks/performance

You are a DBA of Cloud SQL for PostgreSQL. You want the applications to have password-less authentication for read and write access to the database. Which authentication mechanism should you use?

1. A. Use Identity and Access Management (IAM) authentication.
2. B. Use Managed Active Directory authentication.
3. C. Use Cloud SQL federated queries.
4. D. Use PostgreSQL database's built-in authentication.

Correct Answer: A
https://cloud.google.com/sql/docs/postgres/authentication

An analytics team needs to read data out of Cloud SQL for SQL Server and update a table in Cloud Spanner. You need to create a service account and grant least privilege access using predefined roles. What roles should you assign to the service account?

1. A. roles/cloudsql.viewer and roles/spanner.databaseUser
2. B. roles/cloudsql.editor and roles/spanner.admin
3. C. roles/cloudsql.client and roles/spanner.databaseReader
4. D. roles/cloudsql.instanceUser and roles/spanner.databaseUser

Correct Answer: A
To read data out of Cloud SQL for SQL Server, you need to use a service account with the roles/cloudsql.viewer role on the Cloud SQL instance. This role grants the service account permission to read data from the instance. Whereas roles/cloudsql.instanceUser will only allow to login to cloud SQL instance. No resource will be allowed to view.

You are writing an application that will run on Cloud Run and require a database running in the Cloud SQL managed service. You want to secure this instance so that it only receives connections from applications running in your VPC environment in Google Cloud. What should you do?

1. A. * 1. Create your instance with a specified external (public) IP address.* 2. Choose the VPC and create firewall rules to allow only connections from Cloud Run into your instance.* 3. Use Cloud SQL Auth proxy to connect to the instance.
2. B. * 1. Create your instance with a specified external (public) IP address.* 2. Choose the VPC and create firewall rules to allow only connections from Cloud Run into your instance.* 3. Connect to the instance using a connection pool to best manage connections to the instance.
3. C. * 1. Create your instance with a specified internal (private) IP address.* 2. Choose the VPC with private service connection configured.* 3. Configure the Serverless VPC Access connector in the same VPC network as your Cloud SQL instance.* 4. Use Cloud SQL Auth proxy to connect to the instance.
4. D. * 1. Create your instance with a specified internal (private) IP address.* 2. Choose the VPC with private service connection configured.* 3. Configure the Serverless VPC Access connector in the same VPC network as your Cloud SQL instance.* 4. Connect to the instance using a connection pool to best manage connections to the instance.

Correct Answer: D
https://cloud.google.com/sql/docs/mysql/connect-run#configure https://cloud.google.com/sql/docs/mysql/connect-run#connection-pools

You support a consumer inventory application that runs on a multi-region instance of Cloud Spanner. A customer opened a support ticket to complain about slow response times. You
notice a Cloud Monitoring alert about high CPU utilization. You want to follow Google- recommended practices to address the CPU performance issue. What should you do first?

1. A. Increase the number of processing units.
2. B. Modify the database schema, and add additional indexes.
3. C. Shard data required by the application into multiple instances.
4. D. Decrease the number of processing units.

Correct Answer: A
In case of high CPU utilization like, mentioned in question, refer: https://cloud.google.com/spanner/docs/identify-latency-point#:~:text=Check%20the%20CPU%20utilization%20of%20the%20instance.%20If%20the%20CPU%20utilization%20of%20the%20instance%20is%20above%20the%20recommended%20level%2C%20you%20should%20manually%20add%20more%20nodes%2C%20or%20set%20up%20auto%20scaling. "Check the CPU utilization of the instance. If the CPU utilization of the instance is above the recommended level, you should manually add more nodes, or set up auto scaling." Indexes and schema are reviewed post identifying query with slow performance. Refer : https://cloud.google.com/spanner/docs/troubleshooting- performance-regressions#review-schema