Home Microsoft Exams Google Cloud Exams

Loading page

Curious about new developments and updates? Follow our social media.

Get a free certification question every week.

Microsoft Exams

AZ-104 Administrator
AZ-204 Developer
AZ-900 Fundamentals
All Microsoft Exams

Google Cloud Exams

Associate Data Practitioner
All Google Cloud Exams

Terms Privacy Cookies About Pricing

© 2026 StudyCerts. All rights reserved.

StudyCerts is an independent service and is not affiliated with, endorsed by, or sponsored by any certification body or cloud provider.

Loading page

Home
Google Cloud Exams
Professional Cloud Data Engineer
Making decisions related to ACID (atomicity, consistency, isolation, and durability) compliance and availability
A global financial enterprise is re-architecting its core pa…

Professional Cloud Data Engineer

professional-cloud-data-engineer

Advanced

Prepare and test your skills

Description
Sample Question
Free Trial
Practice Test

Advanced

Prepare and test your skills

Description
Sample Question
Free Trial
Practice Test

Acid Compliance Global Spanner Database Selection

Section: Making decisions related to ACID (atomicity, consistency, isolation, and durability) compliance and availability

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

...

...

...

...

...

Explanations

...

View source documentation

Related questions

Keep the momentum going with these hand-picked practice scenarios

AdvancedProfessional Cloud Data Engineer

An enterprise is architecting a globally distributed mobile platform deployed across the United States, Europe, and Asia. The application encompasses two distinct operational data paths: Social Activity Stream: Tracks user interactions, presence state, and social reaction counters (such as post likes and upvotes). This workload requires ultra-low latency, multi-continent write accessibility, and maximum availability ($A$) even during cross-continent network partitions ($P$), where temporary stale reads are acceptable. Billing and Wallet Ledger: Processes financial token top-ups, checkout payments, and user balances. This workload strictly mandates ACID compliance, global transactional integrity, and strong consistency ($C$) to prevent double-spending, even if network partitions introduce latency or reject writes to maintain consistency ($CP$). According to CAP theorem principles and Google Cloud database characteristics, which architectural design correctly implements these requirements?

Making decisions related to ACID (atomicity, consistency, isolation, and durability) compliance and availability

AdvancedProfessional Cloud Data Engineer

An e-commerce company is designing an event-driven inventory management pipeline on Google Cloud. The system ingests high-volume inventory mutation events from physical stores and online checkouts through Pub/Sub and processes them using Cloud Dataflow before updating product inventory levels in BigQuery and downstream datastores. The system must meet the following reliability and data integrity requirements: Guarantee inventory count accuracy and consistency despite potential out-of-order and duplicate message delivery caused by transient network retries and at-least-once Pub/Sub delivery. Prevent invalid or malformed messages from stalling the streaming pipeline while preserving them for debugging and compensating corrections. Allow safe recovery and message reprocessing in the event of subscriber-side processing bugs. Which architectural pattern should the data engineering team implement?

Making decisions related to ACID (atomicity, consistency, isolation, and durability) compliance and availability

AdvancedProfessional Cloud Data Engineer

An enterprise analytics team is designing a BigQuery data architecture for high-volume streaming telemetry events. The design must meet the following technical and compliance requirements: Telemetry data must be retained for exactly 90 days, after which expired data must be automatically and permanently removed without incurring continuous query scanning costs. Frequent downstream dashboard queries aggregate telemetry metrics by event_type and filter on specific user_id values over varying daily date ranges. The team wants to use a materialized view to accelerate precomputed aggregations while avoiding expensive full cache invalidations when data reaches the retention limit. How should you configure the base table and materialized view architecture to meet these requirements?

Designing the project, dataset, and table architecture to ensure proper data governance

AdvancedProfessional Cloud Data Engineer

A data engineering team is developing an Apache Beam streaming pipeline deployed on Google Cloud Dataflow. The pipeline ingests high-throughput user activity records from Pub/Sub, processes and enriches the records using custom transforms, and writes the output dataset to Cloud Spanner. During testing and transient worker retries, several pipeline workers fail with com.google.cloud.spanner.SpannerException: ALREADY_EXISTS errors, leading to stalled pipeline execution. Which pipeline mutation logic should the engineering team implement to resolve these write failures?

Processing logic

AdvancedProfessional Cloud Data Engineer

A logistics enterprise is designing a data storage architecture on Google Cloud for a real-time fleet management platform. The system ingests high-frequency telemetry metrics from millions of connected vehicles and must support two primary access patterns: Operational path: High-throughput, low-latency writes and frequent sequential range reads retrieving recent metrics for a specific vehicle. Analytical path: Large-scale ad-hoc batch queries analyzing historical fleet performance across date ranges, filtered and grouped by attributes such as region, fleet_tier, and vehicle_model. You need to design the schema, row keys, and optimization strategies to maximize read/write performance, prevent hotspotting, and optimize query costs. Which storage and schema configuration should you recommend?

Analyzing data access patterns

AdvancedProfessional Cloud DevOps Engineer

An e-commerce platform hosted on Google Cloud experiences periodic flash-sale traffic surges that can exhaust Compute Engine regional vCPU quotas and cause capacity constraints in the primary region (us-central1). The Site Reliability Engineering (SRE) team needs to implement an automated multi-region capacity scaling and rapid failover strategy. The solution must: Ensure client requests automatically overflow to a secondary region (us-east4) as soon as the primary region reaches backend capacity or quota limits. Avoid client-side DNS caching delays during localized saturation incidents. Maintain high availability and automated traffic distribution based on real-time backend capacity. Which architectural strategy should the SRE team implement?

Adding capacity

Want more questions like this?

Get a free certification question every week.

Last updated August 27, 2026

Are you ready for the Professional Cloud Data Engineer?

50 questions in the full practice test

More Making decisions related to ACID (atomicity, consistency, isolation, and durability) compliance and availability practice questions

Get a free certification question with a full explanation every week.

Professional Cloud Data Engineer

Provider: Google Cloud
Passing score: 70%
Questions: 50
Duration: 90 minutes

Other sections in this exam

Designing data processing systems
Ingesting and processing the data
Storing the data
Preparing and using data for analysis
Maintaining and automating data workloads

Ask Scout

Still curious? Scout, our AI tutor, can explain this concept further and answer your follow-up questions.

A global financial enterprise is re-architecting its core payment processing platform on Google Cloud. The system has the following requirements:

Execute distributed multi-table, multi-row financial ledger transactions across multiple cloud regions
Provide strict serializable isolation and external consistency (linearizability) to eliminate stale reads and race conditions
Provide automatic horizontal scaling for relational data with high write throughput

Which Google Cloud database service natively satisfies these requirements?

Cloud Spanner

Cloud SQL for PostgreSQL

Firestore in Datastore mode

Cloud Bigtable

Cloud Spanner

What Cloud Spanner is

Cloud Spanner is a fully managed, mission-critical, enterprise-grade relational database service designed for global scale. It uniquely combines the structure and ACID compliance of traditional relational databases with the horizontal scalability and high availability of NoSQL systems.

How it meets the requirements

Distributed multi-row/multi-table transactions: Cloud Spanner natively supports distributed transactions across multiple tables, splits, and geographic regions using two-phase commit and Paxos consensus.
Strict serializable isolation and linearizability: Spanner utilizes Google's TrueTime API to generate monotonically increasing timestamps, enabling external consistency (strict serializability) globally.
Horizontal scaling: It automatically shards and balances relational data across compute nodes without sacrificing transactional guarantees.

Key advantages

Guarantees ACID consistency across multi-region configurations.
Provides up to 99.999% availability SLAs for multi-region instances.
Eliminates the need for application-managed distributed transaction coordination or manual sharding.
Supports standard SQL querying alongside strong referential integrity.

Why this is optimal

None of the other Google Cloud managed database engines provide both multi-region distributed relational ACID transactions with external consistency and horizontal write scalability.

Cloud SQL for PostgreSQL

Firestore in Datastore mode

Cloud Bigtable