Cloud Interconnect for dedicated connections in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Cloud Interconnect resource with a specified name.

GCP

resource "google_compute_interconnect" "my_interconnect" {
  name = "[1]"
  location = "us-central1"
  interconnect_type = "DEDICATED"
}

Drag options to blanks, or click blank then click option'

Ainterconnect-123

Bcloud-conn

Cmy-interconnect-1

Dgcp-link

Attempts:

3 left

💡 Hint

Common Mistakes

Using spaces or special characters in the name.

Leaving the name blank.

The name must be a valid and unique identifier for the interconnect resource. "interconnect-123" is a suitable example.

2fill in blank

medium

Complete the code to specify the interconnect type as dedicated.

GCP

resource "google_compute_interconnect" "example" {
  name = "dedicated-conn"
  location = "us-central1"
  interconnect_type = "[1]"
}

Drag options to blanks, or click blank then click option'

AVIRTUAL

BPARTNER

CDEDICATED

DSHARED

Attempts:

3 left

💡 Hint

Common Mistakes

Using "PARTNER" which is for partner interconnects.

Using invalid or unsupported types.

The interconnect_type must be set to "DEDICATED" to create a dedicated Cloud Interconnect connection.

3fill in blank

hard

Fix the error in the code by selecting the correct location for the interconnect.

GCP

resource "google_compute_interconnect" "conn" {
  name = "dedicated-conn"
  location = "[1]"
  interconnect_type = "DEDICATED"
}

Drag options to blanks, or click blank then click option'

Aeurope-west1-c

Bus-central1-a

Cus-east1-b

Dus-central1

Attempts:

3 left

💡 Hint

Common Mistakes

Using zone names instead of region names.

Using unsupported or invalid locations.

The location must be a region, not a zone. "us-central1" is a valid region for Cloud Interconnect.

4fill in blank

hard

Fill both blanks to define the bandwidth and admin enabled status for the interconnect.

GCP

resource "google_compute_interconnect" "conn" {
  name = "dedicated-conn"
  location = "us-central1"
  interconnect_type = "DEDICATED"
  bandwidth = "[1]"
  admin_enabled = [2]
}

Drag options to blanks, or click blank then click option'

A10

B100

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using bandwidth as a number without quotes.

Using strings instead of booleans for admin_enabled.

The bandwidth must be a valid value like "10" or "100". The admin_enabled field is a boolean and should be true or false. Here, "10" and true are correct.

5fill in blank

hard

Fill all three blanks to configure the interconnect with a description, customer name, and link type.

GCP

resource "google_compute_interconnect" "conn" {
  name = "dedicated-conn"
  location = "us-central1"
  interconnect_type = "DEDICATED"
  description = "[1]"
  customer_name = "[2]"
  link_type = "[3]"
}

Drag options to blanks, or click blank then click option'

APrimary connection for data

BAcmeCorp

CLINK_TYPE_ETHERNET_10G_LR

DBackup link

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid link_type values.

Leaving description or customer_name empty.

The description should be a meaningful string describing the interconnect. The customer_name is the name of the customer, here "AcmeCorp". The link_type must be a valid enum string like "LINK_TYPE_ETHERNET_10G_LR".

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