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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft AZ-140 Exam - Topic 3 Question 87 Discussion

Actual exam question for Microsoft's AZ-140 exam
Question #: 87
Topic #: 3
[All AZ-140 Questions]

You have an Azure Virtual Desktop deployment.

You plan to create a new host pool named Pool1 that will contain five Windows 11 session hosts.

You need to enable secure boot and vTPM on the session hosts.

How should you configure the Virtual Machines settings?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Elmira at Dec 08, 2024, 01:12 PM

Limited Time Offer

25%

Off

Get Premium AZ-140 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Jesus
3 months ago
C seems useful too, but not for this specific need.
upvoted 0 times
...
Carin
3 months ago
Surprised that B is the only option for this!
upvoted 0 times
...
Charlena
3 months ago
I thought enabling encryption was enough?
upvoted 0 times
...
An
4 months ago
Totally agree, B is the right choice.
upvoted 0 times
...
Wava
4 months ago
B is the way to go for secure boot and vTPM!
upvoted 0 times
...
Bette
4 months ago
Yeah, I agree with Dong. I also recall that Trusted launch is essential for security features, so I would lean towards option B as well.
upvoted 0 times
...
Kenneth
4 months ago
I’m a bit confused about the other options. I don’t think enabling encryption at rest is directly related to secure boot, but I could be wrong.
upvoted 0 times
...
Dong
4 months ago
I think option B sounds right because it mentions Trusted launch, which is linked to secure boot and vTPM. I saw a similar question in our practice tests.
upvoted 0 times
...
Alesia
5 months ago
I remember we discussed secure boot and vTPM in our last study session, but I'm not entirely sure which option directly relates to enabling those features.
upvoted 0 times
...
Leota
5 months ago
This seems like a good opportunity to demonstrate my Azure Virtual Desktop knowledge. I'm pretty confident that setting the Security type to Trusted launch virtual machines is the correct way to enable secure boot and vTPM on the session hosts. I'll make sure to review the details, but I think I've got a solid strategy for this question.
upvoted 0 times
...
Katy
5 months ago
I'm a little confused by the options here. Encryption at rest and a system-assigned managed identity don't seem directly related to the secure boot and vTPM requirements. I'll need to double-check the Azure Virtual Desktop documentation to make sure I understand the right approach.
upvoted 0 times
...
Chaya
5 months ago
Okay, I've got this. Based on the question, I need to set the Security type to Trusted launch virtual machines to enable secure boot and vTPM on the session hosts. Simple enough, I should be able to handle this one.
upvoted 0 times
...
Nickole
5 months ago
Hmm, I'm a bit unsure about this one. I know we need to enable secure boot and vTPM, but I'm not sure if the Trusted launch virtual machines setting is the right way to do that. I'll have to review the Azure Virtual Desktop documentation more closely.
upvoted 0 times
...
Deane
5 months ago
This looks like a straightforward question about configuring Azure Virtual Desktop session hosts. I think the key is to enable the Trusted launch virtual machines setting to get secure boot and vTPM.
upvoted 0 times
...
Felicia
10 months ago
I heard Microsoft is working on a new Azure Virtual Desktop feature called 'Trusted Laugh' for all the jokes in the exam questions.
upvoted 0 times
...
Avery
10 months ago
Encryption at rest? Really? That's for data protection, not enabling hardware security features. B is the winner for sure.
upvoted 0 times
Kristel
9 months ago
Definitely, B is the way to go for configuring the Virtual Machines settings in this case.
upvoted 0 times
...
Chau
9 months ago
I agree, setting Security type to Trusted launch virtual machines will enable secure boot and vTPM on the session hosts.
upvoted 0 times
...
Jessenia
9 months ago
Encryption at rest is not the same as enabling secure boot and vTPM. B is the correct choice.
upvoted 0 times
...
...
Stephaine
10 months ago
Haha, D is just ridiculous. Network security groups? Come on, that's not even close to the right answer.
upvoted 0 times
Kayleigh
9 months ago
C) Enable a system-assigned managed identity.
upvoted 0 times
...
Cathrine
9 months ago
B) Set Security type to Trusted launch virtual machines.
upvoted 0 times
...
Elouise
9 months ago
A) Enable encryption at rest and a platform-managed key.
upvoted 0 times
...
...
Eun
10 months ago
I bet Option C is just a distraction. Managed identities have nothing to do with secure boot or vTPM.
upvoted 0 times
Cory
9 months ago
D) Set Network security group to Advanced.
upvoted 0 times
...
Cathern
9 months ago
C) Enable a system-assigned managed identity.
upvoted 0 times
...
Timmy
9 months ago
B) Set Security type to Trusted launch virtual machines.
upvoted 0 times
...
Arlyne
10 months ago
A) Enable encryption at rest and a platform-managed key.
upvoted 0 times
...
...
Lashawnda
10 months ago
B seems like the right choice here. Trusted launch VMs are the way to go for enabling secure boot and vTPM.
upvoted 0 times
Scarlet
10 months ago
User2: Definitely, trusted launch virtual machines are the best choice for this scenario.
upvoted 0 times
...
Ashlee
10 months ago
User1: I agree, option B is the way to go for enabling secure boot and vTPM.
upvoted 0 times
...
...
Pearly
11 months ago
I'm not sure about that. I think enabling encryption at rest and a platform-managed key might be a better option for security.
upvoted 0 times
...
James
11 months ago
I agree with Carlee. Setting Security type to Trusted launch virtual machines sounds like the right configuration for this scenario.
upvoted 0 times
...
Carlee
11 months ago
I think we should set Security type to Trusted launch virtual machines for secure boot and vTPM.
upvoted 0 times
...

Save Cancel