-- Exhibit
-- Exhibit --
Refer to the exhibit.
Which profile could be removed or changed on this virtual server to reduce CPU load on the LTM device without increasing server side bandwidth usage?
-- Exhibit
-- Exhibit --
Refer to the exhibit.
Which profile could be removed or changed on this virtual server to reduce CPU load on the LTM device without increasing server side bandwidth usage?
The profile that could be removed or changed to reduce CPU load on the LTM device without increasing server side bandwidth usage is 'httpcompression'. Compression is CPU-intensive since the LTM device has to compress or decompress content, but it also reduces the size of data transferred, which means bandwidth usage stays low or even decreases. Removing or changing the 'httpcompression' profile will reduce the CPU load on the LTM device without leading to increased server side bandwidth usage.
C - Correct
Can anyone help explain this one? From what I can see only 1 item has been cached by the F5 so why would turning off compression be the better choice?
Sorry didn't read the question properly. It specifically asks about saving bandwidth (server side) and CPU (on the LTM) - not turning off unnecessary profiles. Passing compression of text files back to the webservers will save CPU cycles on the F5 but wont increase bandwidth usage server-side. It would decrease it if anything as the files the webservers send are now compressed. Whereas turning caching off wont save any CPU cycles on the F5, but will mean more bandwith usage on the server-side as it will be repeatedly sending that 1 cached file over the network.