Question-31: You now hold the position of chief cloud architect at an organisation that already makes use of cloud-based solutions and you work for that organisation. Your firm just completed the acquisition of another business that operates on Google Cloud for its infrastructure. Every business maintains its own own Google Cloud organisation. Every organisation is ensuring that its apps have access to a functional network by using a Shared Virtual Private Cloud, or VPC. There is some duplication in the subnets that are utilised by the two firms. It is necessary for both companies' apps to have connection to a private network in order for the businesses to merge. These apps do not share a subnet with any other ones. You want to provide connection while requiring as little re-engineering as possible. What is it that you ought to do?
A. Set up VPC peering and peer each Shared VPC together.
B. Migrate the projects from the acquired company into your company's Google Cloud organization. Re-launch the instances in your companies Shared VPC.
C. Set up a Cloud VPN gateway in each Shared VPC and peer Cloud VPNs.
D. Configure SSH port forwarding on each application to provide connectivity between applications in the different Shared VPCs.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 1 Explanation: If one VPC's IP range overlaps with another VPC's range, then VPC peering between the two VPCs cannot be formed. C is acceptable since you can set up a VPN that spans all of these VPCs while still only include the IP ranges that are needed by the application. It is stated that these IP ranges do not overlap. These programmes DO NOT share a subnet with one another. In the process of peering, overlapping subnets were observed. Google Cloud does a check during the peering process to see whether or not there are any subnets with overlapping IP ranges between the two VPC networks or any of the networks to which they are peering. Peering cannot be established if there is an overlap in the data. Since a complete mesh connection is built between VM instances, the subnets in the VPC networks that are peering together are not allowed to have overlapping IP ranges. This is because doing so would result in routing problems. I am aware that the subnets where the application is hosted do not overlap, yet because of the overlap, Google Cloud will not allow a VPC peering to take place. This check is performed whenever a VPC subnet is established or an existing subnet's IP range is increased.