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 21

Question 200

The change record states that the team will: Maintain acquisition Cost as the authoritative asset value and validate the supported one-way Asset-to-CI Cost synchronization instead of editing the CI to overwrite the purchase record. The original defect was: Finance changes asset acquisition cost and expects manual reversal from the CI to rewrite the purchase ledger. Which validation finding should be accepted?

  1. The dependent CI matches its existing record when the required parent relationship is supplied
  2. Two imports of an identical host leave one CI with updated source data
  3. Changing asset Cost updates the linked CI cost display; editing the CI cost does not change the authoritative asset Cost
  4. The vendor inventory loads with mapped CI classes and no duplicate source identities

Explanation

Correct Answer

C:

This observation directly validates the implemented control. ServiceNow Asset–CI synchronization permits many mapped attributes in both directions, but the Cost field is informational on the CI and is synchronized only from Asset to CI. The decisive expected result is: Changing asset Cost updates the linked CI cost display; editing the CI cost does not change the authoritative asset Cost.

Incorrect Answers

A:

This checks a different technical dependency: The dependent CI matches its existing record when the required parent relationship is supplied. The case requires proof of “Changing asset Cost updates the linked CI cost display; editing the CI cost does not change the authoritative asset Cost”, which establishes the relevant condition: Changing asset Cost updates the linked CI cost display; editing the CI cost does not change the authoritative asset Cost.

B:

That observation would verify a control associated with: Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. It does not establish the needed acceptance outcome. The direct evidence is “Changing asset Cost updates the linked CI cost display; editing the CI cost does not change the authoritative asset Cost”, testing: Changing asset Cost updates the linked CI cost display; editing the CI cost does not change the authoritative asset Cost.

D:

This checks a different technical dependency: Supported connectors reduce custom upgrade debt and integrate source identification. The case requires proof of “Changing asset Cost updates the linked CI cost display; editing the CI cost does not change the authoritative asset Cost”, which establishes the relevant condition: Changing asset Cost updates the linked CI cost display; editing the CI cost does not change the authoritative asset Cost.

Question 201

A CMDB engineer applied the control: Create an IRE data source rule denying inserts by this import source for the storage CI class, then separately allow authorized updates to already identified storage CIs under the applicable reconciliation configuration. This was meant to resolve: A trusted import is allowed to update existing storage CIs but must not create new storage CIs. Which result most directly confirms the implementation works?

  1. The administrator identifies which parent supplies each required field before making a change
  2. With the intended supported IRE mode, an unmatched storage CI insert is rejected while an identified existing CI receives an authorized update
  3. The reviewer sees both source values and identifies the currently selected value
  4. The missing-source inventory lists the seeded device and excludes a device reported by both feeds

Explanation

Correct Answer

B:

This observation directly validates the implemented control. An IRE data source rule can block a specified source from inserting a new CI while permitting appropriate updates to matches; ServiceNow notes these rules have no impact when dynamic reconciliation rules are in effect. The decisive expected result is: With the intended supported IRE mode, an unmatched storage CI insert is rejected while an identified existing CI receives an authorized update.

Incorrect Answers

A:

That observation would verify a control associated with: The administrator identifies which parent supplies each required field before making a change. It does not establish the needed acceptance outcome. The direct evidence is “With the intended supported IRE mode, an unmatched storage CI insert is rejected while an identified existing CI receives an authorized update”, testing: With the intended supported IRE mode, an unmatched storage CI insert is rejected while an identified existing CI receives an authorized update.

C:

This checks a different technical dependency: The reviewer sees both source values and identifies the currently selected value. The case requires proof of “With the intended supported IRE mode, an unmatched storage CI insert is rejected while an identified existing CI receives an authorized update”, which establishes the relevant condition: With the intended supported IRE mode, an unmatched storage CI insert is rejected while an identified existing CI receives an authorized update.

D:

That observation would verify a control associated with: Multisource gap queries identify CIs not reported by one or more participating data sources. It does not establish the needed acceptance outcome. The direct evidence is “With the intended supported IRE mode, an unmatched storage CI insert is rejected while an identified existing CI receives an authorized update”, testing: With the intended supported IRE mode, an unmatched storage CI insert is rejected while an identified existing CI receives an authorized update.

Question 202

An audit evaluates the completed action: Define and validate a child-class identification rule instead of relying on an unsuitable inherited parent rule. It addressed the problem: A child network-device class needs stricter identification than its broad parent network class. What evidence best demonstrates success?

  1. Linux-specific reports include migrated server CIs without mixing desktop computers
  2. The selected CI value changes only as justified by configured source data and the tested recomputation
  3. Incoming identical network-device payloads resolve to one correctly typed CI
  4. A controlled payload with conflicting values produces the expected selected attribute under the chosen dynamic rule, including a documented tie case

Explanation

Correct Answer

C:

This observation directly validates the implemented control. More specialized CI class rules can be chosen to identify specific subclasses accurately. The decisive expected result is: Incoming identical network-device payloads resolve to one correctly typed CI.

Incorrect Answers

A:

“Linux-specific reports include migrated server CIs without mixing desktop computers” could occur while the stated failure remains unresolved. It tests: Linux-specific reports include migrated server CIs without mixing desktop computers. The required validation instead is “Incoming identical network-device payloads resolve to one correctly typed CI”, because more specialized CI class rules can be chosen to identify specific subclasses accurately.

B:

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 “Incoming identical network-device payloads resolve to one correctly typed CI”, which establishes the relevant condition: More specialized CI class rules can be chosen to identify specific subclasses accurately.

D:

“A controlled payload with conflicting values produces the expected selected attribute under the chosen dynamic rule, including a documented tie case” could occur while the stated failure remains unresolved. It tests: 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. The required validation instead is “Incoming identical network-device payloads resolve to one correctly typed CI”, because more specialized CI class rules can be chosen to identify specific subclasses accurately.

Question 203

Two ServiceNow configuration issues require separate remedies. First: The operations team cannot see where Database Server inherits its mandatory CI fields. Second: A monitoring feed overwrites the serial number populated by a more authoritative Discovery source. Select exactly TWO appropriate steps.

  1. Route incoming CI payloads through a supported IRE-aware ingestion path
  2. Inspect the class hierarchy and inherited attributes in CI Class Manager
  3. Use preview or recompute where supported and verify the result against source history
  4. Use an appropriate CMDB 360 saved query such as Find Gap comparing the two discovery sources
  5. Configure a static attribute-level reconciliation definition that authorizes Discovery above the monitoring source for the serial-number attribute of matched existing server CIs

Explanation

Correct Answers

B:

This satisfies requirement A: Inspect the class hierarchy and inherited attributes in CI Class Manager. Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported. Independently verify: The administrator identifies which parent supplies each required field before making a change.

E:

This satisfies requirement B: Configure a static attribute-level reconciliation definition that authorizes Discovery above the monitoring source for the serial-number attribute of matched existing server CIs. 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. Independently verify: 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:

This is appropriate for another technical scenario: A custom CMDB integration uses a direct table insert and bypasses existing IRE identification logic. Direct table writes can evade identification and reconciliation controls designed to prevent duplicates. It does not directly satisfy either stated requirement; those require inspect the class hierarchy and inherited attributes in CI Class Manager. and configure a static attribute-level reconciliation definition that authorizes Discovery above the monitoring source for the serial-number attribute of matched existing server CIs.

C:

This is appropriate for another technical scenario: An administrator changes reconciliation priorities but assumes old CMDB values will instantly reflect the new rules. Reconciliation rule changes can require reevaluation of existing attribute choices. It does not directly satisfy either stated requirement; those require inspect the class hierarchy and inherited attributes in CI Class Manager. and configure a static attribute-level reconciliation definition that authorizes Discovery above the monitoring source for the serial-number attribute of matched existing server CIs.

D:

This is appropriate for another technical scenario: The operations dashboard should list devices present in Discovery but missing from a second inventory feed. Multisource gap queries identify CIs not reported by one or more participating data sources. It does not directly satisfy either stated requirement; those require inspect the class hierarchy and inherited attributes in CI Class Manager. and configure a static attribute-level reconciliation definition that authorizes Discovery above the monitoring source for the serial-number attribute of matched existing server CIs.

Question 204

A CMDB engineer applied the control: Configure a Recommended-field health rule for the relevant CI class. This was meant to resolve: A team wants server support group to affect completeness but does not want it required by the dictionary. Which result most directly confirms the implementation works?

  1. The selected classes serve the defined use cases and have health acceptance criteria
  2. Empty support groups appear under Recommended without blocking unrelated CI creation
  3. Repeated import cycles preserve the reviewed hardware lifecycle state
  4. Only the truly decommissioned server is retired and the service map points to its replacement

Explanation

Correct Answer

B:

This observation directly validates the implemented control. Recommended completeness assesses configured helpful fields separately from mandatory creation rules. The decisive expected result is: Empty support groups appear under Recommended without blocking unrelated CI creation.

Incorrect Answers

A:

That observation would verify a control associated with: A scoped initial data foundation is easier to govern than an unactionable inventory. It does not establish the needed acceptance outcome. The direct evidence is “Empty support groups appear under Recommended without blocking unrelated CI creation”, testing: Recommended completeness assesses configured helpful fields separately from mandatory creation rules.

C:

This checks a different technical dependency: Repeated import cycles preserve the reviewed hardware lifecycle state. The case requires proof of “Empty support groups appear under Recommended without blocking unrelated CI creation”, which establishes the relevant condition: Recommended completeness assesses configured helpful fields separately from mandatory creation rules.

D:

That observation would verify a control associated with: CI lifecycle changes affect service dependency reporting and should be validated with owners. It does not establish the needed acceptance outcome. The direct evidence is “Empty support groups appear under Recommended without blocking unrelated CI creation”, testing: Recommended completeness assesses configured helpful fields separately from mandatory creation rules.

Question 205

A CMDB change request reports: A sensitive cloud account identifier must be tracked alongside the appropriate business and technical CSDM objects. Select the best implementation. It must pass this acceptance test: A compliance query retrieves the proper owned service and associated identifier.

  1. Create the correctly directed CI relationship with the appropriate relationship type
  2. Fix the source-to-target CI class mapping and verify class eligibility and identifiers
  3. Ingest or construct relationship payloads with resolvable parent and child CIs
  4. Map the regulatory identifier to supported governed attributes or references in the correct model

Explanation

Correct Answer

D:

This is the appropriate control for the stated CI requirement. Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes. Implement: Map the regulatory identifier to supported governed attributes or references in the correct model. Confirm effectiveness by checking: A compliance query retrieves the proper owned service and associated identifier.

Incorrect Answers

A:

Relationship records encode application dependencies beyond the CI attributes themselves. The specific problem here is that compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes.

B:

A correct source mapping is needed before identifier rules can classify incoming device records. The specific problem here is that compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes.

C:

Reliable network maps depend on relationship creation and correctly identified endpoints. The specific problem here is that compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes.

Question 206

Two ServiceNow configuration issues require separate remedies. First: An import succeeds but all devices appear as generic cmdb_ci records rather than servers. Second: A company built direct update scripts to cmdb_ci and upgrades repeatedly break its mapping rules. Select exactly TWO appropriate steps.

  1. Ingest or construct relationship payloads with resolvable parent and child CIs
  2. Replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal
  3. Fix the source-to-target CI class mapping and verify class eligibility and identifiers
  4. Use a supported connector or governed API-based ingestion to populate that CI type
  5. Apply suitable suggested relationship types and governance review for each involved CI class

Explanation

Correct Answers

B:

This satisfies requirement B: Replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal. Supported extension points lower technical debt from direct internal table manipulation. Independently verify: An upgrade test still identifies and updates sample CIs without bypassing IRE.

C:

This satisfies requirement A: Fix the source-to-target CI class mapping and verify class eligibility and identifiers. A correct source mapping is needed before identifier rules can classify incoming device records. Independently verify: Subsequent imports identify the expected server subclasses instead of generic CI entries.

Incorrect Answers

A:

This is appropriate for another technical scenario: Network switches are imported but their upstream connection relationships are missing. Reliable network maps depend on relationship creation and correctly identified endpoints. It does not directly satisfy either stated requirement; those require fix the source-to-target CI class mapping and verify class eligibility and identifiers. and replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal.

D:

This is appropriate for another technical scenario: An enterprise application cannot be discovered by conventional infrastructure scanning but has a supported cloud API inventory. Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs. It does not directly satisfy either stated requirement; those require fix the source-to-target CI class mapping and verify class eligibility and identifiers. and replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal.

E:

This is appropriate for another technical scenario: A team models every CI as Depends on instead of choosing the correct relationship semantics. Relationship types distinguish hosting, containment, and dependencies for impact and service maps. It does not directly satisfy either stated requirement; those require fix the source-to-target CI class mapping and verify class eligibility and identifiers. and replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal.

Question 207

A ServiceNow Data Foundations rollout has two blockers. First: CMDB health completeness is low because most Windows servers are missing a mandatory owned-by field. Second: The system reports probable duplicate storage arrays but no de-duplication task was automatically generated. Which complete two-part implementation addresses both?

  1. (1) Review Required completeness failures and correct the missing mandatory ownership data; (2) create an authorized manual de-duplication task for the verified CI set and review it in the wizard
  2. (1) Review Required completeness failures and correct the missing mandatory ownership data; (2) 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
  3. (1) Schedule a CMDB Data Manager Attestation policy for selected CIs and assign existence-verification tasks to accountable owners; route rejected items to the governed retirement review; (2) 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
  4. (1) Schedule a CMDB Data Manager Attestation policy for selected CIs and assign existence-verification tasks to accountable owners; route rejected items to the governed retirement review; (2) create an authorized manual de-duplication task for the verified CI set and review it in the wizard

Explanation

Correct Answer

A:

Both controls are required. For condition (1), review Required completeness failures and correct the missing mandatory ownership data. Completeness Required measures required-field population for eligible CIs. Verify: Required completeness improves after the sampled Windows servers receive approved owners. For condition (2), create an authorized manual de-duplication task for the verified CI set and review it in the wizard. Manual tasks allow reviewed consolidation when automatic detection does not create a task. Verify independently: A task lists the intended CI identifiers and no unrelated array is included.

Incorrect Answers

B:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: An Orphan correctness score flags CIs missing configured ownership attributes or required relationship types, but operators assume every flagged CI is decommissioned. It should instead use: Create an authorized manual de-duplication task for the verified CI set and review it in the wizard. Both required outcomes must be verified separately.

C:

Part (1) answers a different need: A data owner needs quarterly human confirmation that the servers represented by selected CIs still physically exist, before deciding whether to retire records for missing equipment. It should instead use: Review Required completeness failures and correct the missing mandatory ownership data. Part (2) answers a different need: An Orphan correctness score flags CIs missing configured ownership attributes or required relationship types, but operators assume every flagged CI is decommissioned. It should instead use: Create an authorized manual de-duplication task for the verified CI set and review it in the wizard. Both required outcomes must be verified separately.

D:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: A data owner needs quarterly human confirmation that the servers represented by selected CIs still physically exist, before deciding whether to retire records for missing equipment. It should instead use: Review Required completeness failures and correct the missing mandatory ownership data. Both required outcomes must be verified separately.

Question 208

A CMDB engineer applied the control: Use the Duplicate CI Remediator to choose the main CI and reconcile allowed attributes and relationships. This was meant to resolve: A duplicate server task contains competing IP values and two incident histories. Which result most directly confirms the implementation works?

  1. Manual business records remain while truly stale discoverable infrastructure enters review
  2. The incidents reference the surviving CI and the chosen authoritative IP is retained
  3. A reviewed dry-run selects only explicitly approved retired database test records; production databases that remain active are ineligible
  4. The corrected edge links two valid CIs and no longer appears as orphan

Explanation

Correct Answer

B:

This observation directly validates the implemented control. Guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record. The decisive expected result is: The incidents reference the surviving CI and the chosen authoritative IP is retained.

Incorrect Answers

A:

“Manual business records remain while truly stale discoverable infrastructure enters review” could occur while the stated failure remains unresolved. It tests: Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. The required validation instead is “The incidents reference the surviving CI and the chosen authoritative IP is retained”, because guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record.

C:

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 “The incidents reference the surviving CI and the chosen authoritative IP is retained”, testing: Guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record.

D:

“The corrected edge links two valid CIs and no longer appears as orphan” could occur while the stated failure remains unresolved. It tests: Relationship integrity is separate from a CI having complete attributes. The required validation instead is “The incidents reference the surviving CI and the chosen authoritative IP is retained”, because guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record.

Question 209

During a CMDB review, engineers discover: An operations dashboard lists stale CIs without separating assets in stock from deployed technical equipment. Which proposed action is appropriate if success is measured by: Stock items are not incorrectly represented as deployed servers and true stale CIs are remediated?

  1. Review class scope, asset linkage and deployment lifecycle before mass remediation
  2. Schedule a CMDB Data Manager Attestation policy for selected CIs and assign existence-verification tasks to accountable owners; route rejected items to the governed retirement review
  3. Remediate existing duplicate records separately and test the revised IRE rule for future ingests
  4. Configure an active retirement definition for the laptop CI class, publish an Archive policy scoped to already retired eligible records, and use the approved archival retention criteria

Explanation

Correct Answer

A:

This is the appropriate control for the stated CI requirement. A stocked asset can exist financially without a currently operating CI for production impact. Implement: Review class scope, asset linkage and deployment lifecycle before mass remediation. Confirm effectiveness by checking: Stock items are not incorrectly represented as deployed servers and true stale CIs are remediated.

Incorrect Answers

B:

Attestation is a human confirmation of the represented real infrastructure or application, not equivalent to automatic correctness of every attribute or to a Certification policy for a specified field. The specific problem here is that a stocked asset can exist financially without a currently operating CI for production impact.

C:

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

D:

ServiceNow Data Manager Archive policies require an active class retirement definition and apply only to records already considered retired; archiving moves CIs out of active views for temporary retention rather than immediately deleting them. The specific problem here is that a stocked asset can exist financially without a currently operating CI for production impact.

Question 210

A team configured: Use guided de-duplication or an approved remediation workflow to reconcile references before deletion. Its original requirement was: An administrator deletes a duplicate CI record directly and loses change relationships attached to it. Which observation proves that the desired operational outcome was achieved?

  1. Empty support groups appear under Recommended without blocking unrelated CI creation
  2. An approved renaming request includes owner signoff and traceable changes
  3. A seeded CI missing the configured relationship is flagged; a legitimate active CI is repaired or appropriately excluded instead of bulk-deleted
  4. Related change and incident records reference the retained main CI

Explanation

Correct Answer

D:

This observation directly validates the implemented control. Direct record deletion can leave broken or incomplete related records. The decisive expected result is: Related change and incident records reference the retained main CI.

Incorrect Answers

A:

That observation would verify a control associated with: Recommended completeness assesses configured helpful fields separately from mandatory creation rules. It does not establish the needed acceptance outcome. The direct evidence is “Related change and incident records reference the retained main CI”, testing: Direct record deletion can leave broken or incomplete related records.

B:

“An approved renaming request includes owner signoff and traceable changes” could occur while the stated failure remains unresolved. It tests: Stewardship prevents uncoordinated changes to shared business context. The required validation instead is “Related change and incident records reference the retained main CI”, because direct record deletion can leave broken or incomplete related records.

C:

This checks a different technical dependency: 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 case requires proof of “Related change and incident records reference the retained main CI”, which establishes the relevant condition: Direct record deletion can leave broken or incomplete related records.

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