QuestionQ23

VerifiedConfiguring, implementing and managing a cloud network security solution

You are designing a security-focused network architecture on Google Cloud. Your company has deployed a central inspection VPC containing a fleet of Cloud Next Generation Firewall (NGFW) appliances. The inspection VPC has a default route whose next hop points to the passthrough Network Load Balancer, with NGFW appliances as its backends.

You also have two application VPCs (App-A and App-B) that must not communicate directly with one another, and neither VPC has a default route. You need to make sure that all traffic originating from App-A and App-B is forced through the inspection VPC for analysis by the Cloud NGFW appliances.

What should you do?

Explanation

A Network Connectivity Center hub using star topology separates center and edge spoke route tables. Edge spokes can have routes to center spokes, but Network Connectivity Center prohibits edge-group routes that provide connectivity between different edge spokes. Making the inspection VPC a center spoke and App-A and App-B edge spokes therefore sends their default-routed traffic to the inspection VPC and prevents direct App-A-to-App-B routing. A static route in a VPC spoke can use an internal passthrough Network Load Balancer in another spoke as its next hop when the relevant NCC connectivity requirements are met.

Learn more

Community Discussion

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