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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Data Engineer Exam - Topic 3 Question 33 Discussion

Given the record streams MJTelco is interested in ingesting per day, they are concerned about the cost of Google BigQuery increasing. MJTelco asks you to provide a design solution. They require a single large data table called tracking_table. Additionally, they want to minimize the cost of daily queries while performing fine-grained analysis of each day's events. They also want to use streaming ingestion. What should you do?
B) Create a partitioned table called tracking_table and include a TIMESTAMP column.
A) Create a table called tracking_table and include a DATE column.
C) Create sharded tables for each day following the pattern tracking_table_YYYYMMDD.
D) Create a table called tracking_table with a TIMESTAMP column to represent the day.

Google Professional Data Engineer Exam - Topic 3 Question 33 Discussion

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

Given the record streams MJTelco is interested in ingesting per day, they are concerned about the cost of Google BigQuery increasing. MJTelco asks you to provide a design solution. They require a single large data table called tracking_table. Additionally, they want to minimize the cost of daily queries while performing fine-grained analysis of each day's events. They also want to use streaming ingestion. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Marguerita at May 06, 2022, 09:54 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Mariko
7 months ago
Not sure if this will really minimize costs in the long run...
upvoted 0 times
...
Trinidad
7 months ago
Partitioning is definitely the way to go!
upvoted 0 times
...
Lashawnda
8 months ago
Wait, why not just use a DATE column instead of TIMESTAMP?
upvoted 0 times
...
Paris
8 months ago
I disagree, sharded tables (Option C) could be more manageable.
upvoted 0 times
...
Olga
8 months ago
Option B is the best choice for cost efficiency!
upvoted 0 times
...
Barrett
8 months ago
I vaguely recall that using a DATE column might not be as efficient for querying as a TIMESTAMP. I’m leaning towards option B, but I’m not completely confident.
upvoted 0 times
...
Merissa
8 months ago
I'm not entirely sure, but I think sharded tables could lead to more complexity. Option C feels risky for daily queries.
upvoted 0 times
...
Ernestine
8 months ago
I remember we discussed partitioned tables in class, and they seem to help with cost management. I think option B might be the right choice.
upvoted 0 times
...
Ty
8 months ago
I practiced a similar question where partitioning was emphasized for cost efficiency. Option B sounds familiar, but I'm hesitant about the TIMESTAMP vs. DATE debate.
upvoted 0 times
...
Blondell
8 months ago
Alright, I think I've got a handle on this. Let me walk through it one more time to double-check my understanding before submitting my answer.
upvoted 0 times
...
Nieves
8 months ago
Ah, I remember learning about this in class. I'm pretty confident the correct answer is C - using the import/export utilities. That's the method we discussed for migrating repository data during upgrades.
upvoted 0 times
...

Save Cancel