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 15

Question 140

A CMDB change request reports: An update payload identifies an existing CI but an administrator expects reconciliation rules to apply to first-time inserts identically. Select the best implementation. It must pass this acceptance test: A new allowed CI is inserted once, then only an authorized update source changes protected attributes on the matched CI.

  1. Use preview or recompute where supported and verify the result against source history
  2. Test first-time insertion and later matched updates separately: allow identification and IRE data-source rules to decide inserts, and use reconciliation authorization for existing-CI attribute updates
  3. Add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition
  4. Configure a class-specific recommended field through CI Class Manager health settings

Explanation

Correct Answer

B:

This is the appropriate control for the stated CI requirement. 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. Implement: Test first-time insertion and later matched updates separately: allow identification and IRE data-source rules to decide inserts, and use reconciliation authorization for existing-CI attribute updates. Confirm effectiveness by checking: A new allowed CI is inserted once, then only an authorized update source changes protected attributes on the matched CI.

Incorrect Answers

A:

Reconciliation rule changes can require reevaluation of existing attribute choices. The specific problem here is that 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.

C:

Child-level attributes scope specialized fields to the correct extension class. The specific problem here is that 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.

D:

Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. The specific problem here is that 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.

Question 141

Two ServiceNow configuration issues require separate remedies. First: A compliance tile shows no results despite multiple mandatory fields being filled. Second: An incident assignment group is missing on many production database CIs. Select exactly TWO appropriate steps.

  1. Verify an active retirement definition and preview the published-policy eligibility, requiring already retired class-matched CIs and explicit approval before any Delete execution
  2. 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
  3. Remediate existing duplicate records separately and test the revised IRE rule for future ingests
  4. Assign an authoritative support group or enrich it from governed relationships
  5. Review the service impact and relationship dependencies before retiring or archiving its CI

Explanation

Correct Answers

B:

This satisfies requirement A: 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. Independently 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.

D:

This satisfies requirement B: Assign an authoritative support group or enrich it from governed relationships. Reliable CI ownership fields enable routing and operational accountability. Independently verify: A test incident is directed to the intended database support group.

Incorrect Answers

A:

This is appropriate for another technical scenario: A broadly drafted Data Manager Delete policy appears to include active production databases before its eligibility and retirement rules have been verified. 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 directly satisfy either stated requirement; those require 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. and assign an authoritative support group or enrich it from governed relationships.

C:

This is appropriate for another technical scenario: A duplicate task was created before an identification rule was fixed, and the team assumes fixing the rule auto-merges historical records. Improved identification prevents future collisions but does not retroactively merge every old duplicate. It does not directly satisfy either stated requirement; those require 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. and assign an authoritative support group or enrich it from governed relationships.

E:

This is appropriate for another technical scenario: A retired application server is still linked as actively hosting an important service. CI lifecycle changes affect service dependency reporting and should be validated with owners. It does not directly satisfy either stated requirement; those require 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. and assign an authoritative support group or enrich it from governed relationships.

Question 142

Two ServiceNow configuration issues require separate remedies. First: An external connector imports duplicate rows for a host across multiple scheduled runs. Second: Finance changes asset acquisition cost and expects manual reversal from the CI to rewrite the purchase ledger. Select exactly TWO appropriate steps.

  1. Use a controlled manual CI maintenance process with steward ownership, required fields, and review dates
  2. Replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal
  3. Configure the appropriate Asset State to CI Hardware Status mapping and permitted sync direction
  4. 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
  5. Validate IRE identification configuration and stable native source IDs before increasing dedupe scripts

Explanation

Correct Answers

D:

This satisfies requirement B: 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. 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. Independently verify: Changing asset Cost updates the linked CI cost display; editing the CI cost does not change the authoritative asset Cost.

E:

This satisfies requirement A: Validate IRE identification configuration and stable native source IDs before increasing dedupe scripts. Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. Independently verify: Two imports of an identical host leave one CI with updated source data.

Incorrect Answers

A:

This is appropriate for another technical scenario: A manual SaaS license dependency has no discovery agent and needs occasional verified updates. Non-discoverable configuration data still needs controlled creation and periodic validation. It does not directly satisfy either stated requirement; those require validate IRE identification configuration and stable native source IDs before increasing dedupe scripts. and 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.

B:

This is appropriate for another technical scenario: A company built direct update scripts to cmdb_ci and upgrades repeatedly break its mapping rules. Supported extension points lower technical debt from direct internal table manipulation. It does not directly satisfy either stated requirement; those require validate IRE identification configuration and stable native source IDs before increasing dedupe scripts. and 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.

C:

This is appropriate for another technical scenario: A hardware asset moves to pending disposal but its technical CI still reports the old hardware status. Hardware status mapping reflects asset lifecycle without treating unrelated CI fields as interchangeable. It does not directly satisfy either stated requirement; those require validate IRE identification configuration and stable native source IDs before increasing dedupe scripts. and 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.

Question 143

A team configured: Configure the appropriate suggested relationships for the class in CI Class Manager. Its original requirement was: A new service CI class needs suggested parent-child relationship types visible to its modelers. Which observation proves that the desired operational outcome was achieved?

  1. The relationship editor proposes the intended type for a compatible parent-child pair
  2. A new allowed CI is inserted once, then only an authorized update source changes protected attributes on the matched CI
  3. Incoming identical network-device payloads resolve to one correctly typed CI
  4. The ingest uses identification rules and does not insert another copy of a known CI

Explanation

Correct Answer

A:

This observation directly validates the implemented control. Suggested relationships guide consistent relationship selection without making every pairing physically true. The decisive expected result is: The relationship editor proposes the intended type for a compatible parent-child pair.

Incorrect Answers

B:

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 “The relationship editor proposes the intended type for a compatible parent-child pair”, testing: Suggested relationships guide consistent relationship selection without making every pairing physically true.

C:

“Incoming identical network-device payloads resolve to one correctly typed CI” could occur while the stated failure remains unresolved. It tests: More specialized CI class rules can be chosen to identify specific subclasses accurately. The required validation instead is “The relationship editor proposes the intended type for a compatible parent-child pair”, because suggested relationships guide consistent relationship selection without making every pairing physically true.

D:

This checks a different technical dependency: The ingest uses identification rules and does not insert another copy of a known CI. The case requires proof of “The relationship editor proposes the intended type for a compatible parent-child pair”, which establishes the relevant condition: Suggested relationships guide consistent relationship selection without making every pairing physically true.

Question 144

An organization finds this data-foundation problem: A trusted import is allowed to update existing storage CIs but must not create new storage CIs. Which approach best achieves the required outcome: With the intended supported IRE mode, an unmatched storage CI insert is rejected while an identified existing CI receives an authorized update?

  1. Use an appropriate CMDB 360 saved query such as Find Gap comparing the two discovery sources
  2. Review CMDB 360 potential issues for CIs not recently reported by configured sources
  3. 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
  4. Use CI Class Manager to classify the records under an appropriate derived Linux Server class and its class-specific attributes

Explanation

Correct Answer

C:

This is the appropriate control for the stated CI requirement. 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. Implement: 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. Confirm effectiveness by checking: 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:

Multisource gap queries identify CIs not reported by one or more participating data sources. The specific problem here is that 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.

B:

Per-source reporting timestamps help detect coverage gaps even when a CI has historical data. The specific problem here is that 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.

D:

A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type. The specific problem here is that 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.

Question 145

A team configured: Configure and test the distinct asset/CI status mapping appropriate to the hardware class. Its original requirement was: A team assumes changing CI Install Status automatically updates Hardware Status for the same computer. Which observation proves that the desired operational outcome was achieved?

  1. The imported switch has the expected parent-child relationship rather than an orphan link
  2. A status change affects only the mapped field and not an unrelated status field
  3. Dependency traversal follows the intended application-to-database path
  4. All staged edges resolve to existing CIs after both ingestion batches complete

Explanation

Correct Answer

B:

This observation directly validates the implemented control. Install Status and Hardware Status are independent fields rather than automatic mirrors of each other. The decisive expected result is: A status change affects only the mapped field and not an unrelated status field.

Incorrect Answers

A:

“The imported switch has the expected parent-child relationship rather than an orphan link” could occur while the stated failure remains unresolved. It tests: The imported switch has the expected parent-child relationship rather than an orphan link. The required validation instead is “A status change affects only the mapped field and not an unrelated status field”, because install Status and Hardware Status are independent fields rather than automatic mirrors of each other.

C:

That observation would verify a control associated with: Relationship direction matters for accurate dependency traversals and service modeling. It does not establish the needed acceptance outcome. The direct evidence is “A status change affects only the mapped field and not an unrelated status field”, testing: Install Status and Hardware Status are independent fields rather than automatic mirrors of each other.

D:

“All staged edges resolve to existing CIs after both ingestion batches complete” could occur while the stated failure remains unresolved. It tests: Processing order and endpoint matching prevent dangling or mismatched relationship references. The required validation instead is “A status change affects only the mapped field and not an unrelated status field”, because install Status and Hardware Status are independent fields rather than automatic mirrors of each other.

Question 146

An organization finds this data-foundation problem: A company built direct update scripts to cmdb_ci and upgrades repeatedly break its mapping rules. Which approach best achieves the required outcome: An upgrade test still identifies and updates sample CIs without bypassing IRE?

  1. Apply reconciliation source priority and valid identification as the new data source is onboarded
  2. Replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal
  3. Validate IRE identification configuration and stable native source IDs before increasing dedupe scripts
  4. Apply suitable suggested relationship types and governance review for each involved CI class

Explanation

Correct Answer

B:

This is the appropriate control for the stated CI requirement. Supported extension points lower technical debt from direct internal table manipulation. Implement: Replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal. Confirm effectiveness by checking: An upgrade test still identifies and updates sample CIs without bypassing IRE.

Incorrect Answers

A:

Additional ingestion sources should not overwrite unrelated authoritative CI attributes. The specific problem here is that supported extension points lower technical debt from direct internal table manipulation.

C:

Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. The specific problem here is that supported extension points lower technical debt from direct internal table manipulation.

D:

Relationship types distinguish hosting, containment, and dependencies for impact and service maps. The specific problem here is that supported extension points lower technical debt from direct internal table manipulation.

Question 147

The change record states that the team will: Validate IRE identification configuration and stable native source IDs before increasing dedupe scripts. The original defect was: An external connector imports duplicate rows for a host across multiple scheduled runs. Which validation finding should be accepted?

  1. The imported switch has the expected parent-child relationship rather than an orphan link
  2. The associated hardware CI reflects the approved disposition after the asset state changes
  3. Two imports of an identical host leave one CI with updated source data
  4. All staged edges resolve to existing CIs after both ingestion batches complete

Explanation

Correct Answer

C:

This observation directly validates the implemented control. Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. The decisive expected result is: Two imports of an identical host leave one CI with updated source data.

Incorrect Answers

A:

That observation would verify a control associated with: The imported switch has the expected parent-child relationship rather than an orphan link. It does not establish the needed acceptance outcome. The direct evidence is “Two imports of an identical host leave one CI with updated source data”, testing: Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle.

B:

“The associated hardware CI reflects the approved disposition after the asset state changes” could occur while the stated failure remains unresolved. It tests: The decisive expected result is: The associated hardware CI reflects the approved disposition after the asset state changes. The required validation instead is “Two imports of an identical host leave one CI with updated source data”, because repeatable ingestion must identify the existing CI rather than creating a new object on every cycle.

D:

That observation would verify a control associated with: Processing order and endpoint matching prevent dangling or mismatched relationship references. It does not establish the needed acceptance outcome. The direct evidence is “Two imports of an identical host leave one CI with updated source data”, testing: Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle.

Question 148

The change record states that the team will: Use an appropriate certification or attestation control requiring explicit confirmation of that value. The original defect was: A CMDB steward wants to certify a critical CI's business owner field rather than merely mark it updated recently. Which validation finding should be accepted?

  1. A lower-priority feed cannot overwrite the reviewed authoritative attribute
  2. 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
  3. A reviewed dry-run selects only explicitly approved retired database test records; production databases that remain active are ineligible
  4. The responsible person signs off on the current owner value with dated evidence

Explanation

Correct Answer

D:

This observation directly validates the implemented control. Fresh timestamps do not prove that a human has validated business ownership. The decisive expected result is: The responsible person signs off on the current owner value with dated evidence.

Incorrect Answers

A:

“A lower-priority feed cannot overwrite the reviewed authoritative attribute” could occur while the stated failure remains unresolved. It tests: A lower-priority feed cannot overwrite the reviewed authoritative attribute. The required validation instead is “The responsible person signs off on the current owner value with dated evidence”, because fresh timestamps do not prove that a human has validated business ownership.

B:

This checks a different technical dependency: 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. The case requires proof of “The responsible person signs off on the current owner value with dated evidence”, which establishes the relevant condition: Fresh timestamps do not prove that a human has validated business ownership.

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 responsible person signs off on the current owner value with dated evidence”, testing: Fresh timestamps do not prove that a human has validated business ownership.

Question 149

An organization finds this data-foundation problem: A company wants retired laptop CIs automatically archived after the approved retention interval. Which approach best achieves the required outcome: An eligible retired laptop CI is archived and restorable for the retention period; an in-use laptop CI is not archived by the policy?

  1. Review class scope, asset linkage and deployment lifecycle before mass remediation
  2. Assign class and data-steward ownership with escalation and recurring quality reviews
  3. Define baseline health metrics and scheduled KPIs with owners and achievable thresholds
  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

D:

This is the appropriate control for the stated CI requirement. 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. Implement: 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. Confirm effectiveness by checking: An eligible retired laptop CI is archived and restorable for the retention period; an in-use laptop CI is not archived by the policy.

Incorrect Answers

A:

A stocked asset can exist financially without a currently operating CI for production impact. The specific problem here is that 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.

B:

Governance requires clear decision rights and accountable remediation owners. The specific problem here is that 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.

C:

Continuous KPI governance detects regressions after point-in-time remediation. The specific problem here is that 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.

Question 150

A CMDB engineer applied the control: Configure required or recommended class fields and a scheduled quality backlog. This was meant to resolve: A new principal CI class is selected for governance but its key ownership fields are unpopulated. Which result most directly confirms the implementation works?

  1. Principal class scorecards reflect the corrected ownership information
  2. The published eligible policy appears in the execution history at the next schedule
  3. The selected classes serve the defined use cases and have health acceptance criteria
  4. An oversized task is handled without pretending it supports normal field/relationship merging, and any split or alternate process has an auditable main-CI outcome

Explanation

Correct Answer

A:

This observation directly validates the implemented control. Principal class focus enables targeted data foundation completeness work. The decisive expected result is: Principal class scorecards reflect the corrected ownership information.

Incorrect Answers

B:

“The published eligible policy appears in the execution history at the next schedule” could occur while the stated failure remains unresolved. It tests: Published policies, not simply saved drafts, are processed by the applicable scheduled framework. The required validation instead is “Principal class scorecards reflect the corrected ownership information”, because principal class focus enables targeted data foundation completeness work.

C:

This checks a different technical dependency: A scoped initial data foundation is easier to govern than an unactionable inventory. The case requires proof of “Principal class scorecards reflect the corrected ownership information”, which establishes the relevant condition: Principal class focus enables targeted data foundation completeness work.

D:

That observation would verify a control associated with: 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. It does not establish the needed acceptance outcome. The direct evidence is “Principal class scorecards reflect the corrected ownership information”, testing: Principal class focus enables targeted data foundation completeness work.

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