Which two events trigger a significant log? (Choose two.)

Question

Options

• AClient received a 301 - Moved Permanently response
• BClient request came from a U.S. embargoed country
• CConnection was prematurely closed by the client
• DRequest response time was greater than the configured threshold
• EClient request was made to a Virtual Service that is down

• A
  4% (1)
• B
  8% (2)
• C
  69% (18)
• E
  19% (5)

Explanation

Significant logs are generated when something unexpected or performance-impacting occurs during an active connection - not for routine HTTP behaviors or policy decisions.

C is correct because a premature client connection close is an abnormal mid-session event. The server was actively processing a request when the client unexpectedly dropped it, which warrants a significant log to flag potential client issues, network problems, or application errors.

D is correct because exceeding a configured response-time threshold is explicitly a performance warning that administrators have pre-defined as significant. It directly signals that SLA or latency expectations are being violated.

A is wrong because a 301 redirect is a standard, expected HTTP response - it is normal behavior, not an error or anomaly worth significant logging.

B is wrong because geo-based access control (embargoed countries) generates a security or policy log, not a significant performance or connection log.

E is wrong because requests to a down Virtual Service typically generate availability or error-state logs tied to the service's health monitoring, not a significant log triggered by the individual request event itself.

Memory tip: Think "significant = something went wrong during the transaction itself." A dropped connection (C) and a slow response (D) both happen while serving the request - that's your trigger. Redirects are planned, geo-blocks are policy, and service-down states are infrastructure health events.

No community discussion yet for this question.