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 25

Question 240

A ServiceNow configuration project has two acceptance conditions. The first issue is: The operations team cannot see where Database Server inherits its mandatory CI fields. The second is: An administrator changes reconciliation priorities but assumes old CMDB values will instantly reflect the new rules. Which paired approach is suitable?

  1. (1) Inspect the class hierarchy and inherited attributes in CI Class Manager; (2) use preview or recompute where supported and verify the result against source history
  2. (1) Use an appropriate CMDB 360 saved query such as Find Gap comparing the two discovery sources; (2) add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition
  3. (1) Use an appropriate CMDB 360 saved query such as Find Gap comparing the two discovery sources; (2) use preview or recompute where supported and verify the result against source history
  4. (1) Inspect the class hierarchy and inherited attributes in CI Class Manager; (2) add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition

Explanation

Correct Answer

A:

Both controls are required. For condition (1), 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. Verify: The administrator identifies which parent supplies each required field before making a change. For condition (2), use preview or recompute where supported and verify the result against source history. Reconciliation rule changes can require reevaluation of existing attribute choices. Verify independently: The selected CI value changes only as justified by configured source data and the tested recomputation.

Incorrect Answers

B:

Part (1) answers a different need: The operations dashboard should list devices present in Discovery but missing from a second inventory feed. It should instead use: Inspect the class hierarchy and inherited attributes in CI Class Manager. Part (2) answers a different need: A child CI class requires a new application build field but sibling classes must remain unaffected. It should instead use: Use preview or recompute where supported and verify the result against source history. Both required outcomes must be verified separately.

C:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: The operations dashboard should list devices present in Discovery but missing from a second inventory feed. It should instead use: Inspect the class hierarchy and inherited attributes in CI Class Manager. Both required outcomes must be verified separately.

D:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: A child CI class requires a new application build field but sibling classes must remain unaffected. It should instead use: Use preview or recompute where supported and verify the result against source history. Both required outcomes must be verified separately.

Question 241

A CMDB administrator must resolve both independent failures: (1) A compliance tile shows no results despite multiple mandatory fields being filled. (2) A duplicate server task contains competing IP values and two incident histories. Which coordinated plan satisfies both requirements?

  1. (1) Remediate existing duplicate records separately and test the revised IRE rule for future ingests; (2) use the Duplicate CI Remediator to choose the main CI and reconcile allowed attributes and relationships
  2. (1) Remediate existing duplicate records separately and test the revised IRE rule for future ingests; (2) review class scope, asset linkage and deployment lifecycle before mass remediation
  3. (1) Activate and execute a relevant CMDB compliance audit with the approved expected-value template or script, and ensure the latest completed audit run is recorded before evaluating the score; (2) use the Duplicate CI Remediator to choose the main CI and reconcile allowed attributes and relationships
  4. (1) Activate and execute a relevant CMDB compliance audit with the approved expected-value template or script, and ensure the latest completed audit run is recorded before evaluating the score; (2) review class scope, asset linkage and deployment lifecycle before mass remediation

Explanation

Correct Answer

C:

Both controls are required. For condition (1), activate and execute a relevant CMDB compliance audit with the approved expected-value template or script, and ensure the latest completed audit run is recorded before evaluating the score. Completeness of mandatory fields is separate from compliance; CMDB compliance KPIs use actual recent completed audit evidence, and scripted audits require their Last run date to be recorded. Verify: A completed compliance audit reports seeded passing and failing CI conditions with a valid latest-run timestamp rather than treating an empty tile as passing. For condition (2), use the Duplicate CI Remediator to choose the main CI and reconcile allowed attributes and relationships. Guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record. Verify independently: The incidents reference the surviving CI and the chosen authoritative IP is retained.

Incorrect Answers

A:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: A duplicate task was created before an identification rule was fixed, and the team assumes fixing the rule auto-merges historical records. It should instead use: Activate and execute a relevant CMDB compliance audit with the approved expected-value template or script, and ensure the latest completed audit run is recorded before evaluating the score. Both required outcomes must be verified separately.

B:

Part (1) answers a different need: A duplicate task was created before an identification rule was fixed, and the team assumes fixing the rule auto-merges historical records. It should instead use: Activate and execute a relevant CMDB compliance audit with the approved expected-value template or script, and ensure the latest completed audit run is recorded before evaluating the score. Part (2) answers a different need: An operations dashboard lists stale CIs without separating assets in stock from deployed technical equipment. It should instead use: Use the Duplicate CI Remediator to choose the main CI and reconcile allowed attributes and relationships. Both required outcomes must be verified separately.

D:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: An operations dashboard lists stale CIs without separating assets in stock from deployed technical equipment. It should instead use: Use the Duplicate CI Remediator to choose the main CI and reconcile allowed attributes and relationships. Both required outcomes must be verified separately.

Question 242

After implementing the approved change — Verify compliance activation, audit definition and last completed run before treating a blank CMDB Health compliance indicator as meaningful — the data steward needs proof that it fixed: A dashboard shows empty compliance results after no audit has run. What should the steward observe?

  1. The report lists matching discovered servers while excluding other sources
  2. The target data-center servers are returned and unrelated servers are excluded
  3. The saved query returns all matching application, database and Linux server paths
  4. The tile shows expected passing and failing sample results after a valid completed audit with a recorded run date

Explanation

Correct Answer

D:

This observation directly validates the implemented control. 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 decisive expected result is: The tile shows expected passing and failing sample results after a valid completed audit with a recorded run date.

Incorrect Answers

A:

This checks a different technical dependency: Multisource records queries enable source-specific inventory reporting. The case requires proof of “The tile shows expected passing and failing sample results after a valid completed audit with a recorded run date”, which establishes the relevant condition: 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.

B:

That observation would verify a control associated with: The target data-center servers are returned and unrelated servers are excluded. It does not establish the needed acceptance outcome. The direct evidence is “The tile shows expected passing and failing sample results after a valid completed audit with a recorded run date”, testing: 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.

C:

“The saved query returns all matching application, database and Linux server paths” could occur while the stated failure remains unresolved. It tests: A relationship-aware query traverses edges rather than filtering only a flat CI list. The required validation instead is “The tile shows expected passing and failing sample results after a valid completed audit with a recorded run date”, because 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.

Question 243

A CMDB engineer applied the control: Enable and validate CMDB 360, then define a supported dynamic reconciliation rule for that specific attribute and explicitly choose its most-reported or other supported selection method. This was meant to resolve: An attribute priority based solely on source ordering gives a poor result when most sources agree on another value. Which result most directly confirms the implementation works?

  1. Incoming identical network-device payloads resolve to one correctly typed CI
  2. Linux-specific reports include migrated server CIs without mixing desktop computers
  3. A controlled payload with conflicting values produces the expected selected attribute under the chosen dynamic rule, including a documented tie case
  4. A new allowed CI is inserted once, then only an authorized update source changes protected attributes on the matched CI

Explanation

Correct Answer

C:

This observation directly validates the implemented control. 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 decisive expected result is: A controlled payload with conflicting values produces the expected selected attribute under the chosen dynamic rule, including a documented tie case.

Incorrect Answers

A:

That observation would verify a control associated with: More specialized CI class rules can be chosen to identify specific subclasses accurately. It does not establish the needed acceptance outcome. The direct evidence is “A controlled payload with conflicting values produces the expected selected attribute under the chosen dynamic rule, including a documented tie case”, testing: 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.

B:

“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 “A controlled payload with conflicting values produces the expected selected attribute under the chosen dynamic rule, including a documented tie case”, because 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.

D:

That observation would verify a control associated with: IRE identification decides new versus existing CIs; standard reconciliation rules apply to updates of matched CIs, not identically to the first insertion of a new CI. It does not establish the needed acceptance outcome. The direct evidence is “A controlled payload with conflicting values produces the expected selected attribute under the chosen dynamic rule, including a documented tie case”, testing: 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.

Question 244

After implementing the approved change — Use a properly credentialed Discovery schedule covering the intended address ranges — the data steward needs proof that it fixed: A branch network has thousands of reachable devices whose hardware properties change daily. What should the steward observe?

  1. A scheduled run updates the known network devices and discovers a seeded new host
  2. The imported switch has the expected parent-child relationship rather than an orphan link
  3. Subsequent imports identify the expected server subclasses instead of generic CI entries
  4. Financial tracking and service impact reports use the appropriate connected records without treating all CIs as physical assets

Explanation

Correct Answer

A:

This observation directly validates the implemented control. Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance. The decisive expected result is: A scheduled run updates the known network devices and discovers a seeded new host.

Incorrect Answers

B:

“The imported switch has the expected parent-child relationship rather than an orphan link” can be suitable where the imported switch has the expected parent-child relationship rather than an orphan link. It does not resolve this question’s narrower failure, which follows: Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance. The relevant action is “A scheduled run updates the known network devices and discovers a seeded new host”.

C:

The offered action, “Subsequent imports identify the expected server subclasses instead of generic CI entries”, addresses a different dependency: Subsequent imports identify the expected server subclasses instead of generic CI entries. The failure reported here instead follows: Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance. The targeted response is “A scheduled run updates the known network devices and discovers a seeded new host”.

D:

The alternative focuses on the technical control described by: Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. The present requirement is governed by: Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance. Apply “A scheduled run updates the known network devices and discovers a seeded new host” to address that particular cause.

Question 245

A data governance release must meet both conditions: A: Two sources insert separate server CIs because hostname alone is not a stable unique key. B: An administrator changes reconciliation priorities but assumes old CMDB values will instantly reflect the new rules. Select the TWO necessary actions.

  1. Use preview or recompute where supported and verify the result against source history
  2. Configure a class-specific recommended field through CI Class Manager health settings
  3. Review CMDB 360 potential issues for CIs not recently reported by configured sources
  4. 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
  5. Use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value

Explanation

Correct Answers

A:

This satisfies requirement B: Use preview or recompute where supported and verify the result against source history. Reconciliation rule changes can require reevaluation of existing attribute choices. Independently verify: The selected CI value changes only as justified by configured source data and the tested recomputation.

D:

This satisfies requirement A: 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. Independently verify: Two independently sourced payloads for one verified server select the same CI, while a distinct server remains a separate CI.

Incorrect Answers

B:

This is appropriate for another technical scenario: The governance team needs a recommended support group field for one class without making it universally mandatory. Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. It does not directly satisfy either stated requirement; those require 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. and use preview or recompute where supported and verify the result against source history.

C:

This is appropriate for another technical scenario: A source stopped reporting network devices three weeks ago even though their CIs still exist. Per-source reporting timestamps help detect coverage gaps even when a CI has historical data. It does not directly satisfy either stated requirement; those require 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. and use preview or recompute where supported and verify the result against source history.

E:

This is appropriate for another technical scenario: Cloud inventory and Discovery report different operating system versions for the same CI. CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. It does not directly satisfy either stated requirement; those require 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. and use preview or recompute where supported and verify the result against source history.

Question 246

A data steward is asked to resolve: A relationship health report contains edges with missing parent CI references. Which solution meets the requirement and verifies: The corrected edge links two valid CIs and no longer appears as orphan?

  1. Configure required or recommended class fields and a scheduled quality backlog
  2. Configure the supported dependent-CI approval and lifecycle handling path
  3. Check glide.duplicate_ci_remediator.max.cis (default 1000, never above 5000) and the wizard limited-remediation behavior for larger duplicate sets, then plan an approved staged or alternate remediation
  4. Investigate and repair orphan relationships in the relationship health results

Explanation

Correct Answer

D:

This is the appropriate control for the stated CI requirement. Relationship integrity is separate from a CI having complete attributes. Implement: Investigate and repair orphan relationships in the relationship health results. Confirm effectiveness by checking: The corrected edge links two valid CIs and no longer appears as orphan.

Incorrect Answers

A:

Principal class focus enables targeted data foundation completeness work. The specific problem here is that relationship integrity is separate from a CI having complete attributes.

B:

Lifecycle cascades should not silently remove dependent records without approved controls. The specific problem here is that relationship integrity is separate from a CI having complete attributes.

C:

When a de-duplication task exceeds its configured threshold the wizard restricts main-CI selection and does not reconcile conflicting attributes or relationships; raising the setting above 5000 cannot restore those functions. The specific problem here is that relationship integrity is separate from a CI having complete attributes.

Question 247

A ServiceNow implementation team encounters this issue: A portfolio manager wants an overall view spanning strategy, delivery and consumer-facing services. Which control most directly resolves the issue and produces this outcome: Portfolio review traces a service from planning through delivery to consumption?

  1. Use the CSDM Manage Portfolio cross-domain view and governed lifecycle linkages
  2. Keep the design-level Business Application in Design and Planning and explicitly relate it to its operational Service Instance/Application Service in Service Delivery
  3. Record customer-visible service commitments and support hours on the appropriate Business Service Offering in Service Consumption rather than a server CI
  4. Establish stable service records and correct CSDM links instead of copying separate spreadsheet services

Explanation

Correct Answer

A:

This is the appropriate control for the stated CI requirement. Portfolio governance spans CSDM domains rather than duplicating their objects. Implement: Use the CSDM Manage Portfolio cross-domain view and governed lifecycle linkages. Confirm effectiveness by checking: Portfolio review traces a service from planning through delivery to consumption.

Incorrect Answers

B:

A Business Application is an application portfolio object spanning environments, whereas a Service Instance represents a specific deployed runtime stack and may contain multiple underlying applications. The specific problem here is that portfolio governance spans CSDM domains rather than duplicating their objects.

C:

A Business Service Offering expresses the consumer commitment for a business service; infrastructure server attributes are operational configuration, not a customer-facing SLA catalog contract. The specific problem here is that portfolio governance spans CSDM domains rather than duplicating their objects.

D:

Shared CSDM objects reduce semantic drift across workflows and reporting. The specific problem here is that portfolio governance spans CSDM domains rather than duplicating their objects.

Question 248

A ServiceNow configuration project has two acceptance conditions. The first issue is: An incident assignment group is missing on many production database CIs. The second is: A governance team proposes deleting every CI not seen by a discovery scan even when some are manually maintained contracts. Which paired approach is suitable?

  1. (1) Review the de-duplication task and choose the valid main CI with its associated evidence; (2) separate discoverable and non-discoverable populations with suitable policies and review gates
  2. (1) Review the de-duplication task and choose the valid main CI with its associated evidence; (2) review Required completeness failures and correct the missing mandatory ownership data
  3. (1) Assign an authoritative support group or enrich it from governed relationships; (2) separate discoverable and non-discoverable populations with suitable policies and review gates
  4. (1) Assign an authoritative support group or enrich it from governed relationships; (2) review Required completeness failures and correct the missing mandatory ownership data

Explanation

Correct Answer

C:

Both controls are required. For condition (1), assign an authoritative support group or enrich it from governed relationships. Reliable CI ownership fields enable routing and operational accountability. Verify: A test incident is directed to the intended database support group. For condition (2), separate discoverable and non-discoverable populations with suitable policies and review gates. Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. Verify independently: Manual business records remain while truly stale discoverable infrastructure enters review.

Incorrect Answers

A:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: An IRE job detects two CIs representing the same router and creates a duplicate remediation task. It should instead use: Assign an authoritative support group or enrich it from governed relationships. Both required outcomes must be verified separately.

B:

Part (1) answers a different need: An IRE job detects two CIs representing the same router and creates a duplicate remediation task. It should instead use: Assign an authoritative support group or enrich it from governed relationships. Part (2) answers a different need: CMDB health completeness is low because most Windows servers are missing a mandatory owned-by field. It should instead use: Separate discoverable and non-discoverable populations with suitable policies and review gates. Both required outcomes must be verified separately.

D:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: CMDB health completeness is low because most Windows servers are missing a mandatory owned-by field. It should instead use: Separate discoverable and non-discoverable populations with suitable policies and review gates. Both required outcomes must be verified separately.

Question 249

A CMDB program needs two changes. Requirement A: A new dependent CI class fails identification because its hosting relationship is unavailable in the payload. Requirement B: A cloud infrastructure vendor has a supported Service Graph Connector and the team is considering a bespoke CMDB REST importer. Select exactly TWO actions that jointly satisfy the requirements.

  1. Model procurement assets and operational CIs separately and link them where the model category supports it
  2. Fix the source-to-target CI class mapping and verify class eligibility and identifiers
  3. Use IntegrationHub ETL with documented transformation mappings and supported IRE integration
  4. Configure supported dependent identification or hosting relationship rules and supply the required parent reference
  5. Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path

Explanation

Correct Answers

D:

This satisfies requirement A: Configure supported dependent identification or hosting relationship rules and supply the required parent reference. Dependent identification may rely on relationships to identify CIs within a parent context. Independently verify: The dependent CI matches its existing record when the required parent relationship is supplied.

E:

This satisfies requirement B: Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path. Supported connectors reduce custom upgrade debt and integrate source identification. Independently verify: The vendor inventory loads with mapped CI classes and no duplicate source identities.

Incorrect Answers

A:

This is appropriate for another technical scenario: A software CI exists for an application but a procurement team assumes it represents the same thing as a purchased physical asset. Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. It does not directly satisfy either stated requirement; those require configure supported dependent identification or hosting relationship rules and supply the required parent reference. and prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path.

B:

This is appropriate for another technical scenario: An import succeeds but all devices appear as generic cmdb_ci records rather than servers. A correct source mapping is needed before identifier rules can classify incoming device records. It does not directly satisfy either stated requirement; those require configure supported dependent identification or hosting relationship rules and supply the required parent reference. and prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path.

C:

This is appropriate for another technical scenario: One source API has nested device properties requiring repeatable transformations into several CMDB classes. A governed ETL pipeline maps source schemas to class attributes and relationships. It does not directly satisfy either stated requirement; those require configure supported dependent identification or hosting relationship rules and supply the required parent reference. and prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path.

Question 250

A CMDB change request reports: A CMDB manager wants to distinguish correctness, completeness and compliance in a monthly report. Select the best implementation. It must pass this acceptance test: The monthly scorecard attributes changes to individual CI submetrics and distinct relationship-health failures rather than hiding both in a single blended score.

  1. Define a service owner approval and change-control process for governed naming updates
  2. Report Completeness Required/Recommended, Correctness Duplicate/Staleness/Orphan, Compliance completed-audit results, and separate relationship-health indicators by relevant class
  3. Validate eligibility and publish the Data Manager policy instead of assuming drafts run
  4. Align lifecycle attribute source authority and the asset-CI status mapping

Explanation

Correct Answer

B:

This is the appropriate control for the stated CI requirement. 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. Implement: Report Completeness Required/Recommended, Correctness Duplicate/Staleness/Orphan, Compliance completed-audit results, and separate relationship-health indicators by relevant class. Confirm effectiveness by checking: The monthly scorecard attributes changes to individual CI submetrics and distinct relationship-health failures rather than hiding both in a single blended score.

Incorrect Answers

A:

Stewardship prevents uncoordinated changes to shared business context. The specific problem here is that 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.

C:

Published policies, not simply saved drafts, are processed by the applicable scheduled framework. The specific problem here is that 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.

D:

Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates. The specific problem here is that 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.

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