ExamTopics Logo
Mail Us[email protected]
Menu
Microsoft Discussions
exam questions

Exam AZ-104 All Questions

View all questions & answers for the AZ-104 exam
Go to Exam

Exam AZ-104 topic 1 question 26 discussion

Actual exam question from Microsoft's AZ-104
Question #: 26
Topic #: 1
[All AZ-104 Questions]

Note: The question is included in a number of questions that depicts the identical set-up. However, every question has a distinctive result. Establish if the solution satisfies the requirements.
Your company's Azure subscription includes two Azure networks named VirtualNetworkA and VirtualNetworkB.
VirtualNetworkA includes a VPN gateway that is configured to make use of static routing. Also, a site-to-site VPN connection exists between your company's on- premises network and VirtualNetworkA.
You have configured a point-to-site VPN connection to VirtualNetworkA from a workstation running Windows 10. After configuring virtual network peering between
VirtualNetworkA and VirtualNetworkB, you confirm that you are able to access VirtualNetworkB from the company's on-premises network. However, you find that you cannot establish a connection to VirtualNetworkB from the Windows 10 workstation.
You have to make sure that a connection to VirtualNetworkB can be established from the Windows 10 workstation.
Solution: You download and re-install the VPN client configuration package on the Windows 10 workstation.
Does the solution meet the goal?

  • A. Yes
  • B. No
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️
by godchild at April 24, 2022, 7:18 a.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
NaoVaz
Highly Voted 9 months ago
Selected Answer: A
"If you make a change to the topology of your network and have Windows VPN clients, the VPN client package for Windows clients must be downloaded and installed again in order for the changes to be applied to the client."
upvoted 42 times
jackdryan
2 years, 4 months ago
A is correct
upvoted 4 times
...
...
Benjam
Highly Voted 2 years, 1 month ago
I have done this at work many times A is correct.
upvoted 11 times
...
NicoVick
Most Recent 3 weeks, 4 days ago
Selected Answer: A
a is correct
upvoted 1 times
...
gurungde
1 month ago
Selected Answer: B
downloading and re-installing the VPN client configuration on windows 10 will help only in updating the configuration to connect to VNet-A but here the issue is in routing with VNet-B.
upvoted 1 times
...
Helpnosense
3 months, 3 weeks ago
Selected Answer: B
Need to update configuration then redownload and reinstall the VPN client.
upvoted 1 times
...
ea4b48e
4 months, 1 week ago
Selected Answer: B
The solution provided of downloading and re-installing the VPN client configuration package on the Windows 10 workstation is not likely to meet the goal. The issue here likely stems from the fact that when you establish a point-to-site VPN connection to VirtualNetworkA, the client configuration package does not automatically update to include routes to any newly peered virtual networks, in this case, VirtualNetworkB. To resolve this, you would need to update the VPN client configuration package to include the new routes. Therefore, the correct answer is: B. No
upvoted 3 times
...
bhaskarraobaipothu
6 months ago
Selected Answer: B
Enable Remote Gateway Usage: Ensure that the peering between VNet A and VNet B is correctly configured. Enable Allow Gateway Transit on the peering for VNet A. Enable Use Remote Gateway on the peering for VNet B. Configure Routing: Add the necessary routes to ensure that the Windows 10 workstation can route traffic to VNet B. This can be done by: Configuring custom routes in Azure Route Tables. Ensuring that the Windows 10 workstation (or the VPN client) has routes to VNet B. You may need to manually add these routes to the VPN client or configure them in Azure's route tables.
upvoted 2 times
...
Mark74
6 months, 2 weeks ago
Selected Answer: A
A is correct , refresh correct routes
upvoted 1 times
...
tsummey
9 months ago
Selected Answer: B
B is correct. The question implies that the Windows 10 workstation should access both VirtualNetworkA and VirtualNetworkB. The scenario says that VirtualNetworkA and VirtualNetworkB are peered, and the Windows 10 workstation has a site-to-site VPN connection with VirtualNetworkA, so you need to turn on the Allow gateway transit option on VirtualNetworkA Downloading and re-installing the VPN client configuration package on the Windows 10 workstation won't fix the problem of connecting to VirtualNetworkB from the workstation.
upvoted 1 times
...
[Removed]
9 months, 3 weeks ago
Selected Answer: A
A is correct
upvoted 1 times
...
pooh0805
1 year, 8 months ago
Selected Answer: B
Downloading and re-installing the VPN client configuration package on the Windows 10 workstation is unlikely to resolve the issue of not being able to establish a connection to VirtualNetworkB from the Windows 10 workstation. This issue is related to the configuration of the VPN client and routing, and simply re-installing the client configuration package is unlikely to address the underlying problem.
upvoted 1 times
...
abinnnnnnnnnn
1 year, 10 months ago
No, downloading and re-installing the VPN client configuration package on the Windows 10 workstation is not the right solution to establish a connection to VirtualNetworkB from the Windows 10 workstation1. To establish a connection to VirtualNetworkB from the Windows 10 workstation, you need to enable the Allow gateway transit setting on VirtualNetworkA and the Use remote gateways setting on VirtualNetworkB23. This will allow VirtualNetworkB to use the VPN gateway in VirtualNetworkA for connectivity purposes, and the Windows 10 workstation will be able to establish a connection to VirtualNetworkB through the point-to-site VPN connection to VirtualNetworkA
upvoted 2 times
...
dhivyamohanbabu
1 year, 12 months ago
Option A is correct
upvoted 1 times
...
Madbo
2 years, 2 months ago
The solution in option A as YES (downloading and re-installing the VPN client configuration package on the Windows 10 workstation) may resolve the issue of not being able to establish a connection to VirtualNetworkB from the Windows 10 workstation. This is because when a VPN gateway is configured to use static routing, it may require updating the VPN client package configuration after making changes to the VPN gateway, such as adding a virtual network peering. Therefore, downloading and re-installing the VPN client configuration package on the Windows 10 workstation could potentially fix the issue.
upvoted 1 times
...
lokii9980
2 years, 2 months ago
B. No, downloading and re-installing the VPN client configuration package on the Windows 10 workstation is unlikely to resolve the issue of not being able to connect to VirtualNetworkB. This is because the issue seems to be related to the virtual network peering between VirtualNetworkA and VirtualNetworkB, and not with the VPN client configuration on the Windows 10 workstation. A more appropriate solution would be to check the virtual network peering configuration, and ensure that the appropriate routes are in place to allow traffic to flow between VirtualNetworkA and VirtualNetworkB. Additionally, checking the network security groups and the Azure Firewall rules can help ensure that traffic is allowed to flow from the Windows 10 workstation to VirtualNetworkB.
upvoted 4 times
...
habbey
2 years, 2 months ago
I agree. A is correct based on MSC documentation.
upvoted 1 times
...
Shajeecool
2 years, 4 months ago
Selected Answer: A
Correct answer is A
upvoted 1 times
...
Load full discussion...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel