How does NPM monitor remote or cloud-based devices, and what considerations apply?

• A. Remote/cloud devices can be monitored via standard protocols (SNMP/WMI/SSH) with proper firewall access; cloud-native monitoring may require vendor-specific modules or API integrations.
• B. Cloud devices can only be monitored via dedicated agents installed on each VM, not SNMP/WMI.
• C. NPM cannot monitor remote devices, only local network devices.
• D. Cloud monitoring requires a separate, standalone tool.

Answer: (B)

Monitoring remote or cloud-based devices with NPM relies on using standard management protocols and cloud APIs, as long as the network path to those devices is reachable and properly secured. In practice, you poll devices over SNMP for most routers and switches, WMI for Windows hosts, and SSH for Linux/Unix systems. This works across WANs or cloud networks when firewall rules and credentials allow the Orion polling engine to reach the devices. For cloud-native or cloud-hosted devices, many metrics live behind cloud provider APIs or vendor-specific telemetry, so you bring in those API integrations or vendor modules to collect and normalize the data into NPM. An agent-based approach is available for situations where direct protocol access is restricted or you need deeper telemetry, but it isn’t required for every remote or cloud device. The key factors are reachability, proper credentials, and access to the needed metrics—whether via standard protocols or through cloud/vendor API integrations.