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 72 Discussion

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

You are migrating a table to BigQuery and are deeding on the data model. Your table stores information related to purchases made across several store locations and includes information like the time of the transaction, items purchased, the store ID and the city and state in which the store is located You frequently query this table to see how many of each item were sold over the past 30 days and to look at purchasing trends by state city and individual store. You want to model this table to minimize query time and cost. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Francine
6 months ago
You know, I was leaning towards option A at first, but now I'm not so sure. I think Aide makes a good point about the importance of being able to quickly query across states and cities. This is a tough decision!
upvoted 0 times
...
Aide
6 months ago
Ah, I see your point Mabel, but I'm not convinced. What if we need to quickly look at trends across all stores in a given state or city? Wouldn't it be better to have that as the top-level clustering?
upvoted 0 times
...
Mabel
6 months ago
I disagree, I think option B is the way to go. Partitioning by transaction time makes sense since we're often querying recent data, and clustering by store ID first will help us quickly find all the purchases for a given store.
upvoted 0 times
...
Yvonne
6 months ago
Hmm, this is an interesting question. I think the key here is to optimize for the types of queries we'll be running on this table. Since we're frequently looking at purchasing trends by state, city, and store, I'm leaning towards option C - top-level cluster by state, then city, then store ID.
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