AZ-300 Exam QuestionsBrowse all questions from this exam

AZ-300 Exam - Question 75


HOTSPOT -

You have an on-premises data center and an Azure subscription. The data center contains two VPN devices. The subscription contains an Azure virtual network named VNet1. VNet1 contains a gateway subnet.

You need to create a site-to-site VPN. The solution must ensure that is a single instance of an Azure VPN gateway fails, or a single on-premises VPN device fails, the failure will not cause an interruption that is longer than two minutes.

What is the minimum number of public IP addresses, virtual network gateways, and local network gateways required in Azure? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

Hot Area:

Exam AZ-300 Question 75
Show Answer
Correct Answer:
Exam AZ-300 Question 75

Box 1: 4 -

Two public IP addresses in the on-premises data center, and two public IP addresses in the VNET.

The most reliable option is to combine the active-active gateways on both your network and Azure, as shown in the diagram below.

Exam AZ-300 Question 75

Box 2: 2 -

Every Azure VPN gateway consists of two instances in an active-standby configuration. For any planned maintenance or unplanned disruption that happens to the active instance, the standby instance would take over (failover) automatically, and resume the S2S VPN or VNet-to-VNet connections.

Box 3: 2 -

Dual-redundancy: active-active VPN gateways for both Azure and on-premises networks

References:

https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable

Discussion

50 comments
Sign in to comment
Mathew
Jan 15, 2020

Every Azure VPN gateway consists of two instances in an active-standby configuration. For any planned maintenance or unplanned disruption that happens to the active instance, the standby instance would take over (failover) automatically, and resume the S2S VPN or VNet-to-VNet connections. The switch over will cause a brief interruption. For planned maintenance, the connectivity should be restored within 10 to 15 seconds. For unplanned issues, the connection recovery will be longer, about 1 minute to 1 and a half minutes in the worst case. So I think active-standby will be good enough one Public IP , one VPN gateway and two local gateways.

Daren
Mar 5, 2020

Correct. I started to believe that I`m the only one thinking like this. Thanks!

Explen
Jun 30, 2020

Me too, i was scrolling down looking for this same explanation.

hihedij
Jun 2, 2020

I suppose 3 PIP will be use. First - for VPN gateway, second and third for local network gateways. "2. The local network gateways corresponding to your VPN devices must have unique public IP addresses in the "GatewayIpAddress" property." https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable#multiple-on-premises-vpn-devices

binroon
Jun 29, 2020

I agree with your explanation. But I think it's 2 PIP (one for VPN gateway, one for local network gateway), one VPN gateway and one local gateway.

binroon
Jun 29, 2020

wrong answer. it's 1-1-2. in the solution, it must at least use 1 VPN gateway, 2 VPN devices, thus 2 local network gateways of course. 2 PIPs for VNP devices are not Azure resources.

binroon
Jun 29, 2020

wrong answer. it's 1-1-2. in the solution, it must at least use 1 VPN gateway, 2 VPN devices, thus 2 local network gateways of course. 2 PIPs for VNP devices are not Azure resources.

Explen
Jun 30, 2020

Me too, i was scrolling down looking for this same explanation.

praveen97
Jul 17, 2020

Agree with Mathew. See the below link for additional details. https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable#multiple-on-premises-vpn-devices

mohitchandan
Dec 4, 2021

For unplanned issues, the connection recovery will be longer, about 1 to 3 minutes in the worst case https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable#about-vpn-gateway-redundancy

Ekramy_Elnaggar
Dec 15, 2019

the question said "In Azure" , so: 2 Public IPs , 1 VPN Gateway in active/active config , 2 Local Network Gateways I already implemented this before.

simonxinyu
Feb 4, 2020

Question is "What is the minimum number of public IP addresses, virtual network gateways, and local network gateways required in Azure?" , which means 3 resources all in Azure.

sameer2803
Apr 16, 2020

you are missing this line "the failure will not cause an interruption that is longer than two minutes.". they are ok with a downtime of 2mins so we don't have to be active-active.

Shades
Oct 29, 2020

yes, thats why 1 Public IP should be enough

Shades
Oct 29, 2020

yes, thats why 1 Public IP should be enough

vossglass
Oct 31, 2020

Microsoft publishes another VPN Gateway in the background for failover

shayer0
Feb 7, 2020

It should be 1 Virtual network gateway (in active/stand-by mode as they can tolerate 2 minutes interruption), so one Azure IP as well. And 2 Local network Gateways. The IPs for these 2 local network gateways are not Azure IP, they are VPN device IPs. so answers is: 1-1-2

Daren
Mar 5, 2020

This is correct. I had to read all the dumb shit above to get to this clear explanation.

Gjferweb
Mar 26, 2020

It also say the minimum, no most reliable, so i go with active pasive gtw which can tolerate at most 1:30 min at most

Happiman
Mar 6, 2020

1 Public IP address 1 Active/Standby VPN Gateway 2 Local Network Gateways

Tino
Apr 10, 2020

guys, i think that 1 public IP for the active/standby setup will be enough for the requirements: "For any planned maintenance or unplanned disruption that happens to the active instance, the standby instance would take over (failover) automatically, and resume the S2S VPN or VNet-to-VNet connections. The switch over will cause a brief interruption. For planned maintenance, the connectivity should be restored within 10 to 15 seconds. For unplanned issues, the connection recovery will be longer, about 1 minute to 1 and a half minutes in the worst case." https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable#multiple-on-premises-vpn-devices With active/active: no downtime, 2 IPs, 1 gateway and 2 local gateways with active standby:a max of 1 min and a half in downtime (lesser than requirements), 1 IP, 1 gateway and 2 local gateways

petermogaka91
May 27, 2020

the question do we factor in the 2 ips for the local gateways(this are for the on prem vpn devices). I think the question is vague here. one can argue 3ips or 1ip since we all use put them in Azure

SunnyAU
Aug 23, 2020

I saw the same ambiguity in the question as well. My interpretation, while the 2 IPs for the LNG are required as configuration items in Azure, they are not PIP resources defined in Azure. So technically, in Azure you only need 1 Public IP (or PIP) for a Vpn GW in Active/Standby with regards to the amount in question.

petermogaka91
May 27, 2020

the question allows less than 2 mins downtime hence active/standby for this case.

SunnyAU
Aug 23, 2020

I saw the same ambiguity in the question as well. My interpretation, while the 2 IPs for the LNG are required as configuration items in Azure, they are not PIP resources defined in Azure. So technically, in Azure you only need 1 Public IP (or PIP) for a Vpn GW in Active/Standby with regards to the amount in question.

maheshyadav
Dec 5, 2019

You need only 1 Gateway (Azure VPN gateway in an active-active configuration, and create two local network gateways and two connections for your two on-premises VPN devices as described above. The result is a full mesh connectivity of 4 IPsec tunnels between your Azure virtual network and your on-premises network) This will provide full active-active connection

Adrian1405
Nov 29, 2019

I would say that the correct answer is 3 Public IP address. The best fits Multiple on-premises VPN devices scenario https://docs.microsoft.com/pt-br/azure/vpn-gateway/vpn-gateway-highlyavailable

Benkyoujin
Jan 4, 2020

2, 2, 2 - https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-activeactive-rm-powershell

Benkyoujin
Jan 4, 2020

Sorry, just 2 gateway. But link above shows this clearly.

jayrush
Mar 16, 2020

This same question was in AZ103 and answer is 2,2,2

macco455
Aug 10, 2020

It seems half the people on this thread missed the part where it says AZURE side, so we do not need to take into account the 2 Public IPs needed for the on premesis VPN devices. Just need to account for them when setting up the Local Network Gateway. WIth this said, the Correct answer is: 1 (Azure) IP address 1 Virtual network gateway (uses the IP) 2 Local network gateways (one for each remote VPN device)

princeali
Jun 26, 2020

3-1-2 is correct answer for this. 3: 2 ( 2 local gws need 1 Pubip each so, total 2) + 1 ( pubip for active instance only) 1: just need 1 azure VPN gateway with active - passive HA (fail over takes max 1 min 30 sec) 2: Local device needs its own local gw. so total 2 Local GW needed

Gianlucag77
Jun 30, 2020

no it is wrong, active/passive (the default configuration) is enought see Multiple on-premises VPN devices https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable#activestandby

Albelev
Jul 1, 2020

3x IP, 1x VPN Gateway, 2x local VPN with public IP each. https://docs.microsoft.com/en-gb/azure/vpn-gateway/vpn-gateway-highlyavailable#multiple-on-premises-vpn-devices

gboyega
Jul 12, 2020

2 1 2 you only need 2 Public IP addresses from Azure When configuring the VPN gateway, we set it to Active Active instead of Active Passive We then create 2 LNG for the 2 VPN devices on-prem

gboyega
Jul 15, 2020

More clarity is in this docs https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-activeactive-rm-powershell check out Part 2

wlfjck
Jan 2, 2020

You only need 1 public IP address in azure, refer to below https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable For planned maintenance, the connectivity should be restored within 10 to 15 seconds. For unplanned issues, the connection recovery will be longer, about 1 minute to 1 and a half minutes in the worst case. So the correct answer should be 1. 1 IP 2. 2 Gateway instances

kavvaru
Jan 11, 2020

I would go further and say, only need 1 gateway that needs to be created. According to the doc "Every Azure VPN gateway consists of two instances in an active-standby configuration". This supports the failover recovery under 2 minutes. Azure manages the standby gateway instance behind the scenes, but need only one gateway created by the user. The question says how many vpn gateways, not how many gateway instances. Overall it is a terribly vaguely composed question.

Prash85
Jun 16, 2020

Going over question: condition 1: minimum number (not maximum) Condition 2: required in Azure. So answer is 1 1 2

poohtt
Jul 26, 2020

1) 3 2) 1 3) 2 Explanation: 1) 1 IP for virtual network gateway which works in active-standby mode. "The Azure VPN gateway will allocate a single IP address from the GatewaySubnet range for active-standby VPN gateways" 2 IP for local network gateway (BgpPeerIpAddress) 2) As I wrote active-standby mode requires only 1 gateway. 3) 2 local network gateways, because we have 2 on-prem vpn devices https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-vpn-faq#what-address-does-azure-vpn-gateway-use-for-bgp-peer-ip

MMohammad
Sep 17, 2020

The correct answer is: 1 Public IP address 1 Virtual network gateway 2 Local network gateways Description: 1 Public IP address - Each VPN gateway has two instances, one in active and one in standby. If one instance goes down, we would still have the other one available. Hence, we just need one Virtual Network gateway resource. And for this we just need to one Public IP address resource. 1 Virtual network gateway - Each VPN gateway has two instances, one in active and one in standby. If one instance goes down, we would still have the other one available. Hence, we just need one Virtual Network gateway resource. 2 Local network gateways - Here we would need to have two VPN devices registered on the client side. This would ensure that if one of the client VPN devices were to fail, you would still have another one available. For this we need to register two Local network gateways.

Rajyahoo
Sep 27, 2020

"What is the minimum number of public IP addresses, virtual network gateways, and local network gateways required in Azure?" The question is about resources in Azure, not both azure and on-prem. It should be : 1 PIP 1 Virtual GW 1 Local GW If active-active is not selected when Virtual GW is created , it automatically creates in Active-standby. One pip will do here. For unplanned issues, the connection recovery will be longer, about 1 minute to 1 and a half minutes in the worst case. (well with-in SLA stated) Ref: https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable

sallymaher
Dec 3, 2020

Agree question said less than 2 mins and Active -Standby is fit here so 1 PIP , 1 GW and 1 Local GW , BTW the other choices which said 2 vpn GW are wrong you can't setup more than one Virtual GW but you can have 2 instances

Subhijith
Oct 12, 2020

1,1,2 Each VPN gateway has two instances, one in active and one in standby. If one instance goes down, we would still have the other one available. Hence, we just need one Virtual Network gateway resource. And for this we just need to one Public IP address resource.

Jinder
Jan 4, 2021

To save time for others, Copy pasting from above and its absolutely correct answer: 3-1-2 is correct answer for this. 3: 2 ( 2 local gws need 1 Pubip each so, total 2) + 1 ( pubip for active instance only) 1: just need 1 azure VPN gateway with active - passive HA (fail over takes max 1 min 30 sec) 2: Local device needs its own local gw. so total 2 Local GW needed So the answer is 3 IPs, 1 VPN gateway, 2 Local Gateways

nguyenhung1121990
May 3, 2021

correct

dumpmaster
Nov 22, 2019

Is 4: https://docs.microsoft.com/pt-br/azure/vpn-gateway/vpn-gateway-highlyavailable

silverdeath
Mar 26, 2020

from doc we have : For planned maintenance, the connectivity should be restored within 10 to 15 seconds. For unplanned issues, the connection recovery will be longer, about 1 minute to 1 and a half minutes in the worst case ( so here we are in the active/passive mode we need only one public IP) + The local network gateways corresponding to your VPN devices must have unique public IP addresses in the "GatewayIpAddress" property ( here we need 2 public IPs) so the total is 3 IPs, one Virtual gateway + 2 local network gateways

Gorha
Apr 2, 2020

3 IP addresses: One for the two virtual gateways that are deployed in active-passive, when one fails the other takes over using the same IP address. Two IP addresses for the local gateways. 2 virtual gateways, active-passive 2 local gateways representing on premises

poohtt
Jul 26, 2020

Correct, except second item. We need only one gateway. Every virtual network gateway works in active-stanby mode. No need to create the second one.

milind8451
Apr 17, 2020

You need 4 Public IPs on Azure, as 2 needed for VPN Gateway and 2 for Local gateway (These 2 IP are actually of on-prem VPN devices). 2 VPN Gateway and 2 Local gateways are required for high availability on Azure. If they didn't mention high availability of VPN Gateway then only 1 can do the job in practical way.

andyR
Aug 30, 2020

milind8451 - you are correct

joilec435
Apr 22, 2020

4 2 2 for active active you can do 2 ips per gateway

denkes
Jun 8, 2020

Agree with 1, 1, 2. See also Ms Docs: ... Topic: Change an active-standby gateway to an active-active gateway The following example converts an active-standby gateway into an active-active gateway. When you change an active-standby gateway to active-active, you create another public IP address, then add a second Gateway IP configuration.... https://docs.microsoft.com/th-th/azure/vpn-gateway/vpn-gateway-activeactive-rm-powershell#change-an-active-standby-gateway-to-an-active-active-gateway

bharatgudu
Jun 13, 2020

the correct answer is 1 1 2.. Please give some thought into this and some comments above has some good links. The key is it could be achieved using Active-Standby set up and the set up at on premise are not considered Azure resources.

bharatgudu
Jul 5, 2020

Too bad I cannot change my previous comments. I have landed (again) as 2, 2, 2. https://docs.microsoft.com/en-ca/learn/modules/connect-on-premises-network-with-vpn-gateway/2-connect-on-premises-networks-to-azure-using-site-to-site-vpn-gateways I think even in the Active - Stand By case, it will require to have each VPN Gateway to have its own Public IP and Virtual Network Gateway and Local Network gateway. Because to me VPN gateway consists of these three and when the question says the VPN Network Gateway goes down, I presume a set of these go down. and that activates the stand by. The above link explains this and this is my final take. It also says that we cannot really see the standby configuration anyway in Azure so it might give a false idea that it is running with lower number of resources.

X_L
Jul 10, 2020

As a downtime of 2 minutes is acceptable, a single gateway in A/P mode will suffice, bringing the total count to: 3 PIP's / 2 LNG's / 1 VNG

Ausias18
Jul 22, 2020

This question appeared in my AZ-104 exam

dips31089
Aug 6, 2020

This link below has the solution- https://docs.microsoft.com/pt-br/azure/vpn-gateway/vpn-gateway-highlyavailable#multiple-on-premises-vpn-devices Downtime of 1 - 1.5 mins. Answer is-- 1 Azure public IP address (other public address are for on-prem - gateway IP, BGP Peer IP ) 1 Virtual network gateway (uses the IP) 2 Local network gateways (one for each remote VPN device)

Qudzie
Aug 9, 2020

Hi Guys I will go with; A: 1 Public IP address B: 1 VNG (Default has 2 instances active-standby) C: 2 Local Gateways (connects to on-prem) https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable (About Azure VPN gateway redundancy) & (Multiple on-premises VPN devices) Every Azure VPN gateway consists of two instances in an active-standby configuration. For any planned maintenance or unplanned disruption that happens to the active instance, the standby instance would take over (failover) automatically, and resume the S2S VPN or VNet-to-VNet connections. The switch over will cause a brief interruption. For planned maintenance, the connectivity should be restored within 10 to 15 seconds. For unplanned issues, the connection recovery will be longer, about 1 minute to 1 and a half minutes in the worst case. For P2S VPN client connections to the gateway, the P2S connections will be disconnected and the users will need to reconnect from the client machines. On-Prem the failover is managed by your local VPN devices. The question though is asking about Azure if I understand it correct in Active-Standby mode. My thoughts welcome to correct me.

arseyam
Aug 14, 2020

The correct answer is 1 public IP address, 1 virtual network gateway and 2 local gateways. Since a downtime of 2 min is accepted then an Active/Passive virtual network gateway is enough which means we need only 1 public IP address. As per Microsoft, the connection recovery shouldn't take more than 1 and half minutes in the worst case scenario. https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable

groy
Aug 30, 2020

PUBLIC IP ADDRESS: 4 VIRTUAL N/W GATEWAY: 2 LOCAL N/W GATEWAY: 2

VikasA
Aug 31, 2020

I think It should be one vpn gateway (Behind the scenes there is actually 2 used ). So only one public IP is needed in azure. When you create local gateway , you just state public ip of your on premises devices (So public ip is not utilized in azure just stated in azure).In the event of vpn gateway failure , standby instance can take over between 15 seconds to 90 seconds. So answer will be- one VPN gateway one public IP Two local gateways. https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable

bc5468521
Sep 17, 2020

3,1,2 is the right answer

[Removed]
Jan 5, 2020

2-2-2 Benkyoujin is correct, here is the good link https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-activeactive-rm-powershell

thirstylion
Mar 14, 2020

Dual redundancy is the most reliable option as suggested. As per that I think the answers are correct.

DeveshSolanki
Jul 8, 2020

PUBLIC IP ADDRESS: 4 VIRTUAL N/W GATEWAY: 2 LOCAL N/W GATEWAY: 2

Luiza
Jul 12, 2020

Correct answer is: 3, 1 ,2 The question asks for a minimum of IP, VNG and LNG with a tolerance of 2 minutes of interruption. Then an active-standby would solve. https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable

nabylion
Jul 13, 2020

1:1:2. Active/standby is enough. Only critical mission solutions requires investment in highest availability and crossed tunnels.

KCjoe
Jul 24, 2020

active standby is correct, the maintenance window is within 90 seconds, which satify the requirement (2 min)

KCjoe
Jul 24, 2020

Active/Standby - "For unplanned issues, the connection recovery will be longer, about 1 minute to 1 and a half minutes in the worst case. " https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable

basak
Aug 15, 2020

https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable seems to be 2, 1,2

matie
Sep 9, 2020

For me, the answer of 1 public ip address, 2 virtual and 2 local gateways satisfies the question: "What is the minimum number of public IP addresses, virtual network gateways, and local network gateways required in Azure? " And an active passive AZ vpn gateway set up satisfies the requirement that "The solution must ensure that is a single instance of an Azure VPN gateway fails, or a single on-premises VPN device fails, the failure will not cause an interruption that is longer than two minutes." https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable

faozio
Sep 9, 2020

This is so wrong What is the minimum number of public IP addresses, virtual network gateways, and local network gateways required in Azure? The question specifically said Azure? I have personally labbed this ... When active - active mode is activated on a VPN Gateway, it would have 2 PIP. To create a highly available architecture with two on-premises devices then... 4 connections 1 with PIP 1 to VPN A on-premises connections 2 with PIP 1 to VPN A on-premises connections 3 with PIP 3 to VPN B on-premises connections 4 with PIP 1 to VPN B on-premises Since the LNG have same public endpoint we would need only 2 of them... The correct answer is 2 1 2 Again...The subscription contains an Azure virtual network named VNet1 Looking at that statement, only 1 VPN gateway is allowed in a VNET

faozio
Sep 9, 2020

Apologies, there was no way to edit... We need 4 connections connection 1 with PIP 1 to VPN A on-premises connection 2 with PIP 2 to VPN A on-premises connection 3 with PIP 1 to VPN B on-premises connection 4 with PIP 2 to VPN B on-premises

saran1987
Sep 10, 2020

Understand the existing infrastructure and the requirement. Existing: Two on prem VPN device and 1 Azure Vnet Gateway (This consists one active and standby be default) Requirement: the failure will not cause an interruption that is longer than two minutes Ans: You need 2 public IP for the VPN devices so that you can configure two local network gateway. You need one public IP for your VPN gateway (it has active and standby mode by default so you dont need two VPN gateways for the failover). So 3 public IP and 1 VPN gateway and 2 local Network Gateway

saran1987
Sep 10, 2020

Another reason why we dont need active-active is in the question they clearly mentioned as it shoudn't fail or interrupt not more than 2 minutes. So just active-standby mode is enough for this requirement. The answer given states the mode of active-active which is not required for a flexibility upto 2 minutes failure.

saran1987
Sep 10, 2020

Just onething, if they meant the public IP on in Azure, it should be just 1. I considered both onprem and Azure public IP so it will be 3. In the question they noted as what resources are needed in Azure so it should be 1 public IP which is for Vnet gateway

saran1987
Sep 10, 2020

Just onething, if they meant the public IP on in Azure, it should be just 1. I considered both onprem and Azure public IP so it will be 3. In the question they noted as what resources are needed in Azure so it should be 1 public IP which is for Vnet gateway

Bart78
Sep 17, 2020

3 pub IP's (2x on premise, 1 for the active/standby VPN Gateway (1 - 1.5 minute downtime, questions states max 2 minutes) and 2 local Network Gateways (one for each on premise pub IP

prince_norman_maximus
Sep 18, 2020

2,1,2 https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable#activestandby The configuration described here is "Multiple on-premises VPN devices"

andyR
Sep 18, 2020

Given answer correct refer - Dual-redundancy: active-active VPN gateways for both Azure and on-premises networks

ihustle
Oct 29, 2020

Why one public IP? Shouldn't there be two; one for the on-premise network and one for the azure network?

jasu
Dec 5, 2020

Question is about to resource requirement in Azure; not in on-prem network. This is an Active-Standby at Azure side since 2min down time is mentioned. For Active-Standby, 1 IP, 1 Virtual Network and 2 Local Network (from two VPN Gateways) need to be created.

OsimIndia
Jan 2, 2021

Here is the correct answer : 2,1,2. refer this link https://docs.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-highlyavailable

Showkat
Dec 25, 2021

The questions says required in Azure, I believe its 3 public addresses, 1 IP will be created during the LNG creation and then 2 IPS are required to configure with LNG's, seems its 3, 1, 2.