SolarWinds SCP-NPM Exam With Confidence Using Practice Dumps

 Account limitations are a way of restricting the access of Orion user accounts to specific network objects, such as nodes, interfaces, groups, maps, or alerts. You can use account limitations to prevent a user from seeing or working with select monitored entities through the SolarWinds server. For example, you can limit a user to see only the nodesin a certain group, or only the maps that they have created. You can apply account limitations to individual users or user groups, and you can choose from predefined limitations or create custom limitations based on custom properties. The other options are not effective ways of limiting user access to monitored entities, as they either affect the monitoring status of the entities (unmanage), the permissions of the entities themselves (configure permissions), or the alerting scope of the entities (configure alert limitations). References:

• Limit user access to network areas with account limitations
• Predefined Orion Platform account limitations
• Create custom account limitations

An alert limitation is a filter that restricts the scope of an alert to a specific set of objects, such as nodes, interfaces, applications, or groups. You can use an alert limitation to create an alert that only applies to a select set of nodes in your network, and exclude the rest. To set an alert limitation for the nodes to be included in the alert, follow these steps1:

• Click Alerts & Activity > Alerts > Manage Alerts.
• Find the alert that you want to edit or create a new alert.
• On the Trigger Condition tab, define the condition that triggers the alert, such as Percent Loss is greater than or equal to 50.
• On the Scope of Alert tab, select Limit the scope of this alert to a specific subset of objects.
• Choose the method to define the subset of objects, such as Select objects manually, Use a custom SWQL query, or Use a custom SQL query.
• Select or enter the criteria to filter the objects, such as the node name, IP address, group, custom property, or any other attribute.
• Click Add Selected Objects to add the objects to the alert limitation.
• Click Next and complete the rest of the alert configuration.

You can now save and enable the alert, and it will only notify you when packet loss meets or exceeds 50% for the nodes that you have selected in the alert limitation. References: 1: Limit the objects an alert applies to

Capacity usage trends are calculated based on historical data. By default, the longest time period taken into account for calculating the capacity forecast is 180 days. The more historical data up to 180 days are available, the more precise is the calculated forecast. Forecast calculation methods include peak calculation and average calculation, which can be set globally or customized for individual objects. Capacity forecasting is available for nodes, interfaces, and volumes that meet certain requirements, such as being managed in NPM and having enough historical data in the database. References: Monitor capacity usage trends on the network and forecast capacity issues in NPM, Forecast capacity for nodes, interfaces, or volumes in NPM, Real-Time Network Monitoring Tool