ServiceNow CIS-Discovery Practice Test 64
Question 630
In a Discovery implementation risk workshop at Clearwater Research Institute, the following behavior is documented: A team adds broad protocol probes to a schedule even though only Linux SSH inventory is authorized for the pilot. The relevant mechanism is: Port and service probe configuration should reflect the approved discovery purpose and asset constraints. Only approved target ranges and read-only lab credentials are authorized. What is the MOST immediate reliability or governance consequence?
- Unnecessary probes create operational noise and may violate target access approvals
- False unreachable status can trigger unnecessary network escalations and wrong coverage decisions
- Blindly broadening the range leaves the same hidden gap and increases unnecessary probes
- Credential rotation cannot fix malformed output-to-CI parsing and may disrupt other jobs
Explanation
Correct Answer
A:Unnecessary probes create operational noise and may violate target access approvals. This is the plausible direct consequence of the observed failure for the documented fictional Clearwater Research Institute 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
B:Differentiate unreachable targets from a cancelled discovery job 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.
C:Blindly broadening the range leaves the same hidden gap and increases unnecessary probes. 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.
D:That alternative is relevant to investigate sensor parse failure after successful credentialed connection, but the issue here is 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.
Question 631
A separate authorized configuration data analyst at Lighthouse Financial reopens validate a pattern correction with source and target evidence because a previous closeout did not prove the result. Evidence still indicates: Step logs report success, but a CMDB query still shows the application CI missing its declared service relationship. Business service continuity and CMDB evidence must be preserved throughout validation. Choose TWO: one approved intervention and one reproducible outcome check.
- Filter nonservice interfaces and validate selected addresses against the documented target interface criteria
- Compare the successful step output with the governed CI and relationship payload produced by the full run
- A controlled full replay updates the correct CI and expected relationships with matching source evidence
- The re-run emits the documented source and destination endpoints and maps only the expected application dependency
- A fixture with both fields populates the correct path and does not mistake the application name for a location
Explanation
Correct Answers
B:Compare the successful step output with the governed CI and relationship payload produced by the full run. This is the case-specific scoped correction, not a justification to expand the authorized scan or credential scope. In the fictional Lighthouse Financial scenario, the observed defect is: An engineer marks a pattern incident resolved because a previously failing step now shows green, without checking its CMDB result. The causal principle is: A passing pattern step is necessary but not sufficient to prove the intended CI and relationships were produced. The proposed change must still pass this independent test: A controlled full replay updates the correct CI and expected relationships with matching source evidence.
C:A controlled full replay updates the correct CI and expected relationships with matching source evidence. This is the independently testable outcome that validates the targeted repair. The authorized change for the fictional Lighthouse Financial scenario is: Compare the successful step output with the governed CI and relationship payload produced by the full run. The prior failing observation was: Step logs report success, but a CMDB query still shows the application CI missing its declared service relationship. A deployment record without this tested outcome does not prove effectiveness.
Incorrect Answers
A:Filter nonservice interfaces and validate selected addresses against the documented target interface criteria. The question instead centers on An engineer marks a pattern incident resolved because a previously failing step now shows green, without checking its CMDB result; the governing distinction is compare the successful step output with the governed CI and relationship payload produced by the full run. Check: Step logs report success, but a CMDB query still shows the application CI missing its declared service relationship.
D:That alternative is relevant to debug a connection section before changing application identification, but the issue here is An engineer marks a pattern incident resolved because a previously failing step now shows green, without checking its CMDB result. Compare the successful step output with the governed CI and relationship payload produced by the full run. Check: Step logs report success, but a CMDB query still shows the application CI missing its declared service relationship.
E:A fixture with both fields populates the correct path and does not mistake the application name for a location. It concerns extract a named installation directory from a key-value response, not the failure described here: An engineer marks a pattern incident resolved because a previously failing step now shows green, without checking its CMDB result. Compare the successful step output with the governed CI and relationship payload produced by the full run.
Question 632
The owner of Harborstone Telecom asks for a new risk decision after a prior correction failed to resolve this issue: A discovery target has no response records after an administrator cancels the schedule at the start of its window. The replay still demonstrates: The run history records a user cancellation and no per-target ECC probe messages were generated. No test may merge distinct customer or device identities for convenience. Which adverse result is supported by the available evidence?
- False unreachable status can trigger unnecessary network escalations and wrong coverage decisions
- Cross-customer CI merges can expose wrong dependency data and undermine tenancy controls
- A sensor mapping defect can silently suppress an essential deployed service
- Stale target definitions create false asset counts and missing configuration items
Explanation
Correct Answer
A:False unreachable status can trigger unnecessary network escalations and wrong coverage decisions. This is the plausible direct consequence of the observed failure for the documented fictional Harborstone Telecom case. The defect is: A discovery target has no response records after an administrator cancels the schedule at the start of its window. The governing mechanism is: A missing target result is not proof of network reachability failure unless request execution actually occurred. The supporting measured observation is: The run history records a user cancellation and no per-target ECC probe messages were generated. After treatment, the result must be checked: A permitted rerun generates target probes and produces an explicit reachable or unreachable status.
Incorrect Answers
B:Cross-customer CI merges can expose wrong dependency data and undermine tenancy controls. The question instead centers on A discovery target has no response records after an administrator cancels the schedule at the start of its window; the governing distinction is a missing target result is not proof of network reachability failure unless request execution actually occurred. Check: The run history records a user cancellation and no per-target ECC probe messages were generated.
C:That alternative is relevant to inspect sensor interpretation when two services share a host, but the issue here is A discovery target has no response records after an administrator cancels the schedule at the start of its window. A missing target result is not proof of network reachability failure unless request execution actually occurred. Check: The run history records a user cancellation and no per-target ECC probe messages were generated.
D:Stale target definitions create false asset counts and missing configuration items. It concerns maintain cluster discovery scope when nodes rotate addresses, not the failure described here: A discovery target has no response records after an administrator cancels the schedule at the start of its window. A missing target result is not proof of network reachability failure unless request execution actually occurred. Check: The run history records a user cancellation and no per-target ECC probe messages were generated.
Question 633
During isolated ServiceNow Discovery test instance, the Discovery operations lead at Sunridge Infrastructure observes: A discovery schedule selects a global credential set instead of the authorized site-specific account for a protected environment. Independent logs state: The access audit shows successful authentication from an all-sites account while the site change request specifies a restricted identity. The decision must preserve approved CI source authority and relationship direction. Which discovery and configuration-data mechanism applies to these facts?
- Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation
- Credential binding should follow the schedule's target and authority scope, not select any technically working login
- Discovery completion depends on request dispatch, MID execution, returned ECC output, and sensor consumption
- Cluster coverage should use supported authorized membership and address scope rather than assuming one endpoint represents the fleet
Explanation
Correct Answer
B:Credential binding should follow the schedule's target and authority scope, not select any technically working login. This is the underlying causal Discovery implementation principle for the documented fictional Sunridge Infrastructure case. The defect is: A discovery schedule selects a global credential set instead of the authorized site-specific account for a protected environment. The governing mechanism is: Credential binding should follow the schedule's target and authority scope, not select any technically working login. The supporting measured observation is: The access audit shows successful authentication from an all-sites account while the site change request specifies a restricted identity. After treatment, the result must be checked: The target is discovered with the site identity and audit logs show no use of the prohibited global account.
Incorrect Answers
A:Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. The question instead centers on A discovery schedule selects a global credential set instead of the authorized site-specific account for a protected environment; the governing distinction is credential binding should follow the schedule's target and authority scope, not select any technically working login.
C:That alternative is relevant to correlate ecc input and output to distinguish queue lag, but the issue here is A discovery schedule selects a global credential set instead of the authorized site-specific account for a protected environment. Credential binding should follow the schedule's target and authority scope, not select any technically working login. Check: The access audit shows successful authentication from an all-sites account while the site change request specifies a restricted identity.
D:Cluster coverage should use supported authorized membership and address scope rather than assuming one endpoint represents the fleet. It concerns maintain cluster discovery scope when nodes rotate addresses, not the failure described here: A discovery schedule selects a global credential set instead of the authorized site-specific account for a protected environment. Credential binding should follow the schedule's target and authority scope, not select any technically working login.
Question 634
In a Discovery implementation risk workshop at Northlake Cloud Services, the following behavior is documented: A critical MID Server remains on an unsupported integration version after the ServiceNow instance was upgraded. The relevant mechanism is: Worker maintenance should include supported version compatibility and controlled upgrade planning. Uncommon but critical failure cases must be tested before closing the defect. What is the MOST immediate reliability or governance consequence?
- A completed scan can still populate misleading operational data
- Incompatible workers may misprocess probes or lose supported features
- Shared privileged identities reduce accountability and enlarge the impact of credential compromise
- Stale worker status can delay new jobs and conceal an infrastructure outage
Explanation
Correct Answer
B:Incompatible workers may misprocess probes or lose supported features. This is the plausible direct consequence of the observed failure for the documented fictional Northlake Cloud Services case. The defect is: A critical MID Server remains on an unsupported integration version after the ServiceNow instance was upgraded. The governing mechanism is: Worker maintenance should include supported version compatibility and controlled upgrade planning. The supporting measured observation is: The instance shows an updated release while the MID version report identifies an unsupported build and repeated processing warnings. After treatment, the result must be checked: The upgraded MID validates and completes representative discovery patterns with no new ECC processing errors.
Incorrect Answers
A:A completed scan can still populate misleading operational data. The question instead centers on A critical MID Server remains on an unsupported integration version after the ServiceNow instance was upgraded; the governing distinction is worker maintenance should include supported version compatibility and controlled upgrade planning. Check: The instance shows an updated release while the MID version report identifies an unsupported build and repeated processing warnings.
C:That alternative is relevant to validate the mid server application identity and permissions, but the issue here is A critical MID Server remains on an unsupported integration version after the ServiceNow instance was upgraded. Worker maintenance should include supported version compatibility and controlled upgrade planning. Check: The instance shows an updated release while the MID version report identifies an unsupported build and repeated processing warnings.
D:Stale worker status can delay new jobs and conceal an infrastructure outage. It concerns distinguish stale mid heartbeat from an active discovery success, not the failure described here: A critical MID Server remains on an unsupported integration version after the ServiceNow instance was upgraded. Worker maintenance should include supported version compatibility and controlled upgrade planning. Check: The instance shows an updated release while the MID version report identifies an unsupported build and repeated processing warnings.
Question 635
In a Discovery implementation risk workshop at Sunridge Infrastructure, the following behavior is documented: A storage device is automatically moved into a network class after one ambiguous model string is parsed. The relevant mechanism is: Reclassification must be supported by reliable class evidence and an authorized class-change process. The decision must preserve approved CI source authority and relationship direction. Which adverse result is supported by the available evidence?
- A wrong class can invalidate inherited attributes and dependency reports
- IP-only matching inflates CMDB inventory and fractures incident history
- Losing dependency edges breaks operational impact analysis while appearing to improve taxonomy
- Unauthorized attribute overwrites degrade financial and operational reporting
Explanation
Correct Answer
A:A wrong class can invalidate inherited attributes and dependency reports. This is the plausible direct consequence of the observed failure for the documented fictional Sunridge Infrastructure case. The defect is: A storage device is automatically moved into a network class after one ambiguous model string is parsed. The governing mechanism is: Reclassification must be supported by reliable class evidence and an authorized class-change process. The supporting measured observation is: The original CI is a storage array but the new payload contains only a generic vendor term used by multiple product lines. After treatment, the result must be checked: The fixture with ambiguous model evidence retains its class until the approved discriminator proves a change.
Incorrect Answers
B:IP-only matching inflates CMDB inventory and fractures incident history. The question instead centers on A storage device is automatically moved into a network class after one ambiguous model string is parsed; the governing distinction is reclassification must be supported by reliable class evidence and an authorized class-change process. Check: The original CI is a storage array but the new payload contains only a generic vendor term used by multiple product lines.
C:That alternative is relevant to preserve relationship evidence when an application ci is reclassified, but the issue here is A storage device is automatically moved into a network class after one ambiguous model string is parsed. Reclassification must be supported by reliable class evidence and an authorized class-change process. Check: The original CI is a storage array but the new payload contains only a generic vendor term used by multiple product lines. For the risk decision in this case, the decisive response is to a wrong class can invalidate inherited attributes and dependency reports.
D:Unauthorized attribute overwrites degrade financial and operational reporting. It concerns apply reconciliation priority when discovery and asset management disagree, not the failure described here: A storage device is automatically moved into a network class after one ambiguous model string is parsed. Reclassification must be supported by reliable class evidence and an authorized class-change process. Check: The original CI is a storage array but the new payload contains only a generic vendor term used by multiple product lines.
Question 636
During isolated ServiceNow Discovery test instance, the Discovery operations lead at Alder Point Banking observes: A pattern treats a client-side ephemeral port as a stable database instance identifier. Independent logs state: The same database appears as different records whenever its client uses a new ephemeral source port. The decision must preserve approved CI source authority and relationship direction. Which ServiceNow Discovery principle BEST explains the failure? Choose ONE.
- Transient connection details are not reliable identity attributes and must be mapped separately from persistent instance keys
- Fallback logic should apply only when authoritative extraction failed and must not override verified results
- Identity discovery and optional connection evidence should fail with a bounded status that preserves valid known information
- A structured extraction should use stable header names or a schema-aware branch rather than fixed offsets on varying formats
Explanation
Correct Answer
A:Transient connection details are not reliable identity attributes and must be mapped separately from persistent instance keys. This is the underlying causal Discovery implementation principle for the documented fictional Alder Point Banking case. The defect is: A pattern treats a client-side ephemeral port as a stable database instance identifier. The governing mechanism is: Transient connection details are not reliable identity attributes and must be mapped separately from persistent instance keys. The supporting measured observation is: The same database appears as different records whenever its client uses a new ephemeral source port. After treatment, the result must be checked: Multiple client sessions update the same database CI while connections preserve their observed endpoints.
Incorrect Answers
B:Fallback logic should apply only when authoritative extraction failed and must not override verified results. The question instead centers on A pattern treats a client-side ephemeral port as a stable database instance identifier; the governing distinction is transient connection details are not reliable identity attributes and must be mapped separately from persistent instance keys. Check: The same database appears as different records whenever its client uses a new ephemeral source port.
C:That alternative is relevant to preserve identification data when an optional connection step fails, but the issue here is A pattern treats a client-side ephemeral port as a stable database instance identifier. Transient connection details are not reliable identity attributes and must be mapped separately from persistent instance keys. Check: The same database appears as different records whenever its client uses a new ephemeral source port.
D:A structured extraction should use stable header names or a schema-aware branch rather than fixed offsets on varying formats. It concerns validate a tabular mapping with missing optional columns, not the failure described here: A pattern treats a client-side ephemeral port as a stable database instance identifier. Transient connection details are not reliable identity attributes and must be mapped separately from persistent instance keys.
Question 637
A separate authorized Discovery operations lead at Eastgate Hospitality reopens distinguish classification failure from identification failure because a previous closeout did not prove the result. Evidence still indicates: The ECC trace shows a completed SSH probe and a failed classifier response with no horizontal pattern execution. Only approved target ranges and read-only lab credentials are authorized. Choose TWO: one approved intervention and one reproducible outcome check.
- Apply class-appropriate stable identifiers and scoped source ownership before allowing merge behavior
- Validate the approved classification input and rules, then replay from the failing stage
- The rebuilt instance updates the intended existing CI and preserves supported relationships without a second record
- The same test target is classified correctly and invokes the expected identification and exploration pattern
- The device receives the correct network class and subsequent discovery does not duplicate the prior CI
Explanation
Correct Answers
B:Validate the approved classification input and rules, then replay from the failing stage. This is the case-specific scoped correction, not a justification to expand the authorized scan or credential scope. In the fictional Eastgate Hospitality scenario, the observed defect is: A device responds to SSH but never receives the expected server class, and the team edits an application pattern. The causal principle is: Classification chooses the target class before its identification and exploration pattern can be selected. The proposed change must still pass this independent test: The same test target is classified correctly and invokes the expected identification and exploration pattern.
D:The same test target is classified correctly and invokes the expected identification and exploration pattern. This is the independently testable outcome that validates the targeted repair. The authorized change for the fictional Eastgate Hospitality scenario is: Validate the approved classification input and rules, then replay from the failing stage. The prior failing observation was: The ECC trace shows a completed SSH probe and a failed classifier response with no horizontal pattern execution. A deployment record without this tested outcome does not prove effectiveness.
Incorrect Answers
A:That alternative is relevant to resolve target name collisions across segregated discovery domains, but the issue here is A device responds to SSH but never receives the expected server class, and the team edits an application pattern. Validate the approved classification input and rules, then replay from the failing stage. Check: The ECC trace shows a completed SSH probe and a failed classifier response with no horizontal pattern execution.
C:The rebuilt instance updates the intended existing CI and preserves supported relationships without a second record. It concerns prevent duplicate server cis when primary identifiers change, not the failure described here: A device responds to SSH but never receives the expected server class, and the team edits an application pattern. Validate the approved classification input and rules, then replay from the failing stage.
E:Use the correct classifier after SNMP port detection 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. Validate the approved classification input and rules, then replay from the failing stage. Check: The ECC trace shows a completed SSH probe and a failed classifier response with no horizontal pattern execution.
Question 638
During synthetic CMDB reconciliation rehearsal, the MID Server operator at Horizon Public Library observes: A discovery scan request reaches a MID Server and yields output, but the instance never records a discovered CI. Independent logs state: MID logs show a successful response attached to an ECC input record that remains unprocessed in the instance. Only approved target ranges and read-only lab credentials are authorized. Which technical explanation is supported by the Discovery log? Choose ONE.
- Staged discovery rollout should gate expansion on validated reachability, identity quality, and target-owner approval
- Request execution and instance-side ECC response processing are separate lifecycle steps requiring correlated status
- Schedule windows need an explicitly understood timezone and local maintenance constraint where targets span regions
- Pattern results and their sensor mapping must retain distinct identified application instances and relationships
Explanation
Correct Answer
B:Request execution and instance-side ECC response processing are separate lifecycle steps requiring correlated status. This is the underlying causal Discovery implementation principle for the documented fictional Horizon Public Library case. The defect is: A discovery scan request reaches a MID Server and yields output, but the instance never records a discovered CI. The governing mechanism is: Request execution and instance-side ECC response processing are separate lifecycle steps requiring correlated status. The supporting measured observation is: MID logs show a successful response attached to an ECC input record that remains unprocessed in the instance. After treatment, the result must be checked: The response is consumed once and produces the expected class and CI update without resending unrelated scans.
Incorrect Answers
A:That alternative is relevant to preserve a controlled pilot before enabling production schedules, but the issue here is A discovery scan request reaches a MID Server and yields output, but the instance never records a discovered CI. Request execution and instance-side ECC response processing are separate lifecycle steps requiring correlated status. Check: MID logs show a successful response attached to an ECC input record that remains unprocessed in the instance.
C:Schedule windows need an explicitly understood timezone and local maintenance constraint where targets span regions. It concerns verify schedule timezone in globally distributed discovery deployments, not the failure described here: A discovery scan request reaches a MID Server and yields output, but the instance never records a discovered CI. Request execution and instance-side ECC response processing are separate lifecycle steps requiring correlated status.
D:Inspect sensor interpretation when two services share a host is a separate consideration. In the stated situation, A discovery scan request reaches a MID Server and yields output, but the instance never records a discovered CI. Request execution and instance-side ECC response processing are separate lifecycle steps requiring correlated status. Check: MID logs show a successful response attached to an ECC input record that remains unprocessed in the instance. For the mechanism decision in this case, the decisive response is to request execution and instance-side ECC response processing are separate lifecycle steps requiring correlated status.
Question 639
The owner of Copper Hill Retail asks for a new risk decision after a prior correction failed to resolve this issue: A pattern captures both serial and chassis ID into the same output variable, leaving the final CI identity dependent on step order. The replay still demonstrates: The debug history shows two valid source fields but the second match overwrites the first before the identification payload is built. No test may merge distinct customer or device identities for convenience. Which outcome is directly supported if the issue remains unresolved?
- An optional topology error should not erase accurate application inventory data
- Incomplete identities can generate duplicate or unnamed application instances
- The CMDB can contain an isolated application CI and omit an essential dependency
- A collision between identifiers can merge distinct devices or generate duplicate CIs
Explanation
Correct Answer
D:A collision between identifiers can merge distinct devices or generate duplicate CIs. This is the plausible direct consequence of the observed failure for the documented fictional Copper Hill Retail case. The defect is: A pattern captures both serial and chassis ID into the same output variable, leaving the final CI identity dependent on step order. The governing mechanism is: Each extracted identifier should be stored in a separately named typed variable until the identification rule selects the correct source. The supporting measured observation is: The debug history shows two valid source fields but the second match overwrites the first before the identification payload is built. After treatment, the result must be checked: The known-identity fixture produces the correct serial and chassis values without overwrites and reidentifies the existing CI.
Incorrect Answers
A:That alternative is relevant to preserve identification data when an optional connection step fails, but the issue here is A pattern captures both serial and chassis ID into the same output variable, leaving the final CI identity dependent on step order. Each extracted identifier should be stored in a separately named typed variable until the identification rule selects the correct source. Check: The debug history shows two valid source fields but the second match overwrites the first before the identification payload is built.
B:Incomplete identities can generate duplicate or unnamed application instances. It concerns require nonempty values before mapping a pattern variable, not the failure described here: A pattern captures both serial and chassis ID into the same output variable, leaving the final CI identity dependent on step order. Each extracted identifier should be stored in a separately named typed variable until the identification rule selects the correct source.
C:Debug a connection section before changing application identification is a separate consideration. In the stated situation, A pattern captures both serial and chassis ID into the same output variable, leaving the final CI identity dependent on step order. Each extracted identifier should be stored in a separately named typed variable until the identification rule selects the correct source. Check: The debug history shows two valid source fields but the second match overwrites the first before the identification payload is built.
Question 640
An owner-private simulated closeout at Westfield University addresses this failure: A discovered hardware payload matches two existing CIs after years of parallel ingestion and an integration picks the first record. Its independent defect indicator is: The IRE result lists two distinct CI IDs for the same device serial and raises a duplicate condition. The operator may not broaden credential or subnet permissions to bypass a failed test. Select TWO actions: correct the identified issue and independently prove it is resolved.
- Create an approved ownership enrichment workflow tied to authoritative asset records and retain missing-owner exceptions
- A new low-priority import cannot alter the verified serial while a permitted authoritative update still succeeds
- A post-run relationship health check finds the correct application-service edge and no unrelated links
- Create a governed duplicate remediation task and establish the correct survivor and reference links
- The next identification simulation finds one intended CI and no ambiguous matches remain
Explanation
Correct Answers
D:Create a governed duplicate remediation task and establish the correct survivor and reference links. This is the case-specific scoped correction, not a justification to expand the authorized scan or credential scope. In the fictional Westfield University scenario, the observed defect is: A discovered hardware payload matches two existing CIs after years of parallel ingestion and an integration picks the first record. The causal principle is: Multiple matches require explicit duplicate review and stable identity remediation, not arbitrary record selection. The proposed change must still pass this independent test: The next identification simulation finds one intended CI and no ambiguous matches remain.
E:The next identification simulation finds one intended CI and no ambiguous matches remain. This is the independently testable outcome that validates the targeted repair. The authorized change for the fictional Westfield University scenario is: Create a governed duplicate remediation task and establish the correct survivor and reference links. The prior failing observation was: The IRE result lists two distinct CI IDs for the same device serial and raises a duplicate condition. A deployment record without this tested outcome does not prove effectiveness.
Incorrect Answers
A:Create an approved ownership enrichment workflow tied to authoritative asset records and retain missing-owner exceptions. It concerns inspect a cmdb health failure from a missing required owner field, not the failure described here: A discovered hardware payload matches two existing CIs after years of parallel ingestion and an integration picks the first record. Create a governed duplicate remediation task and establish the correct survivor and reference links.
B:Protect manufacturer-provided serial number from lower-trust overwrite is a separate consideration. In the stated situation, A discovered hardware payload matches two existing CIs after years of parallel ingestion and an integration picks the first record. Create a governed duplicate remediation task and establish the correct survivor and reference links. Check: The IRE result lists two distinct CI IDs for the same device serial and raises a duplicate condition.
C:A post-run relationship health check finds the correct application-service edge and no unrelated links. The question instead centers on A discovered hardware payload matches two existing CIs after years of parallel ingestion and an integration picks the first record; the governing distinction is create a governed duplicate remediation task and establish the correct survivor and reference links. Check: The IRE result lists two distinct CI IDs for the same device serial and raises a duplicate condition.