ServiceNow CIS-Discovery Practice Test 55
Question 540
In a Discovery implementation risk workshop at Willowbrook Payment Services, the following behavior is documented: An IP range is approved for discovery but a default exclusion rule still blocks the management interface of a critical server. The relevant mechanism is: Schedule inclusion and exclusion rules must be evaluated together to determine effective target coverage. The operator may not broaden credential or subnet permissions to bypass a failed test. What specific risk is most likely to follow from the described context defect?
- Blindly broadening the range leaves the same hidden gap and increases unnecessary probes
- Overeager matching can collapse unrelated physical assets into one configuration item
- False unreachable status can trigger unnecessary network escalations and wrong coverage decisions
- Excess parallel probing may interrupt network control or cause false device health reports
Explanation
Correct Answer
A:Blindly broadening the range leaves the same hidden gap and increases unnecessary probes. This is the plausible direct consequence of the observed failure for the documented fictional Willowbrook Payment Services case. The defect is: An IP range is approved for discovery but a default exclusion rule still blocks the management interface of a critical server. The governing mechanism is: Schedule inclusion and exclusion rules must be evaluated together to determine effective target coverage. The supporting measured observation is: The target preview shows the server in the CIDR yet omitted from the effective scan set by an older exclusion. After treatment, the result must be checked: The intended server appears in the effective scan list while explicitly protected exclusions remain enforced.
Incorrect Answers
B:Overeager matching can collapse unrelated physical assets into one configuration item. It concerns investigate duplicate ip assignments before altering ci identity rules, not the failure described here: An IP range is approved for discovery but a default exclusion rule still blocks the management interface of a critical server. Schedule inclusion and exclusion rules must be evaluated together to determine effective target coverage.
C:Differentiate unreachable targets from a cancelled discovery job is a separate consideration. In the stated situation, An IP range is approved for discovery but a default exclusion rule still blocks the management interface of a critical server. Schedule inclusion and exclusion rules must be evaluated together to determine effective target coverage. Check: The target preview shows the server in the CIDR yet omitted from the effective scan set by an older exclusion.
D:Excess parallel probing may interrupt network control or cause false device health reports. The question instead centers on An IP range is approved for discovery but a default exclusion rule still blocks the management interface of a critical server; the governing distinction is schedule inclusion and exclusion rules must be evaluated together to determine effective target coverage. Check: The target preview shows the server in the CIDR yet omitted from the effective scan set by an older exclusion.
Question 541
A second configuration data analyst at Lighthouse Financial revisits an unresolved finding during governed production-change review: A team adds broad protocol probes to a schedule even though only Linux SSH inventory is authorized for the pilot. A fresh run still shows: The proposed scan list includes management protocols for unrelated devices while pilot requirements permit SSH on selected hosts. Business service continuity and CMDB evidence must be preserved throughout validation. Which discovery and configuration-data mechanism applies to these facts?
- An authorized discovery job must apply the account and network ownership boundary before sending probes
- The schedule control status describes job lifecycle and does not by itself prove all target identification succeeded
- Port and service probe configuration should reflect the approved discovery purpose and asset constraints
- Authentication failure should be resolved against target-specific account permissions and authorized credential records
Explanation
Correct Answer
C:Port and service probe configuration should reflect the approved discovery purpose and asset constraints. This is the underlying causal Discovery implementation principle for the documented fictional Lighthouse Financial case. The defect is: A team adds broad protocol probes to a schedule even though only Linux SSH inventory is authorized for the pilot. The governing mechanism is: Port and service probe configuration should reflect the approved discovery purpose and asset constraints. The supporting measured observation is: The proposed scan list includes management protocols for unrelated devices while pilot requirements permit SSH on selected hosts. After treatment, the result must be checked: The captured probe list contains only approved targets and services and still classifies the pilot Linux hosts.
Incorrect Answers
A:An authorized discovery job must apply the account and network ownership boundary before sending probes. It concerns use schedule-specific domain or network permissions, not the failure described here: A team adds broad protocol probes to a schedule even though only Linux SSH inventory is authorized for the pilot. Port and service probe configuration should reflect the approved discovery purpose and asset constraints.
B:Avoid assuming completion from a green schedule status is a separate consideration. In the stated situation, A team adds broad protocol probes to a schedule even though only Linux SSH inventory is authorized for the pilot. Port and service probe configuration should reflect the approved discovery purpose and asset constraints. Check: The proposed scan list includes management protocols for unrelated devices while pilot requirements permit SSH on selected hosts.
D:Authentication failure should be resolved against target-specific account permissions and authorized credential records. The question instead centers on A team adds broad protocol probes to a schedule even though only Linux SSH inventory is authorized for the pilot; the governing distinction is port and service probe configuration should reflect the approved discovery purpose and asset constraints. Check: The proposed scan list includes management protocols for unrelated devices while pilot requirements permit SSH on selected hosts.
Question 542
During nonproduction Discovery regression suite, the security architecture reviewer at Oakridge Logistics observes: An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field. Independent logs state: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer. Business service continuity and CMDB evidence must be preserved throughout validation. Which technical explanation is supported by the Discovery log? Choose ONE.
- Reconciliation should enforce which authorized data source may update each CI attribute
- Attribute reconciliation must respect the source proven authoritative for identifying fields
- A controlled reclassification must evaluate inherited fields and supported relationships rather than only class labels
- CMDB classes should represent the supported technology type using reliable discovered attributes
Explanation
Correct Answer
A:Reconciliation should enforce which authorized data source may update each CI attribute. This is the underlying causal Discovery implementation principle for the documented fictional Oakridge Logistics case. The defect is: An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field. The governing mechanism is: Reconciliation should enforce which authorized data source may update each CI attribute. The supporting measured observation is: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer. After treatment, the result must be checked: A controlled Discovery update preserves cost center and still refreshes the approved operating-system version.
Incorrect Answers
B:Attribute reconciliation must respect the source proven authoritative for identifying fields. It concerns protect manufacturer-provided serial number from lower-trust overwrite, not the failure described here: An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field. Reconciliation should enforce which authorized data source may update each CI attribute. Check: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer.
C:Preserve relationship evidence when an application CI is reclassified is a separate consideration. In the stated situation, An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field. Reconciliation should enforce which authorized data source may update each CI attribute. Check: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer.
D:CMDB classes should represent the supported technology type using reliable discovered attributes. The question instead centers on An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field; the governing distinction is reconciliation should enforce which authorized data source may update each CI attribute. Check: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer.
Question 543
During a second independent isolated ServiceNow Discovery test instance for Highland Municipal Works, an attempted correction to the documented failure remains unverified: A discovery rollout puts its only MID Server in a public cloud tenant with no authorized route to an isolated plant subnet. The governing rule is: MID Server placement must reflect network reachability and approved isolation boundaries for targeted assets. Use only ServiceNow assets and network access approved for the target environment. Which test finding BEST establishes the claimed context problem?
- Average target response times are unchanged but ECC queue wait time and worker utilization have doubled
- A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud
- The first target group has tight outage tolerances while a lower-risk test segment shares the same discovery protocols
- The MID service log contains repeated instance authentication denials and the instance MID status remains unvalidated
Explanation
Correct Answer
B:A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud. This is the reproducible observation that distinguishes this failure for the documented fictional Highland Municipal Works case. The defect is: A discovery rollout puts its only MID Server in a public cloud tenant with no authorized route to an isolated plant subnet. The governing mechanism is: MID Server placement must reflect network reachability and approved isolation boundaries for targeted assets. The supporting measured observation is: A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud. After treatment, the result must be checked: A controlled site test discovers approved plant assets without creating a new cross-zone access route.
Incorrect Answers
A:Average target response times are unchanged but ECC queue wait time and worker utilization have doubled. It concerns monitor ecc queue backlog and mid work completion trends, not the failure described here: A discovery rollout puts its only MID Server in a public cloud tenant with no authorized route to an isolated plant subnet. MID Server placement must reflect network reachability and approved isolation boundaries for targeted assets.
C:Choose staged rollout order based on service dependency risk is a separate consideration. In the stated situation, A discovery rollout puts its only MID Server in a public cloud tenant with no authorized route to an isolated plant subnet. MID Server placement must reflect network reachability and approved isolation boundaries for targeted assets. Check: A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud.
D:The MID service log contains repeated instance authentication denials and the instance MID status remains unvalidated. The question instead centers on A discovery rollout puts its only MID Server in a public cloud tenant with no authorized route to an isolated plant subnet; the governing distinction is mID Server placement must reflect network reachability and approved isolation boundaries for targeted assets. Check: A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud.
Question 544
During a second independent governed production-change review for Pine Valley Insurance, an attempted correction to the documented failure remains unverified: A Unix discovery job reports authentication denied and an engineer proposes a universal administrator account. The governing rule is: Authentication failure should be resolved against target-specific account permissions and authorized credential records. Business service continuity and CMDB evidence must be preserved throughout validation. Which concrete observation MOST strongly supports the reported defect?
- The proposed scan list includes management protocols for unrelated devices while pilot requirements permit SSH on selected hosts
- The test host rejects the configured scoped credential and logs show the account lacks a required read permission
- The status history shows multiple denied scoped attempts followed by success under a forbidden broad credential
- The only completed ECC artifact is a port-scan result, with no successful operating-system classifier or identity payload
Explanation
Correct Answer
B:The test host rejects the configured scoped credential and logs show the account lacks a required read permission. This is the reproducible observation that distinguishes this failure for the documented fictional Pine Valley Insurance case. The defect is: A Unix discovery job reports authentication denied and an engineer proposes a universal administrator account. The governing mechanism is: Authentication failure should be resolved against target-specific account permissions and authorized credential records. The supporting measured observation is: The test host rejects the configured scoped credential and logs show the account lacks a required read permission. After treatment, the result must be checked: The target discovery succeeds with a least-privileged account and unauthorized write attempts remain denied.
Incorrect Answers
A: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 Unix discovery job reports authentication denied and an engineer proposes a universal administrator account. Authentication failure should be resolved against target-specific account permissions and authorized credential records.
C:Avoid suppressing meaningful discovery errors as successful retries is a separate consideration. In the stated situation, A Unix discovery job reports authentication denied and an engineer proposes a universal administrator account. Authentication failure should be resolved against target-specific account permissions and authorized credential records. Check: The test host rejects the configured scoped credential and logs show the account lacks a required read permission. For the evidence decision, the decisive evidence or measure is the test host rejects the configured scoped credential and logs show the account lacks a required read permission.
D:The only completed ECC artifact is a port-scan result, with no successful operating-system classifier or identity payload. The question instead centers on A Unix discovery job reports authentication denied and an engineer proposes a universal administrator account; the governing distinction is authentication failure should be resolved against target-specific account permissions and authorized credential records. Check: The test host rejects the configured scoped credential and logs show the account lacks a required read permission.
Question 545
A ServiceNow Discovery review at Pine Valley Insurance examines the following issue: A device responds to SSH but never receives the expected server class, and the team edits an application pattern. The suspected consequence is: A classifier failure can block an otherwise healthy pattern from running at all. The result must be reproducible against the original failed fixture and a passing control. Which trace or data finding would make this conclusion defensible?
- The proposed scan list includes management protocols for unrelated devices while pilot requirements permit SSH on selected hosts
- The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window
- The run closes normally but per-device statuses include authentication failures and missing pattern updates
- The ECC trace shows a completed SSH probe and a failed classifier response with no horizontal pattern execution
Explanation
Correct Answer
D:The ECC trace shows a completed SSH probe and a failed classifier response with no horizontal pattern execution. This is the reproducible observation that distinguishes this failure for the documented fictional Pine Valley Insurance case. The defect is: A device responds to SSH but never receives the expected server class, and the team edits an application pattern. The governing mechanism is: Classification chooses the target class before its identification and exploration pattern can be selected. The supporting measured observation is: The ECC trace shows a completed SSH probe and a failed classifier response with no horizontal pattern execution. After treatment, the result must be checked: The same test target is classified correctly and invokes the expected identification and exploration pattern.
Incorrect Answers
A: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 device responds to SSH but never receives the expected server class, and the team edits an application pattern. Classification chooses the target class before its identification and exploration pattern can be selected.
B:Prevent overlapping schedules from scanning the same critical devices is a separate consideration. In the stated situation, A device responds to SSH but never receives the expected server class, and the team edits an application pattern. Classification chooses the target class before its identification and exploration pattern can be selected. Check: The ECC trace shows a completed SSH probe and a failed classifier response with no horizontal pattern execution.
C:The run closes normally but per-device statuses include authentication failures and missing pattern updates. The question instead centers on A device responds to SSH but never receives the expected server class, and the team edits an application pattern; the governing distinction is classification chooses the target class before its identification and exploration pattern can be selected. Check: The ECC trace shows a completed SSH probe and a failed classifier response with no horizontal pattern execution.
Question 546
A second configuration data analyst at Pine Valley Insurance revisits an unresolved finding during governed production-change review: A pattern emits a relationship to a database CI before its database instance identity is established. A fresh run still shows: The trace shows a relationship request with a missing target identifier while the later step creates the database record. Business service continuity and CMDB evidence must be preserved throughout validation. Which discovery and configuration-data mechanism applies to these facts?
- An expected literal file path must be escaped before it is used as a regular-expression search expression
- Connection mapping needs identified endpoints or supported dependency rules before a relationship can be committed reliably
- Connection discovery must collect and map endpoints before dependent relationship output can be trusted
- Relationship discovery should use observed endpoints or approved configuration semantics and validate ambiguous aliases
Explanation
Correct Answer
B:Connection mapping needs identified endpoints or supported dependency rules before a relationship can be committed reliably. This is the underlying causal Discovery implementation principle for the documented fictional Pine Valley Insurance case. The defect is: A pattern emits a relationship to a database CI before its database instance identity is established. The governing mechanism is: Connection mapping needs identified endpoints or supported dependency rules before a relationship can be committed reliably. The supporting measured observation is: The trace shows a relationship request with a missing target identifier while the later step creates the database record. After treatment, the result must be checked: A full replay identifies both CIs and creates only the expected typed relationship without orphan references.
Incorrect Answers
A:An expected literal file path must be escaped before it is used as a regular-expression search expression. It concerns use literal escaping for a path containing regular-expression tokens, not the failure described here: A pattern emits a relationship to a database CI before its database instance identity is established. Connection mapping needs identified endpoints or supported dependency rules before a relationship can be committed reliably.
C:Debug a connection section before changing application identification is a separate consideration. In the stated situation, A pattern emits a relationship to a database CI before its database instance identity is established. Connection mapping needs identified endpoints or supported dependency rules before a relationship can be committed reliably. Check: The trace shows a relationship request with a missing target identifier while the later step creates the database record.
D:Relationship discovery should use observed endpoints or approved configuration semantics and validate ambiguous aliases. The question instead centers on A pattern emits a relationship to a database CI before its database instance identity is established; the governing distinction is connection mapping needs identified endpoints or supported dependency rules before a relationship can be committed reliably. Check: The trace shows a relationship request with a missing target identifier while the later step creates the database record.
Question 547
A ServiceNow Discovery review at Brightwater Airlines examines the following issue: A Unix discovery job reports authentication denied and an engineer proposes a universal administrator account. The suspected consequence is: Blanket administrative access would expand risk without establishing the minimal required permission. Only approved target ranges and read-only lab credentials are authorized. Which recorded artifact most directly substantiates the assessment?
- The IRE error refers to missing mandatory identifier data while the pattern execution itself reports success
- The target preview shows the server in the CIDR yet omitted from the effective scan set by an older exclusion
- The effective target list contains IPs assigned to a different customer while the change order is restricted to one tenant
- The test host rejects the configured scoped credential and logs show the account lacks a required read permission
Explanation
Correct Answer
D:The test host rejects the configured scoped credential and logs show the account lacks a required read permission. This is the reproducible observation that distinguishes this failure for the documented fictional Brightwater Airlines case. The defect is: A Unix discovery job reports authentication denied and an engineer proposes a universal administrator account. The governing mechanism is: Authentication failure should be resolved against target-specific account permissions and authorized credential records. The supporting measured observation is: The test host rejects the configured scoped credential and logs show the account lacks a required read permission. After treatment, the result must be checked: The target discovery succeeds with a least-privileged account and unauthorized write attempts remain denied.
Incorrect Answers
A:The IRE error refers to missing mandatory identifier data while the pattern execution itself reports success. It concerns reconcile a ci update failure due to mandatory identification data, not the failure described here: A Unix discovery job reports authentication denied and an engineer proposes a universal administrator account. Authentication failure should be resolved against target-specific account permissions and authorized credential records.
B:Validate exclusion lists before enabling new discovery coverage is a separate consideration. In the stated situation, A Unix discovery job reports authentication denied and an engineer proposes a universal administrator account. Authentication failure should be resolved against target-specific account permissions and authorized credential records. Check: The test host rejects the configured scoped credential and logs show the account lacks a required read permission.
C:The effective target list contains IPs assigned to a different customer while the change order is restricted to one tenant. The question instead centers on A Unix discovery job reports authentication denied and an engineer proposes a universal administrator account; the governing distinction is authentication failure should be resolved against target-specific account permissions and authorized credential records. Check: The test host rejects the configured scoped credential and logs show the account lacks a required read permission.
Question 548
The owner of Cedarline Media asks for a new risk decision after a prior correction failed to resolve this issue: A Windows software pattern stores the display label in install_path when a command returns both Name and InstallLocation fields. The replay still demonstrates: The raw command has Name=AtlasAgent and InstallLocation=C:\\Program Files\\Atlas while the mapped path equals AtlasAgent. The operator may not broaden credential or subnet permissions to bypass a failed test. Which outcome is directly supported if the issue remains unresolved?
- A changing source port can create repeated duplicate CI inserts
- A wrong installation path prevents follow-on version checks and relationship discovery
- Mismatched fingerprints can create false certificate associations or fail integrity checks
- An unrelated MID route produces false application absence and tempts unnecessary pattern edits
Explanation
Correct Answer
B:A wrong installation path prevents follow-on version checks and relationship discovery. This is the plausible direct consequence of the observed failure for the documented fictional Cedarline Media case. The defect is: A Windows software pattern stores the display label in install_path when a command returns both Name and InstallLocation fields. The governing mechanism is: Field extraction should match a stable named key and validate the value type before mapping a CI attribute. The supporting measured observation is: The raw command has Name=AtlasAgent and InstallLocation=C:\\Program Files\\Atlas while the mapped path equals AtlasAgent. After treatment, the result must be checked: A fixture with both fields populates the correct path and does not mistake the application name for a location.
Incorrect Answers
A:A changing source port can create repeated duplicate CI inserts. It concerns distinguish database client endpoints from database instance identity, not the failure described here: A Windows software pattern stores the display label in install_path when a command returns both Name and InstallLocation fields. Field extraction should match a stable named key and validate the value type before mapping a CI attribute. Check: The raw command has Name=AtlasAgent and InstallLocation=C:\\Program Files\\Atlas while the mapped path equals AtlasAgent.
C:Preserve whitespace significant to a certificate fingerprint is a separate consideration. In the stated situation, A Windows software pattern stores the display label in install_path when a command returns both Name and InstallLocation fields. Field extraction should match a stable named key and validate the value type before mapping a CI attribute. Check: The raw command has Name=AtlasAgent and InstallLocation=C:\\Program Files\\Atlas while the mapped path equals AtlasAgent.
D:An unrelated MID route produces false application absence and tempts unnecessary pattern edits. The question instead centers on A Windows software pattern stores the display label in install_path when a command returns both Name and InstallLocation fields; the governing distinction is field extraction should match a stable named key and validate the value type before mapping a CI attribute. Check: The raw command has Name=AtlasAgent and InstallLocation=C:\\Program Files\\Atlas while the mapped path equals AtlasAgent.
Question 549
In a Discovery implementation risk workshop at Harborstone Telecom, the following behavior is documented: A weekly dashboard counts every CI as covered although hundreds have not been successfully rediscovered for months. The relevant mechanism is: Coverage and health should include recent successful source observations rather than raw CI record counts. Production-affecting actions require an independently verified change approval. Which adverse result is supported by the available evidence?
- Stale inventory can mislead security planning and change risk analysis
- IP-only matching inflates CMDB inventory and fractures incident history
- Impact analysis can omit a critical dependency despite apparently complete records
- Corrupted identifiers can misassociate devices and bypass duplicate prevention
Explanation
Correct Answer
A:Stale inventory can mislead security planning and change risk analysis. This is the plausible direct consequence of the observed failure for the documented fictional Harborstone Telecom case. The defect is: A weekly dashboard counts every CI as covered although hundreds have not been successfully rediscovered for months. The governing mechanism is: Coverage and health should include recent successful source observations rather than raw CI record counts. The supporting measured observation is: The CI list is large but the last-discovered timestamps for a critical subnet predate a network reconfiguration. After treatment, the result must be checked: The reviewed population meets its approved discovery-age limit or has recorded exceptions with owners.
Incorrect Answers
B:IP-only matching inflates CMDB inventory and fractures incident history. It concerns use ire identification rules to prevent ci duplication on ip changes, not the failure described here: A weekly dashboard counts every CI as covered although hundreds have not been successfully rediscovered for months. Coverage and health should include recent successful source observations rather than raw CI record counts. Check: The CI list is large but the last-discovered timestamps for a critical subnet predate a network reconfiguration. For the risk decision in this case, the decisive response is to stale inventory can mislead security planning and change risk analysis.
C:Detect an absent business service relationship in CMDB health is a separate consideration. In the stated situation, A weekly dashboard counts every CI as covered although hundreds have not been successfully rediscovered for months. Coverage and health should include recent successful source observations rather than raw CI record counts. Check: The CI list is large but the last-discovered timestamps for a critical subnet predate a network reconfiguration.
D:Corrupted identifiers can misassociate devices and bypass duplicate prevention. The question instead centers on A weekly dashboard counts every CI as covered although hundreds have not been successfully rediscovered for months; the governing distinction is coverage and health should include recent successful source observations rather than raw CI record counts. Check: The CI list is large but the last-discovered timestamps for a critical subnet predate a network reconfiguration. For the risk decision in this case, the decisive response is to stale inventory can mislead security planning and change risk analysis.
Question 550
The owner of Lighthouse Financial asks for a new risk decision after a prior correction failed to resolve this issue: A host accepts approved credentials and returns expected command output but discovery marks the device unidentified. The replay still demonstrates: The MID trace includes a successful command payload while the instance logs a parsing error at a named mapping field. Business service continuity and CMDB evidence must be preserved throughout validation. Which outcome is directly supported if the issue remains unresolved?
- Blindly broadening the range leaves the same hidden gap and increases unnecessary probes
- Overbroad discovery can probe systems outside change authorization and distort coverage data
- Credential rotation cannot fix malformed output-to-CI parsing and may disrupt other jobs
- Network rerouting cannot fix a stale protocol credential and may introduce exposure
Explanation
Correct Answer
C:Credential rotation cannot fix malformed output-to-CI parsing and may disrupt other jobs. This is the plausible direct consequence of the observed failure for the documented fictional Lighthouse Financial case. The defect is: A host accepts approved credentials and returns expected command output but discovery marks the device unidentified. The governing mechanism is: Sensor interpretation can fail independently of transport and authentication even when source output is correct. The supporting measured observation is: The MID trace includes a successful command payload while the instance logs a parsing error at a named mapping field. After treatment, the result must be checked: A replay consumes the same raw output and produces a valid class-matched CI payload.
Incorrect Answers
A:Blindly broadening the range leaves the same hidden gap and increases unnecessary probes. It concerns validate exclusion lists before enabling new discovery coverage, not the failure described here: A host accepts approved credentials and returns expected command output but discovery marks the device unidentified. Sensor interpretation can fail independently of transport and authentication even when source output is correct.
B:Restrict discovery IP range to an approved CIDR is a separate consideration. In the stated situation, A host accepts approved credentials and returns expected command output but discovery marks the device unidentified. Sensor interpretation can fail independently of transport and authentication even when source output is correct. Check: The MID trace includes a successful command payload while the instance logs a parsing error at a named mapping field.
D:Network rerouting cannot fix a stale protocol credential and may introduce exposure. The question instead centers on A host accepts approved credentials and returns expected command output but discovery marks the device unidentified; the governing distinction is sensor interpretation can fail independently of transport and authentication even when source output is correct. Check: The MID trace includes a successful command payload while the instance logs a parsing error at a named mapping field.