Cloud Interconnect for dedicated connections in GCP - Step-by-Step Execution

Process Flow - Cloud Interconnect for dedicated connections

Request Dedicated Connection

↓

Google Provisioning Link

↓

Customer Sets Up Router

↓

Establish BGP Sessions

↓

Traffic Flows Over Dedicated Link

↓

Monitor & Manage

This flow shows how a dedicated Cloud Interconnect connection is requested, provisioned by Google, configured by the customer, and then used for traffic.

Execution Sample

GCP

1. Request dedicated connection
2. Google provisions physical link
3. Customer configures router
4. Establish BGP sessions
5. Traffic flows securely

Steps to set up a dedicated Cloud Interconnect connection between customer network and Google Cloud.

Process Table

Step	Action	Result	Next Step
1	Customer requests dedicated connection	Google schedules physical link provisioning	Google provisions link
2	Google provisions physical link	Physical fiber link established	Customer configures router
3	Customer configures router with VLAN and BGP	Router ready to exchange routes	Establish BGP sessions
4	BGP sessions established	Routing information exchanged	Traffic flows over link
5	Traffic flows over dedicated link	Secure, high-bandwidth connection active	Monitor and manage connection
6	Monitor and manage connection	Connection health and usage tracked	Ongoing operation

💡 Process completes when dedicated connection is active and monitored

Status Tracker

Variable	Start	After Step 2	After Step 4	Final
Physical Link Status	Not provisioned	Provisioned	Provisioned	Provisioned and active
Router Configured	No	No	Yes	Yes
BGP Session	Not established	Not established	Established	Established
Traffic Flow	None	None	Active	Active

Key Moments - 2 Insights

Why does the customer need to configure their router after Google provisions the link?

Because Google only provides the physical link; the customer must set up VLANs and BGP sessions to exchange routing information, as shown in steps 3 and 4 of the execution_table.

What happens if BGP sessions are not established?

Without BGP sessions (step 4), routing information won't be exchanged, so traffic cannot flow over the dedicated link (step 5).

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the physical fiber link established?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Check the 'Result' column for step 2 in the execution_table.

According to variable_tracker, when does the BGP session become established?

A After Step 2

B After Step 4

C After Step 3

D At Start

💡 Hint

Look at the 'BGP Session' row and see when it changes to 'Established'.

If the customer skips router configuration, what will be the impact on traffic flow?

A Traffic will flow normally

B Google will configure the router automatically

C Traffic flow will be blocked

D Physical link will not be provisioned

💡 Hint

Refer to steps 3 and 5 in execution_table and router config status in variable_tracker.

Concept Snapshot

Cloud Interconnect dedicated connections provide a private, high-speed link between your network and Google Cloud.
1. Request connection
2. Google provisions physical link
3. Customer configures router with VLAN and BGP
4. BGP sessions exchange routes
5. Traffic flows securely
Monitor connection health continuously.

Full Transcript

Cloud Interconnect for dedicated connections involves requesting a private physical link from Google. Google provisions the fiber link. The customer then configures their router with VLANs and BGP sessions to exchange routing information. Once BGP is established, traffic flows securely over the dedicated link. The connection is monitored for health and usage. This process ensures a reliable, high-bandwidth connection between customer infrastructure and Google Cloud.

Practice

1. What is the main purpose of Cloud Interconnect in Google Cloud?

easy

A. To provide a private and fast connection between your on-premises network and Google Cloud

B. To host virtual machines in Google Cloud

C. To store data in Google Cloud Storage

D. To manage user permissions in Google Cloud

Solution

1. Step 1: Understand Cloud Interconnect's role

   Cloud Interconnect is designed to create private network connections between your physical data center and Google Cloud.

2. Step 2: Identify the correct purpose

   Among the options, only private and fast connection matches Cloud Interconnect's function.

3. Final Answer:

   To provide a private and fast connection between your on-premises network and Google Cloud -> Option A

4. Quick Check:

   Cloud Interconnect = Private fast connection [OK]

Hint: Cloud Interconnect connects your network privately to Google Cloud [OK]

Common Mistakes:

• Confusing Cloud Interconnect with storage or VM services
• Thinking it manages user permissions
• Assuming it hosts virtual machines

2. Which of the following is the correct order to set up a Dedicated Cloud Interconnect connection?

easy

A. Create a Cloud Router, then an Interconnect, then an Interconnect Attachment

B. Create an Interconnect, then a Cloud Router, then an Interconnect Attachment

C. Create an Interconnect Attachment, then a Cloud Router, then an Interconnect

D. Create a Cloud Router, then an Interconnect Attachment, then an Interconnect

Solution

1. Step 1: Recall the setup sequence

   First, you create the physical Interconnect, then the Cloud Router to manage routes, and finally attach them with an Interconnect Attachment.

2. Step 2: Match the correct order

   Create an Interconnect, then a Cloud Router, then an Interconnect Attachment correctly lists: Interconnect, Cloud Router, Interconnect Attachment.

3. Final Answer:

   Create an Interconnect, then a Cloud Router, then an Interconnect Attachment -> Option B

4. Quick Check:

   Setup order = Interconnect, Router, Attachment [OK]

Hint: Remember: Interconnect first, then Router, then Attachment [OK]

Common Mistakes:

• Mixing up the order of creating components
• Creating Attachment before Interconnect
• Skipping Cloud Router creation

3. Given the following setup code snippet for a Dedicated Interconnect, what will be the state of the Interconnect Attachment after creation?

interconnect = createInterconnect('my-interconnect')
cloudRouter = createCloudRouter('my-router')
attachment = createInterconnectAttachment(interconnect, cloudRouter)
print(attachment.state)

medium

A. ACTIVE

B. UNKNOWN

C. PENDING

D. FAILED

Solution

1. Step 1: Understand Interconnect Attachment lifecycle

   When an Interconnect Attachment is first created, it starts in a PENDING state until the physical connection is verified and established.

2. Step 2: Determine the initial state after creation

   Since the snippet just created the attachment, it will be in PENDING state before becoming ACTIVE.

3. Final Answer:

   PENDING -> Option C

4. Quick Check:

   New attachment state = PENDING [OK]

Hint: New attachments start as PENDING until connection is active [OK]

Common Mistakes:

• Assuming attachment is ACTIVE immediately
• Confusing FAILED with initial state
• Thinking UNKNOWN is default

4. You created a Dedicated Interconnect and an Interconnect Attachment, but the attachment state remains in PENDING for hours. What is the most likely cause?

medium

A. The physical connection is not yet provisioned by the provider

B. The Cloud Router is misconfigured with wrong BGP settings

C. The Interconnect Attachment was deleted accidentally

D. The Google Cloud project quota is exceeded

Solution

1. Step 1: Analyze the PENDING state meaning

   PENDING means the physical link is not yet active or provisioned by the provider.

2. Step 2: Identify the cause of delay

   If the attachment stays PENDING for hours, it usually means the provider has not completed the physical connection setup.

3. Final Answer:

   The physical connection is not yet provisioned by the provider -> Option A

4. Quick Check:

   PENDING long time = Physical link not ready [OK]

Hint: Long PENDING means physical link not ready from provider [OK]

Common Mistakes:

• Blaming Cloud Router misconfiguration immediately
• Assuming attachment was deleted
• Thinking quota issues cause PENDING state

5. You want to maximize bandwidth and redundancy using Dedicated Cloud Interconnect. Which setup should you choose?

hard

A. Create one Interconnect with multiple Interconnect Attachments in the same location

B. Use VPN tunnels instead of Dedicated Interconnect for redundancy

C. Create one Interconnect and one Cloud Router, then attach multiple VPC networks to it

D. Create two Interconnects in different locations, each with its own Cloud Router and Interconnect Attachment

Solution

1. Step 1: Understand bandwidth and redundancy needs

   To maximize bandwidth and have redundancy, you need multiple physical connections in different locations.

2. Step 2: Evaluate options for redundancy

   Create two Interconnects in different locations, each with its own Cloud Router and Interconnect Attachment creates two Interconnects in different locations, each with its own Cloud Router and Attachment, providing both bandwidth aggregation and failover.

3. Step 3: Rule out other options

   Create one Interconnect with multiple Interconnect Attachments in the same location lacks location diversity; Create one Interconnect and one Cloud Router, then attach multiple VPC networks to it does not increase physical bandwidth; Use VPN tunnels instead of Dedicated Interconnect for redundancy uses VPN, which is slower and not Dedicated Interconnect.

4. Final Answer:

   Create two Interconnects in different locations, each with its own Cloud Router and Interconnect Attachment -> Option D

5. Quick Check:

   Max bandwidth + redundancy = Multiple Interconnects different locations [OK]

Hint: Use multiple Interconnects in different locations for best redundancy [OK]

Common Mistakes:

• Using multiple attachments in one location only
• Relying on single Interconnect for redundancy
• Confusing VPN with Dedicated Interconnect