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:

Amina
14 days ago
Who needs speed when you can just sit back and enjoy the slow, steady progress of your query? It's like watching grass grow, but with numbers!
upvoted 0 times
...
Tammara
16 days ago
I'm pretty sure the users are just running too many queries at the same time. They need to schedule their queries better!
upvoted 0 times
...
Haydee
25 days ago
Hmm, I bet the data is skewed in the country column. Too many rows with the same value would explain the slow performance.
upvoted 0 times
Rene
4 days ago
A) Users are running too many concurrent queries in the system
upvoted 0 times
...
...
Eleni
1 months 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
Amie
2 days ago
A) Users are running too many concurrent queries in the system
upvoted 0 times
...
Nell
14 days ago
D) Most rows in the [myproject:mydataset.mytable] table have the same value in the country column, causing data skew
upvoted 0 times
...
Ahmed
16 days ago
C) Either the state or the city columns in the [myproject:mydataset.mytable] table have too many NULL values
upvoted 0 times
...
Zana
21 days ago
B) The [myproject:mydataset.mytable] table has too many partitions
upvoted 0 times
...
Buddy
29 days ago
A) Users are running too many concurrent queries in the system
upvoted 0 times
...
...
Marvel
2 months 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
Mammie
14 days ago
B) The [myproject:mydataset.mytable] table has too many partitions
upvoted 0 times
...
Wai
19 days ago
A) Users are running too many concurrent queries in the system
upvoted 0 times
...
...
Virgilio
2 months ago
But could it also be because of too many partitions in the table?
upvoted 0 times
...
Jaime
2 months ago
I agree with Kiley, data skew can definitely slow down the query.
upvoted 0 times
...
Kiley
2 months ago
I think the delay is caused by data skew.
upvoted 0 times
...

Save Cancel