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?

AUsers are running too many concurrent queries in the system

BThe [myproject:mydataset.mytable] table has too many partitions

CEither the state or the city columns in the [myproject:mydataset.mytable] table have too many
NULL values

DMost rows in the [myproject:mydataset.mytable] table have the same value in the country column, causing data skew

Show Suggested Answer

Suggested Answer: C

by Dalene at Jan 09, 2023, 01:26 PM

Limited Time Offer

25%

Off

Get Premium Professional Data Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Amina

1 months 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

1 months 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

Annice

4 days ago

Maybe the table has too many partitions causing the slow query.

upvoted 0 times

...

Teresita

11 days ago

I think the delay is because of too many concurrent queries.

upvoted 0 times

...

Haydee

1 months 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

Ettie

3 days ago

B) The [myproject:mydataset.mytable] table has too many partitions

upvoted 0 times

...

Mariko

4 days ago

C) Either the state or the city columns in the [myproject:mydataset.mytable] table have too many NULL values

upvoted 0 times

...

Miesha

5 days ago

B) The [myproject:mydataset.mytable] table has too many partitions

upvoted 0 times

...

Gwenn

8 days ago

A) Users are running too many concurrent queries in the system

upvoted 0 times

...

Rene

21 days ago

A) Users are running too many concurrent queries in the system

upvoted 0 times

...

Eleni

2 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

Shaunna

4 days ago

C) Either the state or the city columns in the [myproject:mydataset.mytable] table have too many NULL values

upvoted 0 times

...

Louann

6 days ago

B) The [myproject:mydataset.mytable] table has too many partitions

upvoted 0 times

...

Amie

19 days ago

A) Users are running too many concurrent queries in the system

upvoted 0 times

...

Nell

1 months 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

1 months ago

C) Either the state or the city columns in the [myproject:mydataset.mytable] table have too many NULL values

upvoted 0 times

...

Zana

1 months ago

B) The [myproject:mydataset.mytable] table has too many partitions

upvoted 0 times

...

Buddy

2 months 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