Examkin

Question

Difficulty: EasyPlanning Virtual Private Cloud (VPC) Networks and Subnets

A cloud engineer is designing a custom-mode Virtual Private Cloud (VPC) network in Google Cloud that will be connected to an on-premises data center using Cloud VPN. Which design requirement must be met when allocating primary IP address ranges for the subnets?

  1. The primary IP address ranges of the subnets must not overlap with the IP address ranges used in the on-premises network.Answer
  2. B
    Subnets must use overlapping IP address ranges so that default VPC routing can perform automatic network address translation.
  3. C
    Auto-mode VPC creation must be enabled to automatically detect and reassign conflicting IP ranges dynamically.
  4. D
    Firewall rules must be configured with high priority to block conflicting IP traffic before it enters the VPN tunnel.

Answer

The primary IP address ranges of the subnets must not overlap with the IP address ranges used in the on-premises network.
When connecting a Google Cloud VPC to an on-premises network via Cloud VPN or Cloud Interconnect, all subnet IP address ranges must be unique and non-overlapping. Overlapping CIDRs lead to routing conflicts where network packets cannot be properly forwarded.

Step-by-Step Solution

1
Analyze hybrid network connectivity requirements
Identify that Cloud VPN establishes Layer 3 connectivity between Google Cloud VPC subnets and on-premises networks.
Traffic routing between VPCs and local networks requires unambiguous IP destination routes.
2
Evaluate IP address planning rules for Google Cloud VPC subnets
Ensure non-overlapping CIDR blocks are chosen across all connected environments.
Overlapping CIDR blocks create routing ambiguities, preventing packets from reaching their destination.

Key Concept

VPC Subnet IP Address Allocation and Non-Overlapping CIDR Requirements
Rate this question

Topics

Planning Virtual Private Cloud (VPC) Networks and Subnets

More questions from this topic