Answer-first summary for fast verification
Answer: Configure the project with Cloud VPN., Configure the project with Cloud Interconnect.
The question requires connecting from Google Cloud Compute Engine instances to on-premises workloads while ensuring access is restricted to the private company network. Cloud VPN (A) establishes secure, encrypted IPsec VPN tunnels between Google Cloud and on-premises networks, keeping traffic within the private network. Cloud Interconnect (C) provides dedicated, high-performance connections (via Dedicated Interconnect or Partner Interconnect) that bypass the public internet, ensuring private connectivity. These options align with the requirement of restricting access to the private network. Shared VPC (B) is for sharing VPC networks across Google Cloud projects, not for on-premises connectivity. VPC peering (D) connects VPC networks within Google Cloud, not to on-premises. Private Access (E) enables Google Cloud services to access resources without public IPs but does not facilitate on-premises connections. The community discussion, with 100% consensus and upvoted comments, strongly supports A and C as the correct answers, citing Google Cloud documentation that these are the primary methods for secure on-premises connectivity.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
A company has workloads in an on-premises server room that must only be accessible from its private internal network. You need to connect to these workloads from Compute Engine instances in a Google Cloud project.
Which two approaches can you use to meet this requirement? (Choose two.)
A
Configure the project with Cloud VPN.
B
Configure the project with Shared VPC.
C
Configure the project with Cloud Interconnect.
D
Configure the project with VPC peering.
E
Configure all Compute Engine instances with Private Access.
No comments yet.