ServiceNow CIS-Discovery Practice Test 10
Question 90
An owner-private simulated closeout at Lighthouse Financial addresses this failure: The main schedule shows Completed while dozens of per-target discovery statuses are unresolved errors. Its independent defect indicator is: The run closes normally but per-device statuses include authentication failures and missing pattern updates. The result must be reproducible against the original failed fixture and a passing control. Which TWO options form the appropriate remediation-and-verification pair?
- Set bounded concurrency or pacing for the fragile subnet and validate against the equipment's limits
- Reconcile successful classifications and CI updates with all in-scope target results and failures
- The response is consumed once and produces the expected class and CI update without resending unrelated scans
- The rebuilt instance updates the intended existing CI and preserves supported relationships without a second record
- Every authorized target has a documented success or reviewed exception with testable follow-up
Explanation
Correct Answers
B:Reconcile successful classifications and CI updates with all in-scope target results and failures. 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: The main schedule shows Completed while dozens of per-target discovery statuses are unresolved errors. The causal principle is: The schedule control status describes job lifecycle and does not by itself prove all target identification succeeded. The proposed change must still pass this independent test: Every authorized target has a documented success or reviewed exception with testable follow-up.
E:Every authorized target has a documented success or reviewed exception with testable follow-up. This is the independently testable outcome that validates the targeted repair. The authorized change for the fictional Lighthouse Financial scenario is: Reconcile successful classifications and CI updates with all in-scope target results and failures. The prior failing observation was: The run closes normally but per-device statuses include authentication failures and missing pattern updates. A deployment record without this tested outcome does not prove effectiveness.
Incorrect Answers
A:Set bounded concurrency or pacing for the fragile subnet and validate against the equipment's limits. It concerns set target rate limits to protect legacy network equipment, not the failure described here: The main schedule shows Completed while dozens of per-target discovery statuses are unresolved errors. Reconcile successful classifications and CI updates with all in-scope target results and failures. Check: The run closes normally but per-device statuses include authentication failures and missing pattern updates.
C:Trace a MID Server response that remains unprocessed in ECC is a separate consideration. In the stated situation, The main schedule shows Completed while dozens of per-target discovery statuses are unresolved errors. Reconcile successful classifications and CI updates with all in-scope target results and failures. Check: The run closes normally but per-device statuses include authentication failures and missing pattern updates.
D:The rebuilt instance updates the intended existing CI and preserves supported relationships without a second record. The question instead centers on The main schedule shows Completed while dozens of per-target discovery statuses are unresolved errors; the governing distinction is reconcile successful classifications and CI updates with all in-scope target results and failures. Check: The run closes normally but per-device statuses include authentication failures and missing pattern updates.
Question 91
A second MID Server operator at Sunridge Infrastructure revisits an unresolved finding during internal Discovery implementation review: A new integration plans to change a database instance class and relationship using an untested payload format. A fresh run still shows: The proposed payload lacks a required parent reference and dry-run identification returns an error. Uncommon but critical failure cases must be tested before closing the defect. Which discovery and configuration-data mechanism applies to these facts?
- IRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes
- Reconciliation should enforce which authorized data source may update each CI attribute
- Reclassification must be supported by reliable class evidence and an authorized class-change process
- Normalized identity attributes should use a documented canonical representation before CMDB identification
Explanation
Correct Answer
A:IRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes. This is the underlying causal Discovery implementation principle for the documented fictional Sunridge Infrastructure case. The defect is: A new integration plans to change a database instance class and relationship using an untested payload format. The governing mechanism is: IRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes. The supporting measured observation is: The proposed payload lacks a required parent reference and dry-run identification returns an error. After treatment, the result must be checked: The tested payload identifies one expected CI and produces valid relationship mappings without unapproved writes.
Incorrect Answers
B:Reconciliation should enforce which authorized data source may update each CI attribute. It concerns apply reconciliation priority when discovery and asset management disagree, not the failure described here: A new integration plans to change a database instance class and relationship using an untested payload format. IRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes.
C:Review a planned CI reclassification before it alters service impact is a separate consideration. In the stated situation, A new integration plans to change a database instance class and relationship using an untested payload format. IRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes. Check: The proposed payload lacks a required parent reference and dry-run identification returns an error.
D:Normalized identity attributes should use a documented canonical representation before CMDB identification. The question instead centers on A new integration plans to change a database instance class and relationship using an untested payload format; the governing distinction is iRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes. Check: The proposed payload lacks a required parent reference and dry-run identification returns an error.
Question 92
A second configuration data analyst at Pine Valley Insurance revisits an unresolved finding during governed production-change review: A Unix discovery job reports authentication denied and an engineer proposes a universal administrator account. A fresh run still shows: The test host rejects the configured scoped credential and logs show the account lacks a required read permission. Business service continuity and CMDB evidence must be preserved throughout validation. Which technical explanation is supported by the Discovery log? Choose ONE.
- Retries should not conceal authorization failures or silently bypass the approved access policy
- Scanning discovers a reachable service; classification must interpret returned protocol attributes before identification
- Pattern results and their sensor mapping must retain distinct identified application instances and relationships
- Authentication failure should be resolved against target-specific account permissions and authorized credential records
Explanation
Correct Answer
D:Authentication failure should be resolved against target-specific account permissions and authorized credential records. This is the underlying causal Discovery implementation principle 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:Retries should not conceal authorization failures or silently bypass the approved access policy. It concerns avoid suppressing meaningful discovery errors as successful retries, 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:Use the correct classifier after SNMP port detection 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:Pattern results and their sensor mapping must retain distinct identified application instances and relationships. 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 93
In a Discovery implementation risk workshop at Brookhaven Freight, the following behavior is documented: A pattern discards a valid application CI update when a secondary outbound-link query times out. The relevant mechanism is: Identity discovery and optional connection evidence should fail with a bounded status that preserves valid known information. The operator may not broaden credential or subnet permissions to bypass a failed test. Which outcome is directly supported if the issue remains unresolved?
- An optional topology error should not erase accurate application inventory data
- Column shifts corrupt multiple CI attributes in one execution
- A collision between identifiers can merge distinct devices or generate duplicate CIs
- Conflation of identity and connection can hide business services and merge configuration records
Explanation
Correct Answer
A:An optional topology error should not erase accurate application inventory data. This is the plausible direct consequence of the observed failure 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
B:Column shifts corrupt multiple CI attributes in one execution. It concerns validate a tabular mapping with missing optional columns, 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. Check: Logs show stable instance ID and version followed by a timeout on an optional remote connection inventory step.
C:Detect conflicting capture groups in a pattern identifier parser 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:Conflation of identity and connection can hide business services and merge configuration records. 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 94
A second Discovery operations lead at Eastgate Hospitality revisits an unresolved finding during controlled pattern debugger execution: A middleware CI receives a more specific class while its existing service dependency links disappear. A fresh run still shows: A before-after comparison shows the instance identifier still matches but its service relationships are absent after class change. Only approved target ranges and read-only lab credentials are authorized. Which principle should the reviewer use to interpret this test?
- Reconciliation should enforce which authorized data source may update each CI attribute
- A controlled reclassification must evaluate inherited fields and supported relationships rather than only class labels
- Attribute reconciliation must respect the source proven authoritative for identifying fields
- Coverage and health should include recent successful source observations rather than raw CI record counts
Explanation
Correct Answer
B:A controlled reclassification must evaluate inherited fields and supported relationships rather than only class labels. This is the underlying causal Discovery implementation principle for the documented fictional Eastgate Hospitality case. The defect is: A middleware CI receives a more specific class while its existing service dependency links disappear. The governing mechanism is: A controlled reclassification must evaluate inherited fields and supported relationships rather than only class labels. The supporting measured observation is: A before-after comparison shows the instance identifier still matches but its service relationships are absent after class change. After treatment, the result must be checked: The verified class changes without losing authorized identity or previously validated service dependencies.
Incorrect Answers
A:Reconciliation should enforce which authorized data source may update each CI attribute. It concerns apply reconciliation priority when discovery and asset management disagree, not the failure described here: A middleware CI receives a more specific class while its existing service dependency links disappear. A controlled reclassification must evaluate inherited fields and supported relationships rather than only class labels.
C:Protect manufacturer-provided serial number from lower-trust overwrite is a separate consideration. In the stated situation, A middleware CI receives a more specific class while its existing service dependency links disappear. A controlled reclassification must evaluate inherited fields and supported relationships rather than only class labels. Check: A before-after comparison shows the instance identifier still matches but its service relationships are absent after class change.
D:Coverage and health should include recent successful source observations rather than raw CI record counts. The question instead centers on A middleware CI receives a more specific class while its existing service dependency links disappear; the governing distinction is a controlled reclassification must evaluate inherited fields and supported relationships rather than only class labels. Check: A before-after comparison shows the instance identifier still matches but its service relationships are absent after class change.
Question 95
During nonproduction Discovery regression suite, the security architecture reviewer at Oakridge Logistics observes: An extraction regex designed for Service version 3.2 fails when the new CLI prints Version: 3.2.1 with a prefix. Independent logs state: The debugger shows the command succeeded and contains the version, but the capture group is empty on the prefixed output. Business service continuity and CMDB evidence must be preserved throughout validation. What Discovery implementation principle MOST directly explains the cause?
- Regex maintenance should use anchored representative samples and retain correct boundaries for old and new supported formats
- Application identification keys and connection relationships serve different purposes and require appropriate evidence
- Pattern failures should be resolved with minimum necessary authorized target access rather than broad privilege escalation
- Required pattern attributes need explicit nonempty validation and controlled failure when evidence is insufficient
Explanation
Correct Answer
A:Regex maintenance should use anchored representative samples and retain correct boundaries for old and new supported formats. This is the underlying causal Discovery implementation principle for the documented fictional Oakridge Logistics case. The defect is: An extraction regex designed for Service version 3.2 fails when the new CLI prints Version: 3.2.1 with a prefix. The governing mechanism is: Regex maintenance should use anchored representative samples and retain correct boundaries for old and new supported formats. The supporting measured observation is: The debugger shows the command succeeded and contains the version, but the capture group is empty on the prefixed output. After treatment, the result must be checked: Old and new fixture strings produce the corresponding version without consuming unrelated numeric fields.
Incorrect Answers
B:Application identification keys and connection relationships serve different purposes and require appropriate evidence. It concerns separate application identification from host connection enumeration, not the failure described here: An extraction regex designed for Service version 3.2 fails when the new CLI prints Version: 3.2.1 with a prefix. Regex maintenance should use anchored representative samples and retain correct boundaries for old and new supported formats.
C:Keep a targeted pattern fix within the approved credential boundary is a separate consideration. In the stated situation, An extraction regex designed for Service version 3.2 fails when the new CLI prints Version: 3.2.1 with a prefix. Regex maintenance should use anchored representative samples and retain correct boundaries for old and new supported formats. Check: The debugger shows the command succeeded and contains the version, but the capture group is empty on the prefixed output.
D:Required pattern attributes need explicit nonempty validation and controlled failure when evidence is insufficient. The question instead centers on An extraction regex designed for Service version 3.2 fails when the new CLI prints Version: 3.2.1 with a prefix; the governing distinction is regex maintenance should use anchored representative samples and retain correct boundaries for old and new supported formats. Check: The debugger shows the command succeeded and contains the version, but the capture group is empty on the prefixed output.
Question 96
In a Discovery implementation risk workshop at Greenford University, the following behavior is documented: A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing. The relevant mechanism is: Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. The result must be reproducible against the original failed fixture and a passing control. What is the MOST immediate reliability or governance consequence?
- Premature conclusions can produce unknown or misclassified asset inventory
- A processing backlog can mimic a credential or target network problem
- Unnecessary firewall openings expand attack surface without repairing account authorization
- Treating a pattern as complete can leave CMDB inventory silently stale
Explanation
Correct Answer
C:Unnecessary firewall openings expand attack surface without repairing account authorization. This is the plausible direct consequence of the observed failure for the documented fictional Greenford University case. The defect is: A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing. The governing mechanism is: Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. The supporting measured observation is: A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status. After treatment, the result must be checked: The controlled WMI query succeeds under the approved account and firewall rules remain unchanged.
Incorrect Answers
A:Premature conclusions can produce unknown or misclassified asset inventory. It concerns explain discovery stages when a port is open but no os evidence exists, not the failure described here: A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing. Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. Check: A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status.
B:Trace a MID Server response that remains unprocessed in ECC is a separate consideration. In the stated situation, A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing. Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. Check: A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status.
D:Treating a pattern as complete can leave CMDB inventory silently stale. The question instead centers on A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing; the governing distinction is connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. Check: A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status.
Question 97
During a second independent bounded discovery schedule pilot for Blackstone Regional Services, an attempted correction to the documented failure remains unverified: A hardware inventory shows a valid serial and model but passes as operationally complete without an assigned support group. The governing rule is: CMDB governance can require both technical attributes and service ownership for accountable operations. The result must be reproducible against the original failed fixture and a passing control. Which test finding BEST establishes the claimed context problem?
- The raw connection log shows the application consuming database service while the CMDB edge points from database as consumer
- The audit history shows a verified Discovery serial replaced by a different value from a lower-priority manual feed
- A field-level audit finds the support group blank on critical production servers discovered last night
- The proposed payload lacks a required parent reference and dry-run identification returns an error
Explanation
Correct Answer
C:A field-level audit finds the support group blank on critical production servers discovered last night. This is the reproducible observation that distinguishes this failure for the documented fictional Blackstone Regional Services case. The defect is: A hardware inventory shows a valid serial and model but passes as operationally complete without an assigned support group. The governing mechanism is: CMDB governance can require both technical attributes and service ownership for accountable operations. The supporting measured observation is: A field-level audit finds the support group blank on critical production servers discovered last night. After treatment, the result must be checked: The affected records receive documented accountable owners or remain visible in an unresolved health report.
Incorrect Answers
A:The raw connection log shows the application consuming database service while the CMDB edge points from database as consumer. It concerns avoid wrong relationship direction in a discovered service dependency, not the failure described here: A hardware inventory shows a valid serial and model but passes as operationally complete without an assigned support group. CMDB governance can require both technical attributes and service ownership for accountable operations.
B:Protect manufacturer-provided serial number from lower-trust overwrite is a separate consideration. In the stated situation, A hardware inventory shows a valid serial and model but passes as operationally complete without an assigned support group. CMDB governance can require both technical attributes and service ownership for accountable operations. Check: A field-level audit finds the support group blank on critical production servers discovered last night.
D:The proposed payload lacks a required parent reference and dry-run identification returns an error. The question instead centers on A hardware inventory shows a valid serial and model but passes as operationally complete without an assigned support group; the governing distinction is cMDB governance can require both technical attributes and service ownership for accountable operations. Check: A field-level audit finds the support group blank on critical production servers discovered last night.
Question 98
The owner of Willowbrook Payment Services asks for a new risk decision after a prior correction failed to resolve this issue: A pattern incorrectly matches a similarly named configuration file because the expected path contains dots and brackets treated as regex syntax. The replay still demonstrates: The fixture has config[prod].ini and config-prod.ini, and the match selects the second file. Production-affecting actions require an independently verified change approval. What specific risk is most likely to follow from the described context defect?
- Reading the wrong file can produce a convincing but inaccurate CI configuration
- A disabled security control can be misreported as enabled in inventory reports
- Incomplete identities can generate duplicate or unnamed application instances
- An unrelated MID route produces false application absence and tempts unnecessary pattern edits
Explanation
Correct Answer
A:Reading the wrong file can produce a convincing but inaccurate CI configuration. This is the plausible direct consequence of the observed failure for the documented fictional Willowbrook Payment Services case. The defect is: A pattern incorrectly matches a similarly named configuration file because the expected path contains dots and brackets treated as regex syntax. The governing mechanism is: An expected literal file path must be escaped before it is used as a regular-expression search expression. The supporting measured observation is: The fixture has config[prod].ini and config-prod.ini, and the match selects the second file. After treatment, the result must be checked: The test selects config[prod].ini and rejects similarly named paths in randomized file listings.
Incorrect Answers
B:A disabled security control can be misreported as enabled in inventory reports. It concerns transform command booleans consistently for the target attribute, not the failure described here: A pattern incorrectly matches a similarly named configuration file because the expected path contains dots and brackets treated as regex syntax. An expected literal file path must be escaped before it is used as a regular-expression search expression.
C:Require nonempty values before mapping a pattern variable is a separate consideration. In the stated situation, A pattern incorrectly matches a similarly named configuration file because the expected path contains dots and brackets treated as regex syntax. An expected literal file path must be escaped before it is used as a regular-expression search expression. Check: The fixture has config[prod].ini and config-prod.ini, and the match selects the second file.
D:An unrelated MID route produces false application absence and tempts unnecessary pattern edits. The question instead centers on A pattern incorrectly matches a similarly named configuration file because the expected path contains dots and brackets treated as regex syntax; the governing distinction is an expected literal file path must be escaped before it is used as a regular-expression search expression. Check: The fixture has config[prod].ini and config-prod.ini, and the match selects the second file.
Question 99
During internal Discovery implementation review, the application pattern reviewer at Silvergate Health observes: A network appliance is recorded as a generic server despite discovery obtaining its vendor chassis model and role. Independent logs state: The collected payload includes a network-appliance model while the resulting record is in the generic computer class. A reviewed fault must be distinguished from a guessed cause. What Discovery implementation principle MOST directly explains the cause?
- Attribute reconciliation must respect the source proven authoritative for identifying fields
- CMDB classes should represent the supported technology type using reliable discovered attributes
- Identification decides whether a CI already exists; reconciliation governs allowed updates to an identified existing record
- Normalized identity attributes should use a documented canonical representation before CMDB identification
Explanation
Correct Answer
B:CMDB classes should represent the supported technology type using reliable discovered attributes. This is the underlying causal Discovery implementation principle for the documented fictional Silvergate Health case. The defect is: A network appliance is recorded as a generic server despite discovery obtaining its vendor chassis model and role. The governing mechanism is: CMDB classes should represent the supported technology type using reliable discovered attributes. The supporting measured observation is: The collected payload includes a network-appliance model while the resulting record is in the generic computer class. After treatment, the result must be checked: The target appears in the supported network-device class with stable identity and preserved relevant relationships.
Incorrect Answers
A: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: A network appliance is recorded as a generic server despite discovery obtaining its vendor chassis model and role. CMDB classes should represent the supported technology type using reliable discovered attributes.
C:Distinguish IRE identification from reconciliation on a new CI is a separate consideration. In the stated situation, A network appliance is recorded as a generic server despite discovery obtaining its vendor chassis model and role. CMDB classes should represent the supported technology type using reliable discovered attributes. Check: The collected payload includes a network-appliance model while the resulting record is in the generic computer class.
D:Normalized identity attributes should use a documented canonical representation before CMDB identification. The question instead centers on A network appliance is recorded as a generic server despite discovery obtaining its vendor chassis model and role; the governing distinction is cMDB classes should represent the supported technology type using reliable discovered attributes. Check: The collected payload includes a network-appliance model while the resulting record is in the generic computer class.
Question 100
During a second independent approval-gated incident investigation for Clearwater Research Institute, an attempted correction to the documented failure remains unverified: An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field. The governing rule is: Reconciliation should enforce which authorized data source may update each CI attribute. A reviewed fault must be distinguished from a guessed cause. Which recorded artifact most directly substantiates the assessment?
- The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer
- The collected payload includes a network-appliance model while the resulting record is in the generic computer class
- The CI list is large but the last-discovered timestamps for a critical subnet predate a network reconfiguration
- The IRE result lists two distinct CI IDs for the same device serial and raises a duplicate condition
Explanation
Correct Answer
A:The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer. This is the reproducible observation that distinguishes this failure for the documented fictional Clearwater Research Institute 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:The collected payload includes a network-appliance model while the resulting record is in the generic computer class. It concerns assign the correct ci class after model identification, 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:Use CMDB freshness metrics to detect stale discovered devices 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:The IRE result lists two distinct CI IDs for the same device serial and raises a duplicate condition. 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.