@@AGuideToCloud : I agree with @Jami Susijärvi as NIC1 and NIC2 are provided with private IP address, pointing to 2 different subnets. Also it is mentioned that we need to keep the communication. If NIC2 has to communicate to Public IP then, We may have remove NIC2 and assign Public IP to it, since the 2 subnets are part of same VNET, the communication will not be disturbed and public internet will be enabled but in the answer 3 it doesn't mention to recreate NIC2 with public IP so I guess that is not the answer. If the vm is created with a Size where it can have 3 NICs then closest possibility is answer 2, to assign public IP to 3rd NIC and add the inbound rule.
@@AGuideToCloud : Sorry for the confusion, I figured it out and you are right. A public and private IP (both) can be associated with a NIC. The bonding is created internally but eth0 interface with respective mac id doesn't reference the public IP while checking from inside the VM which is strange. It only shows the association with private IP. Anyways, a good tutorial and great work. Much appreciated!
Question 6, Why adding third nic with public ip address with inbound security rule is incorrect?
@Jami Susijärvi I've provided the explanation for why option 3 was correct ;)
@@AGuideToCloud : I agree with @Jami Susijärvi as NIC1 and NIC2 are provided with private IP address, pointing to 2 different subnets. Also it is mentioned that we need to keep the communication. If NIC2 has to communicate to Public IP then, We may have remove NIC2 and assign Public IP to it, since the 2 subnets are part of same VNET, the communication will not be disturbed and public internet will be enabled but in the answer 3 it doesn't mention to recreate NIC2 with public IP so I guess that is not the answer. If the vm is created with a Size where it can have 3 NICs then closest possibility is answer 2, to assign public IP to 3rd NIC and add the inbound rule.
Thanks for the suggestion @Jami Susijärvi & @subinjohn babu!
@@AGuideToCloud : Sorry for the confusion, I figured it out and you are right. A public and private IP (both) can be associated with a NIC. The bonding is created internally but eth0 interface with respective mac id doesn't reference the public IP while checking from inside the VM which is strange. It only shows the association with private IP.
Anyways, a good tutorial and great work. Much appreciated!
Congratulations for this excellent content, thank you so much!
Glad you enjoy it!
Question No.6 Why would you require Public IP to NIC2 ?
thank you for sharing
@Jason Chen Thanks for watching!
Thanks
Welcome
Red fonts are very difficult to read. Change the color of the fonts to white and post the video again.
Question 9: isn't NAT rule also correct
depends
Gross how much DNS is on the exam lol? Man this part is getting me.