Direct Peering allows privately connecting to GCP services directly through a physical connection without using a VPC.

Hybrid connectivity enables communication between GCP and on-premises networks using VPNs or dedicated interconnects.

Firewall policies that apply at the organization or folder level to enforce consistent security rules across multiple projects.

VPC peering allows private communication between two VPCs without requiring public IPs or VPNs.

Each VPC can have up to 300 subnets by default.

RFC 1918 private IP ranges are used in GCP VPCs.

VPC peering does not support transitive peering; routes between two VPCs cannot traverse through a third VPC.

Custom static routes direct traffic to specific destinations not covered by default routes, like on-premises or another VPC.

Alias IP ranges bind multiple IP addresses to a VM instance for use in load balancing or containerized applications.

Network tags can be applied to VM instances to apply specific firewall rules based on the assigned tags.

Yes, VPCs are global resources that can span multiple regions.

Subnets allow you to partition the IP address range of a VPC into smaller blocks allocated to specific regions.

Private Google Access enables instances in a subnet to reach Google services, like BigQuery or Storage, without public IPs.

A route specifies how packets leaving a VM instance should be directed, either within the VPC or externally.

A globally distributed private network managed by Google Cloud that allows you to define and control networking resources.

Subnet-level routes apply to all instances in the subnet, while VM-level routes override subnet-level rules for specific VMs.

Cloud NAT allows VMs without public IPs to connect to external services securely while preventing external access to those VMs.

In custom mode, only explicitly created routes propagate, unlike automatic propagation of subnets in auto mode VPCs.

Logging that captures all connections occurring within a VPC for monitoring and debugging purposes.

Yes, the default network can be deleted or disabled if not needed for greater security and customization.

Access is governed by IAM policies defining which projects can use the shared network.

Static routing requires manual configuration, while dynamic routing uses Cloud Router to automatically exchange routes between networks.

Shared VPCs allow you to share a VPC across multiple GCP projects to simplify resource management.

Rules that allow or deny network traffic to or from VMs based on specified source, destination, and protocol criteria.

Partner Interconnect allows private connectivity to GCP through a service provider rather than via a direct physical connection.

Default rules allow internal traffic, deny all inbound traffic, and allow all outbound traffic.

Ingress rules control incoming traffic to instances while egress rules control outgoing traffic from instances.

A Cloud VPN establishes a secure, encrypted connection between GCP and on-premises networks.

A Cloud Router is used with Cloud VPN or Interconnect to exchange route information dynamically.

The rule with the most specific target (like IP range or tag) takes precedence when priorities are the same.

CIDR (Classless Inter-Domain Routing) notation specifies IP address ranges and their subnet masks in "address/prefix-length" format.

Secondary IP ranges allow allocating multiple IP ranges to a single subnet for use cases like alias IPs.

Regional dynamic routing propagates routes only to routers in the same region, while global dynamic routing propagates routes to all routers in the VPC across regions.

Rules are prioritized based on a priority value, with lower numbers being higher priority.