Bird
Raised Fist0
GCPcloud~5 mins

Routes and routing in GCP - Cheat Sheet & Quick Revision

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Recall & Review
beginner
What is a route in Google Cloud Platform networking?
A route is a rule that tells network traffic where to go. It connects a source to a destination by specifying the next step or gateway.
Click to reveal answer
beginner
What does the 'next hop' mean in a route?
The 'next hop' is the next place where the traffic should be sent. It can be an IP address, a gateway, or a virtual machine instance.
Click to reveal answer
intermediate
How does Google Cloud decide which route to use when multiple routes match a destination?
Google Cloud uses the most specific route, meaning the route with the longest matching prefix, to decide where to send traffic.
Click to reveal answer
intermediate
What is the difference between a system route and a custom route in GCP?
System routes are automatically created by GCP to connect subnets and internet gateways. Custom routes are created by users to control traffic flow.
Click to reveal answer
beginner
Why is routing important in cloud networks?
Routing directs traffic efficiently, ensuring data reaches the right destination securely and quickly, just like road signs guide drivers to their destinations.
Click to reveal answer
In GCP, what does a route's 'next hop' specify?
AThe next destination for network traffic
BThe source IP address
CThe firewall rule applied
DThe storage bucket location
Which route does GCP choose when multiple routes match a destination?
AThe route with the shortest prefix
BThe route with the longest prefix
CThe first route created
DA random route
What type of route is automatically created by GCP for subnets?
ACustom route
BStatic route
CDynamic route
DSystem route
What is a common use of custom routes in GCP?
ATo control traffic flow between networks
BTo store data securely
CTo create virtual machines
DTo monitor network traffic
Why is routing compared to road signs in real life?
ABecause it creates virtual machines
BBecause it stores data
CBecause it directs traffic to the right destination
DBecause it controls user access
Explain what a route is in Google Cloud and why the 'next hop' is important.
Think about how traffic moves from one place to another.
You got /3 concepts.
    Describe how Google Cloud chooses the best route when multiple routes match a destination.
    Consider how to pick the most precise direction.
    You got /3 concepts.

      Practice

      (1/5)
      1. What is the main purpose of a route in Google Cloud Platform networking?
      easy
      A. To create virtual machines
      B. To store data in the cloud
      C. To direct network traffic from one place to another
      D. To monitor network usage

      Solution

      1. Step 1: Understand what routes do in networking

        Routes tell network traffic where to go, like a map for data packets.

      2. Step 2: Identify the correct purpose in GCP context

        In GCP, routes guide traffic between subnets, VMs, and external networks.

      3. Final Answer:

        To direct network traffic from one place to another -> Option C

      4. Quick Check:

        Routes guide traffic = C [OK]
      Hint: Routes always guide traffic flow in networks [OK]
      Common Mistakes:
      • Confusing routes with storage or compute services
      • Thinking routes monitor traffic instead of directing it
      • Mixing routes with firewall rules
      2. Which of the following is the correct way to specify a next hop in a GCP route configuration?
      easy
      A. nextHopAddress: "192.168.1.1"
      B. nextHop: "192.168.1.1"
      C. nextHopGateway: "192.168.1.1"
      D. nextHopIp: "192.168.1.1"

      Solution

      1. Step 1: Recall GCP route next hop syntax

        GCP routes use specific fields like nextHopIp to define the next hop IP address.

      2. Step 2: Match the correct field name

        Among options, only nextHopIp is valid for specifying an IP address as next hop.

      3. Final Answer:

        nextHopIp: "192.168.1.1" -> Option D

      4. Quick Check:

        Correct field for IP next hop = nextHopIp [OK]
      Hint: Use nextHopIp to specify IP address next hop [OK]
      Common Mistakes:
      • Using incorrect field names like nextHop or nextHopAddress
      • Confusing next hop IP with gateway name
      • Omitting quotes around IP address
      3. Given the following route configuration snippet in GCP, what destination IP range will this route apply to?
      {"destRange": "10.0.0.0/16", "nextHopIp": "192.168.1.1"}
      medium
      A. All IP addresses in 10.0.0.0 to 10.0.255.255
      B. Only the IP 10.0.0.0
      C. All IP addresses in 192.168.1.0/24
      D. All IP addresses in 0.0.0.0/0

      Solution

      1. Step 1: Understand CIDR notation 10.0.0.0/16

        The /16 means the first 16 bits are fixed, covering IPs from 10.0.0.0 to 10.0.255.255.

      2. Step 2: Identify the destination range

        The destRange field defines the IP range this route applies to, which is 10.0.0.0/16 here.

      3. Final Answer:

        All IP addresses in 10.0.0.0 to 10.0.255.255 -> Option A

      4. Quick Check:

        10.0.0.0/16 covers 10.0.0.0-10.0.255.255 [OK]
      Hint: CIDR /16 covers 65,536 IPs starting at base address [OK]
      Common Mistakes:
      • Thinking /16 means only one IP
      • Confusing nextHopIp with destination range
      • Assuming 0.0.0.0/0 means local subnet
      4. You created a route with destination range 0.0.0.0/0 but forgot to specify a next hop. What will happen when you try to deploy this route?
      medium
      A. The route will fail to create due to missing next hop
      B. The route will be created and direct traffic to the internet automatically
      C. The route will create but traffic will be dropped silently
      D. The route will create and send traffic to the default gateway

      Solution

      1. Step 1: Recall route requirements in GCP

        Every route must have a destination and a next hop to know where to send traffic.

      2. Step 2: Understand deployment validation

        Without a next hop, GCP rejects the route creation because it cannot route traffic properly.

      3. Final Answer:

        The route will fail to create due to missing next hop -> Option A

      4. Quick Check:

        Missing next hop causes creation failure [OK]
      Hint: Routes need next hop or gateway to deploy [OK]
      Common Mistakes:
      • Assuming route auto-assigns next hop
      • Thinking route silently drops traffic
      • Confusing route creation with firewall rules
      5. You want to route all traffic destined for 10.1.0.0/24 subnet through a VM instance with IP 192.168.5.10. Which route configuration is correct?
      hard
      A. {"destRange": "192.168.5.10/24", "nextHopIp": "10.1.0.0"}
      B. {"destRange": "10.1.0.0/24", "nextHopIp": "192.168.5.10"}
      C. {"destRange": "10.1.0.0/24", "nextHopGateway": "192.168.5.10"}
      D. {"destRange": "0.0.0.0/0", "nextHopIp": "10.1.0.0"}

      Solution

      1. Step 1: Identify destination subnet to route

        The destination subnet is 10.1.0.0/24, so destRange must be this value.

      2. Step 2: Specify next hop as VM IP

        The next hop should be the VM's IP 192.168.5.10, using nextHopIp field.

      3. Step 3: Validate correct JSON structure

        {"destRange": "10.1.0.0/24", "nextHopIp": "192.168.5.10"} correctly sets destRange and nextHopIp with proper values and syntax.

      4. Final Answer:

        {"destRange": "10.1.0.0/24", "nextHopIp": "192.168.5.10"} -> Option B

      5. Quick Check:

        Destination subnet + VM IP next hop = {"destRange": "10.1.0.0/24", "nextHopIp": "192.168.5.10"} [OK]
      Hint: Destination subnet in destRange, VM IP in nextHopIp [OK]
      Common Mistakes:
      • Swapping destination and next hop IPs
      • Using nextHopGateway instead of nextHopIp for VM IP
      • Setting wrong destination range