CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Google
  5. PROFESSIONAL-CLOUD-DATABASE-ENGINEER

Free PROFESSIONAL-CLOUD-DATABASE-ENGINEER Exam Braindumps

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?

  1. Recommend solid-state drives (SSD).
  2. Recommend splitting the Bigtable instance into two instances in order to load balance the concurrent reads.
  3. Recommend hard disk drives (HDD).
  4. Recommend mixed storage types.

Answer(s): A

Explanation:

if you plan to store extensive historical data for a large number of remote-sensing devices and then use the data to generate daily reports, the cost savings for HDD storage might justify the performance tradeoff. On the other hand, if you plan to use the data to display a real-time dashboard, it probably would not make sense to use HDD storage--reads would be much more frequent in this case, and reads that are not scans are much slower with HDD storage.



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?

  1. 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.
  2. 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.
  3. 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.
  4. 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.

Answer(s): B

Explanation:

https://cloud.google.com/sql/docs/sqlserver/intro-to-cloud-sql-disaster-recovery



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?

  1. Use Firestore.
  2. Use Cloud SQL with an external (public) IP address.
  3. Use an in-app embedded database.
  4. Use Cloud Spanner.

Answer(s): A

Explanation:

https://firebase.google.com/docs/firestore



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

  1. If the corruption is significant, use backup and restore, and specify a recovery timestamp.
  2. If the corruption is significant, perform a stale read and specify a recovery timestamp. Write the results back.
  3. If the corruption is significant, use import and export.
  4. If the corruption is insignificant, use backup and restore, and specify a recovery timestamp.
  5. If the corruption is insignificant, perform a stale read and specify a recovery timestamp. Write the results back.

Answer(s): A,E

Explanation:

https://cloud.google.com/spanner/docs/pitr#ways-to-recover To recover the entire database, backup or export the database specifying a timestamp in the past and then restore or import it to a new database. This is typically used to recover from data corruption issues when you have to revert the entire database to a point-in-time before the corruption occurred.
This part describes significant corruption - A

To recover a portion of the database, perform a stale read specifying a query-condition and timestamp in the past, and then write the results back into the live database. This is typically used for surgical operations on a live database. For example, if you accidentally delete a particular row or incorrectly update a subset of data, you can recover it with this method.
This describes insignificant corruption case ­ E
https://cloud.google.com/spanner/docs/pitr https://cloud.google.com/spanner/docs/backup/restore-backup






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