Network intelligence tools in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding VPC Flow Logs Behavior

You enable VPC Flow Logs on a Google Cloud VPC subnet. What information will you NOT see in the flow logs?

A Source and destination IP addresses of the traffic

B Payload content of the packets

C Protocol and port numbers used

D Bytes and packets count for each flow

💡 Hint

Think about what flow logs capture versus packet capture tools.

VPC Flow Logs capture metadata about network traffic, such as IPs, ports, protocols, and counts, but they do NOT capture the actual payload content of packets.

❓ Architecture

intermediate

Choosing the Right Network Intelligence Tool for Latency Analysis

You want to analyze latency and packet loss between your Google Cloud VM instances across regions. Which GCP tool should you use?

A Cloud Trace

B Cloud Logging

C Network Intelligence Center Connectivity Tests

D Cloud Armor

💡 Hint

Consider which tool tests network paths and connectivity.

Network Intelligence Center Connectivity Tests can simulate and analyze network paths, measuring latency and packet loss between endpoints.

❓ security

advanced

Interpreting Firewall Rule Impact with Network Intelligence Center

You run a Connectivity Test between two VM instances but the test fails. You suspect a firewall rule is blocking traffic. Which feature of Network Intelligence Center helps you identify the exact firewall rule causing the block?

A Reachability Analysis

B Packet Mirroring

C Cloud IDS

D Flow Logs Viewer

💡 Hint

Look for a tool that analyzes network paths and policy impact.

Reachability Analysis simulates network paths and shows which firewall or route is blocking traffic.

✅ Best Practice

advanced

Optimizing Network Intelligence Center Usage for Large Environments

In a large Google Cloud environment with many VPCs and subnets, what is the best practice to efficiently monitor network health using Network Intelligence Center?

A Use automated scripts to create and manage Connectivity Tests for critical paths only

B Create Connectivity Tests for every possible VM pair manually

C Enable VPC Flow Logs on all subnets and ignore Connectivity Tests

D Rely solely on Cloud Logging for network issues

💡 Hint

Think about scalability and focusing on important network paths.

Manually creating tests for every VM pair is not scalable. Automating tests for critical paths ensures efficient monitoring.

🧠 Conceptual

expert

Analyzing Network Topology Changes with Network Intelligence Center

You want to detect and visualize changes in your Google Cloud network topology over time. Which Network Intelligence Center feature provides this capability?

A Packet Mirroring

B Connectivity Tests

C Firewall Insights

D Network Topology

💡 Hint

Look for a feature that shows network layout and changes visually.

Network Topology in Network Intelligence Center visualizes your network and tracks changes over time.

Practice

1. What is the main purpose of GCP's Network Intelligence Tools?

easy

A. To manage user permissions

B. To create virtual machines

C. To check and understand cloud network connections

D. To store large amounts of data

Solution

1. Step 1: Understand the role of Network Intelligence Tools

   These tools are designed to help users check and understand how their cloud network connections work.

2. Step 2: Compare with other options

   Creating virtual machines, storing data, and managing permissions are handled by other GCP services, not Network Intelligence Tools.

3. Final Answer:

   To check and understand cloud network connections -> Option C

4. Quick Check:

   Network Intelligence Tools = Check network connections [OK]

Hint: Network tools check connections, not create or store [OK]

Common Mistakes:

• Confusing network tools with VM creation
• Thinking network tools manage data storage
• Assuming network tools handle user permissions

2. Which gcloud command is used to run a connectivity test with Network Intelligence Tools?

easy

A. gcloud network-intelligence connectivity-tests create

B. gcloud compute instances create

C. gcloud storage buckets list

D. gcloud iam roles describe

Solution

1. Step 1: Identify the command for running connectivity tests

   The correct command to run a connectivity test is gcloud network-intelligence connectivity-tests create.

2. Step 2: Eliminate unrelated commands

   Other commands relate to creating instances, listing storage buckets, or describing IAM roles, which are unrelated to network tests.

3. Final Answer:

   gcloud network-intelligence connectivity-tests create -> Option A

4. Quick Check:

   Run connectivity test = gcloud network-intelligence connectivity-tests create [OK]

Hint: Look for 'network-intelligence connectivity-tests create' command [OK]

Common Mistakes:

• Using compute or storage commands instead
• Confusing IAM commands with network tests
• Missing 'network-intelligence' in the command

3. What will be the output of this command?

gcloud network-intelligence connectivity-tests describe test-1

Assuming test-1 exists and ran successfully.

medium

A. Error: test-1 not found

B. Details of the connectivity test including source, destination, and result

C. List of all connectivity tests

D. Command to create a new test

Solution

1. Step 1: Understand the describe command

   The describe command shows detailed information about a specific connectivity test.

2. Step 2: Confirm test existence and success

   Since test-1 exists and ran successfully, the output will include its details like source, destination, and test result.

3. Final Answer:

   Details of the connectivity test including source, destination, and result -> Option B

4. Quick Check:

   Describe test = show test details [OK]

Hint: Describe shows details of one test, not list or errors [OK]

Common Mistakes:

• Expecting a list of tests instead of details
• Assuming error if test exists
• Confusing describe with create command

4. You run gcloud network-intelligence connectivity-tests describe test-2 but get an error saying the test does not exist. What is the likely cause?

medium

A. Network Intelligence Tools are not enabled in the project

B. The command syntax is incorrect

C. The source VM is down

D. The test test-2 was not created

Solution

1. Step 1: Analyze the error message

   The error says the test does not exist, meaning it was never created.

2. Step 2: Check command and environment

   The command syntax is correct, and the error is specific to the test name, not the service or VM status.

3. Final Answer:

   The test test-2 was not created -> Option D

4. Quick Check:

   Describe error = test missing [OK]

Hint: Create test before describing it to avoid 'not exist' error [OK]

Common Mistakes:

• Assuming syntax error without checking test existence
• Blaming service enablement without error details
• Thinking VM status causes test not found error

5. You want to check if a VM in one region can connect to a Cloud SQL instance in another region. Which Network Intelligence Tool and approach should you use?

hard

A. Create and run a connectivity test specifying the VM as source and Cloud SQL as destination

B. Use Cloud Storage to transfer data between regions

C. Run a firewall rule audit to check permissions only

D. Create a new VM in the same region as Cloud SQL

Solution

1. Step 1: Identify the tool for cross-region connectivity checks

   Network Intelligence Tools allow creating connectivity tests between source and destination resources across regions.

2. Step 2: Choose the correct approach

   Creating and running a connectivity test with the VM as source and Cloud SQL as destination directly tests network reachability.

3. Step 3: Eliminate other options

   Cloud Storage is unrelated to connectivity tests, firewall audits check rules but not actual connectivity, and creating a new VM does not test existing network paths.

4. Final Answer:

   Create and run a connectivity test specifying the VM as source and Cloud SQL as destination -> Option A

5. Quick Check:

   Connectivity test = VM to Cloud SQL check [OK]

Hint: Use connectivity test for cross-region VM to Cloud SQL checks [OK]

Common Mistakes:

• Confusing storage transfer with network testing
• Thinking firewall audit alone confirms connectivity
• Creating new VM instead of testing existing connection