Microsoft Exam MD-102 Topic 14 Question 17 Discussion

Actual exam question for Microsoft's MD-102 exam

Question #: 17
Topic #: 14

[All MD-102 Questions]

You have a computer named Computed that has Windows 10 installed.

You create a Windows PowerShell script named config.psl.

You need to ensure that config.psl runs after feature updates are installed on Computer5.

Which file should you modify on Computer5?

ALiteTouch.wsf

BSetupConfig.ini

CUnattendb*

DUnattend.xml

Show Suggested Answer

Suggested Answer: B

SetupConfig.ini is a file that can be used to customize the behavior of Windows Setup during feature updates. You can use this file to specify commands or scripts that run before or after the installation process. To run a PowerShell script after a feature update, you can use the PostOOBE parameter in SetupConfig.ini and specify the path to the script file.Reference:[SetupConfig.ini reference]

by Graciela at Feb 10, 2024, 10:42 PM

Limited Time Offer

25%

Off

Get Premium MD-102 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Delila

9 months ago

I see your point, Heike. Unattendb* does make sense for running the PowerShell script after feature updates.

upvoted 0 times

...

Heike

9 months ago

Hmm, that's a good point. Unattendb* might actually be the correct file to modify.

upvoted 0 times

...

An

9 months ago

But wouldn't Unattendb* be a better choice?

upvoted 0 times

...

Delila

9 months ago

I'm leaning towards LiteTouch.wsf, as that seems like the right file to modify.

upvoted 0 times

...

Heike

9 months ago

I disagree, I believe it should be Unattend.xml.

upvoted 0 times

...

An

10 months ago

I think the file to modify is SetupConfig.ini.

upvoted 0 times

...

Arlette

10 months ago

I see your point, maybe Unattend.xml is the right choice after all.

upvoted 0 times

...

Frederic

10 months ago

I agree with Emerson, Unattend.xml is the file we should modify for this task.

upvoted 0 times

...

Emerson

10 months ago

But isn't Unattend.xml specifically for running scripts after feature updates?

upvoted 0 times

...

Arlette

10 months ago

No, I believe it should be SetupConfig.ini.

upvoted 0 times

...

Emerson

11 months ago

I think we should modify Unattend.xml.

upvoted 0 times

...

Paul

1 years ago

Hmm, I'm not so sure about that. Wouldn't it be easier to just use a scheduled task or something? I mean, modifying the Unattend.xml file seems a bit overkill for this scenario. But I guess if that's the recommended approach, then I'm on board.

upvoted 0 times

Wayne

11 months ago

Definitely not Unattendb*. Stick with Unattend.xml for feature updates.

upvoted 0 times

...

Lisbeth

11 months ago

C) Unattendb*

upvoted 0 times

...

Kimberlie

12 months ago

I'm not sure about that one. Maybe Unattend.xml is a better choice for this scenario.

upvoted 0 times

...

Glen

12 months ago

A) LiteTouch.wsf

upvoted 0 times

...

Patrick

12 months ago

Yeah, but Unattend.xml is specifically for feature updates, so that might be the best option.

upvoted 0 times

...

Stephane

12 months ago

D) Unattend.xml

upvoted 0 times

...

Enola

12 months ago

I think modifying SetupConfig.ini should do the trick.

upvoted 0 times

...

Deonna

12 months ago

B) SetupConfig.ini

upvoted 0 times

...

Donte

1 years ago

Ah, good old Unattend.xml. That's the file we need to modify. It's like the Swiss Army knife of Windows automation - you can do all sorts of cool stuff with it, including running scripts. Plus, it's super easy to work with, right? *wink wink*

upvoted 0 times

...

Hubert

1 years ago

I agree with you on that one. The Unattend.xml file is the way to go here. It's a common file used to customize the Windows setup process, so it should be able to handle running our PowerShell script after the updates are installed.

upvoted 0 times

...

Nu

1 years ago

Hmm, this is an interesting one. I'm not too familiar with the Windows 10 update process, but I think the answer might be D) Unattend.xml. That file is typically used to automate the Windows installation process, so it makes sense that we could use it to run a script after feature updates are installed.

upvoted 0 times

...