Examkin

Soru

Zorluk: KolayConfiguring Network Topology and VPC Infrastructure

An network administrator is setting up a hub-and-spoke VPC architecture in Google Cloud. The environment consists of three custom mode VPC networks: `vpc-hub`, `vpc-spoke-1`, and `vpc-spoke-2`. Peering is configured between `vpc-hub` and `vpc-spoke-1`, and between `vpc-hub` and `vpc-spoke-2`. No direct peering exists between `vpc-spoke-1` and `vpc-spoke-2`. Which two statements regarding communication and configuration in this VPC network topology are correct? (Select TWO.)

  1. Virtual machine instances in `vpc-spoke-1` cannot communicate directly with instances in `vpc-spoke-2` through `vpc-hub` because VPC Network Peering is non-transitive.Cevap
  2. Establishing a functional VPC Network Peering connection requires explicit peering configuration setup in both participating VPC networks.Cevap
  3. C
    Instances in `vpc-spoke-1` automatically route traffic to `vpc-spoke-2` through `vpc-hub` as long as global dynamic routing mode is enabled on `vpc-hub`.
  4. D
    Dedicated Interconnect must be provisioned between `vpc-spoke-1` and `vpc-spoke-2` to allow private IP address communication between two VPC networks in Google Cloud.
  5. E
    Establishing VPC Network Peering automatically enforces security perimeters that prevent data exfiltration to external Google Cloud projects.

Cevap

VPC Network Peering is non-transitive, meaning traffic cannot traverse an intermediate VPC to reach another peered network. Furthermore, VPC Network Peering connections are bidirectional and must be explicitly configured in both VPC networks for route exchange to function.
VPC Network Peering in Google Cloud is non-transitive by design. If VPC A is peered with VPC B, and VPC B is peered with VPC C, instances in VPC A cannot communicate with instances in VPC C unless a direct peering connection between A and C is established. Additionally, peering configuration is bidirectional: both VPC networks must configure a peering request targeting each other for the connection to become active.

Adım Adım Çözüm

1
Analyze the peering topology
`vpc-spoke-1` is peered to `vpc-hub`, and `vpc-hub` is peered to `vpc-spoke-2`.
Identify the network connection pathways and peering endpoints.
2
Evaluate transitivity in GCP VPC Network Peering
Recognize that GCP VPC Peering routes are not advertised transitively from `vpc-spoke-1` through `vpc-hub` to `vpc-spoke-2`.
Google Cloud VPC Network Peering explicitly restricts transitive routing across intermediate VPC networks.
3
Evaluate VPC Network Peering setup requirements
Confirm that a peering relationship requires creating peering connections from both network sides.
Peering is bidirectional and remains in an inactive state until both sides approve and configure the connection.

Anahtar Kavram

VPC Network Peering Non-Transitivity and Bidirectional Setup
Bu soruyu puanla

Konular

Configuring Network Topology and VPC Infrastructure

Bu konudan daha fazla soru