New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft DP-100 Exam - Topic 4 Question 114 Discussion

Actual exam question for Microsoft's DP-100 exam
Question #: 114
Topic #: 4
[All DP-100 Questions]

You create an Azure Machine Learning workspace named woricspace1. The workspace contains a Python SDK v2 notebook that uses MLflow to collect model training metrics and artifacts from your local computer.

You must reuse the notebook to run on Azure Machine Learning compute instance in workspace1.

You need to continue to log metrics and artifacts from your data science code.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

0/2000 characters
Herminia
3 months ago
I disagree, it’s not about the MLCIient class here.
upvoted 0 times
...
Pamella
3 months ago
Wait, can you really log metrics without logging into the workspace first?
upvoted 0 times
...
Arlen
4 months ago
Definitely A, tracking URI is essential for logging.
upvoted 0 times
...
Bettina
4 months ago
I think it's B, instantiating the job class is key.
upvoted 0 times
...
Joni
4 months ago
Gotta configure the tracking URI for MLflow!
upvoted 0 times
...
Santos
4 months ago
Instantiating the MLCient class sounds familiar, but I can't recall if it directly relates to logging metrics in this context.
upvoted 0 times
...
Lettie
5 months ago
I feel like logging into the workspace is a basic step, but I’m not convinced it’s the main action needed for continuing to log metrics.
upvoted 0 times
...
Inocencia
5 months ago
I'm not entirely sure, but I think we also discussed instantiating the job class for running experiments. Could that be relevant here?
upvoted 0 times
...
Casey
5 months ago
I remember we talked about configuring the tracking URI in class; it seems like that might be the right step to log metrics in Azure.
upvoted 0 times
...
Dong
5 months ago
Logging into the workspace seems like an obvious step, but I'm not sure if that's the complete solution here. I'll need to think through the full process of setting up the MLflow integration with the Azure Machine Learning environment.
upvoted 0 times
...
Aliza
5 months ago
I feel pretty confident about this one. The key is to configure the tracking URI so that the MLflow logging from the local notebook can be captured on the Azure Machine Learning compute instance. I'll make sure to do that first before running the notebook.
upvoted 0 times
...
Raina
5 months ago
Okay, I'm a bit confused here. Do I need to instantiate the job class or the MLClient class? I'll need to double-check the documentation to make sure I understand the right approach.
upvoted 0 times
...
Vernell
5 months ago
Hmm, this looks like a tricky one. I think I'll need to carefully review the details about configuring the tracking URI for MLflow to work with the Azure Machine Learning compute instance.
upvoted 0 times
...
Brendan
5 months ago
Hmm, I'm not entirely sure about this one. Let me think it through - a programme resource could be an input, a process, or a grouping of projects. I'll have to weigh the options carefully.
upvoted 0 times
...
Rikki
1 year ago
Option B is an interesting choice, but it doesn't seem to be the right answer here. Instantiating the job class is more for managing the execution of your training job, not for logging metrics and artifacts.
upvoted 0 times
Lore
1 year ago
D) Instantiate the MLCIient class.
upvoted 0 times
...
Marylyn
1 year ago
C) Log into workspace!
upvoted 0 times
...
Raul
1 year ago
A) Configure the tracking URI.
upvoted 0 times
...
...
Cristina
1 year ago
C is a bit suspicious. Logging into the workspace seems unnecessary when you already have an Azure Machine Learning workspace set up. Unless there's some kind of authentication issue, I don't think that's the right answer.
upvoted 0 times
...
Jodi
1 year ago
I'm torn between A and D. Both seem to be the correct approach, but I'm curious to know if there's a specific reason why one might be preferred over the other.
upvoted 0 times
Toshia
1 year ago
D) Instantiate the MLCIient class.
upvoted 0 times
...
Zachary
1 year ago
C) Log into workspace!
upvoted 0 times
...
Johnson
1 year ago
B) Instantiate the job class.
upvoted 0 times
...
Tammi
1 year ago
A) Configure the tracking URI.
upvoted 0 times
...
...
Melodie
1 year ago
I'm not sure. Maybe we should also consider instantiating the MLCIient class for this task.
upvoted 0 times
...
Fernanda
1 year ago
I agree with Rebbecca. Configuring the tracking URI seems like the right step to take.
upvoted 0 times
...
Ettie
1 year ago
D looks good to me. Instantiating the MLClient class will give you the necessary interface to interact with MLflow from your Azure Machine Learning environment.
upvoted 0 times
Mozell
1 year ago
D) Instantiate the MLClient class.
upvoted 0 times
...
Asha
1 year ago
C) Log into workspace!
upvoted 0 times
...
Kirk
1 year ago
B) Instantiate the job class.
upvoted 0 times
...
Kina
1 year ago
A) Configure the tracking URI.
upvoted 0 times
...
...
Ryan
1 year ago
Option A is the way to go. Configuring the tracking URI will allow you to log metrics and artifacts to your Azure Machine Learning workspace.
upvoted 0 times
Lynelle
1 year ago
No, that's not the right step for logging metrics and artifacts.
upvoted 0 times
...
Remona
1 year ago
D) Instantiate the MLCIient class.
upvoted 0 times
...
Merilyn
1 year ago
Yes, logging into the workspace is important for tracking.
upvoted 0 times
...
Kallie
1 year ago
C) Log into workspace!
upvoted 0 times
...
Kenda
1 year ago
Great idea! That will allow you to log metrics and artifacts.
upvoted 0 times
...
Adelina
1 year ago
A) Configure the tracking URI.
upvoted 0 times
...
...
Rebbecca
1 year ago
I think we should configure the tracking URI to continue logging metrics and artifacts.
upvoted 0 times
...

Save Cancel