Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Professional Data Engineer Topic 4 Question 64 Discussion

Actual exam question for Google's Professional Data Engineer exam
Question #: 64
Topic #: 4
[All Professional Data Engineer Questions]

You are using Google BigQuery as your data warehouse. Your users report that the following simple query is running very slowly, no matter when they run the query:

SELECT country, state, city FROM [myproject:mydataset.mytable] GROUP BY country

You check the query plan for the query and see the following output in the Read section of Stage:1:

What is the most likely cause of the delay for this query?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Eleni
8 days ago
Wow, that's a lot of scan bytes! Maybe the table has too many NULL values in the state or city columns, causing the system to work harder to process all the data.
upvoted 0 times
...
Marvel
9 days ago
The query is slow because there are too many partitions in the table. The data is not distributed evenly, causing the system to work harder to process all the partitions.
upvoted 0 times
...
Virgilio
13 days ago
But could it also be because of too many partitions in the table?
upvoted 0 times
...
Jaime
18 days ago
I agree with Kiley, data skew can definitely slow down the query.
upvoted 0 times
...
Kiley
25 days ago
I think the delay is caused by data skew.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77