Don't forget to create account on our site to get access to more material made only for free registered user.  

Azure 70-532 Azure 70 533

Question 4: You have created a subnet with the 100's of instances and other resources. And you are planning to use more services but you run out of IP addresses on the only subnet of your virtual network. What can you do to correct this?

A. You must delete the existing subnet and re-create it with more than current IP addresses.

B. Just add the more IP addresses to the existing subnet.

C. Add a new subnet, and add new VMs to the new subnet.

D. Add a new subnet, migrate all resources to the new subnet, and then delete the old subnet.

1.  A,C

2. C,D

3.  B,C

4.  A,D

Correct Answer : 2 Exp : You can always add a new subnet. With Windows Azure, you can create virtual machines in much the same way as you do on premises using Hyper-V. The difference here is that by default when you create a new Windows Azure VM it is assigned an IP address that unique to the Azure cloud infrastructure. Leveraging Windows Azure virtual networking allows us to create virtual subnets using the IPv4 semantics we choose and are familiar with. It also allows you to create multiple subnets for the purposes of segregating services. For example, if you are creating a multi-tiered application, you can create a subnet for your front end services, another subnet for your logic tier, and another for your data tier. In addition, enabling Windows Azure virtual networks is required to enable cross-premises network connectivity between your virtual machines hosted in Windows Azure and your infrastructure located on-premises.Windows Azure virtual networks are deployed as an overlay network in the Windows Azure cloud and can be configured as isolated, cloud-only networks. Optionally you can easily extend your on-premises network to the cloud using virtual networking and site-to-site VPN. As it is implemented today, it is difficult to make changes to virtual networks after they have been configured, so it is a good idea to plan carefully for your given deployment scenario. For example, today if you implement a Windows Azure virtual network and later choose to add site-to-site VPN connectivity, you will have to delete any virtual machines associated with the virtual network before adding the site-to-site gateway. Also, IP address assignment is handled by DHCP. However, the lease duration is infinite so unless you completely stop (deallocate) a virtual machine the system should retain its assigned IP address for the lifetime of the VM. As such, manually assigning a static IP address to a Windows Azure virtual machine is not necessary, and furthermore it is not supported either. 

You have no rights to post comments