Module 3: Network Topologies

Looking for ‘Networking in Google Cloud: Network Architecture Module 3 Answers’?

In this post, I provide complete, accurate, and detailed explanations for the answers to Module 3: Network Topologies of Course 5: Networking in Google Cloud: Network ArchitecturePreparing for Google Cloud Certification: Cloud Security Engineer Professional Certificate.

Whether you’re preparing for quizzes or brushing up on your knowledge, these insights will help you master the concepts effectively. Let’s dive into the correct answers and detailed explanations for each question!

Quiz.

Graded Assignment

1. You are designing a Google Cloud network for a large financial services company with strict security requirements. The network needs to isolate sensitive customer data from other resources and limit communication between specific network segments. Which of the following network topologies would be most suitable for this scenario?

  • Gated ingress and egress ✅
  • Mesh
  • Hub-and-spoke
  • Mirrored

Explanation:
A gated ingress and egress topology is ideal for scenarios requiring strict segmentation and isolation. It allows for:

  • Controlled entry (ingress) and exit (egress) points for traffic.
  • Tight access control policies around sensitive environments.
  • Limited or no direct communication between segments unless explicitly allowed.

2. You are migrating a large ecommerce company's existing on-premises data center to Google Cloud. The on-premises network consists of geographically dispersed regional offices, each with its own network segment requiring secure isolation. However, central management and communication between all regional offices are critical for business operations. Which network topology would most effectively address these requirements in Google Cloud?

  • Hub-and-spoke ✅
  • Gated ingress and egress
  • Mesh
  • Mirrored

Explanation:
The hub-and-spoke topology is designed for scenarios that require:

  • Centralized management (via the hub VPC).
  • Controlled communication between spoke VPCs (regional offices).
  • Security policies and services (like firewalls, NAT, proxies) in the hub.

Leave a Reply