nerdexam
Cisco

350-201 · Question #117

An organization had an incident with the network availability during which devices unexpectedly malfunctioned. An engineer is investigating the incident and found that the memory pool buffer usage…

The correct answer is D. Enable memory threshold notifications. When memory pool exhaustion has already caused a device malfunction, enabling memory threshold notifications provides proactive SNMP alerts so engineers can intervene before the problem recurs.

Host-Based Analysis

Question

An organization had an incident with the network availability during which devices unexpectedly malfunctioned. An engineer is investigating the incident and found that the memory pool buffer usage reached a peak before the malfunction. Which action should the engineer take to prevent this issue from reoccurring?

Options

  • ADisable memory limit.
  • BDisable CPU threshold trap toward the SNMP server.
  • CEnable memory tracing notifications.
  • DEnable memory threshold notifications.

How the community answered

(36 responses)
  • A
    6% (2)
  • B
    6% (2)
  • C
    17% (6)
  • D
    72% (26)

Why each option

When memory pool exhaustion has already caused a device malfunction, enabling memory threshold notifications provides proactive SNMP alerts so engineers can intervene before the problem recurs.

ADisable memory limit.

Disabling the memory limit removes a safeguard against runaway consumption and would make memory exhaustion more likely, not less.

BDisable CPU threshold trap toward the SNMP server.

Disabling the CPU threshold trap removes a monitoring capability for a different resource and has no effect on the memory pool buffer issue identified in the investigation.

CEnable memory tracing notifications.

Memory tracing is a diagnostic tool for tracking allocation patterns and is not a threshold-based alerting mechanism that would notify engineers before exhaustion occurs.

DEnable memory threshold notifications.Correct

Enabling memory threshold notifications configures the device to generate SNMP traps when memory utilization crosses a defined threshold, giving the operations team advance warning before the buffer pool is exhausted. This allows corrective actions - such as clearing processes or reloading the device - to be taken proactively, preventing the malfunction from recurring rather than reacting after the fact.

Concept tested: SNMP memory threshold notification for proactive resource monitoring

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/snmp/configuration/xe-16/snmp-xe-16-book/sm-trap.html

Topics

#memory threshold#SNMP traps#network device availability#performance monitoring

Community Discussion

No community discussion yet for this question.

Full 350-201 Practice