Your company has decided to build a backup replica of their on-premises user authentication PostgreSQL database on Google Cloud Platform.
The database is 4 TB, and large updates are frequent.
Replication requires private address space communication.
Which networking approach should you use?
Click on the arrows to vote for the correct answer
A. B. C. D.A.
Google Cloud Dedicated Interconnect provides direct physical connections and RFC 1918 communication between your on-premises network and Google's network.
Dedicated Interconnect enables you to transfer large amounts of data between networks, which can be more cost effective than purchasing additional bandwidth over the public Internet or using VPN tunnels.
Benefits: -> Traffic between your on-premises network and your VPC network doesn't traverse the public Internet.
Traffic traverses a dedicated connection with fewer hops, meaning there are less points of failure where traffic might get dropped or disrupted.
-> Your VPC network's internal (RFC 1918) IP addresses are directly accessible from your on-premises network.
You don't need to use a NAT device or VPN tunnel to reach internal IP addresses.
Currently, you can only reach internal IP addresses over a dedicated connection.
To reach Google external IP addresses, you must use a separate connection.
-> You can scale your connection to Google based on your needs.
Connection capacity is delivered over one or more 10 Gbps Ethernet connections, with a maximum of eight connections (80 Gbps total per interconnect)
-> The cost of egress traffic from your VPC network to your on-premises network is reduced.
A dedicated connection is generally the least expensive method if you have a high-volume of traffic to and from Google's network.
https://cloud.google.com/interconnect/docs/details/dedicatedTo replicate an on-premises PostgreSQL database on Google Cloud Platform (GCP), a networking approach must be implemented to facilitate the private address space communication between the on-premises database and the GCP environment.
Option A, Google Cloud Dedicated Interconnect, may not be the best option for this scenario because it is primarily designed to provide a dedicated physical connection between on-premises infrastructure and GCP. This approach is ideal for workloads that require high availability and low latency, but it may not be cost-effective for replicating a 4 TB PostgreSQL database.
Option B, Google Cloud VPN connected to the data center network, is a viable solution for replicating a PostgreSQL database on GCP. This approach establishes a secure VPN connection between the on-premises infrastructure and the GCP environment, allowing for private address space communication between the two environments. The VPN connection can also be configured to ensure secure communication and data encryption, ensuring data confidentiality and integrity.
Option C, using a NAT and TLS translation gateway installed on-premises, is not an ideal solution for replicating a 4 TB PostgreSQL database on GCP. This approach may add complexity and increase the likelihood of errors during the replication process. Additionally, it may not provide the level of security and encryption required for the replication of sensitive data.
Option D, using a Google Compute Engine instance with a VPN server installed connected to the data center network, is a viable solution for replicating a PostgreSQL database on GCP. This approach allows for the establishment of a secure VPN connection between the on-premises infrastructure and the GCP environment, allowing for private address space communication between the two environments. The use of a Compute Engine instance as the VPN server allows for easy scalability and flexibility in terms of configuration and management.
Overall, the best networking approach for replicating a 4 TB on-premises user authentication PostgreSQL database on GCP would be Option B, Google Cloud VPN connected to the data center network, due to its simplicity, cost-effectiveness, and security features.