Ace the F5 301b Exam: Ultimate Preparation Guide

-- Exhibit –

-- Exhibit --

Refer to the exhibit.

A virtual server is set up on an LTM device as follows:

Virtual server address 78.24.213.79

Default Persistence ProfilE. source_addr, 600s.

Pool NamE. Pool1

Pool Members: 10.72.250.52:80 and 10.72.250.60:80 (both on Internal Vlan)

There are several current connections to the virtual server, and pool member 10.72.250.52:80 has been set to a "Disabled" state.

A tcpdump on the Internal Vlan shows traffic going to 10.72.250.52:80.

How soon after the persistence table query was run can existing connections be refreshed/renewed to ensure that no requests are sent to 10.72.250.52?

A failover event is recorded in the following log messages:

Jan 01 00:56:56 BIG-IP notice mcpd[5318]: 01070727:5: Pool /Common/my-pool member /Common/10.0.0.10:80 monitor status down.

Jan 01 00:56:56 BIG-IP notice sod[5855]: 010c0045:5: Leaving active, group score 10 peer group score 20.

Jan 01 00:56:56 BIG-IP notice sod[5855]: 010c0052:5: Standby for traffic group /Common/traffic-group-1.

Jan 01 00:56:56 BIG-IP notice sod[5855]: 010c0018:5: Standby

Jan 01 00:57:06 BIG-IP notice logger: /usr/bin/tmipsecd --tmmcount 4 ==> /usr/bin/bigstart stop racoon

What is the cause of the failover?