You are deploying your infrastructure in the us-central1 region. Your on-premises data center is located in New York City, and the Google Cloud region closest to New York City is us-east4. Your…

Question

Options

• ACreate a Cloud Router and VLAN attachments in the us-east4 region attached to your physical
• BCreate a Cloud Router and VLAN attachments in the us-east4 region attached to your physical
• CCreate a Cloud Router in the us-central1 region and VLAN attachments in the us-east4 region
• DCreate a Cloud Router and VLAN attachments in the us-central1 region attached to your physical

• A
  72% (21)
• B
  17% (5)
• C
  3% (1)
• D
  7% (2)

Explanation

When using Cloud Interconnect, VLAN attachments must be placed in the Google Cloud region closest to the interconnect colocation facility to minimize latency. Ashburn, Virginia maps to the us-east4 region, not us-central1. Even though the application infrastructure runs in us-central1, creating the Cloud Router and VLAN attachments in us-east4 ensures the lowest-latency path between the on-premises data center (NYC area) and Google's network. Traffic from us-east4 to us-central1 then travels over Google's fast private backbone, which is more efficient than routing through a mismatched region. Creating attachments in us-central1 would force traffic to traverse additional network hops before reaching the interconnect in Ashburn, increasing latency. Since bandwidth is under 500 Mbps, a single Dedicated Interconnect VLAN attachment is sufficient, keeping costs low.

No community discussion yet for this question.