According to the Java Memory Leaks document1, one of the ways to detect and troubleshoot Java

memory leaks is to use the Automatic Leak Detection feature on the Memory tab of the Node

Dashboard. This feature captures and analyzes the collections that are actively used and growing in

size over time, indicating a potential memory leak. You can also drill down into the leaking

collections to see the content summary and the access traces that show the code path and the

business transactions that access the collection. Therefore, the correct answer is D. Examining the

values on the Server tab, configuring Object Instance Tracking, or verifying and adjusting the Memory

Monitoring configuration may not directly reveal the source of the memory leak, but they may

provide some useful information or metrics to support the diagnosis. Reference:

Java Memory Leaks