MENU
You are implementing a batch inference ML pipeline in Google Cloud. The model was developed by using TensorFlow and is stored in SavedModel format in Cloud Storage. You need to apply the model to a historical dataset that is stored in a BigQuery table. You want to perform inference with minimal effort. What should you do?
Suggested Answer: B
Get Premium Professional Machine Learning Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Vertex AI batch prediction is the most appropriate and efficient way to apply a pre-trained model like TensorFlow's SavedModel to a large dataset, especially for batch processing.
The Vertex AI batch prediction job works by exporting your dataset (in this case, historical data from BigQuery) to a suitable format (like Avro or CSV) and then processing it in Cloud Storage where the model is stored.
Avro format is recommended for large datasets as it is highly efficient for data storage and is optimized for read/write operations in Google Cloud, which is why option B is correct.
Option A suggests using BigQuery ML for inference, but it does not support running arbitrary TensorFlow models directly within BigQuery ML. Hence, BigQuery ML is not a valid option for this particular task.
Option C (exporting to CSV) is a valid alternative but is less efficient compared to Avro in terms of performance.
39 comments · newest first
EL
Eleonore
11 months ago
D seems like overkill for this task, just use A!
MA
Margo
11 months ago
C is fine, but Avro is more efficient than CSV.
AR
Argelia
11 months ago
Wait, can you really use TensorFlow models directly in BigQuery?
RO
Rozella
11 months ago
I think B is better for handling larger datasets.
LE
Letha
12 months ago
A is the easiest way to integrate TensorFlow with BigQuery ML!
MO
Mozelle
12 months ago
I feel like option D might be overkill for this scenario since we just need batch inference, but I could be wrong about that.
VA
Vanesa
1 year ago
I’m a bit confused about the formats. Is Avro better than CSV for batch predictions in Vertex AI? I can't recall the specifics.
SO
Solange
1 year ago
I remember practicing with Vertex AI, and I feel like options B and C are similar. Exporting data to Cloud Storage seems like a common step.
DE
Delbert
1 year ago
I think option A sounds familiar, but I'm not entirely sure if BigQuery ML can directly import a TensorFlow model like that.
DY
Dyan
1 year ago
I'm leaning towards option C - exporting the data to Cloud Storage in CSV format and using a Vertex AI batch prediction job. That seems like a good balance of leveraging the power of Vertex AI while keeping the setup relatively simple. I feel pretty confident about this approach.
GE
Genevive
1 year ago
Option D looks interesting - using a Vertex AI endpoint to get predictions directly from the BigQuery data. That could be a really efficient way to do this. I'll have to research how to set up a Vertex AI endpoint, but it might be worth the effort.
RO
Rodney
1 year ago
Hmm, I'm a bit unsure about this one. I'm not super familiar with Vertex AI, so I'm not sure if that's the easiest approach. Maybe I should consider the BigQuery ML option (A) since I've used that before. I'll have to think this through a bit more.
AL
Alline
1 year ago
This seems like a straightforward question. I think I'll go with option B - exporting the data to Cloud Storage and using a Vertex AI batch prediction job. That way, I can leverage the power of Vertex AI without having to do too much manual setup.
TR
Truman
2 years ago
I prefer option C. Exporting the data to Cloud Storage in CSV format and configuring a Vertex AI batch prediction job seems like a simple solution.
LA
Lavonne
2 years ago
I don't know, options A and D both sound like they involve a lot of moving parts. Why not just go with the straightforward Cloud Storage export and Vertex AI batch prediction? Can't beat the classics!
VA
Vallie
2 years ago
I agree, keeping it simple with Cloud Storage export and Vertex AI batch prediction is the way to go.
DE
Denae
2 years ago
Yeah, that does sound like a straightforward approach. Option C could work too with CSV format.
KE
Keneth
2 years ago
Option B does seem like a simpler solution. Just export the data to Cloud Storage and use Vertex AI batch prediction.
DE
Deeann
2 years ago
Let's go with the classic approach of exporting to Cloud Storage and using Vertex AI batch prediction. It's reliable.
WI
Willetta
2 years ago
Yeah, Option C also involves exporting to Cloud Storage and using Vertex AI batch prediction. It's a solid choice.
ME
Melynda
2 years ago
I agree, keeping it simple with Cloud Storage export and Vertex AI batch prediction is the way to go.
TO
Tonja
2 years ago
Option B seems like the best choice. Export data to Cloud Storage and use Vertex AI batch prediction.
GE
Gene
2 years ago
I'm not sure about option D. I think option B could also work well if we export the historical data to Cloud Storage in Avro format.
ST
Stefania
2 years ago
Ha, BigQuery ML and TensorFlow in the same sentence? That's a recipe for a headache if I ever saw one. Option B or C for me, keep it simple!
AN
Anissa
2 years ago
Hmm, I'm not sure about option A. Trying to import the TensorFlow model into BigQuery ML seems like it might be more trouble than it's worth. I'd probably go with option C or D.
JE
Jesusita
2 years ago
Yeah, I think option C or D would be easier to implement for the batch inference ML pipeline.
SH
Shasta
2 years ago
I agree, option A does seem like it could be complicated.
MA
Maile
2 years ago
I'm leaning towards option D. Deploying a Vertex AI endpoint and using it to get predictions directly from the BigQuery data sounds like the easiest and most streamlined approach.
JA
Jaime
2 years ago
Let's go with option D then. Deploying a Vertex AI endpoint seems like the easiest way to get predictions.
SA
Sabine
2 years ago
It definitely sounds like the most streamlined approach. Option D is the way to go.
TH
Theron
2 years ago
I agree, deploying an endpoint and getting predictions directly from BigQuery is the way to go.
EL
Elliott
2 years ago
Option D seems like the best choice. Using a Vertex AI endpoint for predictions is efficient.
MA
Maybelle
2 years ago
I agree with Whitney. Option D sounds like the most straightforward approach to apply the model to the historical dataset.
SI
Simona
2 years ago
Option B seems like the most efficient choice here. Exporting the data to Cloud Storage in Avro format and then using Vertex AI batch prediction is a straightforward way to apply the TensorFlow model without having to do too much manual setup.
CR
Cristina
2 years ago
I agree. It's always best to choose the most efficient option when working with ML pipelines.
GR
Graham
2 years ago
Definitely, using Vertex AI batch prediction will save us a lot of time and effort.
JA
Jamika
2 years ago
That sounds like a good plan. It should make the process easier.
ST
Staci
2 years ago
B) Export the historical data to Cloud Storage in Avro format. Configure a Vertex AI batch prediction job to generate predictions for the exported data.
WH
Whitney
2 years ago
I think option D is the best choice. It seems like the most efficient way to get predictions from the historical data.