Exam F5CAB5 Topic 4 Question 38 Discussion

To collect application-layer details such as HTTP status codes (200, 404, 500, etc.) and HTTP methods (GET, POST, PUT, DELETE), the BIG-IP system must use a profile designed for traffic visibility and reporting rather than basic traffic handling. The Analytics profile (Option C) is the correct choice because it is specifically designed to collect, store, and present detailed statistics about HTTP and TCP traffic passing through a virtual server.
When an Analytics profile is attached to a virtual server, BIG-IP can record metrics such as HTTP response codes, request methods, URI paths, latency, throughput, and client-side/server-side performance data. These statistics are then accessible through the BIG-IP GUI under Statistics → Analytics, allowing administrators to validate application behavior and troubleshoot performance or functional issues.
The HTTP profile (Option B) enables HTTP protocol awareness and features like header insertion and compression, but it does not provide historical or statistical reporting of HTTP methods and response codes. Request Adapt (Option A) is used for ICAP-based content adaptation, not visibility. Statistics (Option D) is not a standalone profile and does not provide HTTP-level insight.
Therefore, the Analytics profile is the only default profile that fulfills this requirement.