F5-303 key terms

A BIG-IP configuration object that presents an IP address and port to clients and forwards matching traffic to a pool or other destination according to its assigned profile.

A named group of backend servers, each with an address and port, that a virtual server load balances requests across using a configured method.

An individual server node and port entry inside a pool, whose up or down state determines whether the virtual server sends it traffic.

A BIG-IP object representing a backend host IP address, independent of port, used to track availability and share state across pools.

A settings container attached to a virtual server that controls protocol behavior and features, such as TCP, HTTP, SSL, or persistence handling.

A probe that periodically checks a node or pool member and marks it up or down, so traffic is only sent to endpoints that respond correctly.

The algorithm a pool uses to choose among available members, such as round robin, least connections, or observed, influencing how evenly traffic is distributed.

A configuration that keeps a client's successive connections going to the same pool member for a period, using cookies, source addresses, or SSL session IDs.

A Tcl-based script attached to a virtual server that inspects and modifies traffic events, enabling custom routing, header changes, and redirects.

A declarative, strategy-based rule set that matches connection conditions and applies actions such as forwarding or redirecting, offering a GUI-managed alternative to iRules.

Source network address translation that rewrites client source addresses to a BIG-IP address, so backend servers reply through the device rather than directly to clients.

A logical partition of the network namespace that isolates IP address spaces on one BIG-IP, allowing overlapping addresses and separate routing tables.

A feature that reuses pooled server-side TCP connections for multiple client requests, reducing handshake overhead and backend connection counts.

A client-side or server-side configuration holding certificates, keys, ciphers, and protocol settings that govern how BIG-IP terminates or initiates TLS.

A DNS Express or global traffic management object representing a fully qualified domain name whose resolution is controlled by BIG-IP DNS.

Distributing DNS answers across data centers or sites based on health, proximity, or load, so clients are directed to the best available deployment.

A design where the device terminates client connections and creates separate server-side connections, enabling inspection and modification of both directions.

A device or service that sits between clients and servers to balance load, terminate TLS, optimize traffic, and enforce security policy for applications.

A WAF configuration attached to a virtual server that defines which attack signatures, violations, and protections are enforced for protected web traffic.

A pattern or rule that detects a known exploitation technique in requests or responses, contributing to the violation score that triggers blocking.

A WAF state in which the policy observes traffic and suggests or builds elements such as parameters and URLs without blocking legitimate requests.

An approach that permits only explicitly allowed requests, such as known URLs, parameters, and lengths, and rejects everything else by default.

A detected policy breach, such as a disallowed file type or parameter, that adds to a request's threat score and can lead to blocking.

Controls that detect and mitigate automated client activity, such as credential stuffing or scraping, using challenges, fingerprinting, and behavioral analysis.

Features that detect and absorb volumetric or behavioral flood attacks against applications and network resources, often by rate limiting or dropping traffic.

The Traffic Management Shell, a command-line interface on BIG-IP for configuring and inspecting objects, running scripts, and saving or loading configurations.

A RESTful API for managing BIG-IP objects programmatically, using JSON over HTTPS and standard methods to create, read, update, and delete configuration.

An API-driven method for provisioning a BIG-IP's base configuration, such as network and licensing, from a single declarative JSON document.

Application Services 3 Extension, a declarative API that accepts a JSON declaration describing virtual servers, pools, and profiles and applies it as a transaction.

Replicating configuration changes from one device to peers in a device group, keeping a high-availability cluster consistent.

A set of BIG-IP devices that share configuration and failover state, forming the basis for high availability and sync operations.

The process by which a standby device in a high-availability pair takes over active traffic handling when the active unit becomes unavailable.

A packet capture utility available on BIG-IP for recording traffic on an interface or VLAN, used to diagnose connection and routing problems.

A per-virtual-server log of connection events with reasons for acceptance or rejection, useful for tracing why traffic was dropped or reset.

An asynchronous alert sent from BIG-IP to a monitoring system when a defined event, such as a failed monitor or failover, occurs.

A declarative API that collects metrics, events, and logs from BIG-IP and pushes them to analytics or monitoring consumers.

A feature that decrypts, inspects, and re-encrypts traffic through service chains of security devices, with policy deciding which flows are intercepted.