301b 무료 덤프문제 온라인 액세스

An LTM Specialist has a single HTTPS virtual server doing SSL termination. No server SSL profile is defined. The pool members are on the internal VLAN answering on HTTP port 80. Users with certain browsers are experiencing issues.
Which two locations are most appropriate to gather packets needed to determine the SSL issue? (Choose two.)

• A.LTM device's management interface
• B.server interface
• C.LTM device's internal VLAN
• D.user's computer
• E.LTM device's external VLAN

-- Exhibit-

-- Exhibit --
Refer to the exhibit.
The virtual server is listening on port 443.
What is the solution to the problem?

• A.Modify the virtual server TCP profile to disable Nagle's Algorithm.
• B.Modify the virtual server HTTP Profile to 'Redirect RewritE.Matching'.
• C.Modify the virtual server HTTP Profile to 'Redirect RewritE.All'.
• D.Add an SSL Client profile to the existing virtual server.

An LTM Specialist is tasked with ensuring that the syslogs for the LTM device are sent to a remote syslog server.
The following is an extract from the config file detailing the node and monitor that the LTM device is using for the
remote syslog server:
monitor Syslog_15002 { defaults from udp dest *:15002 }
node 91.223.45.231 { monitor Syslog_15002 screen RemoteSYSLOG }
There seem to be problems communicating with the remote syslog server. However, the pool monitor shows that the remote server is up.
The network department has confirmed that there are no firewall rules or networking issues preventing the LTM device from
communicating with the syslog server. The department responsible for the remote syslog server indicates that there may
be problems with the syslog server. The LTM Specialist checks the BIG-IP LTM logs for errors relating to the remote syslog server. None are found. The LTM Specialist does a tcpdump:
tcpdump -nn port 15002, with the following results: 21:28:36.395543 IP 192.168.100.100.44772 > 91.223.45.231.15002: UDP, length 19 21:28:36.429073 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 169 21:28:36.430714 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 181 21:28:36.840524 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 169 21:28:36.846547 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 181 21:28:39.886343 IP 192.168.100.100.39499 > 91.223.45.231.15002: UDP, length 144
NotE.192.168.100.100 is the self IP of the LTM device.
Why are there no errors for the remote syslog server in the log files?

• A.The -log option for tcpdump needs to be used.
• B.The monitor type used is inappropriate.
• C.The "verbose" logging option needs to be enabled for the pool.
• D.When the remote syslog sever fails, it returns to service before the timeout for the monitor has expired.

Internet clients connecting to a virtual server to download a file are experiencing about 150 ms of latency and no packet loss.
Which built-in client-side TCP profile provides the highest throughput?

• A.tcp-lan-optimized
• B.tcp-legacy
• C.tcp
• D.tcp-wan-optimized

Given this as the first packet displayed of an ssldump:
2 2 1296947622.6313 (0.0001) S>CV3.1(74) Handshake ServerHello Version 3.1 random[32]= 19 21 d7 55 c1 14 65 63 54 23 62 b7 c4 30 a2 f0 b8 c4 20 06 86 ed 9c 1f 9e 46 0f 42 79 45 8a 29 session_id[32]= c4 44 ea 86 e2 ba f5 40 4b 44 b4 c2 3a d8 b4 ad 4c dc 13 0d 6c 48 f2 70 19 c3 05 f4 06 e5 ab a9 cipherSuite TLS_RSA_WITH_RC4_128_SHA compressionMethod NULL
In reviewing the rest of the ssldump, the application data is NOT being decrypted.
Why is ssldump failing to decrypt the application data?

• A.The application data is encrypted with TLSv1.
• B.The data is contained within a resumed TLS session.
• C.The BigDB Key Log.Tcpdump.Level needs to be adjusted.
• D.The application data is encrypted with SSLv3.