Courseiva

CCNA Pcdoe Manage Databases Questions

75 of 175 questions · Page 2/3 · Pcdoe Manage Databases topic · Answers revealed

Practice these questionsExam hubAll questions
76
MCQhard

A Cloud SQL for MySQL instance's storage utilization has reached 95%. The database is 5 TB and needs to grow. The operations team tries to increase storage via gcloud but receives an error. What is the likely cause?

A.The instance is at the maximum storage limit for its machine tier
B.The storage resize operation is only allowed during maintenance windows
C.The instance has binary logging enabled, which prevents storage increase
D.The instance has automatic storage increase disabled
AnswerA

Each Cloud SQL tier has a max storage limit (e.g., 10 TB for db-n1-standard-8). If the instance is already at that limit, resize is blocked.

Why this answer

Cloud SQL allows online storage increases but with limits: the maximum storage cannot exceed 30 TB, and the increase must be done in increments. However, the error is likely because the instance is using the maximum allowed storage for its tier, or the storage cannot be shrunk. But the most common issue is that the instance has an on-demand backup or restore operation in progress, which blocks resize.

Another possibility is that the storage is already at the maximum for that machine type. However, the question implies a common misconfiguration: the instance may have a read replica that is replicating from it, and storage resize is not allowed if the replica is in a different region? Actually, storage resize is allowed regardless. More likely: the user has reached the maximum storage size for the current tier (e.g., db-n1-standard-8 supports up to 10 TB).

The correct answer is tier storage limit.

Practice this question →
77
MCQhard

A large enterprise uses Cloud Bigtable for analytics. They notice that some nodes are handling significantly more traffic than others, causing hot spots and performance degradation. Which tool should they use to identify the specific row keys causing the issue?

A.Bigtable Key Visualiser
B.Stackdriver Error Reporting
C.Bigtable cbt tool with read rows command
D.Cloud Monitoring dashboard for Bigtable
AnswerA

Correct. Key Visualiser visualizes access patterns to identify hot spots.

Why this answer

Key Visualiser is a Bigtable tool that provides a heatmap of row key access patterns, helping to identify hot spots by showing which row key ranges are heavily accessed.

Practice this question →
78
Multi-Selectmedium

A developer is building an application that uses Firestore (in Datastore mode). The application needs to query data across two properties: 'status' and 'timestamp', with an equality filter on 'status' and a range filter on 'timestamp'. Which three steps are required to support this query efficiently? (Choose THREE.)

Select 3 answers
A.Ensure that single-field indexes exist for both 'status' and 'timestamp'
B.Enable automatic composite index creation in Firestore settings
C.Create an index exemption for the 'timestamp' field
D.Create a composite index on the 'status' and 'timestamp' fields
E.Use gcloud alpha firestore indexes composite create to define the index
AnswersA, D, E

Single-field indexes are automatically created, but for composite queries, the composite index is essential.

Why this answer

Option A is correct because Firestore (in Datastore mode) requires single-field indexes to be defined for each property used in a query, even when a composite index is also present. Without a single-field index on 'status' and 'timestamp', the query engine cannot efficiently evaluate the equality and range filters, leading to full table scans or query failures.

Exam trap

Cisco often tests the misconception that automatic index creation (like in Firestore Native mode) applies to Datastore mode, or that index exemptions can substitute for proper composite index design.

Practice this question →
79
MCQeasy

A Cloud SQL for PostgreSQL instance is running out of storage. The engineer wants to configure automatic storage increase to avoid manual intervention. What should they do?

A.Use gcloud sql instances patch with the --disk-size flag to set a larger size.
B.Use gcloud sql instances patch with the --storage-auto-increase flag.
C.Create a cron job to monitor disk usage and increase storage via API.
D.Use gcloud sql instances create to create a new instance with larger storage.
AnswerB

This enables automatic storage increase for the Cloud SQL instance.

Why this answer

Option B is correct because Cloud SQL for PostgreSQL supports automatic storage increase, which can be enabled via the `--storage-auto-increase` flag in the `gcloud sql instances patch` command. This feature automatically increases the instance's storage capacity when it approaches the configured limit, eliminating the need for manual intervention.

Exam trap

The trap here is that candidates may confuse manual resizing (using `--disk-size`) with automatic storage increase, or think that a custom monitoring solution is required, when Cloud SQL's built-in `--storage-auto-increase` flag is the correct and simplest solution.

How to eliminate wrong answers

Option A is wrong because the `--disk-size` flag only sets a static disk size; it does not enable automatic storage increase, so manual resizing would still be required when storage runs out. Option C is wrong because creating a custom cron job to monitor and increase storage via the API is unnecessary and error-prone; Cloud SQL provides a built-in automatic storage increase feature that should be used instead. Option D is wrong because creating a new instance with larger storage is a disruptive, manual migration process that does not solve the need for automatic scaling; it also requires downtime and data migration, whereas the existing instance can be patched to enable auto-increase.

Practice this question →
80
MCQeasy

A company is using Memorystore for Redis and wants to ensure data persistence in case of a failure. What is the recommended approach?

A.Configure a standard tier instance, which provides automatic persistence.
B.Enable RDB persistence and configure the backup interval.
C.Use Cloud Storage snapshots (export) or configure cross-region replication.
D.Enable AOF persistence in Memorystore settings.
AnswerC

Correct. Use scheduled exports to Cloud Storage or cross-region replication for disaster recovery.

Why this answer

Memorystore for Redis does not support native persistence (AOF/RDB). For data durability, the recommendation is to use scheduled Cloud Storage snapshots or cross-region replication.

Practice this question →
81
MCQmedium

A Cloud SQL for PostgreSQL instance has a read replica lagging behind the primary. The team needs to monitor the replica lag and set up an alert if it exceeds 60 seconds. Which metric should they use?

A.bytes_received
B.disk_read_ops
C.replication_lag
D.cpu_utilization
AnswerC

This metric directly measures replica lag in seconds.

Why this answer

The correct metric is `replication_lag` because it directly measures the delay in seconds between the primary and read replica in Cloud SQL for PostgreSQL. This metric reflects how far behind the replica is in applying changes from the primary's write-ahead log (WAL), making it the precise indicator for alerting when lag exceeds 60 seconds.

Exam trap

The trap here is that candidates might confuse performance metrics like CPU or disk I/O with direct replication delay, assuming high resource usage always indicates lag, when in fact `replication_lag` is the only metric that measures the exact time difference between primary and replica.

How to eliminate wrong answers

Option A is wrong because `bytes_received` measures the amount of data received by the instance, not the time delay in replication; it could be high even when lag is low. Option B is wrong because `disk_read_ops` tracks input/output operations on disk, which is unrelated to replication lag and instead indicates storage performance. Option D is wrong because `cpu_utilization` measures processor usage, which does not directly represent the replication delay; high CPU could cause lag but is not a direct measure of it.

Practice this question →
82
MCQmedium

An e-commerce platform uses Cloud Bigtable for session data. They need to ensure that if one zone fails, the data is still available with eventual consistency. What should they configure?

A.Enable Bigtable replication across zones within the same region
B.Create a Cloud Bigtable cluster with multiple nodes
C.Export Bigtable tables to Cloud Storage periodically
D.Use Cloud Bigtable HDD storage for durability
AnswerA

Replication provides async eventual consistency and failover if a zone goes down.

Why this answer

Bigtable replication across zones provides high availability with eventual consistency (async replication). This meets the requirement of surviving a zone failure.

Practice this question →
83
MCQeasy

Your Memorystore for Redis instance needs to survive a zonal failure with minimal data loss. Which feature should you use?

A.Use a Basic tier instance and schedule periodic exports to Cloud Storage.
B.Use a Standard tier instance with replication across zones within the same region.
C.Enable persistence with RDB snapshots stored in Cloud Storage.
D.Create a cross-region replica (read replica in another region).
AnswerB

Standard tier provides multi-AZ replication for high availability.

Why this answer

Option B is correct because a Standard tier Memorystore for Redis instance with replication across zones provides automatic failover to a replica in a different zone, ensuring high availability and minimal data loss during a zonal failure. The Standard tier uses synchronous replication within the region, so data written to the primary is replicated to the cross-zone replica before acknowledging the write, which minimizes data loss to only in-flight transactions that were not yet committed.

Exam trap

Cisco often tests the misconception that persistence (RDB/AOF) alone provides high availability, but persistence only protects against data loss from restarts, not against zonal failures; you need cross-zone replication (Standard tier) for automatic failover and minimal data loss during a zone outage.

How to eliminate wrong answers

Option A is wrong because Basic tier instances are single-zone and lack replication, so a zonal failure causes complete data loss; periodic exports to Cloud Storage only provide point-in-time recovery with potential data loss between exports, not real-time failover. Option C is wrong because enabling persistence with RDB snapshots stored in Cloud Storage is a backup mechanism, not a high-availability feature; it does not provide automatic failover or replication, so a zonal failure still results in downtime and data loss from the last snapshot. Option D is wrong because cross-region replicas (read replicas) are read-only and do not support automatic failover in Memorystore for Redis; they are designed for read scaling and disaster recovery across regions, not for surviving a zonal failure within the same region with minimal data loss.

Practice this question →
84
MCQhard

A Cloud Spanner database has a table 'Orders' with a column 'status'. The development team needs to add a new column 'priority INT64' to the table without downtime. Which statement should the database administrator execute?

A.CREATE INDEX idx_priority ON Orders (priority);
B.UPDATE Orders SET priority = 0; (no prior column)
C.ALTER TABLE Orders ADD priority INT64 NOT NULL DEFAULT 0;
D.ALTER TABLE Orders ADD COLUMN priority INT64;
AnswerD

Correct. This DDL statement adds the column online, non-blocking.

Why this answer

Spanner supports online schema changes that are non-blocking. ALTER TABLE ... ADD COLUMN is the correct DDL statement and executes without locking the table.

Practice this question →
85
Multi-Selectmedium

Which TWO statements about Cloud Spanner schema changes are correct? (Choose 2)

Select 2 answers
A.Schema changes are applied asynchronously and may take minutes to hours to complete.
B.Schema changes require the instance to be restarted.
C.ALTER TABLE statements are non-blocking and can be executed while the database is in use.
D.You can only add columns, not drop them.
E.Creating a secondary index requires taking the table offline.
AnswersA, C

Schema changes are applied in the background and can take time depending on data size.

Practice this question →
86
MCQeasy

A Cloud Bigtable instance has a hot spot causing performance degradation. Which tool helps identify the hot spot?

A.Cloud Monitoring dashboard
B.Cloud Logging
C.Key Visualizer
D.Bigtable Admin API
AnswerC

Key Visualizer is specifically designed to analyze access distribution and detect hot spots.

Why this answer

Key Visualizer is a built-in Bigtable tool that visualizes access patterns and helps identify hot spots (uneven load across row keys).

Practice this question →
87
Multi-Selectmedium

You have a Memorystore for Redis instance used as a cache. You need to scale it to handle increased load. The current instance is Basic Tier with 2 GB memory. Which TWO actions can you take to scale the instance? (Choose two.)

Select 2 answers
A.Vertically scale the instance by increasing its memory size or changing to a higher-tier (e.g., Standard Tier).
B.Create additional instances and implement client-side sharding.
C.Change the eviction policy to noeviction to allow more data.
D.Add read replicas to offload read traffic.
E.Enable Redis Cluster to horizontally scale across multiple shards.
AnswersA, E

Vertical scaling increases capacity by adding more memory to a single node.

Why this answer

Memorystore supports vertical scaling by changing the tier (e.g., from Basic to Standard, or increasing memory size) and horizontal scaling using Redis Cluster (which shards data across multiple nodes). Scaling up within the same tier by increasing memory is also possible, but option A (vertical scaling) and option B (Redis Cluster) are the two general scaling methods.

Practice this question →
88
MCQeasy

A database administrator needs to restore a Cloud SQL for PostgreSQL instance to a specific point in time within the last 3 hours. Which configurations must be enabled to perform a point-in-time recovery (PITR)?

A.Automated backups and binary logging
B.On-demand backups and binary logging
C.Automated backups and WAL archiving with a retention period
D.Automated backups and cross-region replicas
AnswerC

Correct. PITR requires automated backups and WAL archiving (transaction logs) with retention between 1-7 days.

Why this answer

PITR in Cloud SQL for PostgreSQL requires automated backups enabled and write-ahead log (WAL) archiving with a specified transaction log retention period (1-7 days). Binary logging is for MySQL, not PostgreSQL.

Practice this question →
89
Multi-Selecthard

Which THREE metrics should you set up alerts for to proactively monitor the health of a Cloud SQL for MySQL instance? (Choose 3)

Select 3 answers
A.Replication lag (for instances with replicas)
B.Number of queries per second
C.CPU utilization > 80%
D.Network throughput
E.Disk usage
AnswersA, C, E

Replication lag indicates if replicas are falling behind.

Why this answer

Replication lag is a critical metric for Cloud SQL for MySQL instances with replicas because it measures the delay between the primary instance and its read replicas. High replication lag can lead to stale reads and data inconsistency, and if it exceeds certain thresholds, it may indicate network issues, high write load, or insufficient replica resources. Proactive alerts on replication lag help ensure data freshness and application reliability.

Exam trap

Cisco often tests the distinction between metrics that indicate health (e.g., replication lag, CPU utilization, disk usage) versus metrics that indicate performance or throughput (e.g., queries per second, network throughput), leading candidates to select the latter as health indicators.

Practice this question →
90
MCQmedium

A company uses Cloud Spanner for a global inventory system. They need to add a new index on an existing table to support a new query pattern without downtime. What is the correct approach to create the index?

A.Create a new table with the index and migrate data manually
B.Use the Cloud Console to create the index; it requires a maintenance window
C.Take the table offline, create the index, then bring it back online
D.Use the gcloud CLI to create the index; Spanner handles it as an online, non-blocking operation
AnswerD

Correct. Spanner DDL statements are online and non-blocking. The gcloud spanner databases ddl update command can be used.

Why this answer

Option D is correct because Cloud Spanner supports online schema changes, including index creation, without requiring downtime. When you use the gcloud CLI or the Cloud Console to create an index, Spanner performs the operation as a non-blocking, asynchronous background process that allows continued reads and writes on the table.

Exam trap

Cisco often tests the misconception that schema changes in a globally distributed database require downtime or manual migration, but Spanner's online schema change capability eliminates that need.

How to eliminate wrong answers

Option A is wrong because manually creating a new table and migrating data introduces unnecessary complexity, risk of data inconsistency, and potential downtime, whereas Spanner natively supports online index creation. Option B is wrong because the Cloud Console can be used to create the index without a maintenance window; Spanner does not require any downtime for index creation. Option C is wrong because taking the table offline is unnecessary and defeats the purpose of Spanner's managed, highly available architecture; Spanner indexes are built online without blocking DML operations.

Practice this question →
91
MCQhard

A financial application uses Cloud Spanner and requires daily full backups stored in another region for compliance. The backups must be restorable without exporting/importing. Which backup method should they use?

A.Export the database to Avro files in Cloud Storage in another region, then import when needed.
B.Use Cloud Scheduler to trigger a script that takes a snapshot of the database in Cloud Storage.
C.Use Spanner's scheduled backups and configure a cross-region backup policy.
D.Create on-demand backups and copy them to another region manually.
AnswerC

Spanner backups can be created and stored in another region, restorable directly.

Why this answer

Spanner database-level backups can be created and stored in a different region (cross-region backup). These backups can be restored directly to a new database without export/import. Option A is correct.

Option B (export to GCS) requires import. Option C (on-demand backup) can be cross-region, but the question asks for daily; scheduled backups are better. Option D (snapshots using Cloud Storage) is not a built-in Spanner feature.

Practice this question →
92
MCQhard

You notice that your Cloud SQL for MySQL instance's storage is filling up quickly. You have enabled automatic storage increase, but you want to manually increase the storage size by 50 GB to avoid any risk of reaching the limit. The current disk size is 200 GB. What is the correct gcloud command to resize the disk?

A.gcloud sql instances patch my-instance --storage-size 250GB
B.gcloud sql instances patch my-instance --storage-size 250
C.gcloud sql instances update my-instance --storage-size 250
D.gcloud sql instances resize my-instance 250
AnswerB

This increases the disk to 250 GB. The command is valid and disk resize is online.

Why this answer

Option B is correct because the `gcloud sql instances patch` command is used to modify an existing Cloud SQL instance, and the `--storage-size` flag expects the value in GB as an integer (without the 'GB' suffix). Specifying `250` correctly increases the storage from 200 GB to 250 GB.

Exam trap

Cisco often tests the exact syntax of gcloud commands, specifically that the `--storage-size` flag takes a plain integer (no 'GB' suffix) and that `patch` is the correct subcommand for modifying an existing instance, not `update` or `resize`.

How to eliminate wrong answers

Option A is wrong because the `--storage-size` flag does not accept a unit suffix like 'GB'; it expects a plain integer representing gigabytes. Option C is wrong because `gcloud sql instances update` is not a valid command; the correct command is `gcloud sql instances patch`. Option D is wrong because `gcloud sql instances resize` is not a valid gcloud command; Cloud SQL storage resizing is done via the `patch` subcommand with the `--storage-size` flag.

Practice this question →
93
Multi-Selectmedium

A company uses Cloud Spanner and needs to implement change data capture (CDC) to stream changes to a downstream analytics pipeline. Which two features can they use? (Choose TWO.)

Select 2 answers
A.Pub/Sub integration to consume change stream data
B.Cloud SQL for PostgreSQL logical replication
C.Datastream
D.Bigtable replication
E.Spanner change streams
AnswersA, E

Changes from change streams can be published to Pub/Sub.

Why this answer

Spanner provides change streams to capture row-level changes. The changes can be read using the Spanner API and streamed to Pub/Sub for downstream processing. Option A (Change streams) is correct; Option C (Pub/Sub integration) is correct.

Option B (Cloud SQL) is not Spanner. Option D (Datastream) is for database migrations, not CDC. Option E (Bigtable) is not Spanner.

Practice this question →
94
Multi-Selectmedium

A company is migrating on-premises MySQL databases to Cloud SQL. They need to ensure high availability and disaster recovery with minimal data loss. Which TWO configurations should they implement?

Select 2 answers
A.Configure automated backups with 7-day retention.
B.Enable High Availability (HA) configuration on the primary instance.
C.Create a cross-region read replica for failover.
D.Use Cloud SQL Proxy for secure connections.
E.Enable binary logging for point-in-time recovery.
AnswersB, C

HA provides zonal failover with synchronous replication to another zone.

Why this answer

Option B is correct because enabling High Availability (HA) configuration on a Cloud SQL primary instance creates a synchronous standby in a different zone within the same region, providing automatic failover with minimal data loss (typically under one second). This directly addresses the need for high availability with minimal data loss during a zonal outage.

Exam trap

Cisco often tests the distinction between synchronous replication (HA within region) and asynchronous replication (cross-region read replicas), where candidates mistakenly think a cross-region read replica alone provides automatic failover with minimal data loss, but it actually requires manual promotion and has higher RPO.

Practice this question →
95
MCQmedium

A company uses Cloud SQL for PostgreSQL. They need to monitor the replication lag on a read replica. Which metric should they use in Cloud Monitoring?

A.cloudsql.googleapis.com/database/replication/replica_lag
B.cloudsql.googleapis.com/database/postgresql/replication/replica_lag
C.cloudsql.googleapis.com/database/replication/lag_seconds
D.cloudsql.googleapis.com/database/postgresql/replication/lag
AnswerB

Correct. This is the specific metric for PostgreSQL replicas.

Why this answer

For PostgreSQL replicas in Cloud SQL, the metric 'cloudsql.googleapis.com/database/postgresql/replication/replica_lag' measures lag in bytes (seconds can be derived). The metric 'replication_lag' is available for MySQL. For PostgreSQL, the specific metric is 'replica_lag'.

Practice this question →
96
MCQeasy

An engineer needs to monitor the replication lag of a Cloud SQL read replica. Which metric should they use in Cloud Monitoring?

A.replication_lag
B.sent_bytes_count
C.disk_bytes_used
D.cpu_utilization
AnswerA

This metric directly measures the lag between the primary and read replica.

Why this answer

The `replication_lag` metric in Cloud Monitoring directly measures the time delay between a primary Cloud SQL instance and its read replica, reported in seconds. This is the standard metric for monitoring how far behind the replica is in applying changes from the primary, which is critical for ensuring read-after-write consistency and data freshness.

Exam trap

Cisco often tests the distinction between metrics that measure replication *throughput* (like `sent_bytes_count`) versus those that measure replication *latency* (like `replication_lag`), leading candidates to confuse data transfer volume with time delay.

How to eliminate wrong answers

Option B is wrong because `sent_bytes_count` tracks the volume of data transferred from the primary to the replica, not the time delay in replication, so it cannot indicate lag. Option C is wrong because `disk_bytes_used` measures storage consumption on the replica, which is unrelated to replication latency. Option D is wrong because `cpu_utilization` reflects the replica's processing load, not the replication delay, and high CPU does not necessarily correlate with lag.

Practice this question →
97
Multi-Selecthard

You are managing a Memorystore for Redis instance that is part of a high-traffic e-commerce application. The instance uses the volatile-lru eviction policy and has persistence disabled. You need to improve data durability without losing the ability to evict keys with TTL. You also want to ensure that the instance can automatically recover from a zonal failure. Which TWO actions should you take? (Choose TWO.)

Select 2 answers
A.Increase the maxmemory setting to reduce eviction frequency.
B.Enable RDB persistence by setting the persistence mode.
C.Configure a cross-region replica to provide failover in another region.
D.Create a standard tier instance with replication enabled for automatic failover.
E.Set up a Cloud Scheduler job to export the instance to Cloud Storage every hour.
AnswersC, E

A cross-region replica provides durability and failover across regions.

Why this answer

Option C is correct because a cross-region replica provides automatic failover to another region, ensuring recovery from a zonal failure. Option E is correct because exporting the instance to Cloud Storage every hour creates periodic backups, improving data durability without interfering with the volatile-lru eviction policy, which relies on TTL-based keys.

Exam trap

Cisco often tests the distinction between high availability (within-region replication) and disaster recovery (cross-region failover), tricking candidates into choosing a standard tier replica for zonal failure when only a cross-region replica provides multi-zone recovery.

Practice this question →
98
MCQeasy

A Cloud Memorystore for Redis instance is running out of memory. The team wants to automatically remove the least recently used keys when memory is full. Which eviction policy should they configure?

A.volatile-lru
B.volatile-ttl
C.noeviction
D.allkeys-lru
AnswerD

Evicts least recently used keys from all keys.

Why this answer

The `allkeys-lru` eviction policy is correct because it applies the LRU (Least Recently Used) algorithm to all keys in the Redis instance, not just those with an expiry set. This ensures that when memory is full, the least recently accessed keys are automatically removed, regardless of whether they have a TTL, which directly meets the requirement to free memory without manual intervention.

Exam trap

Cisco often tests the distinction between `volatile-lru` and `allkeys-lru`, trapping candidates who assume LRU only applies to keys with TTLs, when the requirement to remove 'least recently used keys' without qualification implies all keys should be considered.

How to eliminate wrong answers

Option A is wrong because `volatile-lru` only evicts keys that have an expiry (TTL) set, leaving keys without expiry untouched, which may not free enough memory if the majority of keys are persistent. Option B is wrong because `volatile-ttl` evicts keys with the shortest remaining TTL first, which is not based on access patterns and may remove frequently used keys that happen to have a short TTL. Option C is wrong because `noeviction` prevents any eviction and instead returns errors on write operations when memory is full, which does not automatically remove any keys and can cause application failures.

Practice this question →
99
Multi-Selectmedium

A company is using Cloud Bigtable and wants to set up monitoring and alerting for replication lag between clusters. Which TWO metrics should they use? (Choose 2)

Select 2 answers
A.cloudbigtable.googleapis.com/cluster/disk_usage
B.cloudbigtable.googleapis.com/cluster/replication_lag
C.cloudbigtable.googleapis.com/cluster/cpu_load
D.cloudbigtable.googleapis.com/cluster/replication_delay
E.cloudbigtable.googleapis.com/cluster/operations_count
AnswersB, D

Correct. This metric shows the lag in operations.

Why this answer

Option B is correct because `replication_lag` directly measures the time difference between the primary cluster and a replica cluster in Cloud Bigtable, which is the key metric for monitoring replication delay. Option D is also correct because `replication_delay` is another metric that tracks the same concept, often reported in seconds, and is used to alert when replicas fall behind. Both metrics are essential for ensuring data consistency and timely failover in multi-cluster Bigtable deployments.

Exam trap

Cisco often tests the distinction between `replication_lag` and `replication_delay` as two separate but valid metrics, while candidates may mistakenly think only one is correct or confuse them with cluster health metrics like CPU or disk usage.

Practice this question →
100
Multi-Selectmedium

A company is designing a disaster recovery plan for Cloud SQL for MySQL. They need to ensure the database can be recovered with minimal data loss (RPO of minutes) in case of a regional outage. Which TWO actions should they take?

Select 2 answers
A.Create a cross-region read replica
B.Set up a same-region read replica
C.Enable binary logging with a PITR retention period
D.Enable automatic storage increase
E.Configure automated daily backups
AnswersA, C

A cross-region replica provides near-real-time data in another region for failover.

Why this answer

To achieve low RPO across regions, enable binary logging for PITR and configure a cross-region replica. Automated backups alone have a RPO of up to 24 hours.

Practice this question →
101
Multi-Selecthard

A team is managing a Memorystore for Redis instance that needs to scale to handle increased traffic. They want to ensure high availability and the ability to distribute data across multiple nodes. Which three actions should they take? (Choose THREE.)

Select 3 answers
A.Use Cloud Storage snapshots for persistence
B.Enable Redis Cluster on the instance to shard data across multiple nodes
C.Upgrade the instance to a higher memory size by changing the tier
D.Create a read replica in a different zone for high availability
E.Enable AOF persistence
AnswersB, C, D

Redis Cluster provides horizontal scaling and sharding.

Why this answer

Memorystore for Redis offers vertical scaling (changing tier) and horizontal scaling via Redis Cluster (enabling clustering). For HA, they can create a standard tier instance with replication (a read replica).

Practice this question →
102
MCQmedium

You have a Cloud Spanner database that needs to be migrated from one region to another. You want to ensure no data loss and minimal downtime. Which approach should you use?

A.Use gcloud spanner instances move to change the region of the existing instance.
B.Create a backup of the database and restore it to a new instance in the target region.
C.Create a read replica in the target region and promote it after replication catches up.
D.Use gcloud command 'gcloud spanner databases export' to export the database to CSV files, then import into the new instance.
AnswerB

Backup/restore is the recommended method for moving a Spanner database between regions.

Why this answer

Option B is correct because Cloud Spanner does not support in-place region changes or read replicas in different regions. The only supported method to migrate a Cloud Spanner database between regions with no data loss and minimal downtime is to create a backup of the database and restore it to a new instance in the target region. This approach ensures a consistent snapshot of the data and allows you to plan the cutover window to minimize downtime.

Exam trap

Cisco often tests the misconception that Cloud Spanner supports cross-region read replicas like other databases (e.g., Cloud SQL or MySQL), but Spanner's architecture uses a single regional or multi-region instance configuration with synchronous replication, not promotable replicas.

How to eliminate wrong answers

Option A is wrong because the `gcloud spanner instances move` command does not exist; Cloud Spanner instances cannot have their region changed after creation. Option C is wrong because Cloud Spanner does not support cross-region read replicas that can be promoted; replicas in Spanner are always part of the same instance and region configuration. Option D is wrong because exporting to CSV files using `gcloud spanner databases export` is not supported; Cloud Spanner only supports export to Avro format, and importing from CSV would require custom tooling and would not guarantee consistency or minimal downtime.

Practice this question →
103
Multi-Selecthard

A company is migrating its on-premises PostgreSQL database to Cloud SQL. The database is 2 TB and the migration must have minimal downtime. The source database supports continuous archiving. Which three steps should they take? (Choose THREE.)

Select 3 answers
A.Use pg_dump to export the database and import into Cloud SQL.
B.Perform the cutover by promoting the Cloud SQL instance to primary.
C.Enable binary logging on the source database.
D.Set up Cloud SQL as an external replica of the on-premises database.
E.Use Database Migration Service with continuous migration.
AnswersB, D, E

Once replication is caught up, promote the Cloud SQL instance to become the new primary.

Why this answer

Option B is correct because promoting the Cloud SQL instance to primary is the final step in a migration using continuous replication, which minimizes downtime by allowing the source database to remain operational until the cutover. This approach leverages Cloud SQL's ability to act as a replica that stays synchronized with the on-premises database via continuous archiving, ensuring data consistency with minimal interruption.

Exam trap

Cisco often tests the distinction between database-specific features, and the trap here is that candidates familiar with MySQL might incorrectly associate binary logging with PostgreSQL, leading them to select Option C, while the correct approach for PostgreSQL involves WAL-based replication and DMS for continuous migration.

Practice this question →
104
MCQmedium

You are using Cloud Spanner and need to add a new column to an existing table. The table has millions of rows and must remain fully available for reads and writes during the schema change. What is the correct approach?

A.Export the table using Dataflow, add the column locally, then import the data back.
B.Use gcloud spanner instances update to modify the table schema.
C.Take the instance offline, run the ALTER TABLE, then bring it back online.
D.Use gcloud spanner databases ddl update with the ALTER TABLE statement; Spanner applies the change online.
AnswerD

Spanner DDL operations are non-blocking, so the table remains available during schema changes.

Why this answer

Cloud Spanner supports non-blocking schema changes using DDL statements like ALTER TABLE ... ADD COLUMN. These operations are applied online without locking the table.

The --async flag is optional for running the command asynchronously. The statement is executed via gcloud spanner databases ddl update.

Practice this question →
105
MCQhard

A Cloud Bigtable instance experiences a sudden increase in read latency and request errors. The operations team notices that one node is handling disproportionately more traffic. Which tool should they use to diagnose the issue?

A.Key Visualiser
B.Stackdriver Monitoring dashboard
C.gcloud bigtable instances describe
D.Use the cbt command to scan the table
AnswerA

Key Visualiser is designed to identify hot spots by visualising read/write patterns across key ranges.

Why this answer

Key Visualizer is the correct tool because it provides a heatmap of access patterns across row key ranges, allowing you to identify hot spots where a single node is overloaded due to uneven key distribution. This directly addresses the symptom of one node handling disproportionately more traffic, which is a common cause of increased latency and errors in Cloud Bigtable.

Exam trap

Cisco often tests the distinction between monitoring aggregate metrics (Cloud Monitoring) and diagnosing specific access patterns (Key Visualizer), leading candidates to choose the familiar monitoring dashboard instead of the specialized diagnostic tool.

How to eliminate wrong answers

Option B is wrong because Stackdriver Monitoring (now Cloud Monitoring) provides aggregate metrics like average latency and error rates, but it does not offer per-node or per-key-range granularity to pinpoint which specific row keys are causing the hot spot. Option C is wrong because 'gcloud bigtable instances describe' returns metadata about the instance (e.g., display name, cluster configuration) but no real-time traffic distribution or performance data. Option D is wrong because the 'cbt' command is used for manual table operations like reading or writing data, not for diagnosing traffic imbalance or hot spots; scanning the table would not reveal which node is overloaded.

Practice this question →
106
Multi-Selecteasy

A database administrator wants to set up monitoring and alerting for Cloud SQL instances. They need to be notified when CPU utilisation exceeds 80% for more than 5 minutes and when replication lag on a read replica exceeds 30 seconds. Which two metrics should they create alerting policies for? (Choose TWO.)

Select 2 answers
A.cloudsql.googleapis.com/database/network/received_bytes_count
B.cloudsql.googleapis.com/database/disk/bytes_used
C.cloudsql.googleapis.com/database/replication/replica_lag
D.cloudsql.googleapis.com/database/cpu/utilization
E.agent.googleapis.com/cpu_usage
AnswersC, D

This metric measures replication lag in seconds.

Why this answer

Cloud SQL provides the metric 'cloudsql.googleapis.com/database/cpu/utilization' for CPU usage and 'cloudsql.googleapis.com/database/replication/replica_lag' for replication lag. Alerting policies can be set on these metrics in Cloud Monitoring.

Practice this question →
107
MCQmedium

A team is designing a disaster recovery strategy for Cloud SQL. They need to be able to recover the database in a different region with a Recovery Point Objective (RPO) of less than 30 minutes. What should they configure?

A.Use on-demand backups every 30 minutes and store them in a multi-regional bucket.
B.Enable binary logging and configure a cross-region replica for PITR.
C.Create a cross-region read replica and promote it to standalone during a disaster.
D.Create automated backups with a retention of 7 days and restore to a new instance in the desired region.
AnswerC

Cross-region read replicas provide asynchronous replication with RPO typically in seconds to minutes. Promoting gives a new primary in the other region.

Practice this question →
108
MCQhard

Your Cloud Bigtable instance uses HDD storage. You need to change to SSD to improve read performance. What is the correct procedure?

A.Use Cloud Bigtable's online storage migration feature to switch to SSD without downtime.
B.Update the instance's storage type using 'gcloud bigtable instances update' with the --storage-type flag.
C.Create a new cluster with SSD storage in the same instance, replicate data, then delete the old cluster.
D.Export the HDD cluster's data to Cloud Storage, then import into a new SSD cluster.
AnswerC

This is the correct approach: create an SSD cluster, enable replication, wait for data sync, then delete the HDD cluster.

Why this answer

Bigtable does not support converting storage type in place. To change from HDD to SSD, you must create a new cluster with SSD storage, then replicate or re-ingest data. The simplest method is to use a backup and restore, or use Dataflow to copy data.

Directly creating a new cluster and enabling replication can also work.

Practice this question →
109
MCQhard

A gaming company uses Firestore in Native mode to store player profiles and game state. They need to query the data by both 'playerId' and 'lastLoginTimestamp' sorted descending. The current index configuration is automatic. How should they configure indexing to support this query efficiently?

A.Create two separate single-field indexes: one on 'playerId' and one on 'lastLoginTimestamp'
B.Use an exemption to remove automatic indexing on 'playerId' and rely on single-field indexes
C.Use the automatic index configuration; Firestore will create the necessary composite index automatically
D.Create a composite index on 'playerId' ascending and 'lastLoginTimestamp' descending
AnswerD

Correct. A composite index with the exact order (asc/desc) is needed for efficient queries with ordering.

Why this answer

Firestore automatically creates single-field indexes for all fields. For queries with ordering on two fields, a composite index is required. The composite index must include both fields in the correct order (ascending or descending).

Practice this question →
110
MCQmedium

A Cloud Spanner database needs a new index added to support a new query pattern. The database is serving live traffic. Which approach should be taken?

A.Export the data, create a new database with the index, and import the data.
B.Create the index using DDL statement 'CREATE INDEX' — it will be applied online without downtime.
C.Stop the application, add the index, and restart.
D.Use gcloud spanner databases add-index command.
AnswerB

Correct. Spanner schema changes are non-blocking for existing database operations.

Why this answer

Cloud Spanner supports online schema changes, including index creation, without downtime. The 'CREATE INDEX' DDL statement is applied asynchronously in the background, allowing the database to continue serving live traffic while the index is built. This is the correct approach because it avoids any interruption to the application.

Exam trap

Cisco often tests the misconception that schema changes in a distributed database require downtime or manual data migration, leading candidates to choose disruptive options like stopping the application or re-importing data.

How to eliminate wrong answers

Option A is wrong because exporting and re-importing data is unnecessary and introduces significant downtime and complexity; Cloud Spanner handles index creation online without data movement. Option C is wrong because stopping the application is not required; Cloud Spanner's online DDL allows schema changes while the database remains fully operational. Option D is wrong because 'gcloud spanner databases add-index' is not a valid gcloud command; index creation is performed using DDL statements, not a dedicated CLI command.

Practice this question →
111
MCQeasy

A Cloud SQL for PostgreSQL instance is experiencing a surge in read traffic. The team wants to offload read queries without affecting write latency. What should they do?

A.Enable automated backups
B.Create a same-region read replica
C.Create a cross-region read replica
D.Increase the CPU of the primary instance
AnswerB

Same-region read replicas offload read traffic with minimal latency, preserving write performance on the primary.

Why this answer

Creating read replicas allows distributing read traffic, reducing load on the primary instance for writes. Read replicas are the standard solution for scaling read workloads.

Practice this question →
112
Multi-Selectmedium

You are designing a disaster recovery strategy for a Cloud SQL for MySQL instance that hosts a critical OLTP application. The instance is in us-central1. You need to ensure that you can recover the database to a different region within 1 hour of a regional outage, with minimal data loss. Which TWO actions should you take? (Choose TWO.)

Select 2 answers
A.Take daily on-demand exports to Cloud Storage.
B.Create two cross-region read replicas for redundancy.
C.Increase the instance tier to have more memory.
D.Enable automated backups and point-in-time recovery with a 7-day retention.
E.Create a cross-region read replica in us-west1.
AnswersD, E

PITR allows restoring to any point within the retention window, complementing the replica for data integrity.

Why this answer

Option D is correct because enabling automated backups with point-in-time recovery (PITR) allows you to restore the database to any point within the retention window (here, 7 days), minimizing data loss to seconds. Option E is correct because a cross-region read replica in us-west1 can be promoted to a standalone primary instance in the event of a regional outage, providing a fully writable database in another region within minutes, meeting the 1-hour RTO.

Exam trap

Cisco often tests the misconception that cross-region read replicas are only for read scaling and cannot be used for disaster recovery, but in Cloud SQL, promoting a cross-region replica is a valid DR strategy that provides a writable instance in another region with minimal data loss.

Practice this question →
113
MCQhard

A financial services company uses Cloud Bigtable for real-time fraud detection. They have a cluster with 10 nodes using HDD storage and are experiencing high latency due to disk throughput bottlenecks. They need to improve performance with minimal downtime. What should they do?

A.Modify the existing cluster's storage type to SSD via the Cloud Console
B.Create a new cluster with SSD storage, replicate data, then update the application to point to the new cluster
C.Use Cloud Bigtable's hot tablet detection to rebalance the data
D.Increase the number of nodes in the existing cluster
AnswerB

Correct. A new cluster with SSD must be created. Use replication to keep data in sync, then cut over with minimal downtime.

Why this answer

Option B is correct because Cloud Bigtable does not support in-place conversion of storage from HDD to SSD. The only way to migrate to SSD storage is to create a new cluster with SSD, replicate data using Bigtable replication, and then update the application connection string to point to the new cluster. This approach minimizes downtime by allowing the old cluster to serve reads during replication.

Exam trap

Cisco often tests the misconception that you can change storage type in-place or that adding nodes solves all performance issues, but the key trap here is that HDD throughput is a hardware limitation that requires a new cluster with SSD to overcome.

How to eliminate wrong answers

Option A is wrong because Cloud Bigtable does not allow modifying the storage type of an existing cluster via the Cloud Console or any API; storage type is fixed at cluster creation. Option C is wrong because hot tablet detection and rebalancing address read/write hotspot issues, not disk throughput bottlenecks caused by HDD vs SSD performance. Option D is wrong because increasing the number of nodes adds CPU and memory capacity but does not resolve the fundamental I/O throughput limitation of HDD storage; the bottleneck is disk speed, not node count.

Practice this question →
114
MCQmedium

A company has a Cloud SQL for MySQL instance with a cross-region read replica for disaster recovery. During a regional outage, they need to promote the read replica to a standalone instance as quickly as possible. What is the correct procedure?

A.Create a backup of the replica and restore it as a new instance
B.Delete the read replica and restore a backup from the primary as a new instance
C.Use the gcloud sql instances promote-replica command on the replica
D.Stop replication on the replica by issuing STOP SLAVE on the instance
AnswerC

Correct. The promote-replica command promotes the replica to a standalone instance.

Why this answer

Promoting a read replica makes it a standalone instance. It can be done via the Cloud Console or gcloud command. The promotion is immediate, but the original primary may still be active if not stopped.

Practice this question →
115
MCQeasy

A developer wants to add a composite index in Firestore to support a query that filters on two fields: 'status' (equality) and 'createdAt' (range). How should the index be configured?

A.Create a composite index with fields 'status' (ascending) and 'createdAt' (ascending).
B.No index is needed; single-field indexes are automatically created.
C.Create a composite index with fields 'createdAt' (ascending) and 'status' (ascending).
D.Add an index exemption on the 'status' field to force index creation.
AnswerA

This composite index configuration supports equality on 'status' and range on 'createdAt'.

Why this answer

Option A is correct because Firestore requires a composite index when a query combines an equality filter on one field with a range filter on another. The index must list the equality field first ('status') followed by the range field ('createdAt'), with ascending order for both to support the range query efficiently. This matches the Firestore index definition rules for composite indexes.

Exam trap

Cisco often tests the misconception that the order of fields in a composite index does not matter, but Firestore strictly requires the equality field to precede the range field to avoid a full collection scan.

How to eliminate wrong answers

Option B is wrong because single-field indexes are automatically created but cannot satisfy a query that filters on two different fields with different operators (equality and range); a composite index is mandatory. Option C is wrong because placing the range field ('createdAt') before the equality field ('status') would cause the query to fail or perform a full scan, as Firestore requires the equality field to be first in the composite index definition. Option D is wrong because an index exemption is used to exclude a field from automatic indexing, not to force index creation; it would actually prevent the needed index from being used.

Practice this question →
116
MCQmedium

An engineer is managing a Cloud Spanner database and needs to add a new column to an existing table without downtime. Which approach should be used?

A.Export the database, modify the schema, and import using Dataflow
B.Use CREATE INDEX for the new column
C.Drop and recreate the table with the new column
D.Use ALTER TABLE ADD COLUMN statement
AnswerD

ALTER TABLE ADD COLUMN in Spanner is an online, non-blocking operation that can be performed without downtime.

Why this answer

In Cloud Spanner, adding a new column to an existing table without downtime is achieved using the ALTER TABLE ADD COLUMN statement. This DDL operation is applied online, meaning the table remains fully available for reads and writes during the schema change, with no need for data migration or table recreation.

Exam trap

Cisco often tests the misconception that schema changes in distributed databases require data migration or table recreation, but Cloud Spanner's online DDL allows ALTER TABLE to add columns without any downtime or export/import steps.

How to eliminate wrong answers

Option A is wrong because exporting and re-importing the database via Dataflow introduces significant downtime and unnecessary complexity; Cloud Spanner supports online schema changes without data movement. Option B is wrong because CREATE INDEX is used to add an index, not a column; it does not modify the table's schema to include a new column. Option C is wrong because dropping and recreating the table would cause complete downtime and data loss unless the data is first migrated, which is not required for a simple column addition.

Practice this question →
117
Multi-Selectmedium

An organization is using Memorystore for Redis and needs to ensure that when memory usage reaches the maximum, the cache evicts keys based on the least recently used (LRU) algorithm among keys with an expiry set. They also want to require password authentication for client connections. Which two configurations should be applied? (Choose TWO.)

Select 2 answers
A.Configure the AUTH password in the Memorystore instance
B.Set maxmemory-policy to 'allkeys-lru'
C.Enable TLS for encryption
D.Set maxmemory-policy to 'volatile-lru'
E.Enable persistence with AOF
AnswersA, D

AUTH password is set in Memorystore to require authentication.

Why this answer

The eviction policy 'volatile-lru' evicts keys with an expiry set using LRU. AUTH is configured by setting a password via the Redis AUTH command or in the Memorystore instance settings.

Practice this question →
118
MCQhard

A Cloud Spanner database has a table with a primary key and a secondary index. The application frequently queries using a filter on the secondary index column and orders by the primary key. The queries are slow. What should the database administrator do to improve query performance?

A.Increase the number of nodes to improve query throughput
B.Create an interleaved table that mirrors the data
C.Create a covering index using CREATE INDEX with the STORING clause to include the required columns
D.Use ALTER TABLE to add a new index on the filter column
AnswerC

A covering index includes all columns needed for the query, allowing Spanner to avoid accessing the base table, which can improve performance.

Why this answer

Cloud Spanner can use a secondary index to filter, but if the ordering is by the primary key, it may need to sort after fetching. A covering index that includes both the filter column and the primary key (or other required columns) can avoid back-and-forth to the table. Storing the primary key in the index is automatic in Spanner (as it is part of the row), but the index may not be ordered by primary key.

Adding an interleaved table changes the schema. Increasing nodes adds capacity but doesn't fix the query plan. Using a STORING clause to include extra columns is helpful, but the main issue is ordering.

Actually, in Spanner, if you have an index on column A and you order by primary key, Spanner may need to sort. To avoid sorting, you could create a custom index that includes both the filter column and the ordering column (primary key). So option D (create a new index with the filter column and include the primary key as a stored column) might help, but primary key is already included.

The correct answer is to create a covering index that includes all columns needed, so Spanner can avoid accessing the base table. Option B (CREATE INDEX ... STORING ...) is the correct way to create a covering index.

Option C (ALTER TABLE ... ADD INDEX) is not valid syntax. Option A (increase number of nodes) is for throughput, not query optimization.

Practice this question →
119
MCQmedium

A Cloud SQL for PostgreSQL instance is experiencing high read traffic. You need to offload read queries and ensure the solution can survive a regional outage. What should you do?

A.Set up Cloud Memorystore as a cache in front of the database.
B.Increase the machine type of the primary instance to handle the load.
C.Create a read replica in the same region and use it for read queries.
D.Create a cross-region read replica and direct read traffic to it.
AnswerD

Cross-region replica offloads reads and can be promoted for regional failover.

Why this answer

Cross-region read replicas serve read traffic and provide disaster recovery if the primary fails. Creating a cross-region read replica reduces read load and can be promoted if the primary region fails. Option D is correct.

Option A (same-region replica) does not survive a regional outage. Option B (increasing tier) helps performance but not regional failover. Option C (cache) reduces latency but not a full recovery solution.

Practice this question →
120
MCQmedium

A company runs an e-commerce platform on Cloud SQL for PostgreSQL. They need to perform point-in-time recovery (PITR) to recover from a user error that occurred 30 minutes ago. Which configuration is required to enable PITR?

A.Enable automated backups and configure a retention of 1-7 days; PITR uses WAL archiving automatically.
B.Enable binary logging and set a backup retention of 1-7 days.
C.Set up cross-region backup replicas and configure a retention of 1-7 days.
D.Enable PITR by setting the 'pitr_enabled' flag to true in the database flags.
AnswerA

In Cloud SQL for PostgreSQL, PITR is enabled by automated backups with a retention of 1-7 days; WAL archiving is handled automatically.

Practice this question →
121
MCQeasy

You need to monitor the replication lag between a Cloud SQL for MySQL primary instance and its read replica. Which metric should you use to set up an alert?

A.cloudsql.googleapis.com/database/replication/replica_count
B.cloudsql.googleapis.com/database/cpu/utilization
C.cloudsql.googleapis.com/database/memory/utilization
D.cloudsql.googleapis.com/database/replication/replication_lag
AnswerD

This is the correct metric for replication lag.

Why this answer

Cloud SQL exposes a metric 'replication/replication_lag' (or 'cloudsql.googleapis.com/database/replication/replication_lag') that measures the lag in seconds between the primary and replica. This is the correct metric for alerting.

Practice this question →
122
MCQhard

A Memorystore for Redis instance is running out of memory. The application can tolerate some data loss but not crashes. The team wants to ensure the instance remains available without manual intervention. Which eviction policy should they configure?

A.volatile-lru
B.volatile-ttl
C.noeviction
D.allkeys-lru
AnswerD

Correct. This evicts the least recently used keys across all keys, ensuring availability.

Why this answer

Option D (allkeys-lru) is correct because it allows Redis to evict the least recently used keys from the entire keyspace when memory is full, which keeps the instance available without crashing. Since the application can tolerate some data loss but not crashes, this policy ensures memory pressure is relieved automatically, preventing out-of-memory errors that would cause the instance to become unavailable.

Exam trap

Cisco often tests the misconception that volatile policies (like volatile-lru or volatile-ttl) are safer because they only affect keys with TTL, but the trap is that if most keys lack expiration, these policies fail to free memory, leading to crashes—whereas allkeys-lru guarantees eviction across all keys to maintain availability.

How to eliminate wrong answers

Option A (volatile-lru) is wrong because it only evicts keys with an expiration set, leaving keys without TTL untouched; if the majority of data lacks expiration, memory may still fill up and cause instability. Option B (volatile-ttl) is wrong because it evicts keys based on shortest remaining TTL among volatile keys, which is unpredictable and may not free enough memory in time, risking crashes. Option C (noeviction) is wrong because it returns errors on write operations when memory is full, which would cause application crashes or unavailability, directly contradicting the requirement to avoid crashes.

Practice this question →
123
MCQmedium

A company is running a Cloud SQL for PostgreSQL instance for an e-commerce application. They need to enable point-in-time recovery (PITR) with a 7-day retention period. What configuration steps must be taken?

A.Create a cross-region backup replica with a 7-day retention.
B.Enable WAL archiving and configure backup retention to 7 days using gcloud sql instances patch --backup-retention-days 7.
C.Enable binary logging and set backup retention to 7 days.
D.Enable automated backups with a 7-day retention; WAL archiving is automatic.
AnswerB

Correct. WAL archiving is needed for PITR, and backup retention is set via the flag.

Why this answer

Option B is correct because Cloud SQL for PostgreSQL uses Write-Ahead Log (WAL) archiving to enable point-in-time recovery (PITR). You must enable automated backups (which automatically enables WAL archiving) and then set the backup retention period to 7 days using the `gcloud sql instances patch --backup-retention-days 7` command. This ensures that WAL logs are retained for the specified duration, allowing PITR within that window.

Exam trap

Cisco often tests the distinction between database-specific recovery mechanisms—candidates mistakenly apply MySQL binary logging concepts to PostgreSQL, where WAL archiving is the correct mechanism, and overlook the explicit command needed to set the retention period.

How to eliminate wrong answers

Option A is wrong because cross-region backup replicas are used for disaster recovery and high availability, not for enabling PITR; they do not provide the WAL log retention required for point-in-time recovery. Option C is wrong because binary logging is a MySQL/MariaDB concept, not applicable to PostgreSQL; PostgreSQL uses WAL (Write-Ahead Log) for PITR, not binary logs. Option D is wrong because while enabling automated backups is necessary, the statement 'WAL archiving is automatic' is misleading; WAL archiving is automatically enabled only when automated backups are turned on, but the retention period must be explicitly configured via the `--backup-retention-days` flag—simply enabling automated backups with a 7-day retention without the patch command does not guarantee the correct configuration.

Practice this question →
124
Multi-Selectmedium

Which TWO actions are required to set up point-in-time recovery (PITR) for Cloud SQL for MySQL? (Choose 2)

Select 2 answers
A.Enable binary logging.
B.Set the 'log_bin' flag to ON in the database flags.
C.Create a read replica in a different region.
D.Configure a cross-region backup replica.
E.Enable automated backups with a retention period between 1 and 7 days.
AnswersA, E

Binary logging is required for PITR in MySQL to capture point-in-time changes.

Practice this question →
125
MCQmedium

A Cloud Bigtable cluster is currently using HDD storage. The team wants to switch to SSD for better performance. What is the correct approach?

A.Create a new cluster in the same instance with SSD, then delete the old HDD cluster.
B.Use the gcloud bigtable clusters update command with the --storage-type flag.
C.Export the table to Cloud Storage, delete the instance, create a new one with SSD, and import.
D.Delete the existing cluster and recreate it with SSD. Data is retained in the instance.
AnswerA

Correct. A Bigtable instance can have multiple clusters; add a new SSD cluster, replicate data, then remove the HDD cluster.

Why this answer

In Cloud Bigtable, storage type is a property of the cluster, not the instance. You cannot change the storage type of an existing cluster. The correct approach is to add a new cluster with SSD storage to the same instance, then delete the original HDD cluster.

This allows you to migrate without data loss or downtime, as data is replicated across clusters in the same instance.

Exam trap

Cisco often tests the misconception that you can update storage type on an existing cluster or that deleting a cluster preserves data in the instance, but in Cloud Bigtable, storage type is immutable per cluster and data is tied to the cluster's existence.

How to eliminate wrong answers

Option B is wrong because the `gcloud bigtable clusters update` command does not support a `--storage-type` flag; storage type is immutable after cluster creation and cannot be changed via any command. Option C is wrong because it unnecessarily involves exporting to Cloud Storage and recreating the instance, which is complex and risks data loss or extended downtime; Cloud Bigtable supports multiple clusters per instance, making a simple cluster swap possible. Option D is wrong because deleting the cluster also deletes all data stored in that cluster; data is not retained in the instance when the only cluster is removed, as Cloud Bigtable stores data only in clusters.

Practice this question →
126
MCQeasy

A team wants to create a Cloud Spanner database backup and store it in a Cloud Storage bucket for long-term archival. Which method should they use?

A.Use gcloud spanner instances create-backup to create a backup of the instance.
B.Use the gcloud spanner databases backup command to create a backup that resides in Cloud Storage.
C.Take a snapshot of the Spanner instance using Cloud Storage snapshots.
D.Use the gcloud spanner databases export command to export to Cloud Storage.
AnswerB

Correct. Backup creates a full backup in Cloud Storage (Avro + Protobuf) that can be restored.

Why this answer

Cloud Spanner provides database-level backups directly to Cloud Storage in Avro + Protobuf format. Export/import is for migration, not archival backups.

Practice this question →
127
MCQmedium

A Cloud Spanner instance is backing up a 2 TB database daily to Cloud Storage using the built-in backup feature. The compliance team requires the backup to be stored in a specific regional bucket with a retention policy of 14 days. How should the database administrator configure this?

A.Schedule a cron job to copy the backup from Spanner's default location to the regional bucket
B.Use the gcloud spanner databases export command to export the database to a Cloud Storage bucket in the desired region, then set a retention policy on the bucket
C.Use the CREATE BACKUP statement and specify a Cloud Storage bucket in the desired region
D.Use the backup retention period in Spanner's backup settings to keep backups for 14 days
AnswerB

Correct. Export to Cloud Storage allows specifying a regional bucket. Object lifecycle rules can enforce a 14-day retention.

Why this answer

Spanner database backups are stored as managed backups within the Spanner service, not directly as files in Cloud Storage. However, they can be exported to Cloud Storage using the export API. The export can be configured to a specific bucket and region, and object lifecycle rules can enforce retention.

Practice this question →
128
MCQmedium

An application uses Firestore in Native mode. The query filters on two fields: 'status' (string) and 'created_date' (timestamp). The query returns results but the billing shows high document reads. What is the most likely cause?

A.The query is using an inequality filter on 'created_date' which requires a composite index.
B.The query is using 'array-contains' which always scans the entire collection.
C.The 'status' field is not indexed because single-field indexes are not automatic.
D.The query is missing an ORDER BY clause causing a full scan.
AnswerA

Correct. Queries with equality on one field and inequality on another need a composite index to avoid scanning all documents.

Why this answer

In Firestore Native mode, queries that apply an inequality filter (e.g., >=, >, <, !=) on a field automatically require a composite index on both the equality filter field and the inequality filter field to avoid a full collection scan. Without that composite index, Firestore performs a back-end scan of all documents matching the equality filter, then applies the inequality filter in memory, resulting in high document reads. Option A correctly identifies that the inequality filter on 'created_date' is the most likely cause of the excessive reads because it forces Firestore to read and discard many documents that do not satisfy the timestamp condition.

Exam trap

Cisco often tests the misconception that missing ORDER BY or using array-contains causes high reads, when in fact the real culprit is the lack of a composite index for inequality filters combined with equality filters.

How to eliminate wrong answers

Option B is wrong because 'array-contains' does not always scan the entire collection; it can use an automatically created single-field index on the array field, and while it may read more documents than a simple equality filter, it does not inherently cause a full collection scan. Option C is wrong because single-field indexes are automatically created for all fields in Firestore Native mode by default, so 'status' is indexed without manual action. Option D is wrong because missing an ORDER BY clause does not cause a full scan; Firestore can still use indexes to satisfy the filter conditions, and ORDER BY only affects the ordering of results, not the number of documents read.

Practice this question →
129
Multi-Selecthard

A team manages a Cloud Spanner database and needs to perform a schema change to add a new column to an existing table and create a secondary index. They want to avoid downtime and ensure the changes are applied without blocking reads or writes. Which two statements are correct about making these changes in Spanner? (Choose TWO.)

Select 2 answers
A.The CREATE INDEX statement will block reads on the table during index creation
B.Indexes can only be created as unique indexes
C.The ALTER TABLE statement to add a column is non-blocking and can be executed using gcloud spanner databases ddl update
D.Both ALTER TABLE and CREATE INDEX can be submitted together in a single DDL batch
E.To create an index, you must first export and re-import the data
AnswersC, D

Spanner DDL changes are online and non-blocking.

Why this answer

In Cloud Spanner, both ALTER TABLE (to add columns) and CREATE INDEX are online, non-blocking operations. They can be run via DDL statements in the gcloud CLI or console. Indexes can be created as UNIQUE to enforce uniqueness.

Practice this question →
130
MCQeasy

A company is using Cloud SQL and wants to automatically increase storage when disk usage reaches a threshold. What should they configure?

A.Enable 'auto-storage increase' in the instance settings.
B.Use Active Assist recommendations to manually resize.
C.Set up a Cloud Monitoring alert to manually increase storage when usage exceeds 80%.
D.Configure a Cloud Function to resize the disk via API when threshold is reached.
AnswerA

Correct. This setting automatically increases storage.

Why this answer

Cloud SQL provides a built-in 'auto-storage increase' setting that, when enabled, automatically increases the instance's storage capacity when disk usage reaches a predefined threshold (typically 90% or when free space drops below a certain amount). This eliminates the need for manual intervention or custom automation, ensuring high availability and preventing out-of-disk errors.

Exam trap

The trap here is that candidates may over-engineer a solution (e.g., Cloud Functions or Monitoring alerts) when a simple, built-in configuration option exists, or they may confuse Active Assist recommendations with automated actions.

How to eliminate wrong answers

Option B is wrong because Active Assist provides recommendations for optimization (e.g., idle resources, underutilized instances) but does not automatically resize storage; it only suggests manual actions. Option C is wrong because setting up a Cloud Monitoring alert to manually increase storage still requires human intervention, which defeats the purpose of automatic scaling and introduces risk of downtime if the alert is missed. Option D is wrong because while a Cloud Function could theoretically resize the disk via API, this approach is unnecessarily complex, introduces custom code maintenance, and is not a native Cloud SQL feature; the built-in 'auto-storage increase' is the recommended and simpler solution.

Practice this question →
131
MCQmedium

A company is using Cloud SQL for PostgreSQL and needs to perform point-in-time recovery (PITR) to recover from a logical error that occurred 30 minutes ago. They have already configured automated backups. What additional configuration is required?

A.Create a cross-region backup replica to enable PITR.
B.Set the 'transaction log retention' to a value between 1 and 7 days.
C.Enable binary logging on the instance.
D.Increase the storage size to accommodate logs.
AnswerB

WAL archiving is controlled by this setting for PostgreSQL instances.

Why this answer

Cloud SQL PITR requires write-ahead log (WAL) archiving, which is enabled by setting the 'transaction log retention' in days (1-7). Automated backups alone do not capture continuous transaction logs.

Practice this question →
132
MCQhard

A Bigtable instance is experiencing high latency and uneven load distribution. The operations team suspects a hot spot. Which tool should they use to identify the hot spot, and what action can they take to mitigate it?

A.Use Key Visualiser to identify the hot row/key; then redesign the row key to distribute load.
B.Use 'gcloud bigtable hot-spots list' command; then split the hot table into multiple tables.
C.Use Cloud Monitoring to check CPU utilisation; then add more nodes to the cluster.
D.Use the Bigtable admin console to view table statistics; then change the storage type from HDD to SSD.
AnswerA

Key Visualiser shows access patterns and hot spots. Redesigning row keys (e.g., salting) spreads the load.

Why this answer

Key Visualizer is the correct tool for identifying hot spots in Cloud Bigtable because it provides a heatmap of row key access patterns, allowing you to pinpoint specific rows or key ranges causing uneven load. Once identified, redesigning the row key (e.g., by salting or reversing keys) distributes writes and reads across nodes, mitigating the hot spot without requiring manual table splits or storage changes.

Exam trap

Cisco often tests the misconception that monitoring CPU or adding nodes solves hot spots, but the trap here is that hot spots are a data design issue, not a capacity issue—only Key Visualizer and key redesign address the root cause.

How to eliminate wrong answers

Option B is wrong because 'gcloud bigtable hot-spots list' is not a valid gcloud command; Bigtable does not expose a CLI command for listing hot spots, and splitting a hot table into multiple tables does not address the root cause of a hot row key—it only creates administrative overhead. Option C is wrong because Cloud Monitoring can show CPU utilization but cannot identify the specific row key causing the hot spot; adding more nodes may temporarily reduce latency but does not fix the underlying data access pattern, and the hot spot will persist. Option D is wrong because the Bigtable admin console shows table-level statistics but not per-key access patterns, and changing storage type from HDD to SSD improves overall performance but does not resolve a hot spot caused by a skewed key distribution.

Practice this question →
133
MCQmedium

A company uses Cloud Spanner and wants to export a database for long-term archival. The export must include the schema in a portable format. Which export option should they choose?

A.Manually run SELECT statements to export data and DESCRIBE commands for schema.
B.Use the Spanner migration tool to export to a SQL dump file.
C.Create a database-level backup from the Cloud Console; it will export data and schema as Avro + Protobuf.
D.Use gcloud spanner databases export with the --async flag to export to a Cloud Storage bucket in Avro format.
AnswerC

Spanner backups export data as Avro and schema as a Protobuf file, which is portable.

Why this answer

Spanner database backups are stored in Cloud Storage as Avro files with a Protobuf schema file, preserving both data and schema.

Practice this question →
134
Multi-Selectmedium

A gaming company uses Cloud Spanner for a global leaderboard. They need to add a column to an existing table and create a secondary index on that column. The database must remain fully available during these changes. Which THREE statements are true?

Select 3 answers
A.The new column cannot be added if the table has existing data.
B.The new column must have a default value if it is defined as NOT NULL.
C.CREATE INDEX will block writes on the table until the index is built.
D.ALTER TABLE can be executed while the database is serving traffic.
E.The DDL statements can be submitted together in a single ALTER DATABASE statement.
AnswersB, D, E

Adding a NOT NULL column without default requires a table lock; with a default it is online.

Why this answer

Option B is correct because in Cloud Spanner, when adding a NOT NULL column to an existing table, the column must have a DEFAULT value. This ensures that existing rows, which will be populated with the default value, satisfy the NOT NULL constraint without requiring a full table scan or blocking writes.

Exam trap

Cisco often tests the misconception that schema changes in distributed databases require downtime or blocking, but Cloud Spanner's online DDL operations are designed to maintain full availability during both ALTER TABLE and CREATE INDEX.

Practice this question →
135
MCQmedium

A company uses Firestore in Native mode and has a collection with many documents containing array fields. They want to index the array values to support queries like 'array-contains'. What is the correct approach?

A.Create an index exemption for the array field to enable indexing
B.Switch to Datastore mode and configure indexes manually
C.Create a composite index that includes the array field
D.No additional index configuration is required; arrays are automatically indexed
AnswerD

In Firestore Native mode, all fields including arrays are automatically indexed, supporting array-contains queries.

Why this answer

Firestore automatically creates single-field indexes for scalar values. For array fields, to support array-contains queries, you must create an index exemption to include the array field. Actually, Firestore automatically creates an index for array fields as well, but for queries with array-contains, you need to explicitly create an index exemption to include the array.

Wait, the domain says: 'index exemptions (for arrays and maps)'. The default behavior: Firestore automatically creates a single-field index for each field, including arrays. However, for arrays, the index automatically includes the array values.

So no exemption needed. Exemptions are to exclude fields from automatic indexing. So if they want to query array-contains, they don't need to do anything special if the field is indexed.

But the domain says 'index exemptions (for arrays and maps)' which might mean that arrays and maps are exempted from automatic indexing? Actually, in Firestore, automatic indexing covers all fields including arrays and maps. But you can create index exemptions to exclude certain fields from indexing. For arrays, to use array-contains, the field must be indexed.

Since it's automatically indexed, no action is needed. However, the domain says 'index exemptions (for arrays and maps)' — that likely means that arrays and maps are not automatically indexed in Datastore mode? Let me check: In Native mode, all fields are automatically indexed. In Datastore mode, you must define indexes manually.

The question says 'Firestore in Native mode', so automatic indexing applies. So the correct answer is that no additional configuration is needed. Option B says 'Create an index exemption for the array field' — that would exclude it from indexing, which is wrong.

Option C 'Create a composite index' is not needed for a single array-contains query. Option D 'Use Datastore mode' is not necessary. So A is correct.

But wait, the domain mentions 'single-field indexes (automatic), composite indexes (manual), index exemptions (for arrays and maps)'. This suggests that arrays and maps are exempted from automatic indexing by default? Actually, in Firestore Native mode, arrays are indexed as composite indexes? I recall that Firestore automatically indexes each field, including arrays. For array-contains queries, the array field must be indexed; it is by default.

So no action needed. However, some sources say that array fields are not indexed automatically. I think the correct answer per GCP documentation is: In Native mode, all fields are automatically indexed.

For arrays, the index includes each element. So no action required. So I'll go with A.

Practice this question →
136
MCQhard

A company uses Memorystore for Redis with Standard Tier (replication) and needs to ensure data durability in case of a zone failure. They also need to scale read throughput beyond a single instance. What should they do?

A.Create a cross-region replica and use it for read traffic.
B.Upgrade to a larger machine type with more memory.
C.Enable persistence using AOF and configure a backup schedule.
D.Migrate to Redis Cluster with 3+ shards.
AnswerD

Redis Cluster provides horizontal scaling by sharding data, and with multiple shards across zones, it improves both availability and read throughput.

Why this answer

Memorystore for Redis Standard Tier provides cross-zone replication for high availability. To scale read throughput, they can use Redis Cluster (which shards data across multiple shards) or create read replicas. However, Memorystore does not support read replicas for Redis; instead, Redis Cluster provides horizontal scalability and high availability.

Upgrading to a larger instance scales vertically but not read throughput horizontally. Persistence is not natively supported in Memorystore.

Practice this question →
137
MCQmedium

A company uses Firestore in Datastore mode. They need to create a composite index for a query that filters on two properties. The query is already running and returning an error that an index is required. What is the correct way to create this index?

A.Create the index using the gcloud datastore indexes create command with a YAML file.
B.Modify the query to use a single filter to avoid needing a composite index.
C.Enable the 'auto-index' feature in the Datastore console.
D.The index will be created automatically based on the query pattern.
AnswerA

Composite indexes are manually defined via a YAML file and created with gcloud.

Why this answer

Option A is correct because in Firestore (Datastore mode), composite indexes must be explicitly created before they can be used by queries that filter on multiple properties. The `gcloud datastore indexes create` command with a YAML file is the standard method to define and deploy these indexes, as the Datastore mode does not automatically create composite indexes from query patterns.

Exam trap

Cisco often tests the misconception that Datastore mode automatically creates composite indexes from query patterns, similar to Firestore Native mode's automatic index creation, but in Datastore mode, composite indexes must be manually defined.

How to eliminate wrong answers

Option B is wrong because modifying the query to use a single filter would change the query's logic and may not return the desired results; the requirement is to support the existing multi-property query, not to alter it. Option C is wrong because there is no 'auto-index' feature in the Datastore console; Firestore in Datastore mode only provides automatic single-property indexes, not composite indexes. Option D is wrong because composite indexes in Datastore mode are not created automatically based on query patterns; they must be explicitly defined and deployed by the user.

Practice this question →
138
MCQeasy

A Cloud SQL for MySQL instance is running low on disk space. You need to increase the storage without downtime. What is the correct approach?

A.Create a new instance with larger storage and migrate the data using mysqldump.
B.Enable automatic storage increase; resize manually is not possible.
C.Stop the instance, resize the attached persistent disk, then restart.
D.Use the gcloud command to resize the storage; the operation is performed online.
AnswerD

Correct. gcloud sql instances patch --storage-size NEW_SIZE resizes online.

Why this answer

Option D is correct because Cloud SQL for MySQL supports online storage resizing using the `gcloud sql instances patch` command or the Google Cloud Console, which allows you to increase the storage capacity without any downtime. The operation is performed while the instance remains available, and the underlying persistent disk is resized live, leveraging Google Cloud's live resize capability for Cloud SQL instances.

Exam trap

The trap here is that candidates may assume that any disk resize requires stopping the instance (as with traditional on-premises or some cloud VMs), but Cloud SQL's managed service allows online resizing without downtime, which is a key differentiator tested in the PCDOE exam.

How to eliminate wrong answers

Option A is wrong because creating a new instance and migrating data with mysqldump would require significant downtime during the dump and restore process, and it is unnecessarily complex when a simple online resize is available. Option B is wrong because while automatic storage increase can be enabled, manual resizing is also possible and is the direct solution to the problem; automatic increase only triggers when a threshold is reached, not for immediate manual intervention. Option C is wrong because stopping the instance to resize the disk would cause downtime, which contradicts the requirement to increase storage without downtime; Cloud SQL does not require stopping the instance for storage resizing.

Practice this question →
139
MCQhard

You need to set up disaster recovery for a Cloud SQL for PostgreSQL instance. The primary instance is in us-central1, and you want a standby in us-west1 that can be promoted to a standalone instance during a regional outage. The solution must minimize data loss and recovery time. Which approach should you take?

A.Configure cross-region automated backups with a retention of 7 days. In the event of a disaster, restore the latest backup to a new instance in us-west1.
B.Set up an on-premise PostgreSQL instance and configure streaming replication from Cloud SQL to the on-premise instance.
C.Create a cross-region read replica in us-west1. During a disaster, promote the replica to a standalone instance.
D.Use gcloud sql instances create with a backup configuration pointing to us-west1, but this does not create a live standby.
AnswerC

A cross-region read replica is the best option: it stays up-to-date (asynchronously) and can be promoted quickly.

Why this answer

Cross-region read replicas in Cloud SQL for PostgreSQL use synchronous replication (for regional replicas, it's asynchronous across regions, but still the best option for DR). Creating a cross-region read replica in us-west1 allows it to be promoted to a standalone instance in DR scenarios. Cross-region backups are point-in-time backups, not a live standby.

External replication is not managed by Cloud SQL.

Practice this question →
140
MCQeasy

A company has a Cloud SQL for PostgreSQL instance and wants to enable point-in-time recovery (PITR) with a recovery window of 5 days. Which configuration step is required?

A.Enable binary logging on the instance
B.Configure a Cloud Storage bucket for WAL archiving
C.Create a cross-region backup replica for disaster recovery
D.Enable automated backups and set backup retention to 5 days
AnswerD

Automated backups must be enabled with a retention period of 5 days to support PITR within that window.

Why this answer

PITR in Cloud SQL for PostgreSQL uses Write-Ahead Logging (WAL) archives. You must enable automated backups and set the backup retention to the desired recovery window (1-7 days). Binary logging is for MySQL, not PostgreSQL.

Cloud Storage archiving is separate. WAL archiving is automatically managed when automated backups are enabled with a retention period.

Practice this question →
141
Multi-Selectmedium

A Cloud SQL for MySQL instance is being used for a production application. The team wants to implement a disaster recovery plan that can recover from a regional outage with minimal data loss and automatic failover. Which three steps should they take? (Choose THREE.)

Select 3 answers
A.Enable automated backups with a suitable retention period.
B.Create a read replica in the same region.
C.Increase the storage size to accommodate future growth.
D.Create a cross-region read replica and configure it for failover.
E.Enable binary logging (log_bin) for point-in-time recovery.
AnswersA, D, E

Backups are essential for recovery.

Why this answer

Option A is correct because automated backups in Cloud SQL for MySQL provide a baseline for disaster recovery by creating daily backups that can be restored to a new instance. With a suitable retention period, you can recover from data corruption or accidental deletion, though backups alone do not provide automatic failover or minimal data loss during a regional outage.

Exam trap

The trap here is that candidates confuse read replicas in the same region as providing disaster recovery for regional outages, but they only offer read scaling and high availability within the same region, not cross-region failover.

Practice this question →
142
MCQhard

A company has a Firestore database in Native mode. They need to run a query that filters on two fields (status and date) and orders by date. The query is slow and returns an error that a matching index is missing. What must the engineer do to resolve this?

A.Enable single-field indexes for both fields; Firestore will automatically use them.
B.Rewrite the query using 'IN' clauses to avoid the need for a composite index.
C.Create a composite index on status and date in the Firebase Console or using gcloud.
D.Change the database to Datastore mode, which does not require indexes.
AnswerC

Firestore in Native mode requires a composite index for queries that filter on multiple fields or combine filters with ordering. The index must include both fields.

Why this answer

Option C is correct because Firestore requires a composite index on both the equality filter field (status) and the order field (date) when a query uses equality filters on one field and an order on another. Without this composite index, the query cannot be executed efficiently and returns an error. Creating the composite index via the Firebase Console or gcloud CLI resolves the issue.

Exam trap

Cisco often tests the misconception that single-field indexes are automatically combined for multi-field queries, or that using 'IN' clauses bypasses indexing requirements, when in fact composite indexes are mandatory for such queries.

How to eliminate wrong answers

Option A is wrong because single-field indexes are insufficient for queries that filter on one field and order by another; Firestore does not automatically combine them to satisfy the query. Option B is wrong because rewriting the query with 'IN' clauses does not eliminate the need for a composite index; it still requires an index on the field being ordered. Option D is wrong because switching to Datastore mode is unnecessary and does not solve the indexing requirement; Datastore mode also requires composite indexes for similar queries.

Practice this question →
143
MCQmedium

Your Memorystore for Redis instance is used as a session store for a web application. You need to ensure that session data is not lost during a node failure. What should you do?

A.Use a Basic Tier instance with a large maxmemory setting.
B.Configure the instance as Standard Tier (with replication) and schedule periodic exports to Cloud Storage.
C.Enable persistence by setting the 'persistence' parameter to 'rdb' in the instance configuration.
D.Enable AOF persistence in the Memorystore instance.
AnswerB

Standard Tier provides high availability via replication, and exports to Cloud Storage provide persistence.

Why this answer

Memorystore for Redis does not provide native persistence. To achieve high availability and durability, you can use a cross-region replica (Standard Tier with replication) or take regular snapshots to Cloud Storage. The Standard Tier with replication provides in-memory replication across zones; in case of a node failure, the replica can take over.

However, data is still not persisted to disk. For durability, you need to export data to Cloud Storage periodically.

Practice this question →
144
MCQmedium

Your team manages a Cloud SQL for MySQL instance used by a critical application. You need to ensure the instance is recoverable to any point within the last 4 days, with a Recovery Point Objective (RPO) of under 5 minutes. What configuration steps are required?

A.Enable automated backups and set the backup retention to 4 days. Binary logging is not required because automated backups already capture all changes.
B.Enable binary logging and set the binary log retention to 4 days. Automated backups are optional and not needed for PITR.
C.Create an on-demand backup daily and set binary log retention to 4 days. This provides the same RPO as automated backups with binary logging.
D.Enable automated backups and binary logging. Set the transaction log retention period to 4 days.
AnswerD

Automated backups plus binary logging (with appropriate retention) enables PITR with a 4-day window.

Why this answer

Point-in-time recovery (PITR) in Cloud SQL for MySQL requires binary logging to be enabled, which automatically turns on automated backups. The retention period for binary logs is set via the transactionLogRetentionDays setting, which can be 1-7 days. Enabling automated backups alone does not provide PITR; binary logging is necessary.

The retention period of 4 days satisfies the 4-day recovery window. Automated backups are already required for PITR, so option B is the complete answer.

Practice this question →
145
MCQhard

A Bigtable cluster is configured with SSD storage. The team needs to reduce costs by switching to HDD storage while maintaining the same cluster ID and node count. What is the correct approach?

A.Edit the cluster settings and change the storage type from SSD to HDD.
B.Delete the cluster and recreate it with HDD storage.
C.Create a new Bigtable instance with HDD storage, then use a table export/import to move data.
D.Use gcloud bigtable instances update to change the storage type.
AnswerC

A new cluster with HDD storage is required; data can be migrated via export/import.

Why this answer

Bigtable does not allow in-place modification of storage type (SSD vs. HDD) on an existing cluster. To switch storage, you must create a new instance with HDD storage and migrate data using export/import (e.g., via Cloud Storage and Dataflow).

Option C correctly describes this process, preserving the cluster ID and node count by recreating the instance with the same configuration but HDD storage.

Exam trap

Cisco often tests the immutability of Bigtable storage type and the misconception that you can simply update it via the console or CLI, leading candidates to choose options A or D.

How to eliminate wrong answers

Option A is wrong because Bigtable does not support editing the storage type of an existing cluster; the storage type is immutable after creation. Option B is wrong because deleting and recreating the cluster would lose the cluster ID and require manual data migration, but the question requires maintaining the same cluster ID, which is not possible with a delete/recreate approach. Option D is wrong because the gcloud bigtable instances update command cannot change the storage type; it only updates display names or labels, not the underlying storage medium.

Practice this question →
146
MCQmedium

A retail company uses Cloud SQL for MySQL with point-in-time recovery (PITR) enabled. They need to recover the database to a specific second from 2 days ago. The backup retention is set to 7 days. Which action should the engineer take to perform the recovery?

A.Use gcloud sql instances restore-backup with the --point-in-time flag and specify the timestamp, restoring to a new instance.
B.Use mysqldump to export the binary logs and replay them from the backup.
C.Use gcloud sql instances restore-backup with the --async flag and specify the timestamp.
D.Create an on-demand backup from the source instance and restore that backup to a new instance.
AnswerA

This is the correct method: using --point-in-time and restoring to a new instance (since same-instance restore is not supported for PITR).

Why this answer

Point-in-time recovery (PITR) in Cloud SQL uses binary logs to recover to any time within the configured retention period. The engineer can restore to a new instance using gcloud sql instances restore-backup with the --point-in-time flag and specify the exact timestamp. Restoring to the same instance is not supported; only to a new instance.

The --async flag is optional but not required. The recovery is not limited to full backups; binary logs allow precise time recovery.

Practice this question →
147
Multi-Selectmedium

A Cloud SQL for MySQL instance has a read replica in a different region. The team wants to monitor replication lag and receive alerts if lag exceeds 60 seconds. Which two steps should they take? (Choose TWO.)

Select 2 answers
A.Create a Cloud Monitoring alerting policy with a condition on 'cloudsql.googleapis.com/database/replication/replica_lag' with threshold >60s.
B.Configure a Cloud Function to query the replica status every minute.
C.Set up a Cloud Scheduler job to run a query on the replica to check lag.
D.Promote the replica to standalone if lag exceeds 60 seconds.
E.Enable the 'replication_lag' metric in Cloud SQL monitoring.
AnswersA, E

This is the correct metric and threshold for alerting on lag.

Why this answer

The replication_lag metric is available in Cloud Monitoring. An alerting policy based on this metric with a threshold of 60 seconds will trigger notifications when lag exceeds that value.

Practice this question →
148
Multi-Selecthard

A company is migrating on-premises PostgreSQL databases to Cloud SQL. They need to minimize downtime and ensure data consistency. Which THREE steps should they follow? (Choose 3)

Select 3 answers
A.Use Database Migration Service to set up continuous replication from the on-premises database.
B.Export the on-premises database to a dump file and import it into Cloud SQL.
C.Manually sync data using a custom script with pg_dump and pg_restore.
D.After replication is caught up, promote the Cloud SQL instance to make it the primary.
E.Create a Cloud SQL for PostgreSQL instance with the same version as the source.
AnswersA, D, E

Correct. DMS supports homogeneous PostgreSQL migrations with minimal downtime.

Why this answer

A typical migration uses Database Migration Service (DMS) with continuous replication for minimal downtime. Setting up replication and then promoting the Cloud SQL instance is standard.

Practice this question →
149
MCQeasy

You are monitoring Cloud Bigtable replication lag. Which metric should you use to determine if replicas are up to date, and what consistency level is typical for Bigtable replication?

A.Use 'replication_lag' metric; consistency is eventually consistent.
B.Use 'cluster_lag' metric; consistency is read-your-writes consistent.
C.Use 'replica_lag' metric; consistency is strongly consistent.
D.Use 'replication_lag' metric; consistency is strongly consistent.
AnswerA

Bigtable replication is asynchronous and eventually consistent; the 'replication_lag' metric measures the delay.

Practice this question →
150
MCQmedium

A company needs to store petabytes of time-series IoT sensor data and query it with single-digit millisecond latency at millions of reads per second. The data has a simple key-value structure with timestamps. Which Google Cloud database is MOST appropriate?

A.Firestore
B.Cloud Bigtable
C.Cloud Spanner
D.BigQuery
AnswerB

Bigtable is the correct choice: wide-column NoSQL, designed for time-series and IoT workloads, single-digit ms latency, and scales to millions of QPS with additional nodes.

Why this answer

Cloud Bigtable is designed for exactly this use case — petabyte-scale, low-latency (single-digit ms), high-throughput NoSQL storage for time-series, IoT, and financial data. It scales horizontally by adding nodes. BigQuery is optimised for analytics (seconds-to-minutes latency), Cloud SQL is for OLTP (limited to tens of thousands of QPS), and Firestore is for document data with hierarchical structure.

Practice this question →
← PreviousPage 2 of 3 · 175 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Pcdoe Manage Databases questions.

Start 20-question session
CCNA Pcdoe Manage Databases Questions — Page 2 of 3 | Courseiva