An application is configured so that the same pool member must be used for an entire session, as well as for HTTP and FTP traffic. A user reports that a session has terminated, and the user must restart the session. The BIG-IP Administrator determines that the active BIG-IP device failed over to the standby BIG-IP device. Which configuration settings should the BIG-IP Administrator verify to ensure proper behaviour when BIG-IP failover occurs? (Choose one answer)

A. cookie persistence and session timeout
B. Stateful failover and Network Failover detection
C. Persistence mirroring and Match Across Services
D. syn-cookie insertion threshold and connection low-water mark

Correct Answer: C

Brave-Dump Clients Votes

C 100%

Comments

Anonymous User 2026-01-19 01:56:14

Selected Answers: C

The requirements tell us several critical things:

Same pool member must be used for an entire session

Persistence must work across HTTP and FTP

Session broke after a BIG-IP failover

This points directly to persistence state not being preserved across failover.

What must be verified:

Persistence mirroring

Ensures persistence records are synchronized between active and standby BIG-IP devices

Without it, a failover causes the standby device to lose session persistence data, forcing users to restart sessions

Match Across Services

Required when multiple services/protocols (HTTP and FTP) must use the same pool member

Ensures persistence applies across different virtual servers and ports

Together, these two settings ensure seamless session continuity after failover.