QuestionQ27

VerifiedPlanning and implementing a cloud solution

Your company is migrating its entire workload to Compute Engine. Some servers need to be reachable from the Internet, while others should be reachable only over the internal network. All servers must be able to communicate with each other over specific ports and protocols.

The current on-premises network design uses:

  • A demilitarized zone (DMZ) for the public-facing servers
  • A Local Area Network (LAN) for the private servers

You need to design the Google Cloud networking infrastructure to match these requirements. What should you do?

Explanation

A single VPC with one subnet for the public-facing (DMZ) servers and one for the private (LAN) servers connects all instances through the automatically created subnet routes, so no peering or VPN is needed. Because VPC networks have an implied deny-ingress rule, you then create ingress allow rules for the required ports and protocols between the DMZ and LAN subnets, plus a separate ingress allow rule from 0.0.0.0/0 that targets only the DMZ instances (which also need external IP addresses). Ingress (not egress) rules are what control whether external clients can reach a server from the Internet, which is what 'reachable from the Internet' requires. Using two separate VPCs (as in choices C and D) would require additional connectivity mechanisms such as VPC Network Peering or Cloud VPN/Interconnect to let the DMZ and LAN servers communicate, adding unnecessary complexity compared to using subnets and firewall rules within a single VPC.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!