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-Machine-Learning-Engineer Topic 5 Question 80 Discussion

Actual exam question for Google's Google Professional Machine Learning Engineer exam
Question #: 80
Topic #: 5
[All Google 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

Contribute your Thoughts:

Val
3 months ago
I'm leaning towards option C. Using the Vertex AI Metadata API inside the custom job to create context, execution, and artifacts for each model seems like a comprehensive approach.
upvoted 0 times
...
Felix
3 months ago
Option C is the way to go. Keeping everything tied together in the Vertex AI Metadata API is the most elegant solution. Plus, it'll make the auditors happy!
upvoted 0 times
Hector
2 months ago
Yeah, it's important to have a clear record of which model was used for each prediction.
upvoted 0 times
...
Katina
2 months ago
I agree, using the Vertex AI Metadata API will definitely help keep everything organized.
upvoted 0 times
...
...
Frederica
3 months ago
Haha, this is a tricky one! I bet the engineers who designed this system had a headache trying to figure out the best way to handle all the versioning and compliance needs.
upvoted 0 times
Erasmo
2 months ago
D) Register each model in Vertex AI Model Registry, and use model labels to store the related dataset and model information.
upvoted 0 times
...
Armanda
2 months ago
C) Use the Vertex AI Metadata API inside the custom job to create context, execution, and artifacts for each model, and use events to link them together.
upvoted 0 times
...
Arlyne
3 months ago
A) Configure a TensorFlow Extended (TFX) ML Metadata database, and use the ML Metadata API.
upvoted 0 times
...
...
Chun
3 months ago
I disagree, I believe option D is the way to go. Registering each model in Vertex AI Model Registry will make it easier to store the related information.
upvoted 0 times
...
Louann
3 months ago
I think we should go with option A, configuring a TFX ML Metadata database seems like the best way to track the models.
upvoted 0 times
...
Alisha
3 months ago
I was leaning towards Option D, but after thinking it through, Option C provides a more comprehensive solution to manage the full lineage of the models and datasets.
upvoted 0 times
Shawnta
2 months ago
I agree, Option C seems like a better solution for tracking the full lineage of the models and datasets.
upvoted 0 times
...
Latia
3 months ago
Option D is a good choice for organizing the models.
upvoted 0 times
...
...
Marisha
4 months ago
Option C seems like the best choice here. Tracking the metadata and linking the artifacts directly in the Vertex AI Metadata API is the most robust approach to meet the compliance requirements.
upvoted 0 times
Iola
3 months ago
I also believe that option C is the best choice. It allows for easy tracking of models and datasets, making it easier to meet the compliance needs.
upvoted 0 times
...
Jannette
3 months ago
Agreed, option C provides a comprehensive way to manage the datasets, models, and artifacts while ensuring compliance with the requirements.
upvoted 0 times
...
Vanda
4 months ago
I think option C is the way to go. Using the Vertex AI Metadata API to link the artifacts and track the metadata seems like the most efficient solution.
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