Network intelligence tools in GCP - Step-by-Step Execution

Process Flow - Network intelligence tools

Start: User wants network info

↓

Choose tool: VPC Flow Logs, Network Intelligence Center, or Packet Mirroring

↓

Collect network data

↓

Analyze data for traffic, latency, or security

↓

Generate insights or alerts

↓

User takes action or monitors

↓

End

This flow shows how GCP network intelligence tools collect and analyze network data to help users monitor and improve their network.

Execution Sample

GCP

1. Enable VPC Flow Logs on subnet
2. Send logs to Cloud Logging
3. Use Network Intelligence Center to view topology
4. Analyze logs for traffic patterns
5. Set alerts for anomalies

This sequence shows how to enable and use GCP network intelligence tools to monitor network traffic and detect issues.

Process Table

Step	Action	Input/Condition	Output/Result
1	Enable VPC Flow Logs	Subnet selected	Flow logs start collecting network traffic data
2	Send logs to Cloud Logging	Flow logs enabled	Logs available in Cloud Logging for analysis
3	View topology in Network Intelligence Center	Logs available	Visual network map displayed
4	Analyze logs	Logs in Cloud Logging	Traffic patterns and latency identified
5	Set alerts	Analyzed data	Alerts configured for unusual network behavior
6	Monitor alerts	Alerts configured	User notified on network issues
7	End	No further action	Monitoring ongoing

💡 Monitoring continues until user disables tools or changes configuration

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	Final
VPC Flow Logs	Disabled	Enabled	Enabled	Enabled	Enabled	Enabled	Enabled
Cloud Logging	No logs	No logs	Logs received	Logs received	Logs received	Logs received	Logs received
Network Topology View	None	None	None	Visible	Visible	Visible	Visible
Alerts	None	None	None	None	Configured	Active	Active

Key Moments - 3 Insights

Why do we enable VPC Flow Logs before viewing network topology?

VPC Flow Logs must be enabled first to collect network traffic data, which Network Intelligence Center uses to build the topology view (see execution_table step 1 and 3).

What happens if logs are not sent to Cloud Logging?

Without logs in Cloud Logging, analysis and alerts cannot be performed, so steps 4 and 5 would have no data to work with (see execution_table step 2).

Can alerts notify users without analyzing logs first?

No, alerts depend on analyzed data from logs to detect anomalies, so analysis must happen before alerts are set (see execution_table steps 4 and 5).

Visual Quiz - 3 Questions

Look at the execution table, at which step does the network topology become visible?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Output/Result' column for when the topology is displayed.

According to the variable tracker, what is the state of 'Alerts' after Step 4?

A None

B Active

C Configured

D Disabled

💡 Hint

Look at the 'Alerts' row under 'After Step 4' in the variable tracker.

If VPC Flow Logs were not enabled at Step 1, how would that affect Step 3?

A Logs would be sent anyway

B Topology would still be visible

C Topology would not be visible

D Alerts would be configured automatically

💡 Hint

Refer to the dependency between Step 1 and Step 3 in the execution table.

Concept Snapshot

Network intelligence tools in GCP help monitor and analyze network traffic.
Enable VPC Flow Logs to collect data.
Send logs to Cloud Logging for storage.
Use Network Intelligence Center to visualize topology.
Analyze logs to find issues and set alerts.
Alerts notify users of network problems.

Full Transcript

Network intelligence tools in Google Cloud Platform help users monitor and understand their network traffic. The process starts by enabling VPC Flow Logs on a subnet, which collects network traffic data. These logs are sent to Cloud Logging, where they are stored and can be analyzed. Using the Network Intelligence Center, users can view a visual map of their network topology based on the collected data. Analysis of logs helps identify traffic patterns and latency issues. Users can then set alerts to be notified of unusual network behavior. Monitoring continues as long as these tools are enabled, helping maintain network health and security.

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