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 Machine Learning Engineer Exam - Topic 4 Question 73 Discussion

You have a custom job that runs on Vertex Al on a weekly basis The job is Implemented using a proprietary ML workflow that produces the datasets. models, and custom artifacts, and sends them to a Cloud Storage bucket Many different versions of the datasets and models were created Due to compliance requirements, your company needs to track which model was used for making a particular prediction, and needs access to the artifacts for each model. How should you configure your workflows to meet these requirement?
D) Register each model in Vertex Al Model Registry, and use model labels to store the related dataset and model information.
A) Configure a TensorFlow Extended (TFX) ML Metadata database, and use the ML Metadata API.
B) Create a Vertex Al experiment, and enable autologging inside the custom job
C) Use the Vertex Al Metadata API inside the custom Job to create context, execution, and artifacts for each model, and use events to link them together.

Google Professional Machine Learning Engineer Exam - Topic 4 Question 73 Discussion

Actual exam question for Google's Professional Machine Learning Engineer exam
Question #: 73
Topic #: 4
[All Professional Machine Learning Engineer Questions]

You have a custom job that runs on Vertex Al on a weekly basis The job is Implemented using a proprietary ML workflow that produces the datasets. models, and custom artifacts, and sends them to a Cloud Storage bucket Many different versions of the datasets and models were created Due to compliance requirements, your company needs to track which model was used for making a particular prediction, and needs access to the artifacts for each model. How should you configure your workflows to meet these requirement?

Show Suggested Answer Hide Answer
Suggested Answer: D

by Tammara at Mar 19, 2024, 03:08 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Erinn
9 months ago
I disagree, B might not provide enough detail for compliance needs.
upvoted 0 times
...
Octavio
9 months ago
Wait, can you really track all that with just the Metadata API?
upvoted 0 times
...
Gladys
10 months ago
A seems a bit overkill for just tracking models, right?
upvoted 0 times
...
Keena
10 months ago
I think D is a solid choice too, especially for organization.
upvoted 0 times
...
Franchesca
10 months ago
Option C sounds like the best fit for tracking everything.
upvoted 0 times
...
Jose
10 months ago
I feel like registering models in the Vertex AI Model Registry makes sense for tracking, but I wonder if it’s enough for our compliance requirements.
upvoted 0 times
...
Levi
11 months ago
The Vertex AI Metadata API sounds familiar, especially for linking models and artifacts, but I’m a bit confused about how to implement it correctly.
upvoted 0 times
...
Mozell
11 months ago
I think enabling autologging in Vertex AI experiments could help, but I can't recall if it covers all the compliance needs we studied.
upvoted 0 times
...
Kindra
11 months ago
I remember we discussed the importance of tracking models and datasets for compliance, but I'm not sure if TFX is the best option here.
upvoted 0 times
...
Gertude
11 months ago
I'm a bit unsure about this one. There are a few different options presented, and I'm not sure which one would be the most appropriate. I think I'll start by reviewing the details of each approach and try to determine the pros and cons before making a decision.
upvoted 0 times
...
Trina
11 months ago
This is a great question that really tests our understanding of Vertex AI and model management. I feel pretty confident that the Vertex AI Metadata API is the way to go here. It allows us to create the necessary context, execution, and artifact tracking to satisfy the compliance requirements.
upvoted 0 times
...
Mignon
11 months ago
Okay, I think I have a strategy for this. Based on the compliance requirements, it sounds like we need a robust way to track the model lineage and associated artifacts. The Vertex AI Metadata API seems like the most comprehensive option to meet those needs, so I'll focus on that approach.
upvoted 0 times
...
Romana
11 months ago
Hmm, I'm a bit confused by all the different options here. I know we need to track the model versions and artifacts, but I'm not sure which approach would be the best fit for our requirements. I'll have to read through the question carefully and think it through.
upvoted 0 times
...
Deonna
11 months ago
This seems like a tricky one. I'm not too familiar with Vertex AI and the different options for tracking model provenance, but I think I'll try to break it down step-by-step.
upvoted 0 times
...
Myra
11 months ago
Easy peasy, the answer is A. tmp_name is the key you want for the provisional file name.
upvoted 0 times
...
Tamar
11 months ago
This looks straightforward. The Scrum Guide is the foundation, so multiple teams must still follow it even when scaling.
upvoted 0 times
...
Lauran
2 years ago
I personally think option C) Use the Vertex AI Metadata API inside the custom Job is the most efficient solution.
upvoted 0 times
...
Gwenn
2 years ago
I disagree, I believe option D) Register each model in Vertex AI Model Registry is the way to go.
upvoted 0 times
...
Brett
2 years ago
I think the best option is A) Configure a TensorFlow Extended (TFX) ML Metadata database, and use the ML Metadata API.
upvoted 0 times
...
Naomi
2 years ago
I'm not sure, but option C sounds good to me. Using Vertex AI Metadata API inside the job seems like a practical approach.
upvoted 0 times
...
Thomasena
2 years ago
I agree with Georgeanna. It's important to have a centralized database to keep track of all the models and datasets.
upvoted 0 times
...
Georgeanna
2 years ago
I think option A is the best choice. By using TFX ML Metadata database, we can easily track the model used for predictions.
upvoted 0 times
...
Twana
2 years ago
Hmm, I'm not sure about option B. Relying on autologging in Vertex AI may not give us enough control over the metadata. And a separate TFX metadata database (option A) sounds like overkill for this use case.
upvoted 0 times
...
Eladia
2 years ago
Option D also sounds promising - registering the models in the Vertex AI Model Registry and using labels could be a simple way to manage the versioning and provenance. But I'm not sure how robust that would be for a complex workflow.
upvoted 0 times
...
Honey
2 years ago
I'm leaning towards option C. Using the Vertex AI Metadata API seems like the most direct way to link the models, datasets, and artifacts together. Plus, we can create custom context and execution details to meet the compliance needs.
upvoted 0 times
Emerson
2 years ago
I'm convinced, option C it is!
upvoted 0 times
...
Shawnee
2 years ago
It's definitely a more structured way to track model usage and artifacts.
upvoted 0 times
...
Brande
2 years ago
Using events to link everything sounds like a good approach.
upvoted 0 times
...
Alona
2 years ago
That makes sense, it's important to link all the necessary information together.
upvoted 0 times
...
Kristeen
2 years ago
We can create custom context and execution details as needed for compliance.
upvoted 0 times
...
Norah
2 years ago
Agreed, using the Vertex AI Metadata API seems like the most direct solution.
upvoted 0 times
...
Truman
2 years ago
I think option C is the best choice.
upvoted 0 times
...
...
Chaya
2 years ago
Whoa, this question looks like a real brain-teaser! We definitely need to track the models and artifacts for compliance, but it's not clear which option is the best approach.
upvoted 0 times
...

Save Cancel