Exam AZ-104 topic 1 question 31 discussion

Set-AzureStaticVNetIP is for Classic VMs and will be retired on September 1, 2023. For new VM it can be don in the portal or using Powershell: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/reset-network-interface #Add/Change static IP. This process will change MAC address $vnet = Get-AzVirtualNetwork -Name $VNET -ResourceGroupName $ResourceGroup $subnet = Get-AzVirtualNetworkSubnetConfig -Name $subnet -VirtualNetwork $vnet $nic = Get-AzNetworkInterface -Name $NetInter -ResourceGroupName $ResourceGroup #Remove the PublicIpAddress parameter if the VM does not have a public IP. $nic | Set-AzNetworkInterfaceIpConfig -Name ipconfig1 -PrivateIpAddress $PrivateIP -Subnet $subnet -PublicIpAddress $publicIP -Primary $nic | Set-AzNetworkInterface

Correct Answer E: Run the Set-AzureStaticVNetIP PowerShell cmdlet.

The answer is E. You cannot set vm ip addy via Azure portal > VM > properties blade It would have to be Azure portal > VM > network settings blade

E. Set-AzureStaticVNetIP is correct answer Why other options are incorrect: A. New-AzureRMVMConfig Used to configure VM parameters, not networking/IP settings. B. Set-AzureSubnet Not a valid cmdlet for configuring VM IPs. C. Modify the VM properties in the Azure Portal While partially true, you don’t assign static IPs directly in VM properties, but in the network interface settings, so this isn’t the most accurate answer in the context of the options. D. Modify the IP properties in Windows Network and Sharing Center Azure assigns dynamic IPs unless you reserve them at the NIC level — setting IPs manually inside the OS causes conflicts and is unsupported. This cmdlet is used to assign a static private IP to an Azure VM's network interface (for the old Azure Service Manager model).

E is Correct Answer

E is the correct answer

Set-AzureStaticVNetIP is from the Azure Service Management (ASM or "Classic") model, and it has been deprecated in favor of the Azure Resource Manager (ARM) model — which is what most deployments use today.

Set-AzureStaticVNetIP (Classic VMs only – Deprecated)

I will vote for C as well. We the command for Option E is already deprecated. I dont think so that they will be evaluating on old content. https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-networks-static-private-ip?tabs=azureportal

In VM settings, we need to go to Networking to make the required changes. C is the correct answer. Set-AzureStaticVnetIP is not a valid option, as that cmdlet was part of the classic model, which is now deprecated. The correct cmdlet is Set-AzNetworkInterface.

Take help from copilot or chatgpt

To configure Azure virtual machines (VMs) with static internal IP addresses, the best approach is to use the Set-AzureStaticVNetIP PowerShell cmdlet. This allows you to assign a static private IP address to the VM within the Azure virtual network (VNet).

To configure static internal IP addresses for Azure VMs, you need to set the IP address configuration directly in the Azure portal or using Azure PowerShell/CLI.

There is no Set-AzureStaticVNetIP anymore. But if there was, I would say that the correct answer should be C & E

C is the closest answer, but the change is done within Settings, not Properties. https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/virtual-networks-static-private-ip?tabs=azureportal In the following steps, you change the private IP address static for the VM created previously: In the portal, search for and select Virtual machines. In Virtual machines, select myVM from the list. On the myVM page, under Settings, select Networking.

Answer is E. You cannot edit the properties in the VM Overview --> Properties. The command might be old but this is probably an old question

E. Run the Set-AzureStaticVNetIP PowerShell cmdlet. --- Explanation: To configure a static internal IP address for Azure VMs in the same virtual network, you need to use the Set-AzureStaticVNetIP PowerShell cmdlet. This cmdlet allows you to assign a specific private IP address to a virtual machine's network interface within a subnet.