Free PROFESSIONAL-CLOUD-DATABASE-ENGINEER Exam Braindumps (page: 14)

Page 14 of 34

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



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?

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

Answer(s): C

Explanation:

https://cloud.google.com/sql/docs/mysql/connect-auth-proxy#troubleshooting C because in docs it says "Make sure to enable the Cloud SQL Admin API. If it is not, you see output like Error 403: Access Not Configured in your Cloud SQL



Page 14 of 34



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

muksgreen commented on March 01, 2024
brainstorming excellent
JAPAN
upvote