An LTM HTTP pool has an associated monitor that sends a string equal to 'GET /test.html'.
Which two configurations could an LTM Specialist implement to allow server administrators to disable their pool member servers without logging into the LTM device? (Choose two.)

• A.Set 'disable pool member' equal to 'SERVER UP' and ask the server team to set string 'SERVER DOWN' in test.html.
• B.Set 'alias' equal to 'SERVER DOWN' and ask the server team to set string 'SERVER DOWN' in test.html.
• C.Set 'receive disable string' equal to 'SERVER DOWN' and ask the server team to set string 'SERVER DOWN' in test.html.
• D.Set 'receive string' equal to 'SERVER UP and ask the server team to set string 'SERVER DOWN' in test.html.
• E.Set monitor to transparent and ask the server team to set string 'TRANSPARENT' in test.html.

Comment: *

Name: *

Email: *

Verification: *

An LTM Specialist must perform a packet capture on a virtual server with an applied standard FastL4 profile. The virtual server 10.0.0.1:443 resides on vlan301.
Which steps should the LTM Specialist take to capture the data payload successfully while ensuring no other virtual servers are affected?

• A.A new FastL4 profile should be created and applied to the virtual server with PVA acceleration disabled. Then the packet capture tcpdump -ni vlan301 should be executed on the command line interface.
• B.The packet capture tcpdump -ni vlan301 should be executed on the command line interface. There is no need to change profiles or PVA acceleration.
• C.The LTM device is under light load. The traffic should be mirrored to a dedicated sniffing device. On the sniffing device, the packet capture tcpdump -ni vlan301 should be executed.
• D.The standard FastL4 profile should have PVA acceleration disabled. Then the packet capture tcpdump -ni vlan301 should be executed on the command line interface.

Comment: *

Name: *

Email: *

Verification: *

An LTM Specialist is troubleshooting virtual server 10.0.0.1:443 residing on VLAN vlan301. The web application is accessed via www.example.com. The LTM Specialist wants to save a packet capture with complete decrypted payload for external analysis.
Which command should the LTM Specialist execute on the LTM device command line interface?

• A.tcpdump -vvv -s 0 'host 10.0.0.1 and port 443' -w /var/tmp/trace.cap
• B.ssldump -Aed -k /config/filestore/files_d/Common_d/certificate_key_d/:Common:www.example.com.key_1
  > /var/tmp/trace.cap
• C.ssldump -Aed -ni vlan301 -k /config/filestore/files_d/Common_d/certificate_key_d/
  :Common:www.example.com.key_1 > /var/tmp/trace.cap
• D.tcpdump -vvv -s 0 -ni vlan301 'host 10.0.0.1 and port 443' -w /var/tmp/trace.cap

Comment: *

Name: *

Email: *

Verification: *

A failover event is recorded in the log messages:
Jan 01 00:00:50 BIG-IP notice sod[5855]: 01140029:5: HA proc_running tmm fails action is go offline and down links.
Jan 01 00:00:50 BIG-IP notice sod[5855]: 010c0050:5: Sod requests links down. Jan 01 00:00:50 BIG-IP notice sod[5855]: 010c0054:5: Offline for traffic group /Common/traffic-group-1.
Jan 01 00:00:50 BIG-IP notice sod[5855]: 010c003e:5: Offline
Jan 01 00:00:50 BIG-IP notice logger: /usr/bin/tmipsecd --tmmcount 4 ==> /usr/bin/bigstart stop racoon Jan 01 00:00:50 BIG-IP info lacpd[5502]: 01160016:6: Failover event detected.
(Switchboard failsafe disabled while offline)
Jan 01 00:00:51 BIG-IP err bcm56xxd[5296]: 012c0010:3: Failover event detected. Marking external interfaces down. bsx.c(3633) Jan 01 00:00:51 BIG-IP info bcm56xxd[5296]: 012c0015:6: Link: 1.1 is DOWN Jan 01 00:00:56 BIG-IP notice mcpd[5318]: 0107143c:5: Connection to CMI peer 10.0.0.3
has been removed
Jan 01 00:00:56 BIG-IP notice mcpd[5318]: 0107143a:5: CMI reconnect timer: enabled
Jan 01 00:00:56 BIG-IP notice mcpd[5318]: 01071431:5: Attempting to connect to CMI peer 10.0.0.3 port 6699
What is the cause of the failover?

• A.Loss of connection to CMI peer 10.0.0.3 initiated the failover.
• B.TMM failed, and VLAN fail-safe initiated the failover.
• C.TMM failed, and system fail-safe initiated the failover.
• D.A switchboard failure caused system fail-safe to initiate the failover.

Comment: *

Name: *

Email: *

Verification: *