A retail company uses Looker to provide interactive executive dashboards over a large BigQuery dataset that receives continuous real-time transaction updates. Business analysts frequently explore the data by applying diverse, dynamic filters and aggregations across various combinations of store locations, product categories, and transaction timestamps. The engineering team must meet the following requirements: Deliver sub-second query response times for interactive, ad-hoc dashboard exploration without requiring fixed pre-aggregated views. Ensure query results reflect incoming real-time streaming data with zero manual pipeline maintenance. Minimize query execution slot utilization during peak dashboard usage. Which acceleration strategy should the data engineering team implement?

Provision a BigQuery BI Engine reservation in the dataset location and optionally specify the transaction table as a preferred table.: ### What BigQuery BI Engine Is **BigQuery BI Engine** is a built-in, distributed in-memory analysis service that accelerates SQL queries by caching frequently accessed data in memory and using an optimized execution engine designed specifically for business intelligence (BI) and dashboard workloads. ### How BI Engine Meets the Scenario Requirements - **Sub-Second Interactive Queries**: BI Engine stores working table partitions in vectorized, in-memory representations, enabling ultra-low latency execution for dynamic aggregations, filters, and multi-dimensional slice-and-dice queries. - **Real-Time Data Freshness**: BI Engine seamlessly handles table modifications and streaming inserts, ensuring that dashboard users query the latest transaction records without needing batch rebuilds or manual cache invalidations. - **Slot Optimization**: BI Engine processes accelerated input stages in memory without consuming standard BigQuery reservation slots, directly reducing slot contention during high-concurrency peak usage hours. - **No Pipeline Overhead**: It requires zero changes to underlying data pipelines or SQL models, unlike static pre-aggregation layers. ### Key Advantages and Capabilities - **Seamless BI Integration**: Natively integrates with Looker and other visualization tools via standard BigQuery SQL. - **Dynamic Acceleration Modes**: Supports `FULL_QUERY`, `FULL_INPUT`, and `PARTIAL_INPUT` acceleration modes to optimize subquery execution automatically. - **Configurable Resource Allocation**: Supports preferred table assignments and granular capacity reservations (from 1 GB up to hundreds of GBs). ### Why This Is Optimal Compared to static caching or manual materialized aggregates, BI Engine excels at handling arbitrary filter combinations on streaming data while significantly reducing slot resource consumption.

Select Bi Engine Acceleration Strategy Dashboards | professional-cloud-data-engineer

Select Bi Engine Acceleration Strategy Dashboards

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.

A retail company uses Looker to provide interactive executive dashboards over a large BigQuery dataset that receives continuous real-time transaction updates. Business analysts frequently explore the data by applying diverse, dynamic filters and aggregations across various combinations of store locations, product categories, and transaction timestamps.

The engineering team must meet the following requirements:

Deliver sub-second query response times for interactive, ad-hoc dashboard exploration without requiring fixed pre-aggregated views.
Ensure query results reflect incoming real-time streaming data with zero manual pipeline maintenance.
Minimize query execution slot utilization during peak dashboard usage.

Which acceleration strategy should the data engineering team implement?

Configure Looker Persistent Derived Tables (PDTs) to pre-aggregate transaction metrics on an hourly cron schedule.

Provision a BigQuery BI Engine reservation in the dataset location and optionally specify the transaction table as a preferred table.

Create a set of BigQuery Materialized Views covering all possible combinations of store, product, and timestamp dimensions.

Rely on BigQuery query result caching and configure Looker to reuse cached query results for 24 hours.

Professional Cloud Data Engineer

Select Bi Engine Acceleration Strategy Dashboards

Related questions