DRAG DROP
You have a solution deployed into a virtual network in Azure named fabVNet. The fabVNet virtual network
has three subnets named Apps, Web, and DB that are configured as shown in the exhibit. (Click the
Exhibits button.)
You want to deploy two new VMs to the DB subnet.You need to modify the virtual network to expand the size of the DB subnet to allow more IP addresses.
Which three steps should you perform in sequence? To answer, move the appropriate actions from the list
of actions to the answer area and arrange them in the correct order.
Answer: See the explanation
Explanation:
Box 1: Empty and delete the DB Subnet.
Box 2: Create the DB subnet to be larger.
Box 3: Recreate the Virtual Network as now required.
Note (which seems to indicate that only two steps would be required):
* Q: Can I modify my virtual network size after I created them?
A: You can add, remove, expand or shrink a subnet if there are no VMs or services deployed within it by
using PowerShell cmdlets or the NETCFG file.
* Q: Can I modify subnets after I created them?A: You can modify the subnet addresses as long as there are no services or VMs deployed within them by
using PowerShell cmdlets or the NETCFG file. You cannot modify or delete a subnet once services or VMs
have been deployed to it.Virtual Network FAQ
If you make DB Larger , the IP addresses will overlap with WEB
To make DB Larger it will need to be deleted,
WEB can be reconfigured to the larger IP address range
Create DB to the Larger IP addresses
0
0
I don’t see how there will be an overlap with the Web segment. That Segment comes before the DB segment.
Question is :> shouldn’t we adjust the VN before adjusting the DB subnet. Then again: “Recreate” a VN seems rather destructive.
0
0
ok lets see:-
Apps /26 – 10.0.0.0 – 10.0.0.63
Web /29 – 10.0.0.64 – 10.0.0.71
DB /29 – 10.0.0.72 – 10.0.0.79
Resources
App:-
fabapps 1 = 10.0.0.4
DB:-
Fabdb1 = 10.0.0.76
fabdb2 = 10.0.0.77
Web:-
$vc2webrole_in_0 = 10.0.0.68
We can not use ip addresses from app 10.0.0.0 – 10.0.0.63 part of App
If we increase DB to /28, which would increase to 16 ip address range 10.0.0.64 to 79 or use the next 10.0.0.80 to 95. Cannot use 64 – 79 as it overlaps with WEB 10.0.0.64 to 10.0.0.71.
So DB will use the 80 to 95 ip range, as you cannot change a Subnet with resources allocated , will need to be empty & deleted DB , Create DB with larger subnet in the 10.0.0.80 to 95 range , Not sure what the 3rd step is,
ip addresses from 72 – 79 will not be part of the subnets
0
0
For reference on Subnets
https://docs.microsoft.com/en-us/azure/virtual-network/virtual-networks-faq
0
0