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
Defining data sources and sinks
A gaming enterprise is architecting the data storage layer f…

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 Gcp Sinks Bigtable Bigquery Latency

Section: Defining data sources and sinks

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

Your data engineering team needs SSH access to a Compute Engine VM that orchestrates data ingestion pipelines. The VM is located inside a VPC Service Controls perimeter to prevent data exfiltration. The engineers are working remotely from unmanaged client devices. You need to provide secure SSH access to the VM without exposing it directly to the public internet, while ensuring the access complies with the VPC Service Controls perimeter restrictions. What should you do?

Defining data sources and sinks

AdvancedProfessional Cloud Data Engineer

A data engineering team is migrating a legacy data ingestion pipeline to Google Cloud Managed Service for Apache Kafka. They need to enforce strict schema validation to prevent malformed data from breaking downstream structured sinks. The team has the following requirements for the new pipeline: Support for a formal schema definition format natively integrated with the Managed Service for Apache Kafka schema registry. Ensure that consumer applications configured with updated schemas can still read data produced with older schema versions. Implement a production-ready schema deployment strategy that prevents unexpected schema changes during runtime. Which architecture and configuration strategy should the team implement?

Defining data sources and sinks

AdvancedProfessional Cloud Data Engineer

An enterprise is deploying an Apache Beam streaming pipeline on Google Cloud Dataflow to ingest high-throughput real-time telemetry from a newly integrated partner source. During integration testing, occasional malformed payloads and invalid schema records cause worker exceptions, which lead to indefinite bundle retries, delayed watermarks, and pipeline processing stalls. The data engineering team must ensure pipeline reliability, prevent malformed records from halting stream execution, preserve failed messages with diagnostic context for post-mortem replay, and establish automated operational alerting. Which error-handling and observability architecture should the team implement?

Integrating with new data sources

AdvancedProfessional Cloud Data Engineer

An enterprise runs two primary BigQuery workloads under a capacity-based reservations model: Interactive BI Dashboards: Used concurrently by analysts and business users throughout the day, requiring consistent low-latency response times without queuing delays. Batch ETL Pipelines: Executed periodically throughout the day and night to process large staging tables; several queries contain complex Common Table Expressions (CTEs) referenced multiple times across downstream calculations. Recent monitoring shows that interactive dashboard queries experience sudden latency spikes when batch ETL tasks trigger rapid slot autoscaling. Furthermore, short-lived ETL queries that finish in a few seconds are driving unnecessary compute expenses by causing the autoscaler to provision large slot spikes, and multi-referenced CTEs are consuming excessive processing resources. Which strategy should you implement to optimize performance, eliminate workload contention, and control costs?

Interactive or batch query jobs

AdvancedProfessional Cloud Data Engineer

An organization is establishing a secure cloud data warehouse architecture on Google Cloud. Corporate compliance policies mandate strict data governance, data residency, and cryptographic controls across all projects: No storage or analytics service may be created using Google default encryption; all new resources must enforce Customer-Managed Encryption Keys (CMEK). All CMEKs must originate strictly from a centralized, audited security project. Data residency rules require all encryption keys and storage resources to align in the same regional location. Service identities must operate under the principle of least privilege to perform cryptographic operations. Which combination of Google Cloud controls should the data engineering team implement to satisfy these requirements?

Mapping business requirements

AdvancedProfessional Cloud Security Engineer

A security engineer is configuring column-level security in BigQuery to restrict access to sensitive personal data across an analytical data warehouse. The engineer has completed the following steps: Created a taxonomy named PII_Taxonomy with a policy tag named High_Sensitivity. Updated the BigQuery table schema so that sensitive columns reference the resource name of the High_Sensitivity policy tag. Granted the BigQuery Data Viewer role at the dataset level to the general data analytics group. During validation, the engineer discovers that members of the data analytics group can still execute queries and read cleartext data from the tagged columns, even though they were never granted access to the policy tag. What action must the security engineer take to ensure that column-level access control is actively enforced?

Restricting access to Google Cloud data services (e.g., BigQuery, Cloud Storage, and Cloud SQL datastores).

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 Defining data sources and sinks 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 gaming enterprise is architecting the data storage layer for a high-throughput telemetry ingestion pipeline on Google Cloud. The system must support two distinct downstream operational access patterns:

Workload 1 (Real-Time State): High-throughput, sub-10 millisecond point reads and writes keyed by player ID to maintain active session states and user profiles.
Workload 2 (Analytical Reporting): Petabyte-scale ad hoc aggregations and complex SQL analytics over years of historical gameplay telemetry, leveraging decoupled compute and columnar storage.

Which storage combination should the team select to serve as the optimal sinks for these workloads?

Use Bigtable as the sink for Workload 1, and BigQuery as the sink for Workload 2.

Use Pub/Sub for Workload 1, and Cloud Spanner for Workload 2.

Use Cloud SQL with read replicas for Workload 1, and Bigtable for Workload 2.

Use BigQuery as the sink for Workload 1, and Cloud Storage with BigLake external tables as the sink for Workload 2.

Use Bigtable as the sink for Workload 1, and BigQuery as the sink for Workload 2.

What Bigtable and BigQuery Are

Cloud Bigtable is a sparsely populated, fully managed NoSQL database optimized for massive operational scale, low latency, and single-row key-based access patterns. BigQuery is a serverless, highly scalable enterprise data warehouse built on a columnar storage architecture (Capacitor) and decoupled compute infrastructure (Dremel).

How They Meet the Requirements

Workload 1 (Real-Time State): Bigtable delivers predictable, single-digit millisecond latency for individual row-key lookups, appends, and updates at millions of operations per second, making it ideal for live player profiles and active session states.
Workload 2 (Analytical Reporting): BigQuery natively separates storage (Colossus) and compute (Slots), allowing petabyte-scale analytical queries and SQL aggregations without managing database indexes, cluster sizing, or query infrastructure.

Key Advantages and Capabilities

Sub-millisecond to low-millisecond point access: Bigtable is tailored for fast row-key lookups.
Columnar scan efficiency: BigQuery's Capacitor format enables high compression ratios and scans only the columns required for analytical aggregations.
Independent compute and storage scaling: BigQuery dynamically provisions slots on demand to execute parallelized analytics over petabyte-scale datasets.
Linear horizontal scalability: Bigtable throughput scales predictably by adding nodes without requiring downtime.

Why This Is Optimal

Choosing Bigtable for key-value point access and BigQuery for analytical columnar aggregations aligns each workload with its optimized engine architecture, ensuring low latency for operations and cost-effective performance for big data analytics.

Use Pub/Sub for Workload 1, and Cloud Spanner for Workload 2.

Use Cloud SQL with read replicas for Workload 1, and Bigtable for Workload 2.

Use BigQuery as the sink for Workload 1, and Cloud Storage with BigLake external tables as the sink for Workload 2.