Google Cloud Professional Data Engineer · Free practice question 7 of 12
Search indexes for log lookups
Security analysts at Penwortham Bank search a 200 TB BigQuery table of application logs for rare values such as a specific IP address or request ID across many text columns. Each lookup scans most of the table. Which feature makes these needle-in-a-haystack lookups much cheaper and faster?
- A.A materialized view that selects all columns
- B.Clustering the table by every searched column
- C.A search index on the relevant columns, queried with the SEARCH function
- D.BI Engine for the project
Show answer and explanation
Correct answer: C. A search index on the relevant columns, queried with the SEARCH function
Why: Search indexes let BigQuery locate the rows that contain specific tokens across text columns, so the SEARCH function reads far less data for point lookups. A materialized view of all columns duplicates the table without helping lookups. Clustering helps with at most four columns used as filters, and BI Engine speeds up aggregations for BI tools rather than token searches.
More free Google Cloud Professional Data Engineer questions
- Sliding windows for moving averages
- Turbo replication on dual-region buckets
- Assured Workloads for sovereign controls
- Data Validation Tool after migration
- Pub/Sub Cloud Storage subscription archive
- Bigtable garbage collection by age
- Data Studio viewer's credentials
- Integer-range partitioning on an ID
- Approximate distinct counts for dashboards
- Scheduled queries for a single SQL job
- Pub/Sub message storage policy regions