TCP

In the Ultra Transcenders books

AZ-305AZ-104AZ-7002V0-17.25AZ-900AI-200SC-900SC-200SC-300AZ-400AZ-802DP-700MD-102ALZ

Each book explains TCP in context, with comparison tables and the common traps.

Related terms

• AH

  Short for Authentication Header, an IPsec protocol that verifies the sender and integrity of an entire IP packet but leaves it unencrypted. Network security group rules can filter on it, as they can on TCP, UDP, ICMP and ESP.

• Azure KMS

  Endpoint used to activate Windows on Azure VMs: azkms.core.windows.net (20.118.99.224 and 40.83.235.53) on TCP port 1688. With forced tunnelling in place, user-defined routes sending those IPs to next hop Internet keep activation working.

• Connections Active

  Online endpoint metric in Azure Monitor showing how many client TCP connections are open at once.

• HA Ports

  A rule on an internal Standard Load Balancer, using protocol All and port 0, that balances every TCP and UDP flow on every port, which suits active-active NVAs.

• Health probe

  A TCP, HTTP or HTTPS check a load balancer uses to decide whether backends are healthy. For an HTTP probe, its path has to return HTTP 200.

• ICMP

  The protocol behind ping, distinct from both UDP and TCP. Between peered VNets, the default AllowVnetInBound NSG rule permits it.

• Idle timeout

  The time, 4 minutes by default, that a TCP flow with no activity is kept open on a load balancer rule. It does not provide session stickiness.

• Ingress

  In Container Apps, turning this on exposes an app over TCP or HTTP, either to the internet or just within its environment, and no load balancer needs creating. AKS handles it differently: Ingress resources carry rules, and an ingress controller enforces them.