Examkin

Soru

Zorluk: KolayConfiguring Network Topology and VPC Infrastructure

An enterprise architecture team is configuring network connectivity between two VPC networks, vpc-analytics and vpc-core, in Google Cloud. They decide to establish VPC Network Peering to allow internal IP address communication across the two networks. Which TWO statements accurately describe the requirements and behavior of VPC Network Peering in this scenario? (Select TWO.)

  1. Peering configuration must be created symmetrically in both directions—from vpc-analytics to vpc-core and from vpc-core to vpc-analytics—before communication is fully established.Cevap
  2. Exporting and importing custom routes must be explicitly enabled on the peering configurations if custom static or dynamic routes need to be shared across the peered networks.Cevap
  3. C
    Traffic from vpc-analytics can transitively reach a third network, vpc-management, by routing through vpc-core if vpc-core is peered to vpc-management.
  4. D
    HA VPN should be used instead of VPC Network Peering whenever inter-VPC traffic requirements exceed 100 Gbps within the same Google Cloud region.
  5. E
    Standard IAM permissions applied to instances in vpc-analytics automatically prevent unauthorized data copy operations to Cloud Storage buckets in vpc-core without needing security perimeter controls.

Cevap

VPC Network Peering requires symmetrical peering setup in both directions and explicit configuration of custom route import/export settings to share non-subnet routes.
VPC Network Peering is established only when both VPC networks create a peering request to each other (symmetrical configuration). Additionally, while subnet routes are exchanged automatically upon peering, sharing custom dynamic or static routes across peered VPCs requires explicitly configuring the import and export custom routes flags on both ends.

Adım Adım Çözüm

1
Analyze VPC Network Peering setup requirements.
VPC Peering requires both network administrators to establish a peering configuration pairing both VPCs (bidirectional setup).
Peering stays in an inactive state until both VPCs explicitly approve the peering request.
2
Evaluate route propagation rules across peered VPC networks.
Subnet routes are exchanged by default, but custom dynamic and static routes require setting import and export custom route flags.
Cloud Router dynamic routes and static routes are not automatically shared without explicitly enabling custom route exchange.
3
Identify invalid VPC networking assumptions.
Reject transitive routing, lower-bandwidth HA VPN alternatives for intra-cloud high throughput, and relying solely on IAM for perimeter security.
VPC Network Peering is non-transitive, HA VPN has throughput caps per tunnel (3 Gbps), and VPC Service Controls are necessary to prevent data exfiltration.

Anahtar Kavram

VPC Network Peering establishing bilateral setup, non-transitivity, and custom route exchange mechanisms.
Bu soruyu puanla

Konular

Configuring Network Topology and VPC Infrastructure

Bu konudan daha fazla soru