F5CABR (BIG-IP Recert) key terms

A BIG-IP object that presents a listener IP address and port to clients and forwards matching traffic to a pool or other destination according to its configured type and profiles.

A named group of pool members, each a node and service port, that receives traffic from a virtual server; the pool supplies health status and load-balancing decisions.

A BIG-IP object representing a backend server by IP address; nodes are combined with service ports to form pool members and can carry their own monitors and state.

The combination of a node address and a service port inside a pool, such as 10.1.1.5:443; it holds availability state and connection limits and is the actual target of load balancing.

The algorithm a pool uses to choose among available members, for example round robin, least connections, or observed; the choice shapes distribution and failover behavior under uneven load.

A pool setting that only distributes traffic to members in the highest active priority group once enough members in that group are available, falling back to lower groups otherwise.

A probe, such as ICMP, TCP, or HTTP, that BIG-IP sends to nodes or members to determine availability; results mark objects up or down and drive load-balancing and failover decisions.

Configuration objects attached to virtual servers that control protocol behavior and features, including TCP, HTTP, client and server SSL, and persistence, layered so later profiles can override earlier settings.

A mechanism that keeps a client's subsequent connections going to the same pool member for a period, using methods such as source address affinity or cookies so session state stays valid.

An HTTP persistence method where BIG-IP inserts or reads a cookie to identify the pool member serving a client, so later requests return to the same member.

A persistence method that maps a client's source IP address to a pool member, sending all connections from that address to the same member until the entry expires.

A Tcl-based script bound to a virtual server that runs at events such as HTTP_REQUEST or CLIENT_ACCEPTED to inspect or modify traffic, select pools, or redirect clients.

A profile that defines how BIG-IP terminates TLS from clients, including certificate and key, cipher support, protocol versions, and client certificate verification settings.

A profile that defines how BIG-IP acts as a TLS client toward backend servers, controlling protocol versions, ciphers, and whether the server certificate is validated.

A digital credential, usually X.509, that binds a public key to a name and is presented during TLS handshakes; on BIG-IP it is managed as a certificate object with a matching key.

The ordered set of certificates from the server certificate through intermediate authorities to a trusted root, which clients need to build a trusted path during TLS validation.

Server Name Indication, a TLS extension where the client states the hostname it wants, letting BIG-IP select the matching client SSL profile and certificate on a shared virtual server.

A set of BIG-IP devices configured to synchronize configuration and, in sync-failover mode, to share a failover relationship so one device actively handles a traffic group.

A collection of floating self IP addresses and virtual servers that moves between devices in a device group during failover, so services follow the active unit.

The process that copies configuration objects from one device in a device group to the others so all members share a consistent configuration; it is separate from connection and persistence state mirroring.

The event where a traffic group becomes active on another device in the group, typically triggered by a monitor failure, manual command, or loss of network reachability.

A self IP address assigned to a VLAN and owned by a traffic group, so it exists on whichever device currently holds that traffic group active.

An IP address configured on a BIG-IP VLAN that the device uses for management traffic, health checks, and communication with servers and peers; it can be floating or non-floating.

A Layer 2 broadcast domain configured on BIG-IP with tagged or untagged interfaces; virtual servers and self IPs are associated with VLANs that determine where traffic enters and exits.

Secure Network Address Translation, which rewrites a client's source address to a translation address so servers reply to BIG-IP; it is often needed for routing and to preserve return paths.

The BIG-IP module that provides identity-aware access control, authentication, and authorization for applications through visual access policies and per-request session evaluation.

An APM object bound to a virtual server that defines which access policy runs, how sessions are managed, and what resources a user may reach after authentication.

The server-side record APM creates after a user authenticates, tracking identity, assigned resources, and timeouts; it is referenced by session variables and cookies.

An Advanced Firewall Manager rule set applied to a virtual server or self IP that permits or denies traffic by address, port, protocol, and state, enforced before traffic reaches the virtual server.

AFM features that detect and mitigate volumetric or behavioral attacks by monitoring traffic rates and applying thresholds, scrubbing, or blacklisting to protect protected objects.

An ASM configuration attached to a virtual server that defines how requests are inspected against signatures and learned parameters, and what action is taken on violations.

The ASM setting that determines whether violations are blocked, alarmed only, or transparently allowed, letting teams tune a policy before enforcing blocking in production.

An ASM capability that observes traffic and suggests or automatically adds elements such as URLs, parameters, and cookies to the security policy, reducing manual tuning.

A setting that copies connection and persistence state to the standby device so established sessions survive failover, avoiding disruption for long-lived or stateful flows.

A failover method where devices exchange heartbeat messages over the network, often on a dedicated VLAN, to detect peer health and coordinate which device should be active.

Rapid repeated up and down transitions of a monitored object; BIG-IP can be configured to require a monitor to fail or succeed multiple times before changing state.

A packet capture utility available on BIG-IP that records traffic on an interface or VLAN to a file for analysis of handshakes, resets, and address translation behavior.

A diagnostic snapshot generated on BIG-IP that collects logs, configuration, and system state into one file, commonly uploaded to support for troubleshooting.

A profile that controls which events, such as request logging or connection errors, are written to local logs or remote syslog servers for a virtual server.