An operator in investigating a problem that requires checking the HTTP cookies supplied by the client. When the logs are viewed, the operator finds that the cookies are not being shown. Which…

Question

Options

• AReal-time metrics
• BLog all headers
• CNon-significant logs
• DDataScript logs

• A
  4% (1)
• B
  9% (2)
• C
  87% (20)

Explanation

Enabling Non-significant logs (Option C) resolves the issue because, in systems like F5 BIG-IP ASM, HTTP cookies are categorized as "non-significant" data by default - they are not flagged as security violations and are therefore omitted from logs to reduce noise and storage. Turning on non-significant logging tells the system to record these additional request details, including cookies, even when no violation is triggered.

Why the distractors are wrong:

• A. Real-time metrics - Deals with live performance and traffic statistics, not detailed per-request data like cookies.
• B. Log all headers - Applies to HTTP headers (e.g., Host, Content-Type), which are a separate logging category from cookies in ASM's logging model.
• D. DataScript logs - Used to debug custom iRule/DataScript logic, not for capturing standard HTTP request components like cookies.

Memory tip: Think of it this way - cookies are everywhere in every request, so the system treats them as "non-significant" (background noise) and hides them by default. To see the "boring" stuff, you have to ask for the non-significant logs.

No community discussion yet for this question.