- 2 перегляди
Exam
Answer confirmed
Preamble
Your on-premises network has an IP address range of 10.0.0.0/23.
You have an Azure virtual network named VNet1 that contains a virtual machine named VM1.
VNet1 has an IP address range of 10.0.1.0/24.
Question
You need to deploy a Site-to-Site (S2S) VPN to connect the on-premises network to VNet1.
What should you do first?
Proposed answer
- A. Deploy Azure Bastion to VNet1.
- B. Deploy Azure Extended Network.
- C. Configure VNet1 to use the IP address range of 10.0.2.0/24.
- D. Configure VNet1 to use an IP address range of 10.0.1.128/25.
Suggested answer
C. Configure VNet1 to use the IP address range of 10.0.2.0/24.
Correct answer
The suggested answer is correct
Due to the fact, that two virtual networks is overlapping, to connect the on-premises network to VNet1 you need to change network IP address, so they will not overlap.
Ni_yot
3 weeks, 1 day ago
To determine if the subnets **10.0.0.0/23** and **10.0.1.0/24** overlap, we need to analyze their IP address ranges. 1. **Subnet 10.0.0.0/23**: - The /23 CIDR notation means it has a subnet mask of 255.255.254.0. - The range of addresses for this subnet is: - **Start**: 10.0.0.0 - **End**: 10.0.1.255 2. **Subnet 10.0.1.0/24**: - The /24 CIDR notation means it has a subnet mask of 255.255.255.0. - The range of addresses for this subnet is: - **Start**: 10.0.1.0 - **End**: 10.0.1.255 ### Overlap Analysis - The range of **10.0.0.0/23** is **10.0.0.0 to 10.0.1.255**. - The range of **10.0.1.0/24** is **10.0.1.0 to 10.0.1.255**. Since the range **10.0.1.0 to 10.0.1.255** falls within the range of **10.0.0.0/23**, these two subnets **do overlap**. Specifically, the overlapping addresses are from **10.0.1.0 to 10.0.1.255**.
upvoted 1 times
Ksk08
3 weeks, 6 days ago
C is correct
upvoted 1 times
sardonique
3 months, 1 week ago
Answer is C, it is a no brainer. Do some math, 10.0.0.0/23 overlaps to the whole vNet range. you can check it on a free online IP calculator.
upvoted 2 times
Krayzr
4 months, 1 week ago
Selected Answer: C
Change IP so IPs are not conflicting.
upvoted 1 times
PrettyFlyWifi
5 months, 1 week ago
Selected Answer: C
This has overlapping IP ranges, but there is no requirement to maintain the same IP addresses for both on-premises and Azure host VMs, so it's C for me, as it's a separate range. IF you had to maintain the IPs, then the extended network would win here.
upvoted 2 times
AK_1234
6 months, 1 week ago
Answer C
upvoted 2 times
SIAMIANJI
6 months, 3 weeks ago
Selected Answer: C
Since your on-premises network has an IP address range of 10.0.0.0/23 and VNet1 currently has an IP address range of 10.0.1.0/24, which overlaps with the on-premises network, you need to change the IP address range of VNet1 to ensure that it does not overlap with the on-premises network. Therefore, the correct option is: C. Configure VNet1 to use the IP address range of 10.0.2.0/24.
upvoted 3 times
Kuikz
7 months, 2 weeks ago
Selected Answer: C
there is an overlap in the ranges 10.0.0.0/23 and 10.0.1.0/24 as the 10.0.1.0/24 range is entirely contained within the 10.0.0.0/23 range.
upvoted 1 times
pnewcap
7 months, 2 weeks ago
is it C or D ?
upvoted 1 times
AlexFlorea
7 months, 3 weeks ago
Selected Answer: C
C. Configure VNet1 to use the IP address range of 10.0.2.0/24. This step ensures that there are no overlapping IP ranges between the on-premises network and the Azure virtual network, which is essential for a successful S2S VPN connection.
upvoted 1 times
Lionred
7 months, 3 weeks ago
Answer is B because of the overlapping of address. On-prem has the range of 10.0.0.0 - 10.0.127.255 Azure VNet1 has the range of 10.0.1.0 - 10.0.1.255 Azure Extended Network can work with overlapping address ranges
upvoted 2 times