F5-304 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 profile and type.

A named collection of pool members that receive traffic from a virtual server, along with the load-balancing method and health-monitoring settings applied to that group.

A single backend server address and port entry inside a pool; its up or down state determines whether the virtual server can select it for new connections.

A BIG-IP object representing a backend host IP address independently of any port, used to share state and connection limits across multiple pool members on that host.

The algorithm a pool uses to choose among available members, such as round robin, least connections, or observed, which weights members by measured performance.

A number assigned to pool members so that BIG-IP sends traffic only to the highest-priority group that currently has at least one available member.

A configured check, such as ICMP, TCP, or HTTP, that BIG-IP sends to pool members to decide whether each member is available to receive traffic.

A profile that keeps a client tied to the same pool member for a period, using methods such as source address affinity or cookies, so session state is preserved.

A persistence method that hashes the client source IP address so requests from the same address continue to reach the same pool member during the persistence timeout.

An HTTP persistence method in which BIG-IP inserts or reads a cookie to identify which pool member served a client, keeping that client on the same member.

A Tcl-based script attached to a virtual server that triggers on events such as HTTP_REQUEST and can inspect or change traffic, select pools, or redirect clients.

A declarative, rule-based object that evaluates conditions against traffic and applies actions such as forwarding to a pool, redirecting, or logging, without writing Tcl code.

The address and port a virtual server listens on; traffic sent to that destination is matched to the virtual server and processed by its profiles and rules.

A virtual server whose destination uses a network or port wildcard, letting one object handle traffic for many addresses or ports that lack a more specific match.

Secure Network Address Translation; BIG-IP replaces the client source address with a translation address so backend servers see BIG-IP rather than the original client.

A SNAT setting that makes BIG-IP translate client addresses to the virtual server's own address or a self IP, chosen automatically without a dedicated SNAT object.

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

A client SSL profile configuration in which BIG-IP decrypts incoming TLS traffic, inspects or modifies it, and may re-encrypt it toward servers using a server SSL profile.

A profile that defines the certificate, key, and TLS protocol settings BIG-IP uses when acting as the server endpoint for encrypted client connections.

A profile that defines how BIG-IP acts as a TLS client toward backend servers, including which protocols, ciphers, and certificate validation it uses.

An APM visual policy that evaluates a user's identity through logon, checks, and actions before granting or denying access to a protected resource.

The APM object that binds an access policy to a virtual server and defines session settings, such as timeouts and cookie options, for authenticated users.

An APM policy evaluated on each HTTP request rather than once per session, used for dynamic authorization, step-up checks, and single sign-on decisions.

An APM feature that authenticates a user once and then supplies credentials or tokens to backend applications, so users do not log in to each application separately.

An APM capability that provides remote users a VPN-style connection to internal networks, with a lease pool, routes, and split or full tunneling options.

A range of IP addresses that APM assigns to remote network-access clients so their tunneled traffic can be routed and identified on the internal network.

An ASM feature that inspects HTTP traffic against learned or declared parameters and signatures, blocking requests that violate the security policy.

The ASM object that defines which URLs, parameters, and attack signatures are enforced for a protected web application, including blocking and alarm settings.

An ASM state in which the system observes traffic and suggests or automatically adds legitimate entities to the security policy before enforcement begins.

A configuration object attached to a virtual server that controls protocol behavior, such as HTTP, TCP, or SSL settings, and is inherited by traffic on that server.

A profile that tunes TCP behavior for a virtual server, including idle timeouts, window scaling, and retransmission settings, affecting how connections are managed.

An address assigned to a BIG-IP VLAN interface that the device uses for management of traffic, health checks, and as a source or translation address.

A Layer 2 broadcast domain configured on BIG-IP interfaces, grouping self IPs and determining which traffic the device accepts and how it is forwarded.

A maximum number of concurrent connections set on a virtual server, pool, member, or node that causes BIG-IP to reject or queue new traffic once reached.

A trigger point in traffic processing, such as CLIENT_ACCEPTED or HTTP_RESPONSE, at which an iRule's code runs and can act on the connection or request.

An alternate destination, often a pool or node, that a virtual server or persistence profile uses when the preferred member is unavailable or persistence cannot be honored.

In APM, the record of an authenticated user's access, holding identity, assigned resources, and timers; it is referenced by access policies and per-request evaluations.

A BIG-IP rule that permits or denies traffic based on addresses, ports, and protocols before it reaches a virtual server, protecting the device and backend networks.

The Traffic Management Shell, a command-line interface on BIG-IP used to create, modify, and display configuration objects and to run show, save, and load commands.

The process of pushing configuration changes from one device in a device group to its peers so all members share consistent objects and settings.

A set of BIG-IP devices configured to synchronize configuration and, when in a sync-failover group, to coordinate active and standby roles.

The process by which a standby device in a redundant pair or group takes over traffic handling when the active device becomes unavailable or is forced offline.

A diagnostic snapshot that collects logs, configuration, and system state from BIG-IP into one file for analysis or for sharing with technical support.

A per-object setting that controls how much detail BIG-IP writes to logs, such as errors only or full debug output, for troubleshooting traffic and policies.