cert
cert-1
cert-2

Pass ServiceNow CIS-Discovery Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
CIS-Discovery Exam - Verified By Experts
CIS-Discovery Premium File

CIS-Discovery Premium File

$69.99
$76.99
  • Premium File 122 Questions & Answers. Last Update: Nov 13, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 10 downloads in the last 7 days
block-screenshots
ServiceNow CIS-Discovery Practice Test 67

Question 660

During a second independent bounded discovery schedule pilot for Blackstone Regional Services, an attempted correction to the documented failure remains unverified: A pattern copies a certificate fingerprint with separators into a CMDB attribute that expects a normalized digest format. The governing rule is: Normalization must follow an approved canonical representation and not silently change digest content. The result must be reproducible against the original failed fixture and a passing control. Which trace or data finding would make this conclusion defensible?

  1. The config names db-prod but observed connections go to a separate cluster virtual address
  2. The captured version includes later warning lines even though the source has a single version entry
  3. The parsed value contains whitespace and colons, while the comparison rule expects a contiguous uppercase hexadecimal digest
  4. The execution trace succeeds through host identification and fails on a single database configuration command with a permission message

Explanation

Correct Answer

C:

The parsed value contains whitespace and colons, while the comparison rule expects a contiguous uppercase hexadecimal digest. This is the reproducible observation that distinguishes this failure for the documented fictional Blackstone Regional Services case. The defect is: A pattern copies a certificate fingerprint with separators into a CMDB attribute that expects a normalized digest format. The governing mechanism is: Normalization must follow an approved canonical representation and not silently change digest content. The supporting measured observation is: The parsed value contains whitespace and colons, while the comparison rule expects a contiguous uppercase hexadecimal digest. After treatment, the result must be checked: Controlled fingerprint samples normalize to identical canonical values without dropping hexadecimal digits.

Incorrect Answers

A:

The config names db-prod but observed connections go to a separate cluster virtual address. The question instead centers on A pattern copies a certificate fingerprint with separators into a CMDB attribute that expects a normalized digest format; the governing distinction is normalization must follow an approved canonical representation and not silently change digest content. Check: The parsed value contains whitespace and colons, while the comparison rule expects a contiguous uppercase hexadecimal digest.

B:

That alternative is relevant to capture multiline service metadata with a bounded match, but the issue here is A pattern copies a certificate fingerprint with separators into a CMDB attribute that expects a normalized digest format. Normalization must follow an approved canonical representation and not silently change digest content. Check: The parsed value contains whitespace and colons, while the comparison rule expects a contiguous uppercase hexadecimal digest.

D:

The execution trace succeeds through host identification and fails on a single database configuration command with a permission message. It concerns locate a failed pattern section instead of restarting the whole scan, not the failure described here: A pattern copies a certificate fingerprint with separators into a CMDB attribute that expects a normalized digest format. Normalization must follow an approved canonical representation and not silently change digest content.

Question 661

A ServiceNow Discovery review at Silvergate Health examines the following issue: A network appliance is recorded as a generic server despite discovery obtaining its vendor chassis model and role. The suspected consequence is: Misclassification can break expected attributes and downstream service relationships. A reviewed fault must be distinguished from a guessed cause. What observed fact most clearly distinguishes this case from an unrelated failure?

  1. The proposed payload lacks a required parent reference and dry-run identification returns an error
  2. The audit history shows a verified Discovery serial replaced by a different value from a lower-priority manual feed
  3. A side-by-side comparison shows identical manufacturer and serial digits with formatting differences only
  4. The collected payload includes a network-appliance model while the resulting record is in the generic computer class

Explanation

Correct Answer

D:

The collected payload includes a network-appliance model while the resulting record is in the generic computer class. This is the reproducible observation that distinguishes this failure 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:

The proposed payload lacks a required parent reference and dry-run identification returns an error. 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.

B:

That alternative is relevant to protect manufacturer-provided serial number from lower-trust overwrite, but the issue here is 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.

C:

A side-by-side comparison shows identical manufacturer and serial digits with formatting differences only. It concerns track normalized serial numbers as governed ci metadata, 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.

Question 662

A separate authorized MID Server operator at Alder Point Banking reopens set target rate limits to protect legacy network equipment because a previous closeout did not prove the result. Evidence still indicates: Device logs show CPU spikes synchronized with bursts from the MID Server while sequential reads succeed. Uncommon but critical failure cases must be tested before closing the defect. Select TWO actions: correct the identified issue and independently prove it is resolved.

  1. Remove the unauthorized fallback, preserve the denial, and obtain a scoped authorized credential fix
  2. A replay consumes the same raw output and produces a valid class-matched CI payload
  3. Set bounded concurrency or pacing for the fragile subnet and validate against the equipment's limits
  4. The captured probe list contains only approved targets and services and still classifies the pilot Linux hosts
  5. An approved load test preserves reachability and retrieves complete inventory without CPU threshold violations

Explanation

Correct Answers

C:

Set bounded concurrency or pacing for the fragile subnet and validate against the equipment's limits. This is the case-specific scoped correction, not a justification to expand the authorized scan or credential scope. In the fictional Alder Point Banking scenario, the observed defect is: A schedule floods an aging access switch with simultaneous management requests that trigger sporadic timeouts. The causal principle is: Discovery concurrency should be tested against asset capacity and approved operational thresholds. The proposed change must still pass this independent test: An approved load test preserves reachability and retrieves complete inventory without CPU threshold violations.

E:

An approved load test preserves reachability and retrieves complete inventory without CPU threshold violations. This is the independently testable outcome that validates the targeted repair. The authorized change for the fictional Alder Point Banking scenario is: Set bounded concurrency or pacing for the fragile subnet and validate against the equipment's limits. The prior failing observation was: Device logs show CPU spikes synchronized with bursts from the MID Server while sequential reads succeed. A deployment record without this tested outcome does not prove effectiveness.

Incorrect Answers

A:

That alternative is relevant to avoid suppressing meaningful discovery errors as successful retries, but the issue here is A schedule floods an aging access switch with simultaneous management requests that trigger sporadic timeouts. Set bounded concurrency or pacing for the fragile subnet and validate against the equipment's limits. Check: Device logs show CPU spikes synchronized with bursts from the MID Server while sequential reads succeed.

B:

A replay consumes the same raw output and produces a valid class-matched CI payload. It concerns investigate sensor parse failure after successful credentialed connection, not the failure described here: A schedule floods an aging access switch with simultaneous management requests that trigger sporadic timeouts. Set bounded concurrency or pacing for the fragile subnet and validate against the equipment's limits. Check: Device logs show CPU spikes synchronized with bursts from the MID Server while sequential reads succeed.

D:

Limit requested IP service probes to approved target protocols is a separate consideration. In the stated situation, A schedule floods an aging access switch with simultaneous management requests that trigger sporadic timeouts. Set bounded concurrency or pacing for the fragile subnet and validate against the equipment's limits. Check: Device logs show CPU spikes synchronized with bursts from the MID Server while sequential reads succeed.

Question 663

During approval-gated incident investigation, the network services engineer at Riverbend Aerospace observes: A pattern copies a certificate fingerprint with separators into a CMDB attribute that expects a normalized digest format. Independent logs state: The parsed value contains whitespace and colons, while the comparison rule expects a contiguous uppercase hexadecimal digest. Use only ServiceNow assets and network access approved for the target environment. What Discovery implementation principle MOST directly explains the cause?

  1. The debugger distinguishes execution failure from parsing failure by recording elapsed time, raw output, and step outcome
  2. Pattern variable lifetime and branch conditions must be checked to ensure later steps receive defined inputs
  3. Attribute normalization must preserve identifying information required by the CI class identification rule
  4. Normalization must follow an approved canonical representation and not silently change digest content

Explanation

Correct Answer

D:

Normalization must follow an approved canonical representation and not silently change digest content. This is the underlying causal Discovery implementation principle for the documented fictional Riverbend Aerospace case. The defect is: A pattern copies a certificate fingerprint with separators into a CMDB attribute that expects a normalized digest format. The governing mechanism is: Normalization must follow an approved canonical representation and not silently change digest content. The supporting measured observation is: The parsed value contains whitespace and colons, while the comparison rule expects a contiguous uppercase hexadecimal digest. After treatment, the result must be checked: Controlled fingerprint samples normalize to identical canonical values without dropping hexadecimal digits.

Incorrect Answers

A:

That alternative is relevant to distinguish command timeout from a malformed pattern expression, but the issue here is A pattern copies a certificate fingerprint with separators into a CMDB attribute that expects a normalized digest format. Normalization must follow an approved canonical representation and not silently change digest content. Check: The parsed value contains whitespace and colons, while the comparison rule expects a contiguous uppercase hexadecimal digest.

B:

Pattern variable lifetime and branch conditions must be checked to ensure later steps receive defined inputs. It concerns retain default variable scope across conditional pattern branches, not the failure described here: A pattern copies a certificate fingerprint with separators into a CMDB attribute that expects a normalized digest format. Normalization must follow an approved canonical representation and not silently change digest content.

C:

Normalize hostnames without losing unique device identity is a separate consideration. In the stated situation, A pattern copies a certificate fingerprint with separators into a CMDB attribute that expects a normalized digest format. Normalization must follow an approved canonical representation and not silently change digest content. Check: The parsed value contains whitespace and colons, while the comparison rule expects a contiguous uppercase hexadecimal digest.

Question 664

A ServiceNow Discovery review at Ashbrook Labs examines the following issue: A discovery rollout puts its only MID Server in a public cloud tenant with no authorized route to an isolated plant subnet. The suspected consequence is: An unreachable MID yields false inventory gaps and can pressure teams to open unsafe network access. No test may merge distinct customer or device identities for convenience. Which test finding BEST establishes the claimed context problem?

  1. The MID status has an old heartbeat timestamp despite previous completed discovery results
  2. The host service log identifies an interactive administrator login rather than the approved noninteractive MID service account
  3. A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud
  4. The credential record has a new secret while scheduled runs still select the retired alias and fail across one site

Explanation

Correct Answer

C:

A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud. This is the reproducible observation that distinguishes this failure for the documented fictional Ashbrook Labs case. The defect is: A discovery rollout puts its only MID Server in a public cloud tenant with no authorized route to an isolated plant subnet. The governing mechanism is: MID Server placement must reflect network reachability and approved isolation boundaries for targeted assets. The supporting measured observation is: A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud. After treatment, the result must be checked: A controlled site test discovers approved plant assets without creating a new cross-zone access route.

Incorrect Answers

A:

That alternative is relevant to distinguish stale mid heartbeat from an active discovery success, but the issue here is A discovery rollout puts its only MID Server in a public cloud tenant with no authorized route to an isolated plant subnet. MID Server placement must reflect network reachability and approved isolation boundaries for targeted assets. Check: A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud. For the evidence decision in this case, the decisive response is to a connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud.

B:

The host service log identifies an interactive administrator login rather than the approved noninteractive MID service account. It concerns validate the mid server application identity and permissions, not the failure described here: A discovery rollout puts its only MID Server in a public cloud tenant with no authorized route to an isolated plant subnet. MID Server placement must reflect network reachability and approved isolation boundaries for targeted assets.

D:

Maintain discovery credential rotation without hidden outages is a separate consideration. In the stated situation, A discovery rollout puts its only MID Server in a public cloud tenant with no authorized route to an isolated plant subnet. MID Server placement must reflect network reachability and approved isolation boundaries for targeted assets. Check: A connection map shows the plant network permits only local management traffic and blocks all inbound routes from the cloud.

Question 665

During a second independent controlled pattern debugger execution for Norwood Retail Cooperative, an attempted correction to the documented failure remains unverified: A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing. The governing rule is: Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. Only approved target ranges and read-only lab credentials are authorized. Which concrete observation MOST strongly supports the reported defect?

  1. The effective target list contains IPs assigned to a different customer while the change order is restricted to one tenant
  2. A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status
  3. Logs show matching short hostnames but different qualified names, owner contexts, and device serials
  4. The ECC response contains a valid OS signature while the classification record references a missing pattern identifier

Explanation

Correct Answer

B:

A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status. This is the reproducible observation that distinguishes this failure for the documented fictional Norwood Retail Cooperative 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:

That alternative is relevant to use schedule-specific domain or network permissions, but the issue here is A Windows discovery attempt fails WMI authentication and the team assumes an inbound firewall rule is missing. Connectivity to a service endpoint and authenticated operation rights need separate evidence before remediation. Check: A permitted transport connectivity check succeeds but the WMI call returns a clear access-denied status.

C:

Logs show matching short hostnames but different qualified names, owner contexts, and device serials. It concerns resolve target name collisions across segregated discovery domains, 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.

D:

Trace a returned classification response with an invalid sensor mapping 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.

Question 666

A separate authorized Discovery implementation specialist at Clearwater Research Institute reopens apply reconciliation priority when discovery and asset management disagree because a previous closeout did not prove the result. Evidence still indicates: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer. A reviewed fault must be distinguished from a guessed cause. Select TWO actions: correct the identified issue and independently prove it is resolved.

  1. Configure or enforce source precedence so asset management owns cost center while Discovery updates permitted technical attributes
  2. A controlled Discovery update preserves cost center and still refreshes the approved operating-system version
  3. Run the supported identification simulation and fix mandatory attributes and relationship references before release
  4. The fixture with ambiguous model evidence retains its class until the approved discriminator proves a change
  5. The target appears in the supported network-device class with stable identity and preserved relevant relationships

Explanation

Correct Answers

A:

Configure or enforce source precedence so asset management owns cost center while Discovery updates permitted technical attributes. This is the case-specific scoped correction, not a justification to expand the authorized scan or credential scope. In the fictional Clearwater Research Institute scenario, the observed defect is: An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field. The causal principle is: Reconciliation should enforce which authorized data source may update each CI attribute. The proposed change must still pass this independent test: A controlled Discovery update preserves cost center and still refreshes the approved operating-system version.

B:

A controlled Discovery update preserves cost center and still refreshes the approved operating-system version. This is the independently testable outcome that validates the targeted repair. The authorized change for the fictional Clearwater Research Institute scenario is: Configure or enforce source precedence so asset management owns cost center while Discovery updates permitted technical attributes. The prior failing observation was: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer. A deployment record without this tested outcome does not prove effectiveness.

Incorrect Answers

C:

Run the supported identification simulation and fix mandatory attributes and relationship references before release. It concerns simulate ire payload changes before production ci updates, not the failure described here: An asset lifecycle system owns the approved cost center but a Discovery feed overwrites it with an empty field. Configure or enforce source precedence so asset management owns cost center while Discovery updates permitted technical attributes.

D:

Review a planned CI reclassification before it alters service impact 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. Configure or enforce source precedence so asset management owns cost center while Discovery updates permitted technical attributes. Check: The asset record has a valid cost center before the Discovery update; afterward it is blank despite no approved ownership transfer.

E:

The target appears in the supported network-device class with stable identity and preserved relevant relationships. 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 configure or enforce source precedence so asset management owns cost center while Discovery updates permitted technical attributes.

Question 667

During bounded discovery schedule pilot, the configuration data analyst at Copper Hill Retail observes: A new integration plans to change a database instance class and relationship using an untested payload format. Independent logs state: The proposed payload lacks a required parent reference and dry-run identification returns an error. Production-affecting actions require an independently verified change approval. Which discovery and configuration-data mechanism applies to these facts?

  1. Attribute reconciliation must respect the source proven authoritative for identifying fields
  2. CMDB classes should represent the supported technology type using reliable discovered attributes
  3. IRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes
  4. A controlled reclassification must evaluate inherited fields and supported relationships rather than only class labels

Explanation

Correct Answer

C:

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 Copper Hill Retail 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

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 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.

B:

Assign the correct CI class after model identification 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. For the mechanism decision in this case, the decisive response is to iRE identification and relationship processing should be validated in a controlled simulation before authorized production data changes.

D:

A controlled reclassification must evaluate inherited fields and supported relationships rather than only class labels. 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.

Question 668

During a second independent synthetic CMDB reconciliation rehearsal for Seacliff Pharma, an attempted correction to the documented failure remains unverified: An IP range is approved for discovery but a default exclusion rule still blocks the management interface of a critical server. The governing rule is: Schedule inclusion and exclusion rules must be evaluated together to determine effective target coverage. The decision must preserve approved CI source authority and relationship direction. Which recorded artifact most directly substantiates the assessment?

  1. The two scan traces have different device serials and MID zones but the same translated IP
  2. No outbound port-probe request appears in the ECC queue for the selected target during the expected run window
  3. The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window
  4. The target preview shows the server in the CIDR yet omitted from the effective scan set by an older exclusion

Explanation

Correct Answer

D:

The target preview shows the server in the CIDR yet omitted from the effective scan set by an older exclusion. This is the reproducible observation that distinguishes this failure for the documented fictional Seacliff Pharma case. The defect is: An IP range is approved for discovery but a default exclusion rule still blocks the management interface of a critical server. The governing mechanism is: Schedule inclusion and exclusion rules must be evaluated together to determine effective target coverage. The supporting measured observation is: The target preview shows the server in the CIDR yet omitted from the effective scan set by an older exclusion. After treatment, the result must be checked: The intended server appears in the effective scan list while explicitly protected exclusions remain enforced.

Incorrect Answers

A:

The two scan traces have different device serials and MID zones but the same translated IP. It concerns investigate duplicate ip assignments before altering ci identity rules, not the failure described here: An IP range is approved for discovery but a default exclusion rule still blocks the management interface of a critical server. Schedule inclusion and exclusion rules must be evaluated together to determine effective target coverage.

B:

Locate the scanning stage from ECC queue evidence is a separate consideration. In the stated situation, An IP range is approved for discovery but a default exclusion rule still blocks the management interface of a critical server. Schedule inclusion and exclusion rules must be evaluated together to determine effective target coverage. Check: The target preview shows the server in the CIDR yet omitted from the effective scan set by an older exclusion.

C:

The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window. The question instead centers on An IP range is approved for discovery but a default exclusion rule still blocks the management interface of a critical server; the governing distinction is schedule inclusion and exclusion rules must be evaluated together to determine effective target coverage. Check: The target preview shows the server in the CIDR yet omitted from the effective scan set by an older exclusion.

Question 669

A ServiceNow Discovery review at Mariner Electronics examines the following issue: Two newly configured discovery schedules cover the same critical firewall subnet at the same hour. The suspected consequence is: Concurrent probes may raise device load and produce ambiguous discovery timestamps. Business service continuity and CMDB evidence must be preserved throughout validation. Which concrete observation MOST strongly supports the reported defect?

  1. The run history records a user cancellation and no per-target ECC probe messages were generated
  2. The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window
  3. The run closes normally but per-device statuses include authentication failures and missing pattern updates
  4. The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone

Explanation

Correct Answer

B:

The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window. This is the reproducible observation that distinguishes this failure for the documented fictional Mariner Electronics case. The defect is: Two newly configured discovery schedules cover the same critical firewall subnet at the same hour. The governing mechanism is: Schedule coordination should avoid redundant overlapping probes where asset stability and scan cost matter. The supporting measured observation is: The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window. After treatment, the result must be checked: The execution ledger shows one scheduled pass per protected device during each maintenance interval.

Incorrect Answers

A:

The run history records a user cancellation and no per-target ECC probe messages were generated. It concerns differentiate unreachable targets from a cancelled discovery job, not the failure described here: Two newly configured discovery schedules cover the same critical firewall subnet at the same hour. Schedule coordination should avoid redundant overlapping probes where asset stability and scan cost matter. Check: The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window.

C:

Avoid assuming completion from a green schedule status is a separate consideration. In the stated situation, Two newly configured discovery schedules cover the same critical firewall subnet at the same hour. Schedule coordination should avoid redundant overlapping probes where asset stability and scan cost matter. Check: The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window.

D:

The schedule's IP range is correct, but its selected behavior routes target requests to a MID in a different isolated zone. The question instead centers on Two newly configured discovery schedules cover the same critical firewall subnet at the same hour; the governing distinction is schedule coordination should avoid redundant overlapping probes where asset stability and scan cost matter. Check: The run calendar and target lists show identical firewall IPs in both active schedules during the same maintenance window.

Question 670

During a second independent nonproduction Discovery regression suite for Willowbrook Payment Services, an attempted correction to the documented failure remains unverified: A manual import overwrites a verified hardware serial with an unvalidated free-text asset note. The governing rule is: Attribute reconciliation must respect the source proven authoritative for identifying fields. Production-affecting actions require an independently verified change approval. Which concrete observation MOST strongly supports the reported defect?

  1. The audit history shows a verified Discovery serial replaced by a different value from a lower-priority manual feed
  2. A side-by-side comparison shows identical manufacturer and serial digits with formatting differences only
  3. The health report shows required fields populated while the known application-to-service dependency edge is absent
  4. The IRE result lists two distinct CI IDs for the same device serial and raises a duplicate condition

Explanation

Correct Answer

A:

The audit history shows a verified Discovery serial replaced by a different value from a lower-priority manual feed. This is the reproducible observation that distinguishes this failure for the documented fictional Willowbrook Payment Services case. The defect is: A manual import overwrites a verified hardware serial with an unvalidated free-text asset note. The governing mechanism is: Attribute reconciliation must respect the source proven authoritative for identifying fields. The supporting measured observation is: The audit history shows a verified Discovery serial replaced by a different value from a lower-priority manual feed. After treatment, the result must be checked: A new low-priority import cannot alter the verified serial while a permitted authoritative update still succeeds.

Incorrect Answers

B:

A side-by-side comparison shows identical manufacturer and serial digits with formatting differences only. It concerns track normalized serial numbers as governed ci metadata, not the failure described here: A manual import overwrites a verified hardware serial with an unvalidated free-text asset note. Attribute reconciliation must respect the source proven authoritative for identifying fields. Check: The audit history shows a verified Discovery serial replaced by a different value from a lower-priority manual feed.

C:

Detect an absent business service relationship in CMDB health is a separate consideration. In the stated situation, A manual import overwrites a verified hardware serial with an unvalidated free-text asset note. Attribute reconciliation must respect the source proven authoritative for identifying fields. Check: The audit history shows a verified Discovery serial replaced by a different value from a lower-priority manual feed.

D:

The IRE result lists two distinct CI IDs for the same device serial and raises a duplicate condition. The question instead centers on A manual import overwrites a verified hardware serial with an unvalidated free-text asset note; the governing distinction is attribute reconciliation must respect the source proven authoritative for identifying fields. Check: The audit history shows a verified Discovery serial replaced by a different value from a lower-priority manual feed.

Certified Implementation Specialist - Discovery (CIS-Discovery) Practice Tests