McAfee Secure

Exam Code: CIS-DF

Exam Name: Certified Implementation Specialist - Data Foundations (CMDB and CSDM)

Certification Provider: ServiceNow

Corresponding Certification: CIS-DF (CMDB and CSDM)

ServiceNow CIS-DF Questions & Answers

Study with Up-To-Date REAL Exam Questions and Answers from the ACTUAL Test

283 Questions & Answers with Testing Engine

"Certified Implementation Specialist - Data Foundations (CMDB and CSDM) Exam", also known as CIS-DF exam, is a ServiceNow certification exam.

Pass your tests with the always up-to-date CIS-DF Exam Engine. Your CIS-DF training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

ServiceNow CIS-DF Practice Test 36

Question 350

During a CMDB review, engineers discover: A cloud infrastructure vendor has a supported Service Graph Connector and the team is considering a bespoke CMDB REST importer. Which proposed action is appropriate if success is measured by: The vendor inventory loads with mapped CI classes and no duplicate source identities?

  1. Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path
  2. Model procurement assets and operational CIs separately and link them where the model category supports it
  3. Stage relationships until their parent and child CIs are resolved then load them via a supported path
  4. Ingest or construct relationship payloads with resolvable parent and child CIs

Explanation

Correct Answer

A:

This is the appropriate control for the stated CI requirement. Supported connectors reduce custom upgrade debt and integrate source identification. Implement: Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path. Confirm effectiveness by checking: The vendor inventory loads with mapped CI classes and no duplicate source identities.

Incorrect Answers

B:

Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. The specific problem here is that supported connectors reduce custom upgrade debt and integrate source identification.

C:

Processing order and endpoint matching prevent dangling or mismatched relationship references. The specific problem here is that supported connectors reduce custom upgrade debt and integrate source identification.

D:

Reliable network maps depend on relationship creation and correctly identified endpoints. The specific problem here is that supported connectors reduce custom upgrade debt and integrate source identification.

Question 351

A CMDB change request reports: A duplicate task was created before an identification rule was fixed, and the team assumes fixing the rule auto-merges historical records. Select the best implementation. It must pass this acceptance test: Existing task is closed appropriately and repeat ingestion does not produce a new duplicate.

  1. Compare freshness and actual ingestion history before altering health thresholds
  2. Remediate existing duplicate records separately and test the revised IRE rule for future ingests
  3. Verify an active retirement definition and preview the published-policy eligibility, requiring already retired class-matched CIs and explicit approval before any Delete execution
  4. Review class scope, asset linkage and deployment lifecycle before mass remediation

Explanation

Correct Answer

B:

This is the appropriate control for the stated CI requirement. Improved identification prevents future collisions but does not retroactively merge every old duplicate. Implement: Remediate existing duplicate records separately and test the revised IRE rule for future ingests. Confirm effectiveness by checking: Existing task is closed appropriately and repeat ingestion does not produce a new duplicate.

Incorrect Answers

A:

Data-source coverage failures can cause stale CI results that should not be hidden by score adjustments. The specific problem here is that improved identification prevents future collisions but does not retroactively merge every old duplicate.

C:

CMDB Data Manager Delete and Archive processors evaluate only CIs considered retired by the active class retirement definition; an apparent broad filter must still be reviewed for safety and actual eligibility. The specific problem here is that improved identification prevents future collisions but does not retroactively merge every old duplicate.

D:

A stocked asset can exist financially without a currently operating CI for production impact. The specific problem here is that improved identification prevents future collisions but does not retroactively merge every old duplicate.

Question 352

An implementation review finds these independent issues: (1) A central team overrides business service names without approval from the service owners. (2) The same hardware CI alternates between In Use and Retired after two different feeds run. Which TWO controls should the team apply?

  1. Report Completeness Required/Recommended, Correctness Duplicate/Staleness/Orphan, Compliance completed-audit results, and separate relationship-health indicators by relevant class
  2. Investigate and repair orphan relationships in the relationship health results
  3. Align lifecycle attribute source authority and the asset-CI status mapping
  4. Verify stable identification evidence before merging a suspected duplicate pair
  5. Define a service owner approval and change-control process for governed naming updates

Explanation

Correct Answers

C:

This satisfies requirement B: Align lifecycle attribute source authority and the asset-CI status mapping. Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates. Independently verify: Repeated import cycles preserve the reviewed hardware lifecycle state.

E:

This satisfies requirement A: Define a service owner approval and change-control process for governed naming updates. Stewardship prevents uncoordinated changes to shared business context. Independently verify: An approved renaming request includes owner signoff and traceable changes.

Incorrect Answers

A:

This is appropriate for another technical scenario: A CMDB manager wants to distinguish correctness, completeness and compliance in a monthly report. CMDB Health uses three aggregate CI KPIs (Completeness, Correctness, Compliance) with distinct submetrics; orphan/duplicate/stale relationships are reported separately and should not be conflated with CI correctness. It does not directly satisfy either stated requirement; those require define a service owner approval and change-control process for governed naming updates. and align lifecycle attribute source authority and the asset-CI status mapping.

B:

This is appropriate for another technical scenario: A relationship health report contains edges with missing parent CI references. Relationship integrity is separate from a CI having complete attributes. It does not directly satisfy either stated requirement; those require define a service owner approval and change-control process for governed naming updates. and align lifecycle attribute source authority and the asset-CI status mapping.

D:

This is appropriate for another technical scenario: Two visually similar server names do not mean two CIs are identical physical hosts. Similar display names alone do not establish identical physical or logical identity. It does not directly satisfy either stated requirement; those require define a service owner approval and change-control process for governed naming updates. and align lifecycle attribute source authority and the asset-CI status mapping.

Question 353

A ServiceNow Data Foundations rollout has two blockers. First: A CMDB manager wants to distinguish correctness, completeness and compliance in a monthly report. Second: An administrator deletes a duplicate CI record directly and loses change relationships attached to it. Which complete two-part implementation addresses both?

  1. (1) Report Completeness Required/Recommended, Correctness Duplicate/Staleness/Orphan, Compliance completed-audit results, and separate relationship-health indicators by relevant class; (2) inspect the class-effective CMDB Health Staleness correctness rule and last-update evidence, including the inherited 60-day default unless an explicit class override exists
  2. (1) Define a service owner approval and change-control process for governed naming updates; (2) use guided de-duplication or an approved remediation workflow to reconcile references before deletion
  3. (1) Define a service owner approval and change-control process for governed naming updates; (2) inspect the class-effective CMDB Health Staleness correctness rule and last-update evidence, including the inherited 60-day default unless an explicit class override exists
  4. (1) Report Completeness Required/Recommended, Correctness Duplicate/Staleness/Orphan, Compliance completed-audit results, and separate relationship-health indicators by relevant class; (2) use guided de-duplication or an approved remediation workflow to reconcile references before deletion

Explanation

Correct Answer

D:

Both controls are required. For condition (1), report Completeness Required/Recommended, Correctness Duplicate/Staleness/Orphan, Compliance completed-audit results, and separate relationship-health indicators by relevant class. CMDB Health uses three aggregate CI KPIs (Completeness, Correctness, Compliance) with distinct submetrics; orphan/duplicate/stale relationships are reported separately and should not be conflated with CI correctness. Verify: The monthly scorecard attributes changes to individual CI submetrics and distinct relationship-health failures rather than hiding both in a single blended score. For condition (2), use guided de-duplication or an approved remediation workflow to reconcile references before deletion. Direct record deletion can leave broken or incomplete related records. Verify independently: Related change and incident records reference the retained main CI.

Incorrect Answers

A:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: Servers remain active in CMDB although their last discovery time is older than the agreed threshold. It should instead use: Use guided de-duplication or an approved remediation workflow to reconcile references before deletion. Both required outcomes must be verified separately.

B:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: A central team overrides business service names without approval from the service owners. It should instead use: Report Completeness Required/Recommended, Correctness Duplicate/Staleness/Orphan, Compliance completed-audit results, and separate relationship-health indicators by relevant class. Both required outcomes must be verified separately.

C:

Part (1) answers a different need: A central team overrides business service names without approval from the service owners. It should instead use: Report Completeness Required/Recommended, Correctness Duplicate/Staleness/Orphan, Compliance completed-audit results, and separate relationship-health indicators by relevant class. Part (2) answers a different need: Servers remain active in CMDB although their last discovery time is older than the agreed threshold. It should instead use: Use guided de-duplication or an approved remediation workflow to reconcile references before deletion. Both required outcomes must be verified separately.

Question 354

An organization finds this data-foundation problem: A service portfolio manager cannot compare service reliability because applications are inconsistently represented in CMDB. Which approach best achieves the required outcome: Two departments' equivalent services appear under consistent classes and governance definitions?

  1. Model supported CMDB CIs and relationships rather than assuming arbitrary tables appear in CI maps
  2. Read the indicator's problem overview, business impact and fix/improve guidance
  3. Monitor CMDB 360 'not reported by source' potential issues and reporting intervals
  4. Align application and service entities with the CSDM model and use suitable foundation indicators

Explanation

Correct Answer

D:

This is the appropriate control for the stated CI requirement. Standardized service representation supports comparable portfolio and operations reporting. Implement: Align application and service entities with the CSDM model and use suitable foundation indicators. Confirm effectiveness by checking: Two departments' equivalent services appear under consistent classes and governance definitions.

Incorrect Answers

A:

Dependency views operate on supported CMDB class and relationship information. The specific problem here is that standardized service representation supports comparable portfolio and operations reporting.

B:

Playbooks translate measured data-quality issues into actionable remediation context. The specific problem here is that standardized service representation supports comparable portfolio and operations reporting.

C:

Missing recent source activity can signal integration failure even when other feeds maintain the CI. The specific problem here is that standardized service representation supports comparable portfolio and operations reporting.

Question 355

A CMDB change request reports: A compliance reviewer cannot distinguish who approved a CI's manual changes from who loaded it. Select the best implementation. It must pass this acceptance test: The updated CI has a source, approver and linked change history.

  1. Require change records, source metadata and reviewer ownership for manual CI updates
  2. Preview or evaluate policy targets and approval requirements before publishing the change
  3. Review the targeted Related Entry [cmdb_related_entry] references and apply the CMDB Data Manager Delete CMDB Related Entry policy only to approved orphaned entries
  4. Use an appropriate certification or attestation control requiring explicit confirmation of that value

Explanation

Correct Answer

A:

This is the appropriate control for the stated CI requirement. Traceable data changes preserve accountability for non-discoverable or manually governed CIs. Implement: Require change records, source metadata and reviewer ownership for manual CI updates. Confirm effectiveness by checking: The updated CI has a source, approver and linked change history.

Incorrect Answers

B:

Evaluated policy scope helps prevent accidental mass retirement or deletion. The specific problem here is that traceable data changes preserve accountability for non-discoverable or manually governed CIs.

C:

The separate Delete CMDB Related Entry processor handles configured related-table entries tracked in cmdb_related_entry; it is not a general-purpose delete-all-non-CMDB-table operation. The specific problem here is that traceable data changes preserve accountability for non-discoverable or manually governed CIs.

D:

Fresh timestamps do not prove that a human has validated business ownership. The specific problem here is that traceable data changes preserve accountability for non-discoverable or manually governed CIs.

Question 356

A data steward is asked to resolve: A service owner needs all database servers used by one application and their hosting Linux machines. Which solution meets the requirement and verifies: The saved query returns all matching application, database and Linux server paths?

  1. Verify compliance activation, audit definition and last completed run before treating a blank CMDB Health compliance indicator as meaningful
  2. Compare relevant health/ownership indicators with observed incident routing or impact analysis outcomes
  3. Build a CMDB Query Builder graph using CI class nodes and correctly typed relationships
  4. Align application and service entities with the CSDM model and use suitable foundation indicators

Explanation

Correct Answer

C:

This is the appropriate control for the stated CI requirement. A relationship-aware query traverses edges rather than filtering only a flat CI list. Implement: Build a CMDB Query Builder graph using CI class nodes and correctly typed relationships. Confirm effectiveness by checking: The saved query returns all matching application, database and Linux server paths.

Incorrect Answers

A:

CMDB compliance scores require the latest completed audit evidence; scripted audits lacking a recorded Last run date can be skipped rather than counted as a passing score. The specific problem here is that a relationship-aware query traverses edges rather than filtering only a flat CI list.

B:

Dashboard measures should connect data quality to measurable operational outcomes. The specific problem here is that a relationship-aware query traverses edges rather than filtering only a flat CI list.

D:

Standardized service representation supports comparable portfolio and operations reporting. The specific problem here is that a relationship-aware query traverses edges rather than filtering only a flat CI list.

Question 357

The change record states that the team will: Inspect the CI class Orphan rule attribute and relationship criteria, verify the flagged CI against the actual source records and assign remediation without automatically deleting it. The original defect was: An Orphan correctness score flags CIs missing configured ownership attributes or required relationship types, but operators assume every flagged CI is decommissioned. Which validation finding should be accepted?

  1. Principal class scorecards reflect the corrected ownership information
  2. Each critical failed metric has a named owner, affected CI sample and due date
  3. A seeded CI missing the configured relationship is flagged; a legitimate active CI is repaired or appropriately excluded instead of bulk-deleted
  4. A reviewed dry-run selects only explicitly approved retired database test records; production databases that remain active are ineligible

Explanation

Correct Answer

C:

This observation directly validates the implemented control. The CMDB Health Orphan correctness metric uses class-specific attribute and/or missing-relationship rules; a flagged CI is not necessarily a deleted, stale or physically decommissioned asset. The decisive expected result is: A seeded CI missing the configured relationship is flagged; a legitimate active CI is repaired or appropriately excluded instead of bulk-deleted.

Incorrect Answers

A:

That observation would verify a control associated with: Principal class focus enables targeted data foundation completeness work. It does not establish the needed acceptance outcome. The direct evidence is “A seeded CI missing the configured relationship is flagged; a legitimate active CI is repaired or appropriately excluded instead of bulk-deleted”, testing: The CMDB Health Orphan correctness metric uses class-specific attribute and/or missing-relationship rules; a flagged CI is not necessarily a deleted, stale or physically decommissioned asset.

B:

“Each critical failed metric has a named owner, affected CI sample and due date” could occur while the stated failure remains unresolved. It tests: An aggregate score becomes useful when failures are traceable to actionable work items. The required validation instead is “A seeded CI missing the configured relationship is flagged; a legitimate active CI is repaired or appropriately excluded instead of bulk-deleted”, because the CMDB Health Orphan correctness metric uses class-specific attribute and/or missing-relationship rules; a flagged CI is not necessarily a deleted, stale or physically decommissioned asset.

D:

That observation would verify a control associated with: CMDB Data Manager Delete and Archive processors evaluate only CIs considered retired by the active class retirement definition; an apparent broad filter must still be reviewed for safety and actual eligibility. It does not establish the needed acceptance outcome. The direct evidence is “A seeded CI missing the configured relationship is flagged; a legitimate active CI is repaired or appropriately excluded instead of bulk-deleted”, testing: The CMDB Health Orphan correctness metric uses class-specific attribute and/or missing-relationship rules; a flagged CI is not necessarily a deleted, stale or physically decommissioned asset.

Question 358

A configuration management team must address: A monitoring feed overwrites the serial number populated by a more authoritative Discovery source. What change should it implement to demonstrate this result: A lower-priority monitoring update cannot replace the Discovery-owned serial number on an existing matched CI, while the authorized source can refresh it?

  1. Use CI Class Manager to classify the records under an appropriate derived Linux Server class and its class-specific attributes
  2. Configure the appropriate suggested relationships for the class in CI Class Manager
  3. Configure a static attribute-level reconciliation definition that authorizes Discovery above the monitoring source for the serial-number attribute of matched existing server CIs
  4. Add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition

Explanation

Correct Answer

C:

This is the appropriate control for the stated CI requirement. Static reconciliation governs source-authorized updates to existing CIs by class and attribute; child-class rules and any active dynamic rule for the attribute must also be evaluated. Implement: Configure a static attribute-level reconciliation definition that authorizes Discovery above the monitoring source for the serial-number attribute of matched existing server CIs. Confirm effectiveness by checking: A lower-priority monitoring update cannot replace the Discovery-owned serial number on an existing matched CI, while the authorized source can refresh it.

Incorrect Answers

A:

A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type. The specific problem here is that static reconciliation governs source-authorized updates to existing CIs by class and attribute; child-class rules and any active dynamic rule for the attribute must also be evaluated.

B:

Suggested relationships guide consistent relationship selection without making every pairing physically true. The specific problem here is that static reconciliation governs source-authorized updates to existing CIs by class and attribute; child-class rules and any active dynamic rule for the attribute must also be evaluated.

D:

Child-level attributes scope specialized fields to the correct extension class. The specific problem here is that static reconciliation governs source-authorized updates to existing CIs by class and attribute; child-class rules and any active dynamic rule for the attribute must also be evaluated.

Question 359

A CMDB engineer applied the control: Use normal table-definition administration for the non-CMDB table rather than CI Class Manager. This was meant to resolve: A team configures a new custom table unrelated to cmdb_ci and expects CI Class Manager to administer it. Which result most directly confirms the implementation works?

  1. The selected CI value changes only as justified by configured source data and the tested recomputation
  2. A controlled payload with conflicting values produces the expected selected attribute under the chosen dynamic rule, including a documented tie case
  3. A lower-priority monitoring update cannot replace the Discovery-owned serial number on an existing matched CI, while the authorized source can refresh it
  4. The non-CMDB table is managed correctly and no phantom CI class appears

Explanation

Correct Answer

D:

This observation directly validates the implemented control. CI Class Manager is designed for classes in the CMDB hierarchy. The decisive expected result is: The non-CMDB table is managed correctly and no phantom CI class appears.

Incorrect Answers

A:

This checks a different technical dependency: The selected CI value changes only as justified by configured source data and the tested recomputation. The case requires proof of “The non-CMDB table is managed correctly and no phantom CI class appears”, which establishes the relevant condition: CI Class Manager is designed for classes in the CMDB hierarchy.

B:

That observation would verify a control associated with: Dynamic reconciliation evaluates CMDB 360 multisource values and takes precedence over a static rule for the same attribute; ties and missing timestamps may require fallback logic, not automatic majority consensus. It does not establish the needed acceptance outcome. The direct evidence is “The non-CMDB table is managed correctly and no phantom CI class appears”, testing: CI Class Manager is designed for classes in the CMDB hierarchy.

C:

“A lower-priority monitoring update cannot replace the Discovery-owned serial number on an existing matched CI, while the authorized source can refresh it” could occur while the stated failure remains unresolved. It tests: A lower-priority monitoring update cannot replace the Discovery-owned serial number on an existing matched CI, while the authorized source can refresh it. The required validation instead is “The non-CMDB table is managed correctly and no phantom CI class appears”, because cI Class Manager is designed for classes in the CMDB hierarchy.

Question 360

A ServiceNow configuration project has two acceptance conditions. The first issue is: A team configures a new custom table unrelated to cmdb_ci and expects CI Class Manager to administer it. The second is: Two sources insert separate server CIs because hostname alone is not a stable unique key. Which paired approach is suitable?

  1. (1) Route incoming CI payloads through a supported IRE-aware ingestion path; (2) configure a CI-class-appropriate IRE identification rule using sufficiently stable identifiers, and compare insert-versus-match results with the Identification Simulator before sending data to production
  2. (1) Use normal table-definition administration for the non-CMDB table rather than CI Class Manager; (2) configure a CI-class-appropriate IRE identification rule using sufficiently stable identifiers, and compare insert-versus-match results with the Identification Simulator before sending data to production
  3. (1) Route incoming CI payloads through a supported IRE-aware ingestion path; (2) use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value
  4. (1) Use normal table-definition administration for the non-CMDB table rather than CI Class Manager; (2) use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value

Explanation

Correct Answer

B:

Both controls are required. For condition (1), use normal table-definition administration for the non-CMDB table rather than CI Class Manager. CI Class Manager is designed for classes in the CMDB hierarchy. Verify: The non-CMDB table is managed correctly and no phantom CI class appears. For condition (2), configure a CI-class-appropriate IRE identification rule using sufficiently stable identifiers, and compare insert-versus-match results with the Identification Simulator before sending data to production. IRE uses class identification criteria to match an existing CI or create a genuinely new one; hostname alone may not uniquely identify a multi-source server. Verify independently: Two independently sourced payloads for one verified server select the same CI, while a distinct server remains a separate CI.

Incorrect Answers

A:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: A custom CMDB integration uses a direct table insert and bypasses existing IRE identification logic. It should instead use: Use normal table-definition administration for the non-CMDB table rather than CI Class Manager. Both required outcomes must be verified separately.

C:

Part (1) answers a different need: A custom CMDB integration uses a direct table insert and bypasses existing IRE identification logic. It should instead use: Use normal table-definition administration for the non-CMDB table rather than CI Class Manager. Part (2) answers a different need: Cloud inventory and Discovery report different operating system versions for the same CI. It should instead use: Configure a CI-class-appropriate IRE identification rule using sufficiently stable identifiers, and compare insert-versus-match results with the Identification Simulator before sending data to production. Both required outcomes must be verified separately.

D:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: Cloud inventory and Discovery report different operating system versions for the same CI. It should instead use: Configure a CI-class-appropriate IRE identification rule using sufficiently stable identifiers, and compare insert-versus-match results with the Identification Simulator before sending data to production. Both required outcomes must be verified separately.

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