Win IT Exam with Last Dumps 2025

You are the DBA working at a large bank in Europe. Your business-critical banking application runs on Oracle 12.2 in your on-premises data center. You decided to modernize your on-premises Oracle database by migrating to AlloyDB. You must meet the following requirements:
• Remain on-premises and maintain open-source portability.
• Meet regulatory requirements for data residency.
• Support both OLTP and OLAP workloads.
• Maintain high availability (HA) mode and automatic failover.
What should you do?

A. Deploy AlloyDB Omni in a standalone VM on-premises, and set up disaster recovery (DR) in AlloyDB for PostgreSQL. B. Migrate to AlloyDB for PostgreSQL by using Database Migration Service. C. Deploy Kubernetes-based AlloyDB Omni database cluster on-premises. Enable HA by using the AlloyDB Omni Kubernetes operator, and migrate your Oracle database to Omni. D. Deploy AlloyDB Omni as a docker-based container in your on-premises VM, enable HA for it, and migrate your Oracle database to the Omni container.

You have an application that performs numerous reads and writes all day running in a single Bigtable cluster. A new batch analytics job needs to read the same data and you want to make sure that the new job does not affect the existing workload. What should you do?

A. Scale up the Bigtable instance by manually adding more nodes. B. Add a new cluster to the existing instance, and enable multi-cluster routing in the app profile. C. Add a new cluster to the existing instance, and isolate the workloads with two app profiles. D. Scale up the Bigtable instance by enabling Autoscaling.

You are setting up a new AlloyDB instance and want users to be able to use their existing Identity and Access Management (IAM) identities to connect to AlloyDB. You have performed the following steps:
• Manually enabled IAM authentication on the AlloyDB instance
• Granted the alloydb.databaseUser and ser-viceusage.serviceUsageconsumer IAM roles to the users
• Created new AlloyDB database users based on corresponding IAM identities
Users are able to connect but are reporting that they are not able to SELECT from application tables. What should you do?

A. Grant the new database users access privileges to the appropriate tables. B. Grant the alloydb.client IAM role to each user. C. Grant the alloydb.viewer IAM role to each user. D. Grant the alloydb.alloydbreplica IAM role to each user.

You are using Memorystore for Redis to cache frequently accessed data and improve your application's performance. Recently, your application is experiencing sudden spikes in latency when interacting with the Memorystore for Redis instance. Upon checking the logs, you discover a high number of "evicted keys" messages. You want to reduce the occurrences of latency spikes and their impact on the application. What should you do?

A. Increase the time to live (TTL) value of all the keys within the cache. B. Redeploy your application to the same zone as the Memorystore instance. C. Scale the Memorystore instance to a larger memory size. D. Enable read replicas. Deploy additional read replica instances to distribute read workloads.

You are migrating an on-premises database to Spanner. There are a few tables, each with a few hundred records that do not have a primary key on the source database. You need to migrate all of the tables over to the news database while avoiding hot-spotting issues. What should you do?

A. Load the data into Spanner, and designate a primary key later based on business need. B. Use the GENERATE_UUID() function to generate universally unique identifier (UUID) values with the STRING(36) data type when you do the migration. C. During the migration, swap the order of keys so that the column that contains the monotonically increasing or decreasing value is the first key par. D. Migrate the tables with no primary key to maintain consistency with source.

You are the DBA of your organization. You provided a cloned instance from the production Cloud SQL for PostgreSQL database to the developers for testing purposes. After the creation of the clone, your developers notice missing data in one of the recently altered tables. What should you do to ensure that all data is included?

A. Take a back up of the production database, and restore it to another Cloud SQL for PostgreSQL instance. Provide access to the new instance to the developers. B. Check for missing roles and privileges in the cloned Cloud SQL instance. Grant missing privileges to the developers. C. Clone the current production database, and restore it to an earlier point-in-time (PITR). Provide access to the cloned instance to the developers. D. Dump the production database to a file. Modify the dumped file to ALTER TABLE to SET LOGGED on tables that were unlogged in production. Reload the data in the new Cloud SQL for PostgreSQL instance.

Your company is developing a 24/7, global, real-time analytics platform that needs to store and process large amounts of versioned time-series data. You need to design a platform that is highly scalable to accommodate traffic spikes and ensure high availability for mission-critical operations. What should you do?

A. Implement a single-cluster Bigtable instance with autoscaling enabled and row key design. B. Implement a multi-cluster Bigtable instance with autoscaling enabled and optimal schema design. C. Implement a multi-cluster Bigtable instance across multiple regions with replication. D. Implement AlloyDB for PostgreSQL to handle the analytical workload using read replica.

You have a non-critical business application running on Google Kubernetes Engine (GKE) in the app-dev VPC. You have created an AlloyDB cluster with Private Service Access (PSA) and no public IP address in the db-dev VPC. You want your application to securely connect to AlloyDB in a cost-effective way. What should you do?

A. Set up a high availability VPN between the app-dev and db-dev VPCs. Connect the application directly to AlloyDB. B. Connect by using the private IP address of the AlloyDB cluster directly from the application. C. Connect by using AlloyDB Auth Proxy installed in the GKE cluster. D. Install a SOCKS proxy in a VM in the db-dev VPC. Install AlloyDB Auth Proxy in your GKE cluster, and connect to the AlloyDB cluster through the SOCKS server and port.

You are migrating your critical production database from Amazon RDS for MySQL to Cloud SQL for MySQL by using Google Cloud's Database Migration Service. You want to keep disruption to your production database to a minimum and, at the same time, optimize migration performance. What should you do?

A. Create and start multiple Database Migration Service jobs to migrate your database to the target Cloud SQL for MySQL instance. B. Upgrade the Amazon RDS for MySQL primary instance to an instance with more vCPUs and memory, and then run Google Cloud's Database Migration Service. C. Create a single Database Migration Service migration job with initial load parallelism configured to maximum on the source Amazon RDS for MySQL read replica. D. Create a single Database Migration Service migration job with initial Load Parallelism configured to Maximum on the Amazon RDS for MySQL primary instance.

You currently have a MySQL database running on Cloud SQL with a read replica in a different zone for non-mission critical analytics workloads. You want to enable high availability (HA) for the analytic workloads while keeping costs low. What should you do?

A. Increase the size of the read replica instance and enable HA. B. Enable HA on the current read replica. C. Create a new HA instance in the same zone as the primary. D. Create a new HA instance in a different region than the primary.