ServiceNow CIS-Discovery Practice Test 36
Question 350
In a Discovery implementation risk workshop at Horizon Public Library, the following behavior is documented: An endpoint switches IP addresses during DHCP renewal and a third-party feed creates a second CI for the same hardware. The relevant mechanism is: IRE identification rules match stable identity evidence before deciding whether to insert or update a record. Only approved target ranges and read-only lab credentials are authorized. What is the MOST immediate reliability or governance consequence?
- Stale inventory can mislead security planning and change risk analysis
- Confusing the stages can allow duplicate insertion and misdiagnose policy effectiveness
- Unowned assets may be omitted from incident routing and patch accountability
- IP-only matching inflates CMDB inventory and fractures incident history
Explanation
Correct Answer
D:IP-only matching inflates CMDB inventory and fractures incident history. This is the plausible direct consequence of the observed failure for the documented fictional Horizon Public Library case. The defect is: An endpoint switches IP addresses during DHCP renewal and a third-party feed creates a second CI for the same hardware. The governing mechanism is: IRE identification rules match stable identity evidence before deciding whether to insert or update a record. The supporting measured observation is: The two entries share the same approved serial and hostname history but have different current IP values. After treatment, the result must be checked: Both IP states resolve to one CI and the change is reflected in the appropriate address attribute.
Incorrect Answers
A:Stale inventory can mislead security planning and change risk analysis. The question instead centers on An endpoint switches IP addresses during DHCP renewal and a third-party feed creates a second CI for the same hardware; the governing distinction is iRE identification rules match stable identity evidence before deciding whether to insert or update a record. Check: The two entries share the same approved serial and hostname history but have different current IP values.
B:That alternative is relevant to distinguish ire identification from reconciliation on a new ci, but the issue here is An endpoint switches IP addresses during DHCP renewal and a third-party feed creates a second CI for the same hardware. IRE identification rules match stable identity evidence before deciding whether to insert or update a record. Check: The two entries share the same approved serial and hostname history but have different current IP values.
C:Unowned assets may be omitted from incident routing and patch accountability. It concerns inspect a cmdb health failure from a missing required owner field, not the failure described here: An endpoint switches IP addresses during DHCP renewal and a third-party feed creates a second CI for the same hardware. IRE identification rules match stable identity evidence before deciding whether to insert or update a record. Check: The two entries share the same approved serial and hostname history but have different current IP values.
Question 351
The owner of Hillside Regional Clinic asks for a new risk decision after a prior correction failed to resolve this issue: A pattern extracts the first listening process row and mistakenly associates an unrelated process with the monitored port. The replay still demonstrates: The test response lists a logging daemon above the target listener, and the pattern stores the daemon process ID. No test may merge distinct customer or device identities for convenience. What specific risk is most likely to follow from the described context defect?
- A collision between identifiers can merge distinct devices or generate duplicate CIs
- Incorrect process ownership produces misleading service dependency relationships
- Repeated discovery can create duplicate CIs and conflicting change histories
- Loss of high-quality inventory data degrades audit comparisons and troubleshooting
Explanation
Correct Answer
B:Incorrect process ownership produces misleading service dependency relationships. This is the plausible direct consequence of the observed failure for the documented fictional Hillside Regional Clinic case. The defect is: A pattern extracts the first listening process row and mistakenly associates an unrelated process with the monitored port. The governing mechanism is: Row selection should use a stable key or filter matching the intended service rather than record ordering. The supporting measured observation is: The test response lists a logging daemon above the target listener, and the pattern stores the daemon process ID. After treatment, the result must be checked: Reordered table fixtures still identify the same target process and port with the approved mapping.
Incorrect Answers
A:A collision between identifiers can merge distinct devices or generate duplicate CIs. The question instead centers on A pattern extracts the first listening process row and mistakenly associates an unrelated process with the monitored port; the governing distinction is row selection should use a stable key or filter matching the intended service rather than record ordering. Check: The test response lists a logging daemon above the target listener, and the pattern stores the daemon process ID.
C:That alternative is relevant to prevent duplicate pattern execution after classification, but the issue here is A pattern extracts the first listening process row and mistakenly associates an unrelated process with the monitored port. Row selection should use a stable key or filter matching the intended service rather than record ordering. Check: The test response lists a logging daemon above the target listener, and the pattern stores the daemon process ID.
D:Loss of high-quality inventory data degrades audit comparisons and troubleshooting. It concerns handle nullable fields without replacing good ci attributes with blanks, not the failure described here: A pattern extracts the first listening process row and mistakenly associates an unrelated process with the monitored port. Row selection should use a stable key or filter matching the intended service rather than record ordering.
Question 352
During a second independent permissioned MID Server integration staging lab for Hillside Regional Clinic, an attempted correction to the documented failure remains unverified: A global discovery schedule accidentally includes addresses from a segregated external customer environment. The governing rule is: An authorized discovery job must apply the account and network ownership boundary before sending probes. No test may merge distinct customer or device identities for convenience. Which trace or data finding would make this conclusion defensible?
- The IRE error refers to missing mandatory identifier data while the pattern execution itself reports success
- The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone
- The effective target list contains IPs assigned to a different customer while the change order is restricted to one tenant
- MID logs show a successful response attached to an ECC input record that remains unprocessed in the instance
Explanation
Correct Answer
C:The effective target list contains IPs assigned to a different customer while the change order is restricted to one tenant. This is the reproducible observation that distinguishes this failure for the documented fictional Hillside Regional Clinic case. The defect is: A global discovery schedule accidentally includes addresses from a segregated external customer environment. The governing mechanism is: An authorized discovery job must apply the account and network ownership boundary before sending probes. The supporting measured observation is: The effective target list contains IPs assigned to a different customer while the change order is restricted to one tenant. After treatment, the result must be checked: The run ledger proves only the named customer's approved hosts were probed.
Incorrect Answers
A:The IRE error refers to missing mandatory identifier data while the pattern execution itself reports success. The question instead centers on A global discovery schedule accidentally includes addresses from a segregated external customer environment; the governing distinction is an authorized discovery job must apply the account and network ownership boundary before sending probes. Check: The effective target list contains IPs assigned to a different customer while the change order is restricted to one tenant.
B:That alternative is relevant to use discovery behaviors to route a subnet to the appropriate mid server, but the issue here is A global discovery schedule accidentally includes addresses from a segregated external customer environment. An authorized discovery job must apply the account and network ownership boundary before sending probes. Check: The effective target list contains IPs assigned to a different customer while the change order is restricted to one tenant.
D:MID logs show a successful response attached to an ECC input record that remains unprocessed in the instance. It concerns trace a mid server response that remains unprocessed in ecc, not the failure described here: A global discovery schedule accidentally includes addresses from a segregated external customer environment. An authorized discovery job must apply the account and network ownership boundary before sending probes.
Question 353
An owner-private simulated closeout at Summit City Transport addresses this failure: A Discovery implementation owner enables enterprise-wide recurring runs before the representative pilot completes its credential and CMDB acceptance checks. Its independent defect indicator is: The pilot's successful-port count looks good but duplicate-CI findings and access denials remain unresolved. No test may merge distinct customer or device identities for convenience. Select TWO complementary choices: a bounded correction and an independent acceptance test.
- Split discovery scope into correctly approved contexts and exclude externally owned address blocks
- The next run uses the approved current account and the failed old record is no longer attempted
- Keep the schedule limited to the pilot assets until the documented acceptance defects are closed
- A scoped SNMP inventory response succeeds without changing network boundaries or using a fallback shared secret
- Pilot CI and protocol tests pass before the next approved subnet is added to the effective schedule
Explanation
Correct Answers
C:Keep the schedule limited to the pilot assets until the documented acceptance defects are closed. This is the case-specific scoped correction, not a justification to expand the authorized scan or credential scope. In the fictional Summit City Transport scenario, the observed defect is: A Discovery implementation owner enables enterprise-wide recurring runs before the representative pilot completes its credential and CMDB acceptance checks. The causal principle is: Staged discovery rollout should gate expansion on validated reachability, identity quality, and target-owner approval. The proposed change must still pass this independent test: Pilot CI and protocol tests pass before the next approved subnet is added to the effective schedule.
E:Pilot CI and protocol tests pass before the next approved subnet is added to the effective schedule. This is the independently testable outcome that validates the targeted repair. The authorized change for the fictional Summit City Transport scenario is: Keep the schedule limited to the pilot assets until the documented acceptance defects are closed. The prior failing observation was: The pilot's successful-port count looks good but duplicate-CI findings and access denials remain unresolved. A deployment record without this tested outcome does not prove effectiveness.
Incorrect Answers
A:That alternative is relevant to use schedule-specific domain or network permissions, but the issue here is A Discovery implementation owner enables enterprise-wide recurring runs before the representative pilot completes its credential and CMDB acceptance checks. Keep the schedule limited to the pilot assets until the documented acceptance defects are closed. Check: The pilot's successful-port count looks good but duplicate-CI findings and access denials remain unresolved.
B:The next run uses the approved current account and the failed old record is no longer attempted. It concerns distinguish missing credentials from wrong account selection priority, not the failure described here: A Discovery implementation owner enables enterprise-wide recurring runs before the representative pilot completes its credential and CMDB acceptance checks. Keep the schedule limited to the pilot assets until the documented acceptance defects are closed.
D:Distinguish expired SNMP credentials from unreachable devices is a separate consideration. In the stated situation, A Discovery implementation owner enables enterprise-wide recurring runs before the representative pilot completes its credential and CMDB acceptance checks. Keep the schedule limited to the pilot assets until the documented acceptance defects are closed. Check: The pilot's successful-port count looks good but duplicate-CI findings and access denials remain unresolved.
Question 354
During read-only asset coverage assessment, the change advisory delegate at Greenford University observes: A host runs two near-identical horizontal patterns and creates conflicting application records after a new classifier was added. Independent logs state: The discovery trace shows both classifiers match the same host characteristics and trigger overlapping pattern IDs. The result must be reproducible against the original failed fixture and a passing control. Which technical explanation is supported by the Discovery log? Choose ONE.
- The classifier-to-pattern mapping must be checked before altering individual pattern operations
- Row selection should use a stable key or filter matching the intended service rather than record ordering
- Normalization must follow an approved canonical representation and not silently change digest content
- Extraction logic must be grounded in observed current command output and tested against permitted variants
Explanation
Correct Answer
A:The classifier-to-pattern mapping must be checked before altering individual pattern operations. This is the underlying causal Discovery implementation principle for the documented fictional Greenford University case. The defect is: A host runs two near-identical horizontal patterns and creates conflicting application records after a new classifier was added. The governing mechanism is: The classifier-to-pattern mapping must be checked before altering individual pattern operations. The supporting measured observation is: The discovery trace shows both classifiers match the same host characteristics and trigger overlapping pattern IDs. After treatment, the result must be checked: The host triggers only the intended pattern and updates the previously identified application record once.
Incorrect Answers
B:That alternative is relevant to select a table row by service identifier rather than its position, but the issue here is A host runs two near-identical horizontal patterns and creates conflicting application records after a new classifier was added. The classifier-to-pattern mapping must be checked before altering individual pattern operations. Check: The discovery trace shows both classifiers match the same host characteristics and trigger overlapping pattern IDs.
C:Normalization must follow an approved canonical representation and not silently change digest content. It concerns preserve whitespace significant to a certificate fingerprint, not the failure described here: A host runs two near-identical horizontal patterns and creates conflicting application records after a new classifier was added. The classifier-to-pattern mapping must be checked before altering individual pattern operations.
D:Inspect raw command output before assigning an application version is a separate consideration. In the stated situation, A host runs two near-identical horizontal patterns and creates conflicting application records after a new classifier was added. The classifier-to-pattern mapping must be checked before altering individual pattern operations. Check: The discovery trace shows both classifiers match the same host characteristics and trigger overlapping pattern IDs.
Question 355
In a Discovery implementation risk workshop at Hillside Regional Clinic, the following behavior is documented: A newly added classifier launches an application-specific connection section before the host-level discovery supplies its environment variables. The relevant mechanism is: Pattern section dependencies need explicit execution order and valid prerequisites across classifications. Production-affecting actions require an independently verified change approval. What is the MOST immediate reliability or governance consequence?
- Overbroad matching can corrupt CI attributes and expose unnecessary diagnostic text
- Premature relationship emission can leave orphaned or inaccurate CMDB dependency links
- Column shifts corrupt multiple CI attributes in one execution
- Changed classification may introduce a hidden dependency regression
Explanation
Correct Answer
D:Changed classification may introduce a hidden dependency regression. This is the plausible direct consequence of the observed failure for the documented fictional Hillside Regional Clinic case. The defect is: A newly added classifier launches an application-specific connection section before the host-level discovery supplies its environment variables. The governing mechanism is: Pattern section dependencies need explicit execution order and valid prerequisites across classifications. The supporting measured observation is: The new classifier path omits the host variable population, causing a connection section to use an undefined hostname. After treatment, the result must be checked: Old and new classified host fixtures yield the same valid endpoint identity and correct connection map.
Incorrect Answers
A:That alternative is relevant to capture multiline service metadata with a bounded match, but the issue here is A newly added classifier launches an application-specific connection section before the host-level discovery supplies its environment variables. Pattern section dependencies need explicit execution order and valid prerequisites across classifications. Check: The new classifier path omits the host variable population, causing a connection section to use an undefined hostname.
B:Premature relationship emission can leave orphaned or inaccurate CMDB dependency links. It concerns run identification before attempting dependent relationship creation, not the failure described here: A newly added classifier launches an application-specific connection section before the host-level discovery supplies its environment variables. Pattern section dependencies need explicit execution order and valid prerequisites across classifications.
C:Validate a tabular mapping with missing optional columns is a separate consideration. In the stated situation, A newly added classifier launches an application-specific connection section before the host-level discovery supplies its environment variables. Pattern section dependencies need explicit execution order and valid prerequisites across classifications. Check: The new classifier path omits the host variable population, causing a connection section to use an undefined hostname.
Question 356
The owner of Westfield University asks for a new risk decision after a prior correction failed to resolve this issue: An operations team blames slow devices after the discovery job takes four hours longer than normal. The replay still demonstrates: Average target response times are unchanged but ECC queue wait time and worker utilization have doubled. Production-affecting actions require an independently verified change approval. Which outcome is directly supported if the issue remains unresolved?
- A completed scan can still populate misleading operational data
- Aggregate metrics can conceal material gaps in the most critical services
- Misattributed delay can trigger unnecessary scan configuration changes
- Shared privileged identities reduce accountability and enlarge the impact of credential compromise
Explanation
Correct Answer
C:Misattributed delay can trigger unnecessary scan configuration changes. This is the plausible direct consequence of the observed failure for the documented fictional Westfield University case. The defect is: An operations team blames slow devices after the discovery job takes four hours longer than normal. The governing mechanism is: MID and ECC telemetry should distinguish target latency from queue and processing congestion. The supporting measured observation is: Average target response times are unchanged but ECC queue wait time and worker utilization have doubled. After treatment, the result must be checked: A representative run completes within the expected window with normal queue age and no target scope expansion.
Incorrect Answers
A:That alternative is relevant to include the cmdb data steward in discovery acceptance, but the issue here is An operations team blames slow devices after the discovery job takes four hours longer than normal. MID and ECC telemetry should distinguish target latency from queue and processing congestion. Check: Average target response times are unchanged but ECC queue wait time and worker utilization have doubled.
B:Aggregate metrics can conceal material gaps in the most critical services. It concerns use per-target discovery errors rather than aggregate success rate, not the failure described here: An operations team blames slow devices after the discovery job takes four hours longer than normal. MID and ECC telemetry should distinguish target latency from queue and processing congestion. Check: Average target response times are unchanged but ECC queue wait time and worker utilization have doubled. For the risk decision in this case, the decisive response is to misattributed delay can trigger unnecessary scan configuration changes.
D:Validate the MID Server application identity and permissions is a separate consideration. In the stated situation, An operations team blames slow devices after the discovery job takes four hours longer than normal. MID and ECC telemetry should distinguish target latency from queue and processing congestion. Check: Average target response times are unchanged but ECC queue wait time and worker utilization have doubled.
Question 357
A separate authorized security architecture reviewer at Copper Hill Retail reopens debug a connection section before changing application identification because a previous closeout did not prove the result. Evidence still indicates: The process-identification step succeeds, but the connection section lists a blank remote endpoint despite an approved sample socket record. No test may merge distinct customer or device identities for convenience. Which TWO options form the appropriate remediation-and-verification pair?
- Debug the connection section against the controlled socket sample and correct the endpoint extraction mapping
- The re-run emits the documented source and destination endpoints and maps only the expected application dependency
- Guard fallback execution on missing or invalid owner values and retain source precedence
- The host triggers only the intended pattern and updates the previously identified application record once
- A fixture with both fields populates the correct path and does not mistake the application name for a location
Explanation
Correct Answers
A:Debug the connection section against the controlled socket sample and correct the endpoint extraction mapping. This is the case-specific scoped correction, not a justification to expand the authorized scan or credential scope. In the fictional Copper Hill Retail scenario, the observed defect is: A dependency pattern discovers a web process but fails to associate its listener with the upstream database host. The causal principle is: Connection discovery must collect and map endpoints before dependent relationship output can be trusted. The proposed change must still pass this independent test: The re-run emits the documented source and destination endpoints and maps only the expected application dependency.
B:The re-run emits the documented source and destination endpoints and maps only the expected application dependency. This is the independently testable outcome that validates the targeted repair. The authorized change for the fictional Copper Hill Retail scenario is: Debug the connection section against the controlled socket sample and correct the endpoint extraction mapping. The prior failing observation was: The process-identification step succeeds, but the connection section lists a blank remote endpoint despite an approved sample socket record. A deployment record without this tested outcome does not prove effectiveness.
Incorrect Answers
C:Guard fallback execution on missing or invalid owner values and retain source precedence. It concerns avoid overwriting a verified attribute with a later fallback match, not the failure described here: A dependency pattern discovers a web process but fails to associate its listener with the upstream database host. Debug the connection section against the controlled socket sample and correct the endpoint extraction mapping.
D:Prevent duplicate pattern execution after classification is a separate consideration. In the stated situation, A dependency pattern discovers a web process but fails to associate its listener with the upstream database host. Debug the connection section against the controlled socket sample and correct the endpoint extraction mapping. Check: The process-identification step succeeds, but the connection section lists a blank remote endpoint despite an approved sample socket record.
E:A fixture with both fields populates the correct path and does not mistake the application name for a location. The question instead centers on A dependency pattern discovers a web process but fails to associate its listener with the upstream database host; the governing distinction is debug the connection section against the controlled socket sample and correct the endpoint extraction mapping. Check: The process-identification step succeeds, but the connection section lists a blank remote endpoint despite an approved sample socket record.
Question 358
During permissioned MID Server integration staging lab, the CMDB steward at Brookhaven Freight observes: A pattern discards a valid application CI update when a secondary outbound-link query times out. Independent logs state: Logs show stable instance ID and version followed by a timeout on an optional remote connection inventory step. The operator may not broaden credential or subnet permissions to bypass a failed test. What Discovery implementation principle MOST directly explains the cause?
- Connection mapping needs identified endpoints or supported dependency rules before a relationship can be committed reliably
- Identity discovery and optional connection evidence should fail with a bounded status that preserves valid known information
- Fallback logic should apply only when authoritative extraction failed and must not override verified results
- Required pattern attributes need explicit nonempty validation and controlled failure when evidence is insufficient
Explanation
Correct Answer
B:Identity discovery and optional connection evidence should fail with a bounded status that preserves valid known information. This is the underlying causal Discovery implementation principle for the documented fictional Brookhaven Freight case. The defect is: A pattern discards a valid application CI update when a secondary outbound-link query times out. The governing mechanism is: Identity discovery and optional connection evidence should fail with a bounded status that preserves valid known information. The supporting measured observation is: Logs show stable instance ID and version followed by a timeout on an optional remote connection inventory step. After treatment, the result must be checked: The CI retains verified attributes and the missing edge is explicitly marked for a scoped retry.
Incorrect Answers
A:Connection mapping needs identified endpoints or supported dependency rules before a relationship can be committed reliably. It concerns run identification before attempting dependent relationship creation, not the failure described here: A pattern discards a valid application CI update when a secondary outbound-link query times out. Identity discovery and optional connection evidence should fail with a bounded status that preserves valid known information.
C:Avoid overwriting a verified attribute with a later fallback match is a separate consideration. In the stated situation, A pattern discards a valid application CI update when a secondary outbound-link query times out. Identity discovery and optional connection evidence should fail with a bounded status that preserves valid known information. Check: Logs show stable instance ID and version followed by a timeout on an optional remote connection inventory step.
D:Required pattern attributes need explicit nonempty validation and controlled failure when evidence is insufficient. The question instead centers on A pattern discards a valid application CI update when a secondary outbound-link query times out; the governing distinction is identity discovery and optional connection evidence should fail with a bounded status that preserves valid known information. Check: Logs show stable instance ID and version followed by a timeout on an optional remote connection inventory step.
Question 359
During synthetic CMDB reconciliation rehearsal, the MID Server operator at Clearwater Research Institute observes: A host accepts approved credentials and returns expected command output but discovery marks the device unidentified. Independent logs state: The MID trace includes a successful command payload while the instance logs a parsing error at a named mapping field. Only approved target ranges and read-only lab credentials are authorized. Which principle should the reviewer use to interpret this test?
- Discovery should rely on applicable stable identification rules and IRE processing rather than IP address as the sole key
- An open port establishes possible service reachability but not platform classification or unique identity
- Sensor interpretation can fail independently of transport and authentication even when source output is correct
- Classification chooses the target class before its identification and exploration pattern can be selected
Explanation
Correct Answer
C:Sensor interpretation can fail independently of transport and authentication even when source output is correct. This is the underlying causal Discovery implementation principle for the documented fictional Clearwater Research Institute 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:Discovery should rely on applicable stable identification rules and IRE processing rather than IP address as the sole key. It concerns prevent duplicate server cis when primary identifiers change, 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:Explain discovery stages when a port is open but no OS evidence exists 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:Classification chooses the target class before its identification and exploration pattern can be selected. 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.
Question 360
In a Discovery implementation risk workshop at Blackstone Regional Services, the following behavior is documented: A sponsor demands every reachable IP be inventoried without naming the business services or CMDB quality target. The relevant mechanism is: Implementation readiness should align approved asset coverage and CI relationship accuracy to specific business outcomes. No test may merge distinct customer or device identities for convenience. Which failure impact should the decision owner prioritize?
- Raw scan volume can look successful while important service dependencies remain unknown
- Incompatible workers may misprocess probes or lose supported features
- Broad inventory alone may not improve incident containment or impact analysis
- Mixed trust zones risk cross-customer probing and incorrect discovery attribution
Explanation
Correct Answer
A:Raw scan volume can look successful while important service dependencies remain unknown. This is the plausible direct consequence of the observed failure for the documented fictional Blackstone Regional Services case. The defect is: A sponsor demands every reachable IP be inventoried without naming the business services or CMDB quality target. The governing mechanism is: Implementation readiness should align approved asset coverage and CI relationship accuracy to specific business outcomes. The supporting measured observation is: The project plan lists scan counts but no critical service inventory baseline, acceptance criterion or accountable owner. After treatment, the result must be checked: The sponsor accepts the pilot against recorded CI and dependency thresholds rather than number of scanned addresses.
Incorrect Answers
B:Incompatible workers may misprocess probes or lose supported features. It concerns track mid server version and upgrade readiness, not the failure described here: A sponsor demands every reachable IP be inventoried without naming the business services or CMDB quality target. Implementation readiness should align approved asset coverage and CI relationship accuracy to specific business outcomes. Check: The project plan lists scan counts but no critical service inventory baseline, acceptance criterion or accountable owner.
C:Map Discovery coverage to a service outage investigation objective is a separate consideration. In the stated situation, A sponsor demands every reachable IP be inventoried without naming the business services or CMDB quality target. Implementation readiness should align approved asset coverage and CI relationship accuracy to specific business outcomes. Check: The project plan lists scan counts but no critical service inventory baseline, acceptance criterion or accountable owner.
D:Mixed trust zones risk cross-customer probing and incorrect discovery attribution. The question instead centers on A sponsor demands every reachable IP be inventoried without naming the business services or CMDB quality target; the governing distinction is implementation readiness should align approved asset coverage and CI relationship accuracy to specific business outcomes. Check: The project plan lists scan counts but no critical service inventory baseline, acceptance criterion or accountable owner.