Free PROFESSIONAL CLOUD DATABASE ENGINEER Exam Braindumps
Professional Cloud Database Engineer Questions 51–55 (page: 12)

Updated On: 10-Feb-2026

You are deploying a new Cloud SQL instance on Google Cloud using the Cloud SQL Auth proxy. You have identified snippets of application code that need to access the new Cloud SQL instance. The snippets reside and execute on an application server running on a Compute Engine machine. You want to follow Google-recommended practices to set up Identity and Access Management (IAM) as quickly and securely as possible.
What should you do?

  1. For each application code, set up a common shared user account.
  2. For each application code, set up a dedicated user account.
  3. For the application server, set up a service account.
  4. For the application server, set up a common shared user account.

Answer(s): C

Explanation:

https://cloud.google.com/sql/docs/mysql/sql-proxy#using-a-service-account



Your organization is running a low-latency reporting application on Microsoft SQL Server. In addition to the database engine, you are using SQL Server Analysis Services (SSAS), SQL Server Reporting Services (SSRS), and SQL Server Integration Services (SSIS) in your on-premises environment. You want to migrate your Microsoft SQL Server database instances to Google Cloud. You need to ensure minimal disruption to the existing architecture during migration.
What should you do?

  1. Migrate to Cloud SQL for SQL Server.
  2. Migrate to Cloud SQL for PostgreSQL.
  3. Migrate to Compute Engine.
  4. Migrate to Google Kubernetes Engine (GKE).

Answer(s): C

Explanation:

https://cloud.google.com/sql/docs/sqlserver/features



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. roles/cloudsql.viewer and roles/spanner.databaseUser
  2. roles/cloudsql.editor and roles/spanner.admin
  3. roles/cloudsql.client and roles/spanner.databaseReader
  4. roles/cloudsql.instanceUser and roles/spanner.databaseUser

Answer(s): A

Explanation:

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 responsible for designing a new database for an airline ticketing application in Google Cloud.
This application must be able to:
Work with transactions and offer strong consistency.
Work with structured and semi-structured (JSON) data. Scale transparently to multiple regions globally as the operation grows. You need a Google Cloud database that meets all the requirements of the application.
What should you do?

  1. Use Cloud SQL for PostgreSQL with both cross-region read replicas.
  2. Use Cloud Spanner in a multi-region configuration.
  3. Use Firestore in Datastore mode.
  4. Use a Bigtable instance with clusters in multiple regions.

Answer(s): B

Explanation:

https://cloud.google.com/blog/products/databases/manage-semi-structured-data-in-cloud-spanner- with-json



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

Answer(s): D

Explanation:

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



Viewing page 12 of 28
Viewing questions 56 - 60 out of 197 questions


Post your Comments and Discuss Google PROFESSIONAL CLOUD DATABASE ENGINEER exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!