Question 220
A bank needs strongly consistent relational transactions with horizontal scale across regions. Which approach should be selected?
- Choose Cloud SQL with a supported relational engine
- Choose BigQuery
- Choose Spanner with an appropriate multi-region instance configuration
- Enable and configure Cloud SQL automated backups
- Choose Firestore in a suitable supported mode
Explanation
Correct Answer
C:Spanner combines relational semantics and distributed horizontal scaling. Multi-region configurations can support high availability and strong transactional consistency.
Incorrect Answers
A:Select this when the goal is to host supported managed relational database engines. Here the decisive requirement is to scale a globally distributed transactional database, and that outcome is not achieved by this action.
B:The result of this choice would be to query large analytical datasets without managing servers. The requested outcome, to scale a globally distributed transactional database, is handled at a different layer or through another operation.
D:In a workflow for cloud sql initial deployment, it can schedule managed relational backups; This question instead asks how to scale a globally distributed transactional database; substituting the former action would leave that distinct technical requirement unmet.
E:Administrators use it to store application documents with managed synchronization, rather than to scale a globally distributed transactional database. Applying it would change the wrong component of this deployment.
Question 221
A telemetry application needs single-digit-millisecond access to massive rows indexed by key, with wide-column patterns. What is the most direct solution?
- Choose Bigtable
- Choose Memorystore with a supported engine
- Choose Pub/Sub
- Choose Dataflow
Explanation
Correct Answer
A:Bigtable is a wide-column database optimized for large-scale key-oriented access and throughput. It is not a general-purpose relational database with joins.
Incorrect Answers
B:Using this action would cache application values in memory, not support high-throughput time-series lookup. Its function is different from the specific change described in the scenario.
C:This setting would transport asynchronous messages. That behavior does not establish the requested ability to support high-throughput time-series lookup; it addresses an adjacent concern instead.
D:This choice is useful to execute managed data transformation pipelines. The stated task is to support high-throughput time-series lookup, which requires a different mechanism or permission scope.
Question 222
An API needs a low-latency in-memory cache for ephemeral lookup results. Which implementation matches this requirement?
- Choose Bigtable
- Choose Pub/Sub
- Choose Dataflow
- Choose Cloud SQL with a supported relational engine
- Choose Memorystore with a supported engine
Explanation
Correct Answer
E:Memorystore provides managed in-memory data services for caching and compatible use cases. Cached values should not be mistaken for the system of record.
Incorrect Answers
A:While this can serve large keyed wide-column datasets, the present task requires an action to reduce repetitive backend reads. This operation does not supply the behavior described in the requirements.
B:Administrators use it to transport asynchronous messages, rather than to reduce repetitive backend reads. Applying it would change the wrong component of this deployment.
C:Its purpose is to execute managed data transformation pipelines. That distinction matters: the scenario calls for an action to reduce repetitive backend reads, not this separate configuration task.
D:The result of this choice would be to host supported managed relational database engines. The requested outcome, to reduce repetitive backend reads, is handled at a different layer or through another operation.
Question 223
A data scientist needs to process batch and streaming transformations on large datasets. What should the administrator do?
- Choose Dataflow
- Choose Memorystore with a supported engine
- Choose Pub/Sub
- Choose BigQuery
- Choose Bigtable
Explanation
Correct Answer
A:Dataflow runs managed Apache Beam pipelines for stream and batch data processing. It transforms data rather than acting as the persistent transactional database.
Incorrect Answers
B:Select this when the goal is to cache application values in memory. Here the decisive requirement is to process streaming and batch records, and that outcome is not achieved by this action.
C:This choice is useful to transport asynchronous messages. The stated task is to process streaming and batch records, which requires a different mechanism or permission scope.
D:In a workflow for database workload selection, it can query large analytical datasets without managing servers; This question instead asks how to process streaming and batch records; substituting the former action would leave that distinct technical requirement unmet.
E:The tool can serve large keyed wide-column datasets, but it cannot be substituted for the capability needed to process streaming and batch records. Its operational effect is not equivalent.
Question 224
A producer and consumer require decoupled asynchronous event delivery. Which choice provides the required behavior?
- Choose Dataflow
- Choose Bigtable
- Implement an Apache Beam streaming pipeline on Dataflow
- Choose Memorystore with a supported engine
- Choose Pub/Sub
Explanation
Correct Answer
E:Pub/Sub provides durable messaging between publishers and subscribers. It handles event distribution while subscribers own business processing and storage.
Incorrect Answers
A:Its purpose is to execute managed data transformation pipelines. That distinction matters: the scenario calls for an action to connect independent event producers and workers, not this separate configuration task.
B:While this can serve large keyed wide-column datasets, the present task requires an action to connect independent event producers and workers. This operation does not supply the behavior described in the requirements.
C:The choice is aimed at a different purpose: to aggregate streaming records; Even if it can perform stream-window computations, that would not accomplish the stated requirement to connect independent event producers and workers.
D:This approach can cache application values in memory. The requirement is to connect independent event producers and workers, so it controls a different part of the workflow and leaves that result unaddressed.
Question 225
A team compares AlloyDB for PostgreSQL against Cloud SQL before migrating a PostgreSQL application. Which TWO statements are technically accurate? (Choose TWO.)
- Cloud SQL queries must always be expressed using BigQuery's serverless warehouse SQL API
- AlloyDB is a replacement for an existing SQL Server database without application or schema changes
- Cloud SQL offers managed PostgreSQL deployments alongside other supported relational engines
- AlloyDB is a managed, PostgreSQL-compatible database option that may need workload compatibility validation
Explanation
Correct Answers
C:Cloud SQL supports familiar relational engines, including PostgreSQL, with managed administration features. It remains a distinct product with its own sizing and availability model.
D:AlloyDB supports PostgreSQL-compatible workloads but is not simply an unchanged server binary. Extensions, operational behavior, and migration compatibility should be checked.
Incorrect Answers
A:Cloud SQL is a managed relational database service using its chosen database engine. It does not require BigQuery's query execution model for ordinary OLTP queries.
B:AlloyDB targets PostgreSQL compatibility rather than SQL Server compatibility. Moving from SQL Server would require explicit database and application migration planning.
Question 226
A SQL Server application must retain its database engine with managed backups and patches. What is the most direct solution?
- Choose Cloud SQL for SQL Server where supported
- Choose Cloud SQL for MySQL
- Choose Spanner with the appropriate SQL dialect and instance configuration
- Evaluate AlloyDB for PostgreSQL
Explanation
Correct Answer
A:Cloud SQL offers managed Microsoft SQL Server instances in supported editions and regions. It avoids rewriting the application into a different database API.
Incorrect Answers
B:This choice is useful to operate a managed MySQL database. The stated task is to migrate a SQL Server database without switching engines, which requires a different mechanism or permission scope.
C:Using this action would scale relational transactions horizontally, not migrate a SQL Server database without switching engines. Its function is different from the specific change described in the scenario.
D:This approach can run performance-oriented PostgreSQL-compatible workloads. The requirement is to migrate a SQL Server database without switching engines, so it controls a different part of the workflow and leaves that result unaddressed.
Question 227
A database requirement emphasizes familiar open-source MySQL behavior and moderate instance-based sizing. Which implementation matches this requirement?
- Evaluate AlloyDB for PostgreSQL
- Choose Spanner with the appropriate SQL dialect and instance configuration
- Choose Cloud SQL for SQL Server where supported
- Choose Cloud SQL for MySQL
- Enable and configure Cloud SQL automated backups
Explanation
Correct Answer
D:Cloud SQL supports managed MySQL instances with automated operations. It is a conventional relational choice, not a document store or warehouse.
Incorrect Answers
A:The result of this choice would be to run performance-oriented PostgreSQL-compatible workloads. The requested outcome, to retain MySQL application compatibility, is handled at a different layer or through another operation.
B:Administrators use it to scale relational transactions horizontally, rather than to retain MySQL application compatibility. Applying it would change the wrong component of this deployment.
C:This mechanism is intended to host managed Microsoft SQL Server. It does not implement the required action to retain MySQL application compatibility, even though both are relevant to the same general service.
E:The choice is aimed at a different purpose: to protect a Cloud SQL database against logical loss; Even if it can schedule managed relational backups, that would not accomplish the stated requirement to retain MySQL application compatibility.
Question 228
A distributed SQL application has selected Spanner and must use its PostgreSQL interface rather than the GoogleSQL dialect. At what point should the team make the dialect choice?
- Change the Spanner instance's machine family to PostgreSQL mode
- Convert the existing Spanner database's GoogleSQL dialect in place by changing a session flag
- Choose the PostgreSQL dialect when creating the Spanner database, then use compatible clients and SQL
- Configure a Cloud SQL PostgreSQL read replica and treat it as the Spanner SQL endpoint
Explanation
Correct Answer
C:Spanner's database dialect is a database-creation decision. The PostgreSQL interface supports a defined subset of PostgreSQL language and tools, so application compatibility still needs review.
Incorrect Answers
A:A Spanner instance is not a Compute Engine VM, and a machine-family toggle does not set SQL dialect. SQL dialect is configured for the database rather than the instance hardware.
B:A session setting cannot convert the persistent database dialect. The application must select the required dialect at database creation and plan migrations separately.
D:Cloud SQL replicas replicate within supported Cloud SQL arrangements. They do not act as a PostgreSQL-dialect interface to a Spanner database.
Question 229
An enterprise has a Kafka-native event ecosystem and wants a managed compatible Kafka service. Which solution should be used?
- Use Google Cloud Managed Service for Apache Kafka
- Implement an Apache Beam streaming pipeline on Dataflow
- Use Storage Transfer Service for a supported source and destination
- Use Pub/Sub topics with separate subscriptions
Explanation
Correct Answer
A:The managed Kafka service supports Kafka-based streaming use cases. It preserves the Kafka ecosystem rather than requiring all clients to adopt Pub/Sub semantics.
Incorrect Answers
B:Administrators use it to perform stream-window computations, rather than to host Kafka-native producers and consumers. Applying it would change the wrong component of this deployment.
C:Its purpose is to orchestrate bulk storage data transfer. That distinction matters: the scenario calls for an action to host Kafka-native producers and consumers, not this separate configuration task.
D:This approach can fan out events to independent subscribers. The requirement is to host Kafka-native producers and consumers, so it controls a different part of the workflow and leaves that result unaddressed.
Question 230
A Pub/Sub pull subscription repeatedly receives a message that its consumer cannot process. Engineers want the message sent to a separate topic after the configured delivery-attempt limit. Which feature should they configure?
- Enable message ordering on the subscription
- Configure a subscription dead-letter topic with its delivery-attempt policy and required Pub/Sub service-agent permissions
- Set the topic's message-retention period to one minute
- Create a second unrelated subscription on the source topic and wait for failed messages to move automatically
Explanation
Correct Answer
B:Dead-letter topics provide a destination for messages that cannot be delivered successfully after the configured number of attempts. The subscription and associated service-agent permissions must be set up correctly.
Incorrect Answers
A:Ordering controls delivery sequence for messages with the same ordering key. It does not redirect persistently undeliverable messages to a separate topic.
C:Retention governs how long messages are retained for eligible subscriptions. It is not a dead-letter routing rule and can instead increase the risk of lost processing opportunities.
D:Independent subscriptions each receive their own message delivery stream. They do not automatically receive only messages that exceeded another subscription's retry limit.