ExamGecko
Home Home / Google / Professional Cloud Database Engineer

Google Professional Cloud Database Engineer Practice Test - Questions Answers, Page 8

Question list
Search
Search

List of questions

Search

Related questions











Your team is running a Cloud SQL for MySQL instance with a 5 TB database that must be available 24/7. You need to save database backups on object storage with minimal operational overhead or risk to your production workloads. What should you do?

A.
Use Cloud SQL serverless exports.
A.
Use Cloud SQL serverless exports.
Answers
B.
Create a read replica, and then use the mysqldump utility to export each table.
B.
Create a read replica, and then use the mysqldump utility to export each table.
Answers
C.
Clone the Cloud SQL instance, and then use the mysqldump utlity to export the data.
C.
Clone the Cloud SQL instance, and then use the mysqldump utlity to export the data.
Answers
D.
Use the mysqldump utility on the primary database instance to export the backup.
D.
Use the mysqldump utility on the primary database instance to export the backup.
Answers
Suggested answer: A

Explanation:

https://cloud.google.com/blog/products/databases/introducing-cloud-sql-serverless-exports

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?

A.
For each application code, set up a common shared user account.
A.
For each application code, set up a common shared user account.
Answers
B.
For each application code, set up a dedicated user account.
B.
For each application code, set up a dedicated user account.
Answers
C.
For the application server, set up a service account.
C.
For the application server, set up a service account.
Answers
D.
For the application server, set up a common shared user account.
D.
For the application server, set up a common shared user account.
Answers
Suggested answer: 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?

A.
Migrate to Cloud SQL for SQL Server.
A.
Migrate to Cloud SQL for SQL Server.
Answers
B.
Migrate to Cloud SQL for PostgreSQL.
B.
Migrate to Cloud SQL for PostgreSQL.
Answers
C.
Migrate to Compute Engine.
C.
Migrate to Compute Engine.
Answers
D.
Migrate to Google Kubernetes Engine (GKE).
D.
Migrate to Google Kubernetes Engine (GKE).
Answers
Suggested answer: 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?

A.
roles/cloudsql.viewer and roles/spanner.databaseUser
A.
roles/cloudsql.viewer and roles/spanner.databaseUser
Answers
B.
roles/cloudsql.editor and roles/spanner.admin
B.
roles/cloudsql.editor and roles/spanner.admin
Answers
C.
roles/cloudsql.client and roles/spanner.databaseReader
C.
roles/cloudsql.client and roles/spanner.databaseReader
Answers
D.
roles/cloudsql.instanceUser and roles/spanner.databaseUser
D.
roles/cloudsql.instanceUser and roles/spanner.databaseUser
Answers
Suggested answer: 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?

A.
Use Cloud SQL for PostgreSQL with both cross-region read replicas.
A.
Use Cloud SQL for PostgreSQL with both cross-region read replicas.
Answers
B.
Use Cloud Spanner in a multi-region configuration.
B.
Use Cloud Spanner in a multi-region configuration.
Answers
C.
Use Firestore in Datastore mode.
C.
Use Firestore in Datastore mode.
Answers
D.
Use a Bigtable instance with clusters in multiple regions.
D.
Use a Bigtable instance with clusters in multiple regions.
Answers
Suggested answer: 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?

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.
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.
Answers
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.
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.
Answers
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.
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.
Answers
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.
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.
Answers
Suggested answer: 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?

A.
Check the app.yaml value cloud_sql_instances for a misspelled or incorrect instance connection name.
A.
Check the app.yaml value cloud_sql_instances for a misspelled or incorrect instance connection name.
Answers
B.
Check whether your service account has cloudsql.instances.connect permission.
B.
Check whether your service account has cloudsql.instances.connect permission.
Answers
C.
Enable the Cloud SQL Admin API.
C.
Enable the Cloud SQL Admin API.
Answers
D.
Ensure that you are using an external (public) IP address interface.
D.
Ensure that you are using an external (public) IP address interface.
Answers
Suggested answer: 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

You are working on a new centralized inventory management system to track items available in 200 stores, which each have 500 GB of dat

a. You are planning a gradual rollout of the system to a few stores each week. You need to design an SQL database architecture that minimizes costs and user disruption during each regional rollout and can scale up or down on nights and holidays. What should you do?

A.
Use Oracle Real Application Cluster (RAC) databases on Bare Metal Solution for Oracle.
A.
Use Oracle Real Application Cluster (RAC) databases on Bare Metal Solution for Oracle.
Answers
B.
Use sharded Cloud SQL instances with one or more stores per database instance.
B.
Use sharded Cloud SQL instances with one or more stores per database instance.
Answers
C.
Use a Biglable cluster with autoscaling.
C.
Use a Biglable cluster with autoscaling.
Answers
D.
Use Cloud Spanner with a custom autoscaling solution.
D.
Use Cloud Spanner with a custom autoscaling solution.
Answers
Suggested answer: D

Explanation:

https://cloud.google.com/spanner/docs/autoscaling-overview

1. CloudSQL max out at 64TB, so unable to told 100TB of data. https://cloud.google.com/sql/docs/quotas#metrics_collection_limit 2. Scale is done manually on SQL Cloud

Your organization has strict policies on tracking rollouts to production and periodically shares this information with external auditors to meet compliance requirements. You need to enable auditing on several Cloud Spanner databases. What should you do?

A.
Use replication to roll out changes to higher environments.
A.
Use replication to roll out changes to higher environments.
Answers
B.
Use backup and restore to roll out changes to higher environments.
B.
Use backup and restore to roll out changes to higher environments.
Answers
C.
Use Liquibase to roll out changes to higher environments.
C.
Use Liquibase to roll out changes to higher environments.
Answers
D.
Manually capture detailed DBA audit logs when changes are rolled out to higher environments.
D.
Manually capture detailed DBA audit logs when changes are rolled out to higher environments.
Answers
Suggested answer: C

Explanation:

To satisfy audit reporting you would need a way to record what was changed and when. The best answer is one which uses some kind of source code control system (SCCS). That rules out A and B. Any mention of anything manual in a cloud environment should look suspicious, which leave option C. As it happens, Liquibase is an SCCS and can be integrated with Spanner. https://cloud.google.com/spanner/docs/use-liquibase

Your organization has a production Cloud SQL for MySQL instance. Your instance is configured with 16 vCPUs and 104 GB of RAM that is running between 90% and 100% CPU utilization for most of the day. You need to scale up the database and add vCPUs with minimal interruption and effort. What should you do?

A.
Issue a gcloud sql instances patch command to increase the number of vCPUs.
A.
Issue a gcloud sql instances patch command to increase the number of vCPUs.
Answers
B.
Update a MySQL database flag to increase the number of vCPUs.
B.
Update a MySQL database flag to increase the number of vCPUs.
Answers
C.
Issue a gcloud compute instances update command to increase the number of vCPUs.
C.
Issue a gcloud compute instances update command to increase the number of vCPUs.
Answers
D.
Back up the database, create an instance with additional vCPUs, and restore the database.
D.
Back up the database, create an instance with additional vCPUs, and restore the database.
Answers
Suggested answer: A

Explanation:

https://cloud.google.com/sdk/gcloud/reference/sql/instances/patch

Total 132 questions
Go to page: of 14