Topic 1 Question 91
Your company's infrastructure is on-premises, but all machines are running at maximum capacity. You want to burst to Google Cloud. The workloads on Google Cloud must be able to directly communicate to the workloads on-premises using a private IP range. What should you do?
In Google Cloud, configure the VPC as a host for Shared VPC.
In Google Cloud, configure the VPC for VPC Network Peering.
Create bastion hosts both in your on-premises environment and on Google Cloud. Configure both as proxy servers using their public IP addresses.
Set up Cloud VPN between the infrastructure on-premises and Google Cloud.
ユーザの投票
コメント(17)
I believe D is the right answer
👍 54SIX2020/06/04Correct Answer is (D):
Access internal IPs directly Your VPC network's internal (RFC 1918) IP addresses are directly accessible from your on-premises network with peering, no NAT device or VPN tunnel required.
Hybrid made easy Today’s business climate demands flexibility. Connecting your on-premises resources to your cloud resources seamlessly, with minimum latency or interruption, is a business-critical requirement. The speed and reliability of Cloud Interconnect lets you extend your organization’s data center network into Google Cloud, simply and easily, while options such as Cloud VPN provide flexibility for all your workloads. This unlocks the potential of hybrid app development and all the benefits the cloud has to offer.
In the graphic below: What GCP Connection is right for you? shows clearly what is the method for extend your on premise network (IP Private communication). What GCP Connection is right for you? https://cloud.google.com/hybrid-connectivity
👍 30ESP_SAP2020/08/17On-premise -> GCP There are 2 ways
- Cloud VPN
- Interconnect Since we have VPN as an option, others is not recommended
👍 3ARVII2021/12/18
シャッフルモード