CCA-AppDS Traffic Management (1Y0-241) key terms

A NetScaler object that owns an IP address and port and receives client traffic; it forwards that traffic to bound services according to its configured protocol, method, and policies.

An object representing a backend server's IP address and port, plus its protocol and monitor bindings; the virtual server distributes requests across the services bound to it.

A container that holds many member services sharing one configuration, such as monitors and settings; binding the group to a virtual server avoids configuring each backend individually.

A health probe bound to a service that periodically tests the backend, for example with an HTTP request or TCP connect; results mark the service UP or DOWN and remove it from load balancing.

A load balancing method that sends each new request to the bound service currently handling the fewest active connections, which suits backends with uneven response times.

A load balancing method that distributes new requests to bound services in rotating order, giving each healthy backend an equal share regardless of its current load.

The algorithm a virtual server uses to choose among bound services, such as round robin, least connections, least response time, or source IP hash.

A load balancing method that hashes the client's source IP address to pick a service, so requests from one client address consistently reach the same backend without cookie-based persistence.

A virtual server that inspects each request and forwards it to a target load balancing virtual server based on content switching policies rather than balancing directly to services.

A rule that evaluates request attributes such as URL, host header, or HTTP method and, when matched, selects the action that names the target virtual server.

A logical statement written in NetScaler's advanced expression syntax, such as comparing an HTTP header to a value, used by content switching and responder policies to match traffic.

The object bound to a content switching policy that specifies which target load balancing virtual server receives matching requests; the policy decides when, the action decides where.

A policy that intercepts matching requests and returns a configured response, such as a redirect or maintenance page, without forwarding the request to any backend server.

A policy that modifies request or response content, for example rewriting URLs or headers, before the traffic continues to its destination; it changes messages rather than selecting targets.

Terminating client TLS on the NetScaler so backends receive decrypted HTTP, which frees servers from encryption work while the appliance handles certificates and handshakes.

A mode where the NetScaler passes encrypted traffic through to the backend without decrypting it, preserving end-to-end encryption but preventing content inspection or cookie persistence.

The server certificate plus its matching private key, installed on the appliance and bound to a virtual server so the appliance can present the certificate during TLS handshakes.

Server Name Indication, a TLS extension in which the client names the host it wants; the appliance uses it to select the correct certificate when many sites share one IP address.

The ordered set of certificates from the server certificate through intermediate authorities to the root, which clients need to validate trust; a missing intermediate causes browser trust errors.

A configuration that keeps a client's successive requests going to the same backend service for a period, which is required for applications that store session state locally.

A persistence type where the appliance inserts or uses a cookie to identify a client and route later requests to the same service, commonly used for HTTP applications behind a load balancer.

A persistence type that maps a client's IP address to a chosen service for a timeout period, so subsequent connections from that address reach the same backend.

The period after which a persistence entry or idle connection expires; too short breaks session affinity, while too long can pin clients to a failed or stale backend.

Global Server Load Balancing, which answers DNS queries with the address of the best site based on metrics such as proximity, site health, or load, directing users across data centers.

A representation of one data center in a GSLB configuration, holding its local GSLB virtual servers and the metrics used to compare sites when answering DNS requests.

The communication between GSLB sites that shares health, load, and performance data so each site can make consistent decisions about which location should answer a query.

A virtual server that listens for DNS queries and replies on behalf of GSLB, returning the address of the selected site instead of the client's local resolver choice.

Two appliances configured as primary and secondary nodes that share addresses and synchronize configuration, so the secondary takes over if the primary fails.

The process in which the standby node assumes the primary role and takes over traffic, triggered by a heartbeat loss or a forced switch; clients should see minimal interruption.

The periodic message exchanged between high availability nodes to confirm the peer is alive; missed heartbeats are what trigger an automatic failover.

A single NetScaler appliance in a high availability deployment; one node is primary and actively serves traffic while the other is secondary and stays synchronized.

A command-line tool that displays NetScaler statistics, such as connection and request counters, useful for verifying traffic behavior and diagnosing performance issues.

CLI commands such as show lb vserver that display configuration and state, including which services are bound, their health, and current persistence entries.

The remote logging facility where the appliance sends event and error messages; log levels and destinations are configured so administrators can audit and troubleshoot.

A record of configuration changes and administrative actions on the appliance, used to trace who changed what and when during troubleshooting.

A traffic management mode where the appliance forwards packets using MAC addresses rather than rewriting destination IPs, used in certain transparent or direct server return designs.

A deployment where the backend sends responses directly to the client, bypassing the appliance on the return path, which reduces appliance load but constrains persistence and inspection.

An object that defines the source IP address and optionally the source port range the appliance uses when connecting to backends, needed when servers filter by source address.

A set of TCP settings applied to a virtual server or service, controlling behavior such as window scaling, keepalives, and buffering for the connections it handles.