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
Choosing managed services (e.g., BigQuery, BigLake, AlloyDB, Bigtable, Spanner, Cloud SQL, Cloud Storage, Firestore, Memorystore)
An enterprise financial services company is modernizing its …

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

Evaluate Transactional Database Scaling Consistency

Section: Choosing managed services (e.g., BigQuery, BigLake, AlloyDB, Bigtable, Spanner, Cloud SQL, Cloud Storage, Firestore, Memorystore)

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 designing a cost-effective data lakehouse architecture on Google Cloud. Several petabytes of structured analytical data are maintained in open columnar formats (such as Parquet) across Cloud Storage buckets and external cloud object stores. The security team requires that analysts query the data using standard BigQuery SQL and authorized views with fine-grained access controls, while strictly prohibiting granting end users direct object read permissions (storage.objects.get) to the underlying storage buckets. Which architecture should you implement to meet these requirements?

Choosing managed services (e.g., BigQuery, BigLake, AlloyDB, Bigtable, Spanner, Cloud SQL, Cloud Storage, Firestore, Memorystore)

AdvancedProfessional Cloud Data Engineer

A connected vehicle platform ingests real-time telemetry from over 500,000 vehicles streaming diagnostic metrics at 1-second intervals. The data engineering team needs to design a high-throughput storage tier in Cloud Bigtable that satisfies the following requirements: Eliminate write hotspots across cluster tablets during peak driving hours. Support low-latency row range scans to retrieve historical telemetry for a specific vehicle over a designated time window. Maintain an instance configuration optimized specifically for query latency under high write volumes. Which row key pattern and cluster target should you implement?

Choosing managed services (e.g., BigQuery, BigLake, AlloyDB, Bigtable, Spanner, Cloud SQL, Cloud Storage, Firestore, Memorystore)

AdvancedProfessional Cloud Data Engineer

A financial services organization is architecting its Google Cloud environment to support automated data pipelines and analytics workloads. The company has distinct compliance requirements across its environments and needs to design a resource hierarchy that enforces strict data governance. The architecture must satisfy the following requirements: Centralize strict security baselines, resource location constraints, and access policies consistently across all production workloads while permitting developers to iterate quickly with fewer restrictions in development. Enable centralized audit log aggregation across all child resources without configuring individual sinks in every data project. Prevent unauthorized egress and cross-boundary data exfiltration from sensitive production analytics data stores (such as BigQuery and Cloud Storage). How should the organization structure its resource hierarchy and security boundaries?

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

AdvancedProfessional Cloud Data Engineer

An enterprise data engineering team operates an automated CI/CD pipeline in project-dev-cicd that deploys and executes nightly ETL workflows in project-analytics-prod. The pipeline must read source files from a dedicated Cloud Storage bucket and write processed tables into a specific BigQuery dataset in the analytics project. Corporate security policy strictly forbids downloading and storing long-lived service account JSON keys and mandates least-privilege resource scoping. How should you configure Cloud IAM and service account permissions to fulfill these requirements?

Identity and Access Management (e.g., Cloud IAM and organization policies)

AdvancedProfessional Cloud Data Engineer

An enterprise publishes shared data listings using BigQuery Analytics Hub. A subscriber team in caller project analytics-subscriber (Project R) has subscribed to a listing and provisioned a linked dataset in project subscriber-warehouse (Project L). The underlying shared dataset contains views in project subscriber-warehouse that reference underlying base tables hosted in project source-storage (Project V). Each project resides in a separate, isolated VPC Service Controls perimeter. Queries executed by analysts in Project R against the linked dataset views are currently failing due to perimeter violations. Which VPC Service Controls ingress and egress rules must you configure to allow users in Project R to query the views while maintaining perimeter security across all projects?

Publishing datasets

AdvancedProfessional Cloud DevOps Engineer

Your engineering team is designing a continuous deployment and rollback strategy for a critical transaction API hosted on Google Cloud. You need to establish rollback criteria that balance rapid automated mitigation against unwarranted rollbacks caused by ambient noise or external dependencies. The deployment strategy must satisfy two core requirements: Automated rollback: Trigger immediately upon deterministic, high-confidence degradation in direct system health or critical Service Level Indicators (SLIs). Manual intervention: Escalate to the on-call Site Reliability Engineer (SRE) when metric deviations are ambiguous, correlate with business-level signals, or may stem from third-party upstream providers. Which operational criteria correctly distinguish between automated rollback triggers and manual escalation scenarios?

Rollback strategies

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 Choosing managed services (e.g., BigQuery, BigLake, AlloyDB, Bigtable, Spanner, Cloud SQL, Cloud Storage, Firestore, Memorystore) 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.

An enterprise financial services company is modernizing its mission-critical core banking system on Google Cloud. The system has the following architectural requirements:

Support a structured relational schema with strict ACID transaction guarantees and serializable isolation.
Provide horizontal write scalability across multiple geographical regions without requiring application-level sharding.
Maintain strong external consistency with synchronous multi-region replication.
Meet a 99.999% (five-nines) availability Service Level Agreement (SLA).

Which database service should the organization select to meet these requirements?

Memorystore

Cloud SQL

Spanner

Firestore

Memorystore

Cloud SQL

Spanner

What Spanner is

Spanner is Google Cloud's fully managed, globally distributed relational database service. It combines the benefits of relational database structure (schemas, ANSI SQL support, ACID transactions) with the horizontal scalability of NoSQL systems.

How it meets the requirements

Structured relational schema and serializable ACID transactions: Spanner natively enforces relational schemas, ANSI SQL queries, and provides serializable isolation by default to maintain external consistency.
Multi-region horizontal write scalability: Spanner scales horizontally across compute nodes and storage without manual application sharding, handling distributed transactions automatically via TrueTime.
Strong external consistency: Spanner uses synchronous, byte-level replication across zones and regions with Paxos consensus, ensuring strict read-after-write consistency globally.
99.999% availability SLA: Spanner's multi-region instance configurations offer an industry-leading 99.999% availability SLA with automatic failover and zero planned downtime.

Key advantages

Unlimited horizontal scaling: Seamlessly scales compute and storage independently to handle massive transactional volumes.
Synchronous replication: Guarantees zero data loss (RPO = 0) across regional failures.
Familiar relational model: Supports standard SQL dialects (GoogleSQL and PostgreSQL interface) and DML.
No maintenance windows: Schema updates and maintenance occur online without service disruption.

Why this is optimal

Spanner is the only Google Cloud managed database that simultaneously provides global horizontal write scaling, multi-region synchronous replication, serializable ACID transactions, and up to 99.999% availability.

Firestore