An enterprise engineering team is deploying a secure subnetwork for internal Compute Engine virtual machines that are configured without external IP addresses. The applications running on these instances require access to Google Cloud APIs (such as Cloud Storage) and also require outbound access to external third-party repositories for software updates without allowing inbound connections from the internet. Which TWO network topology configurations must be implemented in the Virtual Private Cloud (VPC) network to satisfy these connectivity requirements?
- Enable Private Google Access on the subnetwork where the virtual machines are deployed.Answer
- Configure Cloud NAT associated with a Cloud Router on the VPC network for outbound internet connectivity.Answer
- CCreate a VPC Network Peering connection between the workload VPC network and Google API services network.
- DAttach Cloud Armor security policies directly to the subnetwork interface to permit outbound HTTP/HTTPS traffic.
- EProvision a Dedicated Interconnect connection to route all outbound internet update traffic through an on-premises network.
Answer
The required configurations are enabling Private Google Access on the subnetwork and configuring Cloud NAT with a Cloud Router on the VPC network.
Enabling Private Google Access on the subnet provides private connectivity to Google Cloud APIs for instances without public IPs. Configuring Cloud NAT with Cloud Router allows these instances to establish outbound-only connections to third-party repositories on the internet for updates without exposing them to inbound internet traffic.
Step-by-Step Solution
Key Concept
Configuring Private Google Access and Cloud NAT for internal VPC network topologies
Estimated Time:1m 0s