Your company just completed the acquisition of Altostrat (a current GCP customer)
Each company has a separate organization in GCP and has implemented a custom DNS solution.
Each organization will retain its current domain and host names until after a full transition and architectural review is done in one year.
These are the assumptions for both GCP environments.
" Each organization has enabled full connectivity between all of its projects by using Shared VPC.
" Both organizations strictly use the 10.0.0.0/8 address space for their instances, except for bastion hosts (for accessing the instances) and load balancers for serving web traffic.
" There are no prefix overlaps between the two organizations.
" Both organizations already have firewall rules that allow all inbound and outbound traffic from the 10.0.0.0/8 address space.
" Neither organization has Interconnects to their on-premises environment.
You want to integrate networking and DNS infrastructure of both organizations as quickly as possible and with minimal downtime.
Which two steps should you take? (Choose two.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.CD.
Given the assumptions, the two organizations have separate DNS solutions and use the same IP address range (10.0.0.0/8) except for the bastion hosts and load balancers. The objective is to integrate networking and DNS infrastructure with minimal downtime.
Option A: Provision Cloud Interconnect to connect both organizations together This option is not ideal because it requires more effort and cost to set up and maintain an interconnect. It is not necessary to connect the two organizations directly, as they can share resources through shared VPC.
Option B: Set up some variant of DNS forwarding and zone transfers in each organization This option is a good approach because it allows for a seamless integration of DNS infrastructure with minimal downtime. DNS forwarding can be configured to forward requests from one DNS server to the other, and zone transfers can be used to synchronize DNS records between the organizations.
Option C: Connect VPCs in both organizations using Cloud VPN together with Cloud Router This option is not necessary since the organizations are already connected through Shared VPC, and both organizations already allow inbound and outbound traffic from the 10.0.0.0/8 address space.
Option D: Use Cloud DNS to create A records of all VMs and resources across all projects in both organizations This option is not recommended as it requires manually creating A records for each VM and resource in both organizations. It would be time-consuming and error-prone.
Option E: Create a third organization with a new host project, and attach all projects from your company and Altostrat to it using shared VPC. This option is not necessary since the organizations can share resources through shared VPC, and it would add unnecessary complexity to the architecture.
Therefore, the recommended options for integrating networking and DNS infrastructure with minimal downtime are:
Option B: Set up some variant of DNS forwarding and zone transfers in each organization Option C: Connect VPCs in both organizations using Cloud VPN together with Cloud Router (optional, if not already done)