Google PROFESSIONAL-CLOUD-DATABASE-ENGINEER Online Practice Questions and Exam Preparation

Google PROFESSIONAL-CLOUD-DATABASE-ENGINEER Online Questions & Answers

• Question 61:

  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?

  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).
  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.
  C. Create a SQL Server 2019 Standard on High Memory machine type with 16 vCPUs, 104 GB of RAM, and 4 TB of SSD.
  D. Create a SQL Server 2019 Enterprise on High Memory machine type with 16 vCPUs, 104 GB of RAM, and 500 GB of SSD.
  C. Create a SQL Server 2019 Standard on High Memory machine type with 16 vCPUs, 104 GB of RAM, and 4 TB of SSD.

  ---

  Explanation/Reference:

  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

• Question 62:

  You are the database administrator of a Cloud SQL for PostgreSQL instance that has pgaudit disabled. Users are complaining that their queries are taking longer to execute and performance has degraded over the past few months. You need to collect and analyze query performance data to help identity slow-running queries. What should you do?

  A. View Cloud SQL operations to view historical query information.
  B. White a Logs Explorer query to identify database queries with high execution times.
  C. Review application logs to identify database calls.
  D. Use the Query Insights dashboard to identify high execution times.
  D. Use the Query Insights dashboard to identify high execution times.

  ---

  Explanation/Reference:

  A Cloud SQL instance configured for HA is also called a regional instance and has a primary and secondary zone within the configured region. Within a regional instance, the configuration is made up of a primary instance and a standby instance. Through synchronous replication to each zone's persistent disk, all writes made to the primary instance are replicated to disks in both zones before a transaction is reported as committed. In the event of an instance or zone failure, the standby instance becomes the new primary instance. Users are then rerouted to the new primary instance. This process is called a failover.

• Question 63:

  Your company's mission-critical, globally available application is supported by a Cloud Spanner database. Experienced users of the application have read and write access to the database, but new users are assigned read-only access to the database. You need to assign the appropriate Cloud Spanner Identity and Access Management (IAM) role to new users being onboarded soon. What roles should you set up?

  A. roles/spanner.databaseReader
  B. roles/spanner.databaseUser
  C. roles/spanner.viewer
  D. roles/spanner.backupWriter
  A. roles/spanner.databaseReader

  ---

  Explanation/Reference:

  https://cloud.google.com/spanner/docs/iam?hl=it

• Question 64:

  Your online delivery business that primarily serves retail customers uses Cloud SQL for MySQL for its inventory and scheduling application. The required recovery time objective (RTO) and recovery point objective (RPO) must be in minutes rather than hours as a part of your high availability and disaster recovery design. You need a high availability configuration that can recover without data loss during a zonal or a regional failure. What should you do?

  A. Set up all read replicas in a different region using asynchronous replication.
  B. Set up all read replicas in the same region as the primary instance with synchronous replication.
  C. Set up read replicas in different zones of the same region as the primary instance with synchronous replication, and set up read replicas in different regions with asynchronous replication.
  D. Set up read replicas in different zones of the same region as the primary instance with asynchronous replication, and set up read replicas in different regions with synchronous replication.
  C. Set up read replicas in different zones of the same region as the primary instance with synchronous replication, and set up read replicas in different regions with asynchronous replication.

  ---

  Explanation/Reference:

  This answer meets the RTO and RPO requirements by using synchronous replication within the same region, which ensures that all writes made to the primary instance are replicated to disks in both zones before a transaction is reported as committed1. This minimizes data loss and downtime in case of a zonal or an instance failure, and allows for a quick failover to the standby instance1. This answer also meets the high availability and disaster recovery requirements by using asynchronous replication across different regions, which ensures that the data changes made to the primary instance are replicated to the read replicas in other regions with minimal delay2. This provides additional redundancy and backup in case of a regional failure, and allows for a manual failover to the read replica in another region2.

• Question 65:

  Your company is migrating all legacy applications to Google Cloud. All on-premises applications are using legacy Oracle 12c databases with Oracle Real Application Cluster (RAC) for high availability (HA) and Oracle Data Guard for disaster

  recovery. You need a solution that requires minimal code changes, provides the same high availability you have today on-premises, and supports a low latency network for migrated legacy applications.

  What should you do?

  A. Migrate the databases to Cloud Spanner.
  B. Migrate the databases to Cloud SQL, and enable a standby database.
  C. Migrate the databases to Compute Engine using regional persistent disks.
  D. Migrate the databases to Bare Metal Solution for Oracle.
  D. Migrate the databases to Bare Metal Solution for Oracle.

  ---

  Explanation/Reference:

  BMS is the only Google database service which supports Oracle aside from GCVE. It allows you to use all native Oracle features including RAC. Since GCVE isn't mentioned, it has to be D -Bare Metal Solution.

• Question 66:

  You need to issue a new server certificate because your old one is expiring. You need to avoid a restart of your Cloud SQL for MySQL instance. What should you do in your Cloud SQL instance?

  A. Issue a rollback, and download your server certificate.
  B. Create a new client certificate, and download it.
  C. Create a new server certificate, and download it.
  D. Reset your SSL configuration, and download your server certificate.
  C. Create a new server certificate, and download it.

  ---

  Explanation/Reference:

  https://cloud.google.com/sql/docs/sqlserver/configure-ssl-instance#server-certs

• Question 67:

  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?

  A. Use Cloud SQL with read replicas for throughput.
  B. Use Firestore, and rely on automatic serverless scaling.
  C. Use Memorystore for Memcached, and add nodes as necessary to achieve the required throughput.
  D. Use Bigtable, and add nodes as necessary to achieve the required throughput.
  D. Use Bigtable, and add nodes as necessary to achieve the required throughput.

  ---

  Explanation/Reference:

  https://cloud.google.com/memorystore/docs/redis/redis-overview

• Question 68:

  Your company is developing a global ecommerce website on Google Cloud. Your development team is working on a shopping cart service that is durable and elastically scalable with live traffic. Business disruptions from unplanned downtime are expected to be less than 5 minutes per month. In addition, the application needs to have very low latency writes. You need a data storage solution that has high write throughput and provides 99.99% uptime. What should you do?

  A. Use Cloud SQL for data storage.
  B. Use Cloud Spanner for data storage.
  C. Use Memorystore for data storage.
  D. Use Bigtable for data storage.
  B. Use Cloud Spanner for data storage.

  ---

  Explanation/Reference:

  google Cloud Spanner is a highly scalable, reliable, and fully managed relational database service that runs on Google's infrastructure. It's designed to handle large amounts of data and provide high availability, even in the face of failures. Spanner can be used to store and manage data for a variety of applications, including e-commerce websites. Spanner is a good choice for this scenario because it can handle high write throughput and provides 99.99% uptime. It's also a good fit for applications that need to be highly available, even in the face of failures.

• Question 69:

  You want to migrate an existing on-premises application to Google Cloud. Your application supports semi-structured data ingested from 100,000 sensors, and each sensor sends 10 readings per second from manufacturing plants. You need to make this data available for real-time monitoring and analysis. What should you do?

  A. Deploy the database using Cloud SQL.
  B. Use BigQuery, and load data in batches.
  C. Deploy the database using Bigtable.
  D. Deploy the database using Cloud Spanner.
  C. Deploy the database using Bigtable.

  ---

  Explanation/Reference:

  Bigtable is a scalable, fully managed, and high-performance NoSQL database service that can handle semi-structured data and support real-time monitoring and analysis. Cloud SQL is a relational database service that does not support semi-structured data. BigQuery is a data warehouse service that is optimized for batch processing and analytics, not real-time monitoring. Cloud Spanner is a relational database service that supports semi-structured data with JSON data type, but it is more expensive and complex than Bigtable for this use case.

• Question 70:

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

  ---

  Explanation/Reference:

  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.