ServiceNow CIS-DF Practice Test 15 - Prepaway
Practice Exams:

Pass ServiceNow CIS-DF Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

CIS-DF Premium ETE File


  • Premium File 283 Questions & Answers. Last Update: Nov 12, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

ServiceNow CIS-DF Practice Test 15

Question 140

A server hosting a database is imported with a relationship pointing in the opposite direction, breaking dependency analysis for application services. Which TWO actions would be unsuitable or unsafe?

  1. Swap parent and child sys_ids in every relationship without checking each type's intended direction.
  2. Validate in a controlled test that a dependency traversal shows the database hosted on the intended server and impact flows in the expected direction.
  3. Map the correct supported relationship type and parent-child direction for the server and hosted database CIs.
  4. Insert an arbitrary relationship type and assume every graph will infer the right hosting semantics.
  5. Inspect cmdb_rel_ci parent and child fields, relationship type definitions, source mapping, and dependency views.

Explanation

Correct Answer

A:

“Swap parent and child sys_ids in every relationship without checking each type's intended direction” would violate the requirement. Relationship direction and type determine meaningful traversals; simply connecting records does not establish the correct dependency semantics.

D:

This violates the scenario constraints for discovery relationship direction. Relationship direction and type determine meaningful traversals; simply connecting records does not establish the correct dependency semantics. Instead the safe implementation is: Map the correct supported relationship type and parent-child direction for the server and hosted database CIs.

Incorrect Answers

B:

“Validate in a controlled test that a dependency traversal shows the database hosted on the intended server and impact flows in the expected direction” adds a relevant safeguard or verification step rather than weakening the solution. Relationship direction and type determine meaningful traversals; simply connecting records does not establish the correct dependency semantics.

C:

“Map the correct supported relationship type and parent-child direction for the server and hosted database CIs” is the controlled implementation, not an unsafe workaround. Relationship direction and type determine meaningful traversals; simply connecting records does not establish the correct dependency semantics.

E:

“Inspect cmdb_rel_ci parent and child fields, relationship type definitions, source mapping, and dependency views” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Relationship direction and type determine meaningful traversals; simply connecting records does not establish the correct dependency semantics. Confirm that a dependency traversal shows the database hosted on the intended server and impact flows in the expected direction.

Question 141

An infrastructure scanner discovers network devices but none of their connected-to relationships appear in the CMDB. Which corrective design should the implementation specialist recommend?

  1. Enable or repair supported relationship discovery and transform mapping for the relevant device classes.
  2. Have an authorized steward add the approved typed dependency relationship and ownership information in the CMDB.
  3. Delete correctly discovered devices to make the absence of relationships less visible.
  4. Create manual untyped notes between device records and treat them as relationship records.

Explanation

Correct Answer

A:

The requested CMDB/CSDM implementation concerns discovery creates ci without topology links, not just a different useful platform feature. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings. Validate the effect with: A scanned router and switch appear as CIs with the correct supported relationship records after ingestion.

Incorrect Answers

B:

This addresses manual application dependency relation, an important but separate issue. It does not resolve the described discovery creates ci without topology links failure. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings. The targeted action is: Enable or repair supported relationship discovery and transform mapping for the relevant device classes.

C:

“Delete correctly discovered devices to make the absence of relationships less visible” does not implement the control that the facts call for. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings. Instead, enable or repair supported relationship discovery and transform mapping for the relevant device classes.

D:

“Create manual untyped notes between device records and treat them as relationship records” does not implement the control that the facts call for. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings. Instead, enable or repair supported relationship discovery and transform mapping for the relevant device classes.

Question 142

An infrastructure scanner discovers network devices but none of their connected-to relationships appear in the CMDB. The problem persists after the attempted change. What should the specialist inspect?

  1. Inspect discovery pattern output, relationship payloads, transforms, and cmdb_rel_ci for the test devices.
  2. Inspect relationship definitions, dependency map behavior, service topology requirements, and source configuration.
  3. Inspect source offset, ETL date mapping, stored timestamp values, and staleness threshold logic.
  4. Inspect cmdb_rel_ci parent and child fields, relationship type definitions, source mapping, and dependency views.

Explanation

Correct Answer

A:

Inspect discovery pattern output, relationship payloads, transforms, and cmdb_rel_ci for the test devices. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings. A scanned router and switch appear as CIs with the correct supported relationship records after ingestion.

Incorrect Answers

B:

That inspection relates primarily to relationship type selection for dependency rather than the failing discovery creates ci without topology links process. The immediate evidence needed for this case is: Inspect discovery pattern output, relationship payloads, transforms, and cmdb_rel_ci for the test devices.

C:

That inspection relates primarily to import data source timestamp normalization rather than the failing discovery creates ci without topology links process. The immediate evidence needed for this case is: Inspect discovery pattern output, relationship payloads, transforms, and cmdb_rel_ci for the test devices.

D:

That inspection relates primarily to discovery relationship direction rather than the failing discovery creates ci without topology links process. The immediate evidence needed for this case is: Inspect discovery pattern output, relationship payloads, transforms, and cmdb_rel_ci for the test devices.

Question 143

An infrastructure scanner discovers network devices but none of their connected-to relationships appear in the CMDB. Which end-to-end acceptance test establishes success?

  1. Service maps and queries show the database dependency under the intended relationship category.
  2. A pilot scan reaches the intended host, collects CI data, and does not touch excluded subnets.
  3. A scanned router and switch appear as CIs with the correct supported relationship records after ingestion.
  4. Reprocessing both feeds leaves one correct relationship with traceable source contribution.

Explanation

Correct Answer

C:

This tests the actual result for discovery creates ci without topology links instead of merely checking whether a configuration screen can be opened. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings. The test must be performed on the described CI and service scope.

Incorrect Answers

A:

“Service maps and queries show the database dependency under the intended relationship category” pertains to relationship type selection for dependency, not the deciding condition here. A scanned router and switch appear as CIs with the correct supported relationship records after ingestion. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings.

B:

The choice “A pilot scan reaches the intended host, collects CI data, and does not touch excluded subnets” concerns mid server reachability diagnosis; it does not resolve the stated requirement. A scanned router and switch appear as CIs with the correct supported relationship records after ingestion.

D:

This might validate relationship duplication from integrations, but does not establish the acceptance requirement for discovery creates ci without topology links. Instead verify: A scanned router and switch appear as CIs with the correct supported relationship records after ingestion.

Question 144

An infrastructure scanner discovers network devices but none of their connected-to relationships appear in the CMDB. Which explanation best supports the recommended solution?

  1. Out-of-box integration code can be overwritten during upgrades; isolated mappings reduce long-term technical debt.
  2. CI identity consolidation can affect graph edges, so relationship correctness needs explicit post-merge validation.
  3. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings.
  4. Relationship uniqueness depends on resolved CI endpoints and typed edges, not on source-specific display strings.

Explanation

Correct Answer

C:

CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings. Enable or repair supported relationship discovery and transform mapping for the relevant device classes. The decisive evidence is that a scanned router and switch appear as CIs with the correct supported relationship records after ingestion.

Incorrect Answers

A:

Although relevant to connector upgradeability and customization, this does not explain the remedy for discovery creates ci without topology links. The causally relevant rule is: CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings.

B:

Although relevant to relationship audit after ci merge, this does not explain the remedy for discovery creates ci without topology links. The causally relevant rule is: CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings.

D:

Although relevant to relationship duplication from integrations, this does not explain the remedy for discovery creates ci without topology links. The causally relevant rule is: CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings.

Question 145

An infrastructure scanner discovers network devices but none of their connected-to relationships appear in the CMDB. Select TWO proposed changes that would violate the requirement.

  1. Validate in a controlled test that a scanned router and switch appear as CIs with the correct supported relationship records after ingestion.
  2. Enable or repair supported relationship discovery and transform mapping for the relevant device classes.
  3. Delete correctly discovered devices to make the absence of relationships less visible.
  4. Inspect discovery pattern output, relationship payloads, transforms, and cmdb_rel_ci for the test devices.
  5. Create manual untyped notes between device records and treat them as relationship records.

Explanation

Correct Answer

C:

“Delete correctly discovered devices to make the absence of relationships less visible” would violate the requirement. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings.

E:

This violates the scenario constraints for discovery creates ci without topology links. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings. Instead the safe implementation is: Enable or repair supported relationship discovery and transform mapping for the relevant device classes.

Incorrect Answers

A:

“Validate in a controlled test that a scanned router and switch appear as CIs with the correct supported relationship records after ingestion” adds a relevant safeguard or verification step rather than weakening the solution. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings. Confirm that a scanned router and switch appear as CIs with the correct supported relationship records after ingestion.

B:

“Enable or repair supported relationship discovery and transform mapping for the relevant device classes” is the controlled implementation, not an unsafe workaround. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings. Confirm that a scanned router and switch appear as CIs with the correct supported relationship records after ingestion.

D:

“Inspect discovery pattern output, relationship payloads, transforms, and cmdb_rel_ci for the test devices” is the relevant troubleshooting evidence, not a reason to bypass safeguards. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings. Confirm that a scanned router and switch appear as CIs with the correct supported relationship records after ingestion.

Question 146

An internal batch application is not discoverable but service owners know it depends on a critical scheduling service. Which ServiceNow implementation decision best addresses the requirement?

  1. Request owner-backed disposal evidence and update the lifecycle using a governed manual retirement process.
  2. Invent an automated discovery source for the application without any underlying telemetry.
  3. Have an authorized steward add the approved typed dependency relationship and ownership information in the CMDB.
  4. Create the same dependency as an unreviewed free-text note rather than a typed CMDB relation.

Explanation

Correct Answer

C:

The requested CMDB/CSDM implementation concerns manual application dependency relation, not just a different useful platform feature. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable. Validate the effect with: The batch application dependency appears correctly in queries and is subject to owner review on schedule.

Incorrect Answers

A:

This addresses manual record retirement evidence, an important but separate issue. It does not resolve the described manual application dependency relation failure. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable. The targeted action is: Have an authorized steward add the approved typed dependency relationship and ownership information in the CMDB.

B:

“Invent an automated discovery source for the application without any underlying telemetry” does not implement the control that the facts call for. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable. Instead, have an authorized steward add the approved typed dependency relationship and ownership information in the CMDB.

D:

“Create the same dependency as an unreviewed free-text note rather than a typed CMDB relation” does not implement the control that the facts call for. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable. Instead, have an authorized steward add the approved typed dependency relationship and ownership information in the CMDB.

Question 147

An internal batch application is not discoverable but service owners know it depends on a critical scheduling service. After an initial fix fails, which evidence should the team investigate first?

  1. Inspect application and scheduler CI sys_ids, relationship type, evidence record, and review ownership.
  2. Inspect alm_asset record, cmdb_ci computer record, asset linkage, serial and lifecycle status.
  3. Inspect pre-merge relationship inventory, survivor sys_id, cmdb_rel_ci records, and post-merge traversal.
  4. Inspect cmdb_rel_ci parent and child fields, relationship type definitions, source mapping, and dependency views.

Explanation

Correct Answer

A:

Inspect application and scheduler CI sys_ids, relationship type, evidence record, and review ownership. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable. The batch application dependency appears correctly in queries and is subject to owner review on schedule.

Incorrect Answers

B:

“Inspect alm_asset record, cmdb_ci computer record, asset linkage, serial and lifecycle status” would not be the most direct first check for this failure. Inspect application and scheduler CI sys_ids, relationship type, evidence record, and review ownership. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable.

C:

That inspection relates primarily to relationship audit after ci merge rather than the failing manual application dependency relation process. The immediate evidence needed for this case is: Inspect application and scheduler CI sys_ids, relationship type, evidence record, and review ownership.

D:

That inspection relates primarily to discovery relationship direction rather than the failing manual application dependency relation process. The immediate evidence needed for this case is: Inspect application and scheduler CI sys_ids, relationship type, evidence record, and review ownership.

Question 148

An internal batch application is not discoverable but service owners know it depends on a critical scheduling service. What observed outcome most convincingly validates the correction?

  1. Reprocessing both feeds leaves one correct relationship with traceable source contribution.
  2. A dependency traversal shows the database hosted on the intended server and impact flows in the expected direction.
  3. A pilot scan reaches the intended host, collects CI data, and does not touch excluded subnets.
  4. The batch application dependency appears correctly in queries and is subject to owner review on schedule.

Explanation

Correct Answer

D:

This tests the actual result for manual application dependency relation instead of merely checking whether a configuration screen can be opened. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable. The test must be performed on the described CI and service scope.

Incorrect Answers

A:

This might validate relationship duplication from integrations, but does not establish the acceptance requirement for manual application dependency relation. Instead verify: The batch application dependency appears correctly in queries and is subject to owner review on schedule.

B:

This might validate discovery relationship direction, but does not establish the acceptance requirement for manual application dependency relation. Instead verify: The batch application dependency appears correctly in queries and is subject to owner review on schedule.

C:

The choice “A pilot scan reaches the intended host, collects CI data, and does not touch excluded subnets” concerns mid server reachability diagnosis; it does not resolve the stated requirement. The batch application dependency appears correctly in queries and is subject to owner review on schedule.

Question 149

An internal batch application is not discoverable but service owners know it depends on a critical scheduling service. Which technical principle explains the right implementation approach?

  1. CI existence and topology relationship ingestion are distinct operations requiring compatible evidence and mappings.
  2. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable.
  3. Relationship direction and type determine meaningful traversals; simply connecting records does not establish the correct dependency semantics.
  4. Active discovery can collect infrastructure attributes and dependencies, while bulk imports alone may not provide ongoing observation.

Explanation

Correct Answer

B:

Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable. Have an authorized steward add the approved typed dependency relationship and ownership information in the CMDB.

Incorrect Answers

A:

Although relevant to discovery creates ci without topology links, this does not explain the remedy for manual application dependency relation. The causally relevant rule is: Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable.

C:

Although relevant to discovery relationship direction, this does not explain the remedy for manual application dependency relation. The causally relevant rule is: Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable.

D:

Although relevant to discovery versus import set for infrastructure, this does not explain the remedy for manual application dependency relation. The causally relevant rule is: Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable.

Question 150

An internal batch application is not discoverable but service owners know it depends on a critical scheduling service. Select TWO shortcuts that would undermine the intended data integrity or governance.

  1. Have an authorized steward add the approved typed dependency relationship and ownership information in the CMDB.
  2. Inspect application and scheduler CI sys_ids, relationship type, evidence record, and review ownership.
  3. Validate in a controlled test that the batch application dependency appears correctly in queries and is subject to owner review on schedule.
  4. Create the same dependency as an unreviewed free-text note rather than a typed CMDB relation.
  5. Invent an automated discovery source for the application without any underlying telemetry.

Explanation

Correct Answer

D:

“Create the same dependency as an unreviewed free-text note rather than a typed CMDB relation” would violate the requirement. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable.

E:

This violates the scenario constraints for manual application dependency relation. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable. Instead the safe implementation is: Have an authorized steward add the approved typed dependency relationship and ownership information in the CMDB.

Incorrect Answers

A:

“Have an authorized steward add the approved typed dependency relationship and ownership information in the CMDB” is the controlled implementation, not an unsafe workaround. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable. Confirm that the batch application dependency appears correctly in queries and is subject to owner review on schedule.

B:

“Inspect application and scheduler CI sys_ids, relationship type, evidence record, and review ownership” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable.

C:

“Validate in a controlled test that the batch application dependency appears correctly in queries and is subject to owner review on schedule” adds a relevant safeguard or verification step rather than weakening the solution. Manual relations are legitimate when governed evidence exists; undiscoverable does not mean unmodelable.

Certified Implementation Specialist - Data Foundations (CMDB and CSDM) (CIS-DF) Practice Tests