CCNP Network Assurance Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Issue definitions with custom severity

  Why it's wrong here

  Issue definitions categorize problems and assign severity, but they do not let you create a new threshold-based alert for a specific metric such as CPU over 80% for 5 minutes. They are for classifying existing issues, not for defining custom metric thresholds.

• ✗

  Assurance health score thresholds

  Why it's wrong here

  Health score thresholds generate alerts based on overall device or client health scores, which aggregate multiple metrics. They do not allow a specific threshold on a single metric like CPU utilization over a defined duration, so they are not the precise tool for this requirement.

• ✗

  Syslog forwarding to an external server

  Why it's wrong here

  Syslog forwarding sends event messages to an external server, but it does not provide a native alerting mechanism within DNA Center based on a metric threshold. You would need an external system to parse and alert, which does not meet the requirement for a built-in alert.

• ✓

  Assurance custom threshold rules

  Why this is correct

  Assurance custom threshold rules in Cisco DNA Center allow you to define alerts based on specific metric thresholds, such as CPU utilization exceeding 80% for a sustained period. This directly matches the administrator's need to be notified when the condition persists for more than 5 minutes.