ServiceNow CIS-Discovery Practice Test 28
Question 270
A ServiceNow Discovery review at Greenford University examines the following issue: A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing. The suspected consequence is: Unnecessary firewall openings expand attack surface without repairing account authorization. The result must be reproducible against the original failed fixture and a passing control. Which trace or data finding would make this conclusion defensible?
- A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status
- The current schedule finds a retired node and misses new nodes identified in the platform's approved cluster inventory
- Execution history shows active scans during payment peaks and the approved maintenance calendar lists a separate window
- The status history shows multiple denied scoped attempts followed by success under a forbidden broad credential
Explanation
Correct Answer
A:A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status. This is the reproducible observation that distinguishes this failure for the documented fictional Greenford University case. The defect is: A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing. The governing mechanism is: Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. The supporting measured observation is: A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status. After treatment, the result must be checked: The controlled WMI query succeeds under the approved account and firewall rules remain unchanged.
Incorrect Answers
B:The current schedule finds a retired node and misses new nodes identified in the platform's approved cluster inventory. The question instead centers on A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing; the governing distinction is connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. Check: A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status.
C:That alternative is relevant to apply scheduled discovery outside a constrained maintenance window, but the issue here is A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing. Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. Check: A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status.
D:The status history shows multiple denied scoped attempts followed by success under a forbidden broad credential. It concerns avoid suppressing meaningful discovery errors as successful retries, not the failure described here: A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing. Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation.
Question 271
A ServiceNow Discovery review at Greenford University examines the following issue: A multi-region schedule sends an isolated plant subnet through a MID Server that lacks a route to its internal network. The suspected consequence is: Wrong worker placement produces false reachability failures and encourages unnecessary firewall changes. The result must be reproducible against the original failed fixture and a passing control. Which concrete observation MOST strongly supports the reported defect?
- The MID trace includes a successful command payload while the instance logs a parsing error at a named mapping field
- The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone
- The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window
- A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status
Explanation
Correct Answer
B:The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone. This is the reproducible observation that distinguishes this failure for the documented fictional Greenford University case. The defect is: A multi-region schedule sends an isolated plant subnet through a MID Server that lacks a route to its internal network. The governing mechanism is: Discovery behaviors can select an eligible MID Server by reachable scope, including routing restrictions. The supporting measured observation is: The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone. After treatment, the result must be checked: The chosen MID serves all approved plant addresses while unrelated regions remain outside the behavior.
Incorrect Answers
A:The MID trace includes a successful command payload while the instance logs a parsing error at a named mapping field. The question instead centers on A multi-region schedule sends an isolated plant subnet through a MID Server that lacks a route to its internal network; the governing distinction is discovery behaviors can select an eligible MID Server by reachable scope, including routing restrictions. Check: The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone.
C:That alternative is relevant to prevent overlapping schedules from scanning the same critical devices, but the issue here is A multi-region schedule sends an isolated plant subnet through a MID Server that lacks a route to its internal network. Discovery behaviors can select an eligible MID Server by reachable scope, including routing restrictions. Check: The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone.
D:A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status. It concerns differentiate a firewall block from a missing credential on a windows host, not the failure described here: A multi-region schedule sends an isolated plant subnet through a MID Server that lacks a route to its internal network. Discovery behaviors can select an eligible MID Server by reachable scope, including routing restrictions.
Question 272
The owner of Ashbrook Labs asks for a new risk decision after a prior correction failed to resolve this issue: A Discovery program deploys to complex payment systems first because their subnet is easiest to reach. The replay still demonstrates: The first target group has tight outage tolerances while a lower-risk test segment shares the same discovery protocols. The result must be reproducible against the original failed fixture and a passing control. Which outcome is directly supported if the issue remains unresolved?
- High-risk first deployment can interrupt operations before methods are validated
- A completed scan can still populate misleading operational data
- A running service can appear healthy locally while no discovery work can be dispatched
- Mixed trust zones risk cross-customer probing and incorrect discovery attribution
Explanation
Correct Answer
A:High-risk first deployment can interrupt operations before methods are validated. This is the plausible direct consequence of the observed failure for the documented fictional Ashbrook Labs case. The defect is: A Discovery program deploys to complex payment systems first because their subnet is easiest to reach. The governing mechanism is: Rollout sequencing should account for critical service impact, authorized maintenance windows and proof from representative pilots. The supporting measured observation is: The first target group has tight outage tolerances while a lower-risk test segment shares the same discovery protocols. After treatment, the result must be checked: The pilot demonstrates acceptable load and CI quality before payment systems enter an approved schedule.
Incorrect Answers
B:A completed scan can still populate misleading operational data. The question instead centers on A Discovery program deploys to complex payment systems first because their subnet is easiest to reach; the governing distinction is rollout sequencing should account for critical service impact, authorized maintenance windows and proof from representative pilots. Check: The first target group has tight outage tolerances while a lower-risk test segment shares the same discovery protocols.
C:That alternative is relevant to verify a mid server can authenticate to its servicenow instance, but the issue here is A Discovery program deploys to complex payment systems first because their subnet is easiest to reach. Rollout sequencing should account for critical service impact, authorized maintenance windows and proof from representative pilots. Check: The first target group has tight outage tolerances while a lower-risk test segment shares the same discovery protocols.
D:Mixed trust zones risk cross-customer probing and incorrect discovery attribution. It concerns choose mid server placement for separated customer management zones, not the failure described here: A Discovery program deploys to complex payment systems first because their subnet is easiest to reach. Rollout sequencing should account for critical service impact, authorized maintenance windows and proof from representative pilots.
Question 273
A second application pattern reviewer at Northlake Cloud Services revisits an unresolved finding during isolated ServiceNow Discovery test instance: A discovery feed inserts two device records because one reports a serial number with dashes and the other omits separators. A fresh run still shows: A side-by-side comparison shows identical manufacturer and serial digits with formatting differences only. Use only ServiceNow assets and network access approved for the target environment. What Discovery implementation principle MOST directly explains the cause?
- IRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes
- Normalized identity attributes should use a documented canonical representation before CMDB identification
- Identification decides whether a CI already exists; reconciliation governs allowed updates to an identified existing record
- Coverage and health should include recent successful source observations rather than raw CI record counts
Explanation
Correct Answer
B:Normalized identity attributes should use a documented canonical representation before CMDB identification. This is the underlying causal Discovery implementation principle for the documented fictional Northlake Cloud Services case. The defect is: A discovery feed inserts two device records because one reports a serial number with dashes and the other omits separators. The governing mechanism is: Normalized identity attributes should use a documented canonical representation before CMDB identification. The supporting measured observation is: A side-by-side comparison shows identical manufacturer and serial digits with formatting differences only. After treatment, the result must be checked: Both source formats match the same known physical CI and preserve the original collected serial as provenance.
Incorrect Answers
A:IRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes. The question instead centers on A discovery feed inserts two device records because one reports a serial number with dashes and the other omits separators; the governing distinction is normalized identity attributes should use a documented canonical representation before CMDB identification.
C:That alternative is relevant to distinguish ire identification from reconciliation on a new ci, but the issue here is A discovery feed inserts two device records because one reports a serial number with dashes and the other omits separators. Normalized identity attributes should use a documented canonical representation before CMDB identification. Check: A side-by-side comparison shows identical manufacturer and serial digits with formatting differences only.
D:Coverage and health should include recent successful source observations rather than raw CI record counts. It concerns use cmdb freshness metrics to detect stale discovered devices, not the failure described here: A discovery feed inserts two device records because one reports a serial number with dashes and the other omits separators. Normalized identity attributes should use a documented canonical representation before CMDB identification.
Question 274
A second application pattern reviewer at Eastridge Utilities revisits an unresolved finding during isolated ServiceNow Discovery test instance: An administrator adds a broad corporate address block to a discovery schedule because one approved server is missing from results. A fresh run still shows: The request names one subnet but the configured range includes several unrelated production and partner networks. Use only ServiceNow assets and network access approved for the target environment. Which discovery and configuration-data mechanism applies to these facts?
- Discovery schedules must honor the authorized network target inventory rather than scanning adjacent unsanctioned ranges
- Network translation addresses alone do not uniquely identify devices across separated management contexts
- Request execution and instance-side ECC response processing are separate lifecycle steps requiring correlated status
- Port and service probe configuration should reflect the approved discovery purpose and asset constraints
Explanation
Correct Answer
A:Discovery schedules must honor the authorized network target inventory rather than scanning adjacent unsanctioned ranges. This is the underlying causal Discovery implementation principle for the documented fictional Eastridge Utilities case. The defect is: An administrator adds a broad corporate address block to a discovery schedule because one approved server is missing from results. The governing mechanism is: Discovery schedules must honor the authorized network target inventory rather than scanning adjacent unsanctioned ranges. The supporting measured observation is: The request names one subnet but the configured range includes several unrelated production and partner networks. After treatment, the result must be checked: The dry-run target list contains the intended hosts and excludes every neighboring unapproved network.
Incorrect Answers
B:Network translation addresses alone do not uniquely identify devices across separated management contexts. The question instead centers on An administrator adds a broad corporate address block to a discovery schedule because one approved server is missing from results; the governing distinction is discovery schedules must honor the authorized network target inventory rather than scanning adjacent unsanctioned ranges.
C:That alternative is relevant to trace a mid server response that remains unprocessed in ecc, but the issue here is An administrator adds a broad corporate address block to a discovery schedule because one approved server is missing from results. Discovery schedules must honor the authorized network target inventory rather than scanning adjacent unsanctioned ranges. Check: The request names one subnet but the configured range includes several unrelated production and partner networks.
D:Port and service probe configuration should reflect the approved discovery purpose and asset constraints. It concerns limit requested ip service probes to approved target protocols, not the failure described here: An administrator adds a broad corporate address block to a discovery schedule because one approved server is missing from results. Discovery schedules must honor the authorized network target inventory rather than scanning adjacent unsanctioned ranges.
Question 275
In a Discovery implementation risk workshop at Meridian Food Systems, the following behavior is documented: An operator adds several legacy follow-on probes after classification despite the target's selected horizontal pattern already covering identification and exploration. The relevant mechanism is: Pattern-based discovery can perform identification and exploration together after appropriate classification using the selected horizontal pattern. A reviewed fault must be distinguished from a guessed cause. Which failure impact should the decision owner prioritize?
- Unnecessary firewall openings expand attack surface without repairing account authorization
- Premature scale-out can multiply data defects and operational interruptions
- Wrong classification can send incompatible patterns and pollute the CMDB
- Duplicated paths can create conflicting updates and waste scan resources
Explanation
Correct Answer
D:Duplicated paths can create conflicting updates and waste scan resources. This is the plausible direct consequence of the observed failure for the documented fictional Meridian Food Systems case. The defect is: An operator adds several legacy follow-on probes after classification despite the target's selected horizontal pattern already covering identification and exploration. The governing mechanism is: Pattern-based discovery can perform identification and exploration together after appropriate classification using the selected horizontal pattern. The supporting measured observation is: The lifecycle trace names a horizontal pattern and one horizontal sensor, while extra custom legacy probes duplicate its inventory fields. After treatment, the result must be checked: One supported horizontal pattern produces the expected CI attributes without duplicate probe output.
Incorrect Answers
A:Unnecessary firewall openings expand attack surface without repairing account authorization. The question instead centers on An operator adds several legacy follow-on probes after classification despite the target's selected horizontal pattern already covering identification and exploration; the governing distinction is pattern-based discovery can perform identification and exploration together after appropriate classification using the selected horizontal pattern.
B:That alternative is relevant to preserve a controlled pilot before enabling production schedules, but the issue here is An operator adds several legacy follow-on probes after classification despite the target's selected horizontal pattern already covering identification and exploration. Pattern-based discovery can perform identification and exploration together after appropriate classification using the selected horizontal pattern.
C:Wrong classification can send incompatible patterns and pollute the CMDB. It concerns use the correct classifier after snmp port detection, not the failure described here: An operator adds several legacy follow-on probes after classification despite the target's selected horizontal pattern already covering identification and exploration. Pattern-based discovery can perform identification and exploration together after appropriate classification using the selected horizontal pattern.
Question 276
The owner of Sunridge Infrastructure asks for a new risk decision after a prior correction failed to resolve this issue: A new integration plans to change a database instance class and relationship using an untested payload format. The replay still demonstrates: The proposed payload lacks a required parent reference and dry-run identification returns an error. Uncommon but critical failure cases must be tested before closing the defect. Which failure impact should the decision owner prioritize?
- A malformed payload can create missing links or unidentifiable records
- A wrong class can invalidate inherited attributes and dependency reports
- Random updates can attach attributes or relationships to the wrong CI
- Impact analysis can omit a critical dependency despite apparently complete records
Explanation
Correct Answer
A:A malformed payload can create missing links or unidentifiable records. This is the plausible direct consequence of the observed failure for the documented fictional Sunridge Infrastructure case. The defect is: A new integration plans to change a database instance class and relationship using an untested payload format. The governing mechanism is: IRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes. The supporting measured observation is: The proposed payload lacks a required parent reference and dry-run identification returns an error. After treatment, the result must be checked: The tested payload identifies one expected CI and produces valid relationship mappings without unapproved writes.
Incorrect Answers
B:A wrong class can invalidate inherited attributes and dependency reports. The question instead centers on A new integration plans to change a database instance class and relationship using an untested payload format; the governing distinction is iRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes. Check: The proposed payload lacks a required parent reference and dry-run identification returns an error.
C:That alternative is relevant to review a multiple-match ire result instead of choosing arbitrarily, but the issue here is A new integration plans to change a database instance class and relationship using an untested payload format. IRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes. Check: The proposed payload lacks a required parent reference and dry-run identification returns an error.
D:Impact analysis can omit a critical dependency despite apparently complete records. It concerns detect an absent business service relationship in cmdb health, not the failure described here: A new integration plans to change a database instance class and relationship using an untested payload format. IRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes.
Question 277
A second Discovery implementation specialist at Horizon Public Library revisits an unresolved finding during approval-gated incident investigation: A monitoring switch responds on its management port but discovery produces a generic network timeout after community rotation. A fresh run still shows: The target answers a permitted transport probe while authentication logs reject the retired SNMP credentials. A reviewed fault must be distinguished from a guessed cause. Which principle should the reviewer use to interpret this test?
- Credential selection and affinity order should be inspected before creating new privileged accounts
- Discovery concurrency should be tested against asset capacity and approved operational thresholds
- Scanning discovers a reachable service; classification must interpret returned protocol attributes before identification
- Protocol connectivity and credential acceptance are distinct causes of a failed discovery exchange
Explanation
Correct Answer
D:Protocol connectivity and credential acceptance are distinct causes of a failed discovery exchange. This is the underlying causal Discovery implementation principle for the documented fictional Horizon Public Library case. The defect is: A monitoring switch responds on its management port but discovery produces a generic network timeout after community rotation. The governing mechanism is: Protocol connectivity and credential acceptance are distinct causes of a failed discovery exchange. The supporting measured observation is: The target answers a permitted transport probe while authentication logs reject the retired SNMP credentials. After treatment, the result must be checked: A scoped SNMP inventory response succeeds without changing network boundaries or using a fallback shared secret.
Incorrect Answers
A:Credential selection and affinity order should be inspected before creating new privileged accounts. The question instead centers on A monitoring switch responds on its management port but discovery produces a generic network timeout after community rotation; the governing distinction is protocol connectivity and credential acceptance are distinct causes of a failed discovery exchange. Check: The target answers a permitted transport probe while authentication logs reject the retired SNMP credentials.
B:That alternative is relevant to set target rate limits to protect legacy network equipment, but the issue here is A monitoring switch responds on its management port but discovery produces a generic network timeout after community rotation. Protocol connectivity and credential acceptance are distinct causes of a failed discovery exchange. Check: The target answers a permitted transport probe while authentication logs reject the retired SNMP credentials.
C:Scanning discovers a reachable service; classification must interpret returned protocol attributes before identification. It concerns use the correct classifier after snmp port detection, not the failure described here: A monitoring switch responds on its management port but discovery produces a generic network timeout after community rotation. Protocol connectivity and credential acceptance are distinct causes of a failed discovery exchange.
Question 278
A second Discovery implementation specialist at Brightwater Airlines revisits an unresolved finding during approval-gated incident investigation: Two newly configured discovery schedules cover the same critical firewall subnet at the same hour. A fresh run still shows: The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window. A reviewed fault must be distinguished from a guessed cause. Which ServiceNow Discovery principle BEST explains the failure? Choose ONE.
- Schedule coordination should avoid redundant overlapping probes where asset stability and scan cost matter
- Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation
- Discovery schedules must honor the authorized network target inventory rather than scanning adjacent unsanctioned ranges
- The schedule control status describes job lifecycle and does not by itself prove all target identification succeeded
Explanation
Correct Answer
A:Schedule coordination should avoid redundant overlapping probes where asset stability and scan cost matter. This is the underlying causal Discovery implementation principle for the documented fictional Brightwater Airlines case. The defect is: Two newly configured discovery schedules cover the same critical firewall subnet at the same hour. The governing mechanism is: Schedule coordination should avoid redundant overlapping probes where asset stability and scan cost matter. The supporting measured observation is: The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window. After treatment, the result must be checked: The execution ledger shows one scheduled pass per protected device during each maintenance interval.
Incorrect Answers
B:Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. The question instead centers on Two newly configured discovery schedules cover the same critical firewall subnet at the same hour; the governing distinction is schedule coordination should avoid redundant overlapping probes where asset stability and scan cost matter. Check: The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window.
C:That alternative is relevant to restrict discovery ip range to an approved cidr, but the issue here is Two newly configured discovery schedules cover the same critical firewall subnet at the same hour. Schedule coordination should avoid redundant overlapping probes where asset stability and scan cost matter. Check: The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window.
D:The schedule control status describes job lifecycle and does not by itself prove all target identification succeeded. It concerns avoid assuming completion from a green schedule status, not the failure described here: Two newly configured discovery schedules cover the same critical firewall subnet at the same hour. Schedule coordination should avoid redundant overlapping probes where asset stability and scan cost matter.
Question 279
During a second independent synthetic CMDB reconciliation rehearsal for Seacliff Pharma, an attempted correction to the documented failure remains unverified: A pattern reports the loopback address as a production endpoint because it takes the first IPv4 token from command output. The governing rule is: Network extraction requires a suitable interface filter and an explicit address-selection rule. The decision must preserve approved CI source authority and relationship direction. What observed fact most clearly distinguishes this case from an unrelated failure?
- The debug history shows two valid source fields but the second match overwrites the first before the identification payload is built
- The config names db-prod but observed connections go to a separate cluster virtual address
- The fixture includes app01.east.example and app01.west.example, which both become app01 after the transform
- The sample includes 127.0.0.1 followed by the approved service interface address, and the pattern always takes the first match
Explanation
Correct Answer
D:The sample includes 127.0.0.1 followed by the approved service interface address, and the pattern always takes the first match. This is the reproducible observation that distinguishes this failure for the documented fictional Seacliff Pharma case. The defect is: A pattern reports the loopback address as a production endpoint because it takes the first IPv4 token from command output. The governing mechanism is: Network extraction requires a suitable interface filter and an explicit address-selection rule. The supporting measured observation is: The sample includes 127.0.0.1 followed by the approved service interface address, and the pattern always takes the first match. After treatment, the result must be checked: The test selects the service-facing address and excludes loopback across two sample interface orders.
Incorrect Answers
A:The debug history shows two valid source fields but the second match overwrites the first before the identification payload is built. The question instead centers on A pattern reports the loopback address as a production endpoint because it takes the first IPv4 token from command output; the governing distinction is network extraction requires a suitable interface filter and an explicit address-selection rule. Check: The sample includes 127.0.0.1 followed by the approved service interface address, and the pattern always takes the first match.
B:That alternative is relevant to use supported connection data instead of inferred hostnames, but the issue here is A pattern reports the loopback address as a production endpoint because it takes the first IPv4 token from command output. Network extraction requires a suitable interface filter and an explicit address-selection rule. Check: The sample includes 127.0.0.1 followed by the approved service interface address, and the pattern always takes the first match.
C:The fixture includes app01.east.example and app01.west.example, which both become app01 after the transform. It concerns normalize hostnames without losing unique device identity, not the failure described here: A pattern reports the loopback address as a production endpoint because it takes the first IPv4 token from command output. Network extraction requires a suitable interface filter and an explicit address-selection rule.
Question 280
A ServiceNow Discovery review at Maplecrest Manufacturing examines the following issue: A switch responds to SNMP but is assigned to a generic network class because classification does not inspect the model identifier. The suspected consequence is: Wrong classification can send incompatible patterns and pollute the CMDB. The decision must preserve approved CI source authority and relationship direction. Which trace or data finding would make this conclusion defensible?
- The target answers a permitted transport probe while authentication logs reject the retired SNMP credentials
- The only completed ECC artifact is a port-scan result, with no successful operating-system classifier or identity payload
- The SNMP response includes vendor and model OIDs while the classifier trace selects a generic catch-all first
- The proposed scan list includes management protocols for unrelated devices while pilot requirements permit SSH on selected hosts
Explanation
Correct Answer
C:The SNMP response includes vendor and model OIDs while the classifier trace selects a generic catch-all first. This is the reproducible observation that distinguishes this failure for the documented fictional Maplecrest Manufacturing case. The defect is: A switch responds to SNMP but is assigned to a generic network class because classification does not inspect the model identifier. The governing mechanism is: Scanning discovers a reachable service; classification must interpret returned protocol attributes before identification. The supporting measured observation is: The SNMP response includes vendor and model OIDs while the classifier trace selects a generic catch-all first. After treatment, the result must be checked: The device receives the correct network class and subsequent discovery does not duplicate the prior CI.
Incorrect Answers
A:The target answers a permitted transport probe while authentication logs reject the retired SNMP credentials. The question instead centers on A switch responds to SNMP but is assigned to a generic network class because classification does not inspect the model identifier; the governing distinction is scanning discovers a reachable service; classification must interpret returned protocol attributes before identification.
B:That alternative is relevant to explain discovery stages when a port is open but no os evidence exists, but the issue here is A switch responds to SNMP but is assigned to a generic network class because classification does not inspect the model identifier. Scanning discovers a reachable service; classification must interpret returned protocol attributes before identification. Check: The SNMP response includes vendor and model OIDs while the classifier trace selects a generic catch-all first. For the evidence decision, the decisive evidence or measure is the SNMP response includes vendor and model OIDs while the classifier trace selects a generic catch-all first.
D:The proposed scan list includes management protocols for unrelated devices while pilot requirements permit SSH on selected hosts. It concerns limit requested ip service probes to approved target protocols, not the failure described here: A switch responds to SNMP but is assigned to a generic network class because classification does not inspect the model identifier. Scanning discovers a reachable service; classification must interpret returned protocol attributes before identification.