HOTSPOT -
You have a virtual network named VNet1 that has the configuration shown in the following exhibit.
Use the drop-down menus to select the answer choice that completes each statement based on the information presented in the graphic.
NOTE: Each correct selection is worth one point.
Hot Area:
Box 1: add an address space -
Your IaaS virtual machines (VMs) and PaaS role instances in a virtual network automatically receive a private IP address from a range that you specify, based on the address space of the subnet they are connected to. We need to add the 192.168.1.0/24 address space.
Box 2: add a network interface -
The 10.2.1.0/24 network exists. We need to add a network interface.
Reference:
https://docs.microsoft.com/en-us/office365/enterprise/designing-networking-for-microsoft-azure-iaas
- Add an address space - Add a subnet
Agree: Add an Address Space and then Add a subnet. Just tested it on the Portal and worked :)
No you can't add 10.2.1.0/24 because it overlaps with 10.2.0.0/16. Check on Lab
No, I am wrong I am adding 10.2.1.0/24 in address space however it already exists. I need to add a subnet. I get confuse between address spaces and subnets.
Address spaces there can be more than one per vNET; Subnets are subsets of the address spaces, there can be more than a subnet for each address space.
I tested this in the lab. Box 1: Add an address space - explanation: One can add additional address space (192.168.0.0/16) to the VNet1, without having to delete existing (10.2.0.0/16). Box 2: Add subnet - explanation: Defined 'default' subnet from image example (10.2.0.0/24) contains 254 IP addresses, with last IP being 10.2.0.254. In order to assign 10.2.1.0/24 IP address to VM we need to create add new subnet.
Also wrong, the subnet range being created is 10.2.0.0 - 10.2.0.255 . So if you want to add an IP address from 10.2.1.0/24 you need to add a new subnet. Why are so many of these wrong?
don't you mean that the vnet range originally created is 10.2.0.0 - 10.2.255.255?
so what?... if you don't have any subnet how can you use those IPs?... Throw is correct!
There is no dissent. Throw says the initial _subnet_ is 10.2.0.0 - 10.2.0.255. You say the initial vnet _address space_ is 10.2.0.0 - 10.2.255.255. Both is true. However, in the first question you have to _first_ add an address space. (and then a subnet) In the second question you only have to add a subnet as 10.2.1.0/24 is within the vnet's address range 10.2.0.0/16
Yeah there's tons, dunno how anyone is passing, lol.
Using these questions to provoke research and learn the material, not memorise answers, which is ridiculous
How do we invoke MODERATER to validate these?? someone must check.
ya its true and examtopics team is doing nothing for this issue.
Some of them are obviously wrong and not getting corrected. It looks like this service is intentionally kind of paired with MS behind the scenes, to force us learn on dumps instead of us trying to learn dumps answers by hard.
There are other similar dumps on the internet which have incorrect answers. My best guess is the base for these questions come from what the Exam Topics team was able to find online. From that base their moderators can update the questions and community can vote on what looks like the best option. Personally, I like to be able to read everyone's comments and read through the additional information and viewpoints. Some of the questions are just bad in general and I like knowing I'm not the only one who thinks they're bad.
1. Add an address space 2. Add a subnet Laboratory tested 100%
definitly on test, i missed the first one. put delete a subnet by mistake
Have been seeing you comment quite a bit on here, thanks for the heads up! Hopefully you have picked up your certificate by now.
- A1: Add an address space - A2: Add a subnet Is correct!
First Answer: delete subnet Explanation: Current IP Address Range of VNET1 is 10.2.0.0/16 with subnet 10.2.0.0/24. We want VM1 to get IP from 192.168.1.0/24. In order to do that we need to change the IP address range of VNET1. We can not add a new IP address range on existing one. I see so many comments add an address space. 1.Delete Subnet 10.2.0.0/24 2.Change the IP range Address Range in Address Space from 10.2.0.0/16 to 192.168.0.0/16 3.Add Subnet with 192.168.1.0/24 Second Answer: Add Subnet The new Subnet with address10.2.1.0/24 is in the range of IP Address range of VNET1 10.2.0.0/16(10.2.0.0 to 10.2.255.255)
1 is wrong. One CAN add/remove/update address ranges. https://learn.microsoft.com/en-us/azure/virtual-network/manage-virtual-network#add-or-remove-an-address-range
The only subnet in the vnet is of address range 10.2.0.0/24 So address range usable for any VM is 10.2.0.4 to 10.2.0.254 For assigning the IP from the space 10.2.1.0/24 you need a subnet with that IP range.
Right is - Add an address space - Add a subnet
The VNET's address space is set to 10.2... How are you going to add a 192. subnet to a 10.2 VNET? You have to tear down the existing VNET by deleting the subnet and redoing the address space to a 192... Then add subnet for the second question.
To allow a virtual machine on VNet1 to receive an IP address from 192.168.110/24, you must first add a network interface. To allow a virtual machine on VNet1 to receive an IP address from 10.2.1.0/24, you must first add a subnet.
Please correct me if I am wrong. Box 1 should be "Delete Subnet". Without that not possible to edit the address space. Tested in lab
you are right, vm cant get the 192 ip space until you delete and create the vnet
- Add an address space - Add a subnet
Add a network Interface, Add a Subnet. NIC's are added to VM's by default, no need to add one
This was on my exam. The correct answer is provided by vojehol452.
to add /modify a address space, we need to delete the existing subnet (otherwise it will not allow to modify address space)
OpenAI "Before a virtual machine on VNet1 can receive an IP address from 192.168.1.0/24, you must first add a subnet. This is because the current address space of VNet1 is 10.2.0.0/16, which does not include the 192.168.1.0/24 address range. Before a virtual machine on VNet1 can receive an IP address from 10.2.1.0/24, no further action is required as this address range falls within the existing address space of VNet1 (10.2.0.0/16) and a subnet with the required address prefix can be created within this address space."
In don't even know what to believe anymore
ANS1: add an address space ANS2: add a subnet