This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Can an administrator use the Azure NAT Gateway service to configure inbound connections handling?
No. You can’t use Azure NAT Gateway to configure inbound connections handling.
Yes. Azure NAT Gateway provides options to configure inbound connections handling.
Yes. However, you need to install an add-on.
In a deployment, an Azure VM with a public IP assigned is placed in the subnet to which the Azure NAT Gateway service is assigned. Will the public IP address be used after Azure NAT Gateway deployment?
No. The public IP address won’t be used after Azure NAT Gateway is deployed.
Yes. The public IP address is used, but only for inbound connections.
No. The public IP address will be removed from the Azure VM after Azure NAT Gateway is deployed.
A virtual network has four subnets. Azure VMs within these subnets frequently experience port exhaustion. An administrator decides to deploy the Azure NAT Gateway service. How many instances of Azure NAT Gateway should they deploy?
The administrator should deploy four instances of Azure NAT Gateway.
A multiple subnets scenario isn’t supported with Azure NAT Gateway.
Only one instance of Azure NAT Gateway is needed.
Configuring an Azure NAT Gateway service requires configuring a public IP address as well. Is it mandatory to create both a public IP address object and public IP prefix object?
No. It isn’t mandatory to create any IP object.
Yes. You need to create both objects.
You don’t need to create both objects. Only one object is mandatory.
You must answer all questions before checking your work.
Continue
Was this page helpful?