CCA-AppDS Traffic Management (1Y0-241) flashcards
CCA-AppDS Traffic Management (1Y0-241) · Build recall with a focused review session.
31 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Virtual server
- Client-facing listener on the ADC defined by IP address, port, and protocol. It receives requests, applies policies and load balancing, and proxies them to bound services.
- Service
- Server-side object representing a backend server and port. The ADC sends requests to a service and uses bound monitors to determine whether it is UP or DOWN.
- Service group
- A container of multiple backend members sharing one configuration. Monitors and settings bind to the group, so members inherit them without per-member configuration.
- Request switching
- The ADC terminates the client TCP connection and opens a separate connection to the backend. This enables content inspection, persistence, and connection reuse.
- SNIP
- Subnet IP address used for ADC-originated traffic to backend servers. Backends see the SNIP as the source unless USIP or a net profile is configured.
- Least Connection method
- Load balancing method that selects the service with the fewest active connections. It adapts to uneven backend speeds and is the default method.
- Round Robin method
- Load balancing method that distributes requests to each service in turn regardless of current load. Simple but ignores backend capacity and response time.
- Least Response Time
- Load balancing method that picks the service with the lowest measured response time, factoring active connections. It favors the fastest healthy backend.
- Token method
- Weighted load balancing method that distributes requests in proportion to configured weights. Use it when backends have different capacities.
- HTTP-ECV monitor
- Monitor that sends an HTTP request and checks for a specific string in the response body. It verifies application health, not just TCP reachability.
- Content switching vserver
- Front-end vserver that evaluates policies and forwards requests to target load balancing vservers. It enables host- or path-based routing on one VIP.
- Policy priority
- Numeric order in which policies are evaluated. Lower numbers are evaluated first, and the first matching policy applies unless a goto action is used.
- Responder policy
- Policy that acts on requests or responses to redirect, rewrite, or drop traffic. It can return static content without contacting a backend.
- Default target vserver
- Fallback target bound to a content switching vserver. Requests matching no policy are forwarded there instead of returning an error to the client.
- SSL offloading
- TLS termination at the ADC, with clear HTTP sent to the backend. It reduces backend CPU load and centralizes certificate management.
- SSL bridging
- The ADC terminates client TLS and re-encrypts traffic to the backend. It provides end-to-end encryption while still allowing content inspection at the ADC.
- SNI
- Server Name Indication lets one VIP serve multiple certificates. The ADC selects the certificate matching the hostname the client requests during the handshake.
- Certificate chain
- Leaf certificate plus intermediate CA certificates. The ADC must send the full chain or clients cannot build a trusted path to the root CA.
- SSL profile
- Configuration object controlling protocol versions, ciphers, and session reuse for a vserver or service. It enforces the organization's TLS policy.
- Source IP persistence
- Persistence keyed on the client IP address. It breaks when many clients share one NAT address, so cookie persistence is preferred for HTTP.
- Cookie persistence
- Persistence that inserts a cookie naming the selected service. The client returns the cookie and the ADC honors the original binding.
- Persistence timeout
- Idle time before a persistence entry expires. A value of zero keeps the entry until the session ends, potentially pinning traffic indefinitely.
- Backup persistence
- Fallback persistence method applied when the primary method cannot resolve a service, for example when a required cookie is missing.
- GSLB site
- A data center in a GSLB deployment containing local and remote GSLB services. The local ADC health-checks its own site's services directly.
- GSLB method
- Algorithm that selects the site returned in a DNS answer, such as round robin, static proximity, or active-passive failover based on monitor status.
- Static proximity
- GSLB method using a location database to return the site closest to the client's DNS resolver. It improves latency for geographically spread users.
- DNS delegation
- Pointing a domain's NS records at the GSLB vserver, or CNAMEing to the GSLB name, so GSLB answers the domain's queries.
- HA failover
- Standby node takes over VIPs when the primary fails. Triggers include heartbeat loss, peer monitor failure, and forced failover.
- Force sync
- HA command that copies configuration and certificates from the primary to the secondary. Run it after changes to prevent split configuration.
- nstrace
- Packet capture utility on the ADC. It verifies whether the vserver receives traffic and whether the backend service responds.
- AppFlow
- Traffic analytics feature that exports per-application data to external collectors. It provides visibility into latency, throughput, and client behavior.