VPC peering in GCP - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a VPC peering connection between two networks.

GCP

gcloud compute networks peerings create [1] --network=network-a --peer-network=network-b

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

Apeer-connection-1

Bcreate-peer

Cnetwork-peering

Dvpc-link

Attempts:

3 left

💡 Hint

Common Mistakes

Using a command keyword instead of a name.

Using a generic term like 'vpc-link' which is not a valid peering name.

The peer-connection-1 is the name of the VPC peering connection you create. It uniquely identifies the peering.

2fill in blank

medium

Complete the code to list all VPC peerings in a network.

GCP

gcloud compute networks peerings list --network=[1]

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

Adefault

Bnetwork-a

Cvpc-peer

Dpeer-network

Attempts:

3 left

💡 Hint

Common Mistakes

Using a generic term like 'peer-network' instead of the actual network name.

Using 'default' when the peering is not in the default network.

The network-a is the name of the network whose peerings you want to list.

3fill in blank

hard

Fix the error in the command to delete a VPC peering connection.

GCP

gcloud compute networks peerings [1] peer-connection-1 --network=network-a

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

Adelete

Bremove

Cdestroy

Dterminate

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'remove' which is not a valid gcloud subcommand.

Using 'destroy' or 'terminate' which are invalid here.

The correct command to delete a VPC peering is delete.

4fill in blank

hard

Fill both blanks to create a VPC peering with export and import custom routes enabled.

GCP

gcloud compute networks peerings create peer-connection-2 --network=network-x --peer-network=network-y --export-custom-routes=[1] --import-custom-routes=[2]

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

Atrue

Bfalse

Cyes

Dno

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'yes' or 'no' which are invalid boolean values here.

Setting one flag to true and the other to false.

Both --export-custom-routes and --import-custom-routes flags should be set to true to enable route sharing.

5fill in blank

hard

Fill all three blanks to update a VPC peering to disable import and export of custom routes and set the peering name.

GCP

gcloud compute networks peerings update [1] --network=[2] --export-custom-routes=[3] --import-custom-routes=[3]

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

Apeer-connection-3

Bnetwork-z

Cfalse

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'true' instead of 'false' to disable routes.

Mixing up network and peering names.

The peering name is peer-connection-3, the network is network-z, and both import and export custom routes are set to false to disable them.