Answer-first summary for fast verification
Answer: The more specific VPC subnet route is taking priority.
The issue arises from the route prioritization in the VPC. The on-premises router advertises a broad range (10.0.0.0/8) that includes the database server's IP (10.2.1.25). However, the newly created VPC subnet (10.2.0.0/16) is more specific than the on-premises route. In Google Cloud, more specific routes are preferred over less specific ones. Therefore, traffic to the database server is now being routed to the VPC subnet instead of the on-premises network, causing the application to lose connectivity to the database. This makes option B the correct answer as it accurately describes the most likely cause of the problem.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
One of your company's applications stopped working after a network change window. The application relies on an on-premises database server (IP: 10.2.1.25) that is no longer receiving traffic. The only change implemented was the creation of three new VPC subnets: 10.1.0.0/16, 10.2.0.0/16, and 10.3.1.0/24. The on-premises router advertises the 10.0.0.0/8 network.
What is the most likely cause of this issue?
A
The less specific VPC subnet route is taking priority.
B
The more specific VPC subnet route is taking priority.
C
The on-premises router is not advertising a route for the database server.
D
A cloud firewall rule that blocks traffic to the on-premises database server was created during the change.