What are custom properties in NPM used for, and how do they help with organization and reporting?

• A. They assign metadata to nodes/interfaces for filtering, grouping, and targeted alerting.
• B. They store device serial numbers.
• C. They encrypt all data automatically.
• D. They define alert thresholds.

Answer: (D)

Custom properties are user-defined fields you attach to NPM objects (like nodes and interfaces) to store extra metadata. This metadata makes management and reporting much more flexible: you can filter lists and dashboards by these values, group related devices together, and create alerts that target specific subsets of devices based on their property values. In reports, including custom properties lets you break down performance data by location, department, device type, or any category you define, making trends and comparisons clearer. While you could store things like serial numbers in a custom property, and alerting uses thresholds, the main purpose of custom properties is to enrich objects with metadata for organization, filtering, grouping, and targeted reporting. They don’t automatically encrypt data or define alert thresholds themselves.