Refer to the exhibit. A customer-facing URL was down due to DNS failure, but no alert was triggered from the Cisco ThousandEyes dashboard. Which action ensures the alert functions?

Question

Options

• ARemove the Response Code alert condition from the alert.
• BAdd a new Alert Condition for DNS Time.
• CChange the alert severity from Info to Major.
• DAdd a new Alert Condition for Error is present.

• A
  7% (4)
• B
  76% (41)
• C
  13% (7)
• D
  4% (2)

Explanation

Adding a DNS Time alert condition (Option B) directly addresses the monitoring gap: the existing alert was configured only for HTTP Response Code, but DNS failure occurs before any HTTP response is generated, so the Response Code condition is never evaluated and no alert fires. Adding DNS Time gives ThousandEyes a DNS-layer metric to monitor, ensuring a DNS outage triggers the rule.

Why the distractors are wrong:

• A - Removing the Response Code condition makes the alert less capable, not more. It doesn't add DNS visibility.
• C - Severity (Info vs. Major) controls how the alert is classified and who gets notified, not what triggers the alert. A misconfigured alert rule won't fire regardless of severity.
• D - "Error is present" in ThousandEyes typically surfaces HTTP/application-layer errors, not DNS resolution failures, so it wouldn't catch the DNS outage either.

Memory tip: "You can only alert on what you measure." If DNS isn't a condition in your ThousandEyes alert rule, DNS failures are invisible to it - think of each network layer (DNS, HTTP, etc.) as needing its own condition to be covered.

No community discussion yet for this question.