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
Precalculating fields
An analytics team maintains an interactive executive dashboa…

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

Optimize Dashboard Latency Bigquery Materialized Views

Section: Precalculating fields

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 data engineering team uses Cloud Composer to orchestrate batch pipelines that compute daily sales aggregates and precalculate key business metrics. The precalculated datasets are stored in Cloud Storage and must be loaded into an external relational reporting database accessed by visualization dashboards. To ensure data integrity, the pipeline must support automated task retries and backfilling historical dates without creating duplicate aggregate records or causing inconsistent metric states in the target database. How should the team configure the Dataproc Serverless for Apache Spark Cloud Storage to JDBC template to achieve idempotent updates?

Precalculating fields

AdvancedProfessional Cloud Data Engineer

A retail enterprise maintains a central BigQuery table containing precalculated hourly sales performance metrics. A Looker Studio executive dashboard connected to this dataset is accessed frequently by hundreds of regional managers throughout the business day. The underlying data pipeline updates the BigQuery precalculated table every hour on the hour. You need to configure the Looker Studio data source connection to minimize BigQuery query costs and visualization latency while strictly honoring the 1-hour reporting freshness SLA. How should you configure the data source connection in Looker Studio?

Precalculating fields

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

Your organization is designing an enterprise data analytics platform in Google Cloud that processes highly regulated healthcare data across Cloud Storage and BigQuery. Your security and compliance policies dictate the following requirements: All data at rest in Cloud Storage buckets and BigQuery datasets must achieve logical data separation and cryptographic isolation using keys owned and controlled by your organization. Cryptographic keys must be stored in FIPS 140-2 Level 3 Hardware Security Modules (Cloud HSM). A strict separation of duties must be enforced so that data engineers managing storage and analytics resources cannot administer or alter key management configurations. All tables created inside analytics datasets and objects written to ingestion buckets must automatically be encrypted without requiring engineers to explicitly supply key identifiers during write operations. Which architecture and configuration strategy should you implement?

Data security (encryption and key management)

AdvancedProfessional Cloud Data Engineer

An enterprise maintains hundreds of terabytes of clickstream logs stored in Amazon S3 within the us-east-1 region. The data analytics team needs to combine and analyze this remote data alongside core customer demographic tables residing natively in BigQuery in the US multi-region. The solution must satisfy the following constraints: Minimize cross-cloud egress charges and network bandwidth consumption. Eliminate the operational overhead of deploying, managing, or scheduling ETL/ELT pipelines. Enforce unified, fine-grained access governance across cloud providers using standard identity delegation. Which architecture should the team implement?

Designing for data and application portability (e.g., multi-cloud and data residency requirements)

AdvancedProfessional Cloud Security Engineer

An enterprise security engineer is hardening identity governance for a production Google Cloud environment. A security audit reveals that several Compute Engine virtual machines (VMs) are utilizing the Compute Engine default service account (PROJECT_NUMBER-compute@developer.gserviceaccount.com) with the Editor role (roles/editor). Additionally, multiple legacy workloads are being decommissioned, and the operations team plans to immediately delete their associated service accounts. Which strategy should the security engineer implement to remediate the VM identities and manage the decommissioning lifecycle according to Google Cloud best practices?

Creating, disabling, and authorizing service accounts.

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 Precalculating fields 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 analytics team maintains an interactive executive dashboard that frequently executes heavy aggregate calculations across a multi-terabyte transactional table in BigQuery. The table continuously receives new streaming appends throughout the day, and dashboard users are experiencing slow query performance and high computational costs from repeated aggregate calculations.

The team needs to reduce query latency and computational load by precalculating common aggregations while ensuring queries automatically serve real-time, consistent data without requiring any modifications to the dashboard SQL queries.

Which strategy should the team implement?

Create a standard logical view that encapsulates the aggregation logic and point the dashboard queries to this view.

Configure a scheduled query that periodically executes the aggregate logic and overwrites a separate summary destination table.

Create a BigQuery materialized view that defines the required aggregations over the base transactional table.

Export the transactional table to Cloud Storage in Parquet format and query it using BigQuery external tables with hive partitioning.

Create a standard logical view that encapsulates the aggregation logic and point the dashboard queries to this view.

Configure a scheduled query that periodically executes the aggregate logic and overwrites a separate summary destination table.

Create a BigQuery materialized view that defines the required aggregations over the base transactional table.

What BigQuery Materialized Views Are

A BigQuery materialized view is a precomputed view that periodically or incrementally evaluates and stores the results of a query definition for improved performance and efficiency. Unlike standard virtual views, materialized views persist precalculated results—such as aggregated metrics, filters, and complex joins—directly in BigQuery storage, avoiding redundant query execution over massive underlying datasets.

How It Meets the Requirements

Precalculating Aggregations: It computes and stores heavy aggregated values ahead of time, dramatically cutting slot consumption, computational load, and scan latency during dashboard queries.
Zero SQL Changes (Query Rewrite): BigQuery's query optimizer features automatic smart tuning (query rewrite). When a dashboard query references the underlying base table, the optimizer transparently routes the query to the materialized view if it can satisfy the request, requiring no changes to existing dashboard SQL.
Real-Time Data Freshness: Materialized views read incremental changes directly from the base table's delta stream or storage, merging newly appended rows with the precalculated aggregate data at query time to always deliver up-to-date, consistent results.

Key Advantages and Capabilities

Incremental Maintenance: Automatically updates and refreshes precomputed aggregates as new streaming data or batch appends arrive in the base table.
Cost and Slot Optimization: Drastically minimizes bytes scanned and compute resources required by repeated, concurrent dashboard queries.
Seamless Integration: Compatible with native BigQuery features, partitioning, clustering, and BI Engine acceleration.

Why This Is Optimal

Materialized views provide the best balance of precalculated performance gains, real-time consistency on streaming base data, and zero-maintenance transparency for downstream visualization tools.

Export the transactional table to Cloud Storage in Parquet format and query it using BigQuery external tables with hive partitioning.