Professional-Cloud-Database-Engineer 無料問題集「Google Cloud Certified - Professional Cloud Database Engineer」

（A）Place the bulk of the read and write workloads closer to the default leader region.

（B）Keep the total CPU utilization under 45% in each region.

（C）Add more read-write replicas.

（D）Use staleness of at least 15 seconds.

（A）roles/spanner.databaseUser

（B）roles/spanner.databaseReader

（C）roles/spanner.databaseAdmin

（D）roles/spanner.viewer

（A）Watch Cloud Trace for application requests that are failing.

（B）Watch Query Insights for long running queries.

（C）Watch the Cloud SQL instance monitor for CPU utilization metrics.

（D）Watch the Cloud SQL recommenders for overprovisioned instances.

（A）Implement sharding to distribute the write load across multiple Spanner instances.

（B）Configure read-only transactions to improve read performance during peak periods.

（C）Enable autoscaling in the Spanner instance, and set the maximum number of nodes to match the peak write volume.

（D）Use interleaved tables to reduce the number of cross-node transactions.

（A）Use Memorystore for data storage.

（B）Use Cloud SQL for data storage.

（C）Use Cloud Spanner for data storage.

（D）Use Bigtable for data storage.

（A）For GKE and Compute Engine services, create and grant dedicated IAM service accounts with least-privilege roles for Cloud SQL resources, and configure applications to use workload identity account credentials. For developers, use IAM authentication with Cloud SQL Auth Proxy for secure access.

（B）For all service interfaces and developers, create unique database-native user and password credentials directly on each database instance, and store the credentials in a centralized secret management tool.

（C）Configure the GKE and Compute Engine applications to use the Cloud SQL Auth Proxy for all database connections. Instruct developers to use their local clients with database-native user/password authentication.

（D）Enable public IP addresses for all database instances and configure firewall rules to restrict access based on the source IP addresses of the GKE cluster, Compute Engine VMs, and developers' machines.

（A）Choose Memorystore for Redis Cluster and Private Service Connect for networking connectivity.

（B）Choose a Redis instance on a VM in the Shared VPC network.

（C）Choose Bigtable and connect using Private Google Access API endpoint(s).

（D）Choose a Memorystore for Redis instance and Private Service Access for networking connectivity.

（A）Create a clone database from a read replica database, and restore the clone in the same region.

（B）Create a clone database from a read replica database, and restore the clone into a different zone.

（C）Use the Cloud SQL database import feature. Import last week's dump file from Cloud Storage.

（D）Use the Cloud SQL point-in-time recovery (PITR) feature. Restore the copy from two hours ago to a new database instance.

（A）1. Take a full export while the database is online.
2. Create a bucket in Cloud Storage.
3. Transfer the dump file and write-ahead logs to the bucket you just created.
4. Restore the dump file into the Google Cloud primary server.
5. Create a recovery.conf file in the $PG_DATA directory.
6. Stop the source database.
7. Transfer the write-ahead logs to the bucket you created before.
8. Start the PostgreSQL service.
9. Wait until the Google Cloud primary server syncs with the running primary server.

（B）1. Take a full export while the database is offline.
2. Create a bucket in Cloud Storage.
3. Transfer the dump file to the bucket you just created.
4. Import the dump file into the Google Cloud primary server.

（C）1. Take a full export while the database is offline.
2. Create a bucket in Cloud Storage.
3. Transfer the dump file to the bucket you just created.
4. Restore the backup into the Google Cloud primary server.

（D）1. Take a full backup while the database is online.
2. Create a bucket in Cloud Storage.
3. Transfer the backup to the bucket you just created.
4. Restore the backup into the Google Cloud primary server.
5. Create a recovery.conf file in the $PG_DATA directory.
6. Stop the source database.
7. Transfer the write ahead logs to the bucket you created before.
8. Start the PostgreSQL service.
9. Wait until Google Cloud primary server syncs with the running primary server.

（A）Use gcloud sql instances failover <PrimaryInstanceName>.

（B）Use gcloud sql instances promote-replica <PrimaryInstanceName>.

（C）Use gcloud sql instances promote-replica <ReplicaInstanceName>.

（D）Use gcloud sql instances failover <ReplicaInstanceName>.

（A）Use workload identity federation to impersonate a service account.

（B）Use Google Workspace Password Sync to replicate passwords into Google Cloud.

（C）Ask existing users to set their Google password to match their corporate password.

（D）Migrate the application to Google Cloud, and use Identity and Access Management (IAM).

（A）Enable serializable isolation in the Firebase app.

（B）Build a Firestore bundle, and deploy bundles to Cloud CDN.

（C）Deploy a US multi-region Firestore location.

（D）Create a Firestore index on the news story date.

（A）Use backup and restore to roll out changes to higher environments.

（B）Use replication to roll out changes to higher environments.

（C）Use Liquibase to roll out changes to higher environments.

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