ServiceNow CIS-DF Practice Test 35 - 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 35

Question 340

A change rollout creates multiple identical depends-on relationships between the same application and database CIs. Select TWO proposed changes that would violate the requirement.

  1. Inspect cmdb_rel_ci keys, relationship type, duplicate-set details, and source insertion logs.
  2. Identify duplicate relationships by resolved parent, child, type and applicable port before removing extras.
  3. Merge two different application CIs merely because their relationships look similar.
  4. Delete all relationships between the pair instead of preserving the correct unique edge.
  5. Validate in a controlled test that the relationship audit counts one intended edge while preserving unrelated dependency types.

Explanation

Correct Answer

C:

“Merge two different application CIs merely because their relationships look similar” would violate the requirement. Relationship health checks are separate from duplicate CI identification and evaluate repeated graph edges.

D:

“Delete all relationships between the pair instead of preserving the correct unique edge” would violate the requirement. Relationship health checks are separate from duplicate CI identification and evaluate repeated graph edges.

Incorrect Answers

A:

“Inspect cmdb_rel_ci keys, relationship type, duplicate-set details, and source insertion logs” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Relationship health checks are separate from duplicate CI identification and evaluate repeated graph edges. Confirm that the relationship audit counts one intended edge while preserving unrelated dependency types.

B:

“Identify duplicate relationships by resolved parent, child, type and applicable port before removing extras” is the controlled implementation, not an unsafe workaround. Relationship health checks are separate from duplicate CI identification and evaluate repeated graph edges.

E:

“Validate in a controlled test that the relationship audit counts one intended edge while preserving unrelated dependency types” adds a relevant safeguard or verification step rather than weakening the solution. Relationship health checks are separate from duplicate CI identification and evaluate repeated graph edges. Confirm that the relationship audit counts one intended edge while preserving unrelated dependency types.

Question 341

A server CI was removed but a connection record still points to its missing sys_id and dependency graphs fail. Which ServiceNow implementation decision best addresses the requirement?

  1. Find orphaned relationship records and remediate the invalid endpoint reference with appropriate ownership review.
  2. Identify the source mapping gap and populate genuinely known required manufacturer values for the affected class.
  3. Create an unrelated dummy CI with the missing sys_id to silence the audit.
  4. Leave broken graph references indefinitely because the affected relation type is not principal.

Explanation

Correct Answer

A:

The requested CMDB/CSDM implementation concerns relationship orphan health metric, not just a different useful platform feature. Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves. Validate the effect with: Every retained relationship has valid endpoints and the relationship health audit clears the orphan finding.

Incorrect Answers

B:

This addresses required attributes completeness metric, an important but separate issue. It does not resolve the described relationship orphan health metric failure. Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves. The targeted action is: Find orphaned relationship records and remediate the invalid endpoint reference with appropriate ownership review.

C:

“Create an unrelated dummy CI with the missing sys_id to silence the audit” does not implement the control that the facts call for. Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves. Instead, find orphaned relationship records and remediate the invalid endpoint reference with appropriate ownership review.

D:

“Leave broken graph references indefinitely because the affected relation type is not principal” does not implement the control that the facts call for. Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves. Instead, find orphaned relationship records and remediate the invalid endpoint reference with appropriate ownership review.

Question 342

A server CI was removed but a connection record still points to its missing sys_id and dependency graphs fail. After an initial fix fails, which evidence should the team investigate first?

  1. Inspect class staleness rules, last-updated history, source cadence, and health scoring.
  2. Inspect cloud inventory API, source last-seen, staleness rule, incident status, and retirement evidence.
  3. Inspect parent and child references, deleted CI history, relationship audit results, and source integration.
  4. Inspect endpoint class staleness, CI last seen, relationship health results, and update sources.

Explanation

Correct Answer

C:

Inspect parent and child references, deleted CI history, relationship audit results, and source integration. Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves. Every retained relationship has valid endpoints and the relationship health audit clears the orphan finding.

Incorrect Answers

A:

That inspection relates primarily to staleness metric threshold by class rather than the failing relationship orphan health metric process. The immediate evidence needed for this case is: Inspect parent and child references, deleted CI history, relationship audit results, and source integration.

B:

That inspection relates primarily to stale ci versus retired ci judgment rather than the failing relationship orphan health metric process. The immediate evidence needed for this case is: Inspect parent and child references, deleted CI history, relationship audit results, and source integration.

D:

That inspection relates primarily to relationship stale endpoint health rather than the failing relationship orphan health metric process. The immediate evidence needed for this case is: Inspect parent and child references, deleted CI history, relationship audit results, and source integration.

Question 343

A server CI was removed but a connection record still points to its missing sys_id and dependency graphs fail. What observed outcome most convincingly validates the correction?

  1. Every retained relationship has valid endpoints and the relationship health audit clears the orphan finding.
  2. A revalidated active VM remains operational while genuinely terminated resources follow retirement controls.
  3. The dashboard flags records lacking the recommended support group without blocking legitimate CI updates.
  4. A corrected test service topology passes the configured relationship rule and maps with intended direction.

Explanation

Correct Answer

A:

Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves. Every retained relationship has valid endpoints and the relationship health audit clears the orphan finding.

Incorrect Answers

B:

This might validate stale ci versus retired ci judgment, but does not establish the acceptance requirement for relationship orphan health metric. Instead verify: Every retained relationship has valid endpoints and the relationship health audit clears the orphan finding.

C:

This might validate recommended field completeness metric, but does not establish the acceptance requirement for relationship orphan health metric. Instead verify: Every retained relationship has valid endpoints and the relationship health audit clears the orphan finding.

D:

This might validate relationship hosting rule compliance, but does not establish the acceptance requirement for relationship orphan health metric. Instead verify: Every retained relationship has valid endpoints and the relationship health audit clears the orphan finding.

Question 344

A server CI was removed but a connection record still points to its missing sys_id and dependency graphs fail. Which technical principle explains the right implementation approach?

  1. Trust and update authority can differ by attribute, so one source need not own every field.
  2. Relationship health checks are separate from duplicate CI identification and evaluate repeated graph edges.
  3. Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves.
  4. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date.

Explanation

Correct Answer

C:

Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves. Find orphaned relationship records and remediate the invalid endpoint reference with appropriate ownership review.

Incorrect Answers

A:

Although relevant to multi-source cmdb accountability, this does not explain the remedy for relationship orphan health metric. The causally relevant rule is: Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves.

B:

Although relevant to relationship duplicate health metric, this does not explain the remedy for relationship orphan health metric. The causally relevant rule is: Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves.

D:

Although relevant to relationship stale endpoint health, this does not explain the remedy for relationship orphan health metric. The causally relevant rule is: Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves.

Question 345

A server CI was removed but a connection record still points to its missing sys_id and dependency graphs fail. Select TWO shortcuts that would undermine the intended data integrity or governance.

  1. Inspect parent and child references, deleted CI history, relationship audit results, and source integration.
  2. Create an unrelated dummy CI with the missing sys_id to silence the audit.
  3. Leave broken graph references indefinitely because the affected relation type is not principal.
  4. Find orphaned relationship records and remediate the invalid endpoint reference with appropriate ownership review.
  5. Validate in a controlled test that every retained relationship has valid endpoints and the relationship health audit clears the orphan finding.

Explanation

Correct Answer

B:

“Create an unrelated dummy CI with the missing sys_id to silence the audit” would violate the requirement. Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves.

C:

“Leave broken graph references indefinitely because the affected relation type is not principal” would violate the requirement. Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves.

Incorrect Answers

A:

“Inspect parent and child references, deleted CI history, relationship audit results, and source integration” is the relevant troubleshooting evidence, not a reason to bypass safeguards. Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves.

D:

“Find orphaned relationship records and remediate the invalid endpoint reference with appropriate ownership review” is the controlled implementation, not an unsafe workaround. Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves.

E:

“Validate in a controlled test that every retained relationship has valid endpoints and the relationship health audit clears the orphan finding” adds a relevant safeguard or verification step rather than weakening the solution. Orphan relationship health detects graph edges whose parent or child CI reference no longer resolves. Confirm that every retained relationship has valid endpoints and the relationship health audit clears the orphan finding.

Question 346

An application dependency is flagged stale because its database CI has not been updated, even though the relationship record itself was created yesterday. What is the most appropriate configuration or governance action?

  1. Remove the application dependency because a legitimate database is temporarily stale.
  2. Touch every relationship sys_updated_on field to today without validating the CIs.
  3. Investigate freshness of both endpoint CIs and the source ingestion rather than editing the edge timestamp.
  4. Define appropriate recommended-field health rules for the selected class and remediate missing values through stewardship.

Explanation

Correct Answer

C:

The requested CMDB/CSDM implementation concerns relationship stale endpoint health, not just a different useful platform feature. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date. Validate the effect with: The database freshness issue is resolved and the dependency's stale warning clears after recalculation.

Incorrect Answers

A:

“Remove the application dependency because a legitimate database is temporarily stale” would not meet the requirement. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date. Instead, investigate freshness of both endpoint CIs and the source ingestion rather than editing the edge timestamp.

B:

“Touch every relationship sys_updated_on field to today without validating the CIs” would not meet the requirement. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date. Instead, investigate freshness of both endpoint CIs and the source ingestion rather than editing the edge timestamp.

D:

This addresses recommended field completeness metric, an important but separate issue. It does not resolve the described relationship stale endpoint health failure. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date. The targeted action is: Investigate freshness of both endpoint CIs and the source ingestion rather than editing the edge timestamp.

Question 347

An application dependency is flagged stale because its database CI has not been updated, even though the relationship record itself was created yesterday. Which diagnostic evidence best isolates the actual cause?

  1. Inspect orphan rule criteria, cmdb_rel_ci, CI class, lifecycle and health results.
  2. Inspect last health run, scheduled jobs, result timestamps, IRE update history, and remaining findings.
  3. Inspect parent-child relationships, dependent CI policy tasks, approval results, and lifecycle state.
  4. Inspect endpoint class staleness, CI last seen, relationship health results, and update sources.

Explanation

Correct Answer

D:

Inspect endpoint class staleness, CI last seen, relationship health results, and update sources. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date. The database freshness issue is resolved and the dependency's stale warning clears after recalculation.

Incorrect Answers

A:

That inspection relates primarily to orphan ci correctness metric rather than the failing relationship stale endpoint health process. The immediate evidence needed for this case is: Inspect endpoint class staleness, CI last seen, relationship health results, and update sources.

B:

That inspection relates primarily to health schedule and data freshness rather than the failing relationship stale endpoint health process. The immediate evidence needed for this case is: Inspect endpoint class staleness, CI last seen, relationship health results, and update sources.

C:

“Inspect parent-child relationships, dependent CI policy tasks, approval results, and lifecycle state” would not be the most direct first check for this failure. Inspect endpoint class staleness, CI last seen, relationship health results, and update sources.

Question 348

An application dependency is flagged stale because its database CI has not been updated, even though the relationship record itself was created yesterday. Which result demonstrates that the requirement is now satisfied?

  1. The database freshness issue is resolved and the dependency's stale warning clears after recalculation.
  2. A corrected test service topology passes the configured relationship rule and maps with intended direction.
  3. Correctly linked operational routers pass while genuinely isolated CIs remain reviewable.
  4. A disputed service taxonomy change follows the agreed approval route and yields one documented decision.

Explanation

Correct Answer

A:

A relationship can be marked stale when either participating CI is stale regardless of the edge creation date. The database freshness issue is resolved and the dependency's stale warning clears after recalculation.

Incorrect Answers

B:

This might validate relationship hosting rule compliance, but does not establish the acceptance requirement for relationship stale endpoint health. Instead verify: The database freshness issue is resolved and the dependency's stale warning clears after recalculation.

C:

“Correctly linked operational routers pass while genuinely isolated CIs remain reviewable” pertains to orphan ci correctness metric, not the deciding condition here. The database freshness issue is resolved and the dependency's stale warning clears after recalculation. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date.

D:

This might validate cmdb governance charter, but does not establish the acceptance requirement for relationship stale endpoint health. Instead verify: The database freshness issue is resolved and the dependency's stale warning clears after recalculation.

Question 349

An application dependency is flagged stale because its database CI has not been updated, even though the relationship record itself was created yesterday. What underlying CMDB or CSDM behavior justifies the correct decision?

  1. CMDB Health recommended-field checks are configurable and distinct from dictionary-level mandatory required-field checks.
  2. Stewardship requires named responsibility and measurable follow-through on data-quality exceptions.
  3. A failure cap can truncate metric evaluation, so a partial score should not be presented as a complete health result.
  4. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date.

Explanation

Correct Answer

D:

A relationship can be marked stale when either participating CI is stale regardless of the edge creation date. Investigate freshness of both endpoint CIs and the source ingestion rather than editing the edge timestamp.

Incorrect Answers

A:

Although relevant to recommended field completeness metric, this does not explain the remedy for relationship stale endpoint health. The causally relevant rule is: A relationship can be marked stale when either participating CI is stale regardless of the edge creation date.

B:

Although relevant to cmdb stewardship escalation, this does not explain the remedy for relationship stale endpoint health. The causally relevant rule is: A relationship can be marked stale when either participating CI is stale regardless of the edge creation date.

C:

“A failure cap can truncate metric evaluation, so a partial score should not be presented as a complete health result” does not fully explain the decisive technical boundary in this case. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date.

Question 350

An application dependency is flagged stale because its database CI has not been updated, even though the relationship record itself was created yesterday. Which TWO actions would be unsuitable or unsafe?

  1. Investigate freshness of both endpoint CIs and the source ingestion rather than editing the edge timestamp.
  2. Remove the application dependency because a legitimate database is temporarily stale.
  3. Touch every relationship sys_updated_on field to today without validating the CIs.
  4. Inspect endpoint class staleness, CI last seen, relationship health results, and update sources.
  5. Validate in a controlled test that the database freshness issue is resolved and the dependency's stale warning clears after recalculation.

Explanation

Correct Answer

B:

“Remove the application dependency because a legitimate database is temporarily stale” would violate the requirement. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date.

C:

“Touch every relationship sys_updated_on field to today without validating the CIs” would violate the requirement. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date.

Incorrect Answers

A:

“Investigate freshness of both endpoint CIs and the source ingestion rather than editing the edge timestamp” is the controlled implementation, not an unsafe workaround. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date.

D:

“Inspect endpoint class staleness, CI last seen, relationship health results, and update sources” is the relevant troubleshooting evidence, not a reason to bypass safeguards. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date.

E:

“Validate in a controlled test that the database freshness issue is resolved and the dependency's stale warning clears after recalculation” adds a relevant safeguard or verification step rather than weakening the solution. A relationship can be marked stale when either participating CI is stale regardless of the edge creation date.

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