Exam 70-741 topic 1 question 70 discussion

The command New-NetNatIpAddress does not exist!

Q.70 You connect VM2 to Private1 and External1. Run New-NetNatIpAddress and the New-NetNat cmdlets on VM2. Configure VM1 to use VM2 as the default gateway  No Q.71 You connect VM1 to Internal1. Run New-NetNatIpAddress and the New-NetNat cmdlets on Server1. Configure VM1 to use Server1 as the default gateway  No Q.72 You connect VM2 to Private1 and External1. Install the Remote Access server on VM2 and configure NAT in the Routing and Remote Access console. Configure VM1 and VM2 as the default gateway  No Q.85 You connect VM2 to Private1 and External1. Install the Remote Access server on VM2, configure NAT in the Routing and Remote Access console. Configure VM1 to use VM2 as the default gateway  Yes Q.137 You connect VM1 to Internal1. Run New-NetNatIpAddress and the New-NetNat cmdlets on server 1. Configure VM1 to use VM2 as the default gateway  No

Answer is correct however I think the command they're looking for is: New-NetIPAddress, not New-NetNatIPAddress (it doesn't exist). The New-NetIPAddress commands allows you to specify an address, along with a default gateway.

This question and the follow up of them were on my exam, they were the first questions on my exam. My exam was November 27th 2020.

Answer is B. Though you run New-NetNatIpAddress and the New-NetNat on Server 1 instead of VM2, you must run New-VMSwitch before running them.

You need to implement all of this on the Hyper-V Host - not a VM. Hence the answer is no.

Answer is B, the PS scripts are okay, only that they are implemented on the wrong machine, otherwise you are supposed to NAT the server1 that is hosting those VMs

No as server/host does not have RRAS (Routing) role, can't do NAT without it. 2 scenarios are correct: 1. VM2 connected to Pvt NW (same as VM1) as well as Ext NW. VM2 acts as Default Gateway and NAT for VM1.VM2 must have RRAS installed. 2. VM1 connected to Int NW so it can talk to host. Server/Host acts as Default Gateway and NAT for VM1. Server/Host must have RRAS installed.

TMW.... New-NetNatIpAddress is not a valid PowerShell command, the actual command is New-NetIPAddress Reference: https://docs.microsoft.com/en-us/powershell/module/nettcpip/new-netipaddress?view=win10-ps

I have this setup in my home lab. You would need to run the New-NetNatIpAddress and the New-NetNat cmdlets on Server1 (VMHost) for VM1. Then VM1 would be able to use NAT to reach the outside. Imagine VM1 on a 10.78.3.0 subnet (within VMHost Server1), and it needs to translate to the 172.16.0.0 subnet. (outside) (server1 will need a nic for each subnet) Then Server1 will need to be configured to be the NAT server itself. VM2 is already on the outside 172.16.0.0 subnet, which is why this will not work.

I just saw question #85 where Remote Access Services was installed prior to the NAT configuration. This makes sense, as VM2 needs to provide routing services.

I don't get why the solution shouldn't work here. If VM1 is connected to the same private switch as VM2 it should be able to communicate with VM2. The NetNat commands on VM2 should be used on a multihomed computer which VM2 provides. VM2 then could route packets to the corporate network.