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

Microsoft AZ-140 Exam - Topic 1 Question 84 Discussion

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

You have an Azure Virtual Desktop deployment that contains an Azure compute gallery. The Azure compute gallery contains an image definition named

Definitions Definitionl contains the following image versions:

* 1.0.0

* 1.1.0

* 1.2.0

You need to ensure that when a virtual machine is created from the Azure compute gallery, the 1.1.0 image version is used by default.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: B

In order to deploy a VPN gateway to VNet1, you should first add a subnet named GatewaySubnet to VNet1. According to the Microsoft Official Guide AZ-140, 'You must create a gateway subnet for the virtual network that you plan to use for the gateway. The subnet must be named GatewaySubnet and it must use an address range that is large enough to accommodate the number of IP addresses that you plan to use for the gateway and its supporting resources.' Therefore, the first step to ensure that you can deploy the VPN gateway is to add a subnet named GatewaySubnet to VNet1.


Contribute your Thoughts:

0/2000 characters
Caprice
4 months ago
Excluding the latest version is a solid strategy!
upvoted 0 times
...
Dylan
4 months ago
I’m not sure that would work. Anyone tested it?
upvoted 0 times
...
Casie
4 months ago
Wait, why not just tag 1.1.0 as default? Seems easier.
upvoted 0 times
...
Aja
4 months ago
Definitely agree with that! Makes sense.
upvoted 0 times
...
Luisa
5 months ago
I think option B is the way to go. Exclude 1.2.0.
upvoted 0 times
...
Kris
5 months ago
I feel like applying a lock to the image version might not be the right approach here, but I can't remember the details.
upvoted 0 times
...
Bette
5 months ago
I practiced a similar question where we had to set a default image version, and I think it involved excluding the latest version.
upvoted 0 times
...
Wava
5 months ago
I remember something about applying tags to set defaults, but I can't recall if it was for images or something else.
upvoted 0 times
...
Domonique
5 months ago
I think we might need to exclude the latest version to set a default, but I'm not sure which one to exclude.
upvoted 0 times
...
Long
5 months ago
I'm pretty confident this is a straightforward one. The answer is option B - select "Exclude from latest" for the 1.2.0 version. That should make 1.1.0 the default.
upvoted 0 times
...
Chantay
5 months ago
Ah, I see. Based on the options, it looks like we need to select "Exclude from latest" for the 1.0.0 and 1.2.0 versions, so that 1.1.0 becomes the default.
upvoted 0 times
...
Isidra
5 months ago
Okay, I think I've got it now. Option B makes the most sense to me - excluding the 1.2.0 version will ensure 1.1.0 is used by default. Thanks for the help, everyone!
upvoted 0 times
...
Lorean
5 months ago
Hmm, this is an interesting one. I think the key here is to make sure the 1.1.0 image version is the default one used when creating a VM from the gallery.
upvoted 0 times
...
Edmond
6 months ago
I remember talking about this in relation to cloud security risks. Isn't a buffer overrun more about memory issues? It doesn't seem right for this scenario.
upvoted 0 times
...
Lenna
10 months ago
Hold up, 'Definitions Definitionl'? Looks like someone's having a bit of a brain freeze there. I'd go with option C - lock that 1.1.0 version up tight, just to be on the safe side.
upvoted 0 times
Marcelle
9 months ago
Definitely, better safe than sorry when it comes to deployments.
upvoted 0 times
...
Rebecka
9 months ago
Yeah, that way we can ensure it's always used by default.
upvoted 0 times
...
Ceola
9 months ago
I agree, locking the 1.1.0 version seems like the best option.
upvoted 0 times
...
...
Carri
11 months ago
Ooh, an Azure compute gallery! Sounds like a fancy shopping mall for virtual machines. I'd pick option D - tag the 1.1.0 version as 'default' and call it a day.
upvoted 0 times
Laquanda
10 months ago
User3: Agreed, that would ensure the right image version is used by default.
upvoted 0 times
...
Scarlet
10 months ago
User2: Yeah, tagging the 1.1.0 version as 'default' makes sense.
upvoted 0 times
...
Linette
10 months ago
User1: I think option D is the way to go.
upvoted 0 times
...
...
Carlene
11 months ago
What, no option to 'throw the whole thing out and start over'? Guess I'll have to settle for option B - Exclude the 1.2.0 version. Gotta love these Azure multiple-choice questions.
upvoted 0 times
Isadora
9 months ago
User4: Definitely, excluding the 1.2.0 version will make sure everything runs smoothly.
upvoted 0 times
...
Chauncey
9 months ago
User3: Agreed, option B is the most logical solution in this scenario.
upvoted 0 times
...
Jeffrey
9 months ago
User2: Yeah, that seems like the best choice to ensure the 1.1.0 version is used by default.
upvoted 0 times
...
Deja
9 months ago
User1: I think option B is the way to go - Exclude the 1.2.0 version.
upvoted 0 times
...
...
Rikki
11 months ago
Applying a lock? Sounds like a security measure for a secret agent, not an Azure deployment. I'd go with option D - tag the 1.1.0 version as 'default' to make it clear.
upvoted 0 times
...
Precious
11 months ago
Excluding the latest version? That's like trying to live in the past. I'd go with option B - select Exclude from latest for 1.2.0. Keep it simple, you know?
upvoted 0 times
...
Ceola
12 months ago
But wouldn't selecting Exclude from latest for image version 1.2.0 ensure that 1.1.0 is used by default?
upvoted 0 times
...
Chanel
12 months ago
No, I believe we should apply a tag named default to image version 1.1.0.
upvoted 0 times
...
Ceola
12 months ago
I think we should select Exclude from latest for image version 1.2.0.
upvoted 0 times
...

Save Cancel