Your team uses thousands of connected IoT devices to collect device maintenance data for your oil and gas customers in real time. You want to design inspection routines, device repair, and replacement schedules based on insights gathered from the data produced by these devices. You need a managed solution that is highly scalable, supports a multi-cloud strategy, and offers low latency for these IoT devices. What should you do?

Use Cloud Spanner with Data Studio.

Your application follows a microservices architecture and uses a single large Cloud SQL instance, which is starting to have performance issues as your application grows. in the Cloud Monitoring dashboard, the CPU utilization looks normal You want to follow Google-recommended practices to resolve and prevent these performance issues while avoiding any major refactoring. What should you do?

Use many smaller Cloud SQL instances.

Use Cloud Spanner instead of Cloud SQL.

Increase the number of CPUs for your instance.

Increase the storage size for the instance.

Use many smaller Cloud SQL instances.

You need to perform a one-time migration of data from a running Cloud SQL for MySQL instance in the us-central1 region to a new Cloud SQL for MySQL instance in the us-east1 region. You want to follow Google-recommended practices to minimize performance impact on the currently running instance. What should you do?

Create a SQL dump file in Cloud Storage using a temporary instance, and then use that file to import into a new instance.

Create and run a Dataflow job that uses JdbcIO to copy data from one Cloud SQL instance to another.

Create two Datastream connection profiles, and use them to create a stream from one Cloud SQL instance to another.

Create a SQL dump file in Cloud Storage using a temporary instance, and then use that file to import into a new instance.

Create a CSV file by running the SQL statement SELECT...INTO OUTFILE, copy the file to a Cloud Storage bucket, and import it into a new instance.

You are running a mission-critical application on a Cloud SQL for PostgreSQL database with a multi-zonal setup. The primary and read replica instances are in the same region but in different zones. You need to ensure that you split the application load between both instances. What should you do?

Use PgBouncer to set up database connection pooling between the Cloud SQL primary and read replica instances.

Use Cloud Load Balancing for load balancing between the Cloud SQL primary and read replica instances.

Use PgBouncer to set up database connection pooling between the Cloud SQL primary and read replica instances.

Use HTTP(S) Load Balancing for database connection pooling between the Cloud SQL primary and read replica instances.

Use the Cloud SQL Auth proxy for database connection pooling between the Cloud SQL primary and read replica instances.

Your organization deployed a new version of a critical application that uses Cloud SQL for MySQL with high availability (HA) and binary logging enabled to store transactional information. The latest release of the application had an error that caused massive data corruption in your Cloud SQL for MySQL database. You need to minimize data loss. What should you do?

Perform a point-in-time recovery of your Cloud SQL for MySQL database, selecting a date and time before the data was corrupted.

Open the Google Cloud Console, navigate to SQL > Backups, and select the last version of the automated backup before the corruption.

Reload the Cloud SQL for MySQL database using the LOAD DATA command to load data from CSV files that were used to initialize the instance.

Perform a point-in-time recovery of your Cloud SQL for MySQL database, selecting a date and time before the data was corrupted.

Fail over to the Cloud SQL for MySQL HA instance. Use that instance to recover the transactions that occurred before the corruption.

You plan to use Database Migration Service to migrate data from a PostgreSQL on-premises instance to Cloud SQL. You need to identify the prerequisites for creating and automating the task. What should you do? (Choose two.)

Ensure that all PostgreSQL tables have a primary key.

Ensure that pglogical is installed on the source PostgreSQL database.

Drop or disable all users except database administration users.

Disable all foreign key constraints on the source PostgreSQL database.

Ensure that all PostgreSQL tables have a primary key.

Shut down the database before the Data Migration Service task is started.

Ensure that pglogical is installed on the source PostgreSQL database.

You are using Compute Engine on Google Cloud and your data center to manage a set of MySQL databases in a hybrid configuration. You need to create replicas to scale reads and to offload part of the management operation. What should you do?

Use Cloud SQL for MySQL external replica.

Use external server replication.

Use Cloud SQL for MySQL external replica.

Use the mysqldump utility and binary logs.

Your company is shutting down their data center and migrating several MySQL and PostgreSQL databases to Google Cloud. Your database operations team is severely constrained by ongoing production releases and the lack of capacity for additional on-premises backups. You want to ensure that the scheduled migrations happen with minimal downtime and that the Google Cloud databases stay in sync with the on-premises data changes until the applications can cut over.What should you do? (Choose two.)

Use Database Migration Service to migrate the databases to Cloud SQL.

Use replication from an external server to migrate the databases to Cloud SQL.

Use an external read replica to migrate the databases to Cloud SQL.

Use a read replica to migrate the databases to Cloud SQL.

Use Database Migration Service to migrate the databases to Cloud SQL.

Use a cross-region read replica to migrate the databases to Cloud SQL.

Use replication from an external server to migrate the databases to Cloud SQL.

Your company is migrating the existing infrastructure for a highly transactional application to Google Cloud. You have several databases in a MySQL database instance and need to decide how to transfer the data to Cloud SQL. You need to minimize the downtime for the migration of your 500 GB instance. What should you do?

Create migration job using Database Migration Service. Set the migration job type to Continuous, and allow the databases to complete the full dump phase and start sending data in change data capture (CDC) mode. Wait for the replication delay to minimize, initiate a promotion of the new Cloud SQL instance, and wait for the migration job to complete. Update your application connections to the new instance.

Create a Cloud SQL for MySQL instance for your databases, and configure Datastream to stream your database changes to Cloud SQL. Select the Backfill historical data check box on your stream configuration to initiate Datastream to backfill any data that is out of sync between the source and destination. Delete your stream when all changes are moved to Cloud SQL for MySQL, and update your application to use the new instance.

Create migration job using Database Migration Service. Set the migration job type to Continuous, and allow the databases to complete the full dump phase and start sending data in change data capture (CDC) mode. Wait for the replication delay to minimize, initiate a promotion of the new Cloud SQL instance, and wait for the migration job to complete. Update your application connections to the new instance.

Create migration job using Database Migration Service. Set the migration job type to One-time, and perform this migration during a maintenance window. Stop all write workloads to the source database and initiate the dump. Wait for the dump to be loaded into the Cloud SQL destination database and the destination database to be promoted to the primary database. Update your application connections to the new instance.

Use the mysqldump utility to manually initiate a backup of MySQL during the application maintenance window. Move the files to Cloud Storage, and import each database into your Cloud SQL instance. Continue to dump each database until all the databases are migrated. Update your application connections to the new instance.

Your company uses the Cloud SQL out-of-disk recommender to analyze the storage utilization trends of production databases over the last 30 days. Your database operations team uses these recommendations to proactively monitor storage utilization and implement corrective actions. You receive a recommendation that the instance is likely to run out of disk space. What should you do to address this storage alert?

Manually or automatically increase the storage capacity.

Normalize the database to the third normal form.

Compress the data using a different compression algorithm.

Manually or automatically increase the storage capacity.

Create another schema to load older data.

You are managing a mission-critical Cloud SQL for PostgreSQL instance. Your application team is running important transactions on the database when another DBA starts an on-demand backup. You want to verify the status of the backup. What should you do?

Perform the gcloud sql operations list command.

Check the cloudsql.googleapis.com/postgres.log instance log.

Perform the gcloud sql operations list command.

Use Cloud Audit Logs to verify the status.

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?

Increase the number of processing units.

Modify the database schema, and add additional indexes.

Shard data required by the application into multiple instances.

Decrease the number of processing units.

Your company uses Bigtable for a user-facing application that displays a low-latency real-time dashboard. You need to recommend the optimal storage type for this read-intensive database. What should you do?

Recommend solid-state drives (SSD).

Recommend splitting the Bigtable instance into two instances in order to load balance the concurrent reads.

Recommend hard disk drives (HDD).

Your organization has a critical business app that is running with a Cloud SQL for MySQL backend database. Your company wants to build the most fault-tolerant and highly available solution possible. You need to ensure that the application database can survive a zonal and regional failure with a primary region of us-central1 and the backup region of us-east1. What should you do?

Provision a Cloud SQL for MySQL instance in us-central1-a. Create a multiple-zone instance in us-central1-b. Create a read replica in us-east1-b.

Provision a Cloud SQL for MySQL instance in us-central1-a. Create a multiple-zone instance in us-west1-b. Create a read replica in us-east1-c.

Provision a Cloud SQL for MySQL instance in us-central1-a. Create a multiple-zone instance in us-central1-b. Create a read replica in us-east1-b.

Provision a Cloud SQL for MySQL instance in us-central1-a. Create a multiple-zone instance in us-east-b. Create a read replica in us-east1-c.

Provision a Cloud SQL for MySQL instance in us-central1-a. Create a multiple-zone instance in us-east1-b. Create a read replica in us-central1-b.

You are building an Android game that needs to store data on a Google Cloud serverless database. The database will log user activity, store user preferences, and receive in-game updates. The target audience resides in developing countries that have intermittent internet connectivity. You need to ensure that the game can synchronize game data to the backend database whenever an internet network is available. What should you do?

Use Cloud SQL with an external (public) IP address.

Use an in-app embedded database.

You released a popular mobile game and are using a 50 TB Cloud Spanner instance to store game data in a PITR-enabled production environment. When you analyzed the game statistics, you realized that some players are exploiting a loophole to gather more points to get on the leaderboard. Another DBA accidentally ran an emergency bugfix script that corrupted some of the data in the production environment. You need to determine the extent of the data corruption and restore the production environment. What should you do? (Choose two.)

If the corruption is significant, use backup and restore, and specify a recovery timestamp.

If the corruption is insignificant, perform a stale read and specify a recovery timestamp. Write the results back.

If the corruption is significant, use backup and restore, and specify a recovery timestamp.

If the corruption is significant, perform a stale read and specify a recovery timestamp. Write the results back.

If the corruption is significant, use import and export.

If the corruption is insignificant, use backup and restore, and specify a recovery timestamp.

If the corruption is insignificant, perform a stale read and specify a recovery timestamp. Write the results back.

You are starting a large CSV import into a Cloud SQL for MySQL instance that has many open connections. You checked memory and CPU usage, and sufficient resources are available. You want to follow Google-recommended practices to ensure that the import will not time out. What should you do?

Close idle connections or restart the instance before beginning the import operation.

Increase the amount of memory allocated to your instance.

Ensure that the service account has the Storage Admin role.

Increase the number of CPUs for the instance to ensure that it can handle the additional import operation.

You are migrating your data center to Google Cloud. You plan to migrate your applications to Compute Engine and your Oracle databases to Bare Metal Solution for Oracle. You must ensure that the applications in different projects can communicate securely and efficiently with the Oracle databases. What should you do?

Set up a Shared VPC, configure multiple service projects, and create firewall rules.

Set up Private Service Connect.

You are running an instance of Cloud Spanner as the backend of your ecommerce website. You learn that the quality assurance (QA) team has doubled the number of their test cases. You need to create a copy of your Cloud Spanner database in a new test environment to accommodate the additional test cases. You want to follow Google-recommended practices. What should you do?

Use Dataflow to run the export in Avro format.

Use Cloud Functions to run the export in Avro format.

Use Cloud Functions to run the export in text format.

Use Dataflow to run the export in Avro format.

Use Dataflow to run the export in text format.

You need to redesign the architecture of an application that currently uses Cloud SQL for PostgreSQL. The users of the application complain about slow query response times. You want to enhance your application architecture to offer sub-millisecond query latency. What should you do?

Configure Memorystore, and modify your application to offload queries.

Configure Firestore, and modify your application to offload queries.

Configure Bigtable, and modify your application to offload queries.

Configure Cloud SQL for PostgreSQL read replicas to offload queries.

Configure Memorystore, and modify your application to offload queries.

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?

Create a SQL Server 2019 Standard on High Memory machine type with 16 vCPUs, 104 GB of RAM, and 4 TB of SSD.

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

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.

Create a SQL Server 2019 Standard on High Memory machine type with 16 vCPUs, 104 GB of RAM, and 4 TB of SSD.

Create a SQL Server 2019 Enterprise on High Memory machine type with 16 vCPUs, 104 GB of RAM, and 500 GB of SSD.

You are managing a small Cloud SQL instance for developers to do testing. The instance is not critical and has a recovery point objective (RPO) of several days. You want to minimize ongoing costs for this instance. What should you do?

Turn on automated backup, and turn off transaction log retention.

Take no backups, and turn off transaction log retention.

Take one manual backup per day, and turn off transaction log retention.

Turn on automated backup, and turn off transaction log retention.

Turn on automated backup, and turn on transaction log retention.

You manage a meeting booking application that uses Cloud SQL. During an important launch, the Cloud SQL instance went through a maintenance event that resulted in a downtime of more than 5 minutes and adversely affected your production application. You need to immediately address the maintenance issue to prevent any unplanned events in the future. What should you do?

Set your production instance's maintenance window to non-business hours.

Migrate the Cloud SQL instance to Cloud Spanner to avoid any future disruptions due to maintenance.

Contact Support to understand why your Cloud SQL instance had a downtime of more than 5 minutes.

Use Cloud Scheduler to schedule a maintenance window of no longer than 5 minutes.

You are designing a highly available (HA) Cloud SQL for PostgreSQL instance that will be used by 100 databases. Each database contains 80 tables that were migrated from your on-premises environment to Google Cloud. The applications that use these databases are located in multiple regions in the US, and you need to ensure that read and write operations have low latency. What should you do?

Deploy 2 Cloud SQL instances in the us-central1 region with HA enabled, and create read replicas in us-east1 and us-west1.

Deploy 2 Cloud SQL instances in the us-central1 region, and create read replicas in us-east1 and us-west1.

Deploy 4 Cloud SQL instances in the us-central1 region with HA enabled, and create read replicas in us-central1, us-east1, and us-west1.

Deploy 4 Cloud SQL instances in the us-central1 region, and create read replicas in us-central1, us-east1 and us-west1.

You work in the logistics department. Your data analysis team needs daily extracts from Cloud SQL for MySQL to train a machine learning model. The model will be used to optimize next-day routes. You need to export the data in CSV format. You want to follow Google-recommended practices. What should you do?

Use Cloud Scheduler to trigger a Cloud Function through Pub/Sub to call the cloudsql.instances.export API.

Use Cloud Scheduler to trigger a Cloud Function that will run a select * from table(s) query to call the cloudsql.instances.export API.

Use Cloud Scheduler to trigger a Cloud Function through Pub/Sub to call the cloudsql.instances.export API.

Use Cloud Composer to orchestrate an export by calling the cloudsql.instances.export API.

Use Cloud Composer to execute a select * from table(s) query and export results.

You are choosing a database backend for a new application. The application will ingest data points from IoT sensors. You need to ensure that the application can scale up to millions of requests per second with sub-10ms latency and store up to 100 TB of history. What should you do?

Use Bigtable, and add nodes as necessary to achieve the required throughput.

Use Cloud SQL with read replicas for throughput.

Use Firestore, and rely on automatic serverless scaling.

Use Memorystore for Memcached, and add nodes as necessary to achieve the required throughput.

Use Bigtable, and add nodes as necessary to achieve the required throughput.

You are designing a payments processing application on Google Cloud. The application must continue to serve requests and avoid any user disruption if a regional failure occurs. You need to use AES-256 to encrypt data in the database, and you want to control where you store the encryption key. What should you do?

Use Cloud Spanner with a customer-managed encryption key (CMEK).

Use Cloud Spanner with default encryption.

Use Cloud SQL with a customer-managed encryption key (CMEK).

Use Bigtable with default encryption.

You are managing a Cloud SQL for MySQL environment in Google Cloud. You have deployed a primary instance in Zone A and a read replica instance in Zone B, both in the same region. You are notified that the replica instance in Zone B was unavailable for 10 minutes. You need to ensure that the read replica instance is still working. What should you do?

Verify that the new replica is created automatically.

Use the Google Cloud Console or gcloud CLI to manually create a new clone database.

Use the Google Cloud Console or gcloud CLI to manually create a new failover replica from backup.

Verify that the new replica is created automatically.

Start the original primary instance and resume replication.

You are migrating an on-premises application to Google Cloud. The application requires a high availability (HA) PostgreSQL database to support business-critical functions. Your company's disaster recovery strategy requires a recovery time objective (RTO) and recovery point objective (RPO) within 30 minutes of failure. You plan to use a Google Cloud managed service. What should you do to maximize uptime for your application?

Deploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Create a cross-region read replica, and promote the read replica as the primary node for disaster recovery.

Deploy Cloud SQL for PostgreSQL in a regional configuration. Create a read replica in a different zone in the same region and a read replica in another region for disaster recovery.

Deploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Take periodic backups, and use this backup to restore to a new Cloud SQL for PostgreSQL instance in another region during a disaster recovery event.

Deploy Cloud SQL for PostgreSQL in a regional configuration with HA enabled. Create a cross-region read replica, and promote the read replica as the primary node for disaster recovery.

Migrate the PostgreSQL database to multi-regional Cloud Spanner so that a single region outage will not affect your application. Update the schema to support Cloud Spanner data types, and refactor the application.

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?

Use Cloud SQL serverless exports.

Create a read replica, and then use the mysqldump utility to export each table.

Clone the Cloud SQL instance, and then use the mysqldump utlity to export the data.

Use the mysqldump utility on the primary database instance to export the backup.

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?

For the application server, set up a service account.

For each application code, set up a common shared user account.

For each application code, set up a dedicated user account.

For the application server, set up a service account.

For the application server, set up a common shared user 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?

Migrate to Cloud SQL for SQL Server.

Migrate to Cloud SQL for PostgreSQL.

Migrate to Google Kubernetes Engine (GKE).

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?

roles/cloudsql.viewer and roles/spanner.databaseUser

roles/cloudsql.editor and roles/spanner.admin

roles/cloudsql.client and roles/spanner.databaseReader

roles/cloudsql.instanceUser and roles/spanner.databaseUser

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?

Use Cloud Spanner in a multi-region configuration.

Use Cloud SQL for PostgreSQL with both cross-region read replicas.

Use Cloud Spanner in a multi-region configuration.

Use Firestore in Datastore mode.

Use a Bigtable instance with clusters in multiple regions.

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

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.

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.

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.

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.

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?

Enable the Cloud SQL Admin API.

Check the app.yaml value cloud_sql_instances for a misspelled or incorrect instance connection name.

Check whether your service account has cloudsql.instances.connect permission.

Enable the Cloud SQL Admin API.

Ensure that you are using an external (public) IP address interface.

You are working on a new centralized inventory management system to track items available in 200 stores, which each have 500 GB of data. 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?

Use Cloud Spanner with a custom autoscaling solution.

Use Oracle Real Application Cluster (RAC) databases on Bare Metal Solution for Oracle.

Use sharded Cloud SQL instances with one or more stores per database instance.

Use a Biglable cluster with autoscaling.

Use Cloud Spanner with a custom autoscaling solution.

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?

Use Liquibase to roll out changes to higher environments.

Use replication to roll out changes to higher environments.

Use backup and restore to roll out changes to higher environments.

Use Liquibase to roll out changes to higher environments.

Manually capture detailed DBA audit logs when changes are rolled out to higher environments.

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?

Issue a gcloud sql instances patch command to increase the number of vCPUs.

Update a MySQL database flag to increase the number of vCPUs.

Issue a gcloud compute instances update command to increase the number of vCPUs.

Back up the database, create an instance with additional vCPUs, and restore the database.

Google Professional Cloud Database Engineer Practice Test 2

Your company wants you to migrate their Oracle, MySQL, Microsoft SQL Server, and PostgreSQL relational databases to Google Cloud. You need a fully managed, flexible database solution when possible. What should you do?

Become a Premium Member for full access

Unlock Premium Member

Google Professional Cloud Database Engineer Practice Test 2

Question

Google Professional Cloud Database Engineer Practice Tests

Practice Tests