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 39

Question 380

The change record states that the team will: Model the required alternative relationship branches correctly in the query canvas. The original defect was: An analyst needs to compare the CI population connected to either Linux or Windows hosts in one graph. Which validation finding should be accepted?

  1. The report lists matching discovered servers while excluding other sources
  2. Both valid host types appear and unrelated CI pairs do not
  3. The test database change lists its genuinely dependent services for review
  4. The stopped feed appears in the issue list while current feeds remain healthy

Explanation

Correct Answer

B:

This observation directly validates the implemented control. Graph query logic must represent OR alternatives rather than forcing both branches simultaneously. The decisive expected result is: Both valid host types appear and unrelated CI pairs do not.

Incorrect Answers

A:

This checks a different technical dependency: Multisource records queries enable source-specific inventory reporting. The case requires proof of “Both valid host types appear and unrelated CI pairs do not”, which establishes the relevant condition: Graph query logic must represent OR alternatives rather than forcing both branches simultaneously.

C:

“The test database change lists its genuinely dependent services for review” could occur while the stated failure remains unresolved. It tests: Linked CI dependencies reveal potential blast radius before infrastructure changes. The required validation instead is “Both valid host types appear and unrelated CI pairs do not”, because graph query logic must represent OR alternatives rather than forcing both branches simultaneously.

D:

This checks a different technical dependency: Missing recent source activity can signal integration failure even when other feeds maintain the CI. The case requires proof of “Both valid host types appear and unrelated CI pairs do not”, which establishes the relevant condition: Graph query logic must represent OR alternatives rather than forcing both branches simultaneously.

Question 381

An audit evaluates the completed action: Link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks. It addressed the problem: An executive requests one CMDB health score but support teams need practical remediation actions. What evidence best demonstrates success?

  1. Each critical failed metric has a named owner, affected CI sample and due date
  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. An eligible retired laptop CI is archived and restorable for the retention period; an in-use laptop CI is not archived by the policy
  4. Sampled tasks keep their approved main CI and relationship settings after the batch

Explanation

Correct Answer

A:

This observation directly validates the implemented control. An aggregate score becomes useful when failures are traceable to actionable work items. The decisive expected result is: Each critical failed metric has a named owner, affected CI sample and due date.

Incorrect Answers

B:

“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” could occur while the stated failure remains unresolved. It tests: 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 required validation instead is “Each critical failed metric has a named owner, affected CI sample and due date”, because an aggregate score becomes useful when failures are traceable to actionable work items.

C:

This checks a different technical dependency: 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 case requires proof of “Each critical failed metric has a named owner, affected CI sample and due date”, which establishes the relevant condition: An aggregate score becomes useful when failures are traceable to actionable work items.

D:

That observation would verify a control associated with: Reusable templates provide consistent merge decisions across many de-duplication tasks. It does not establish the needed acceptance outcome. The direct evidence is “Each critical failed metric has a named owner, affected CI sample and due date”, testing: An aggregate score becomes useful when failures are traceable to actionable work items.

Question 382

A ServiceNow Data Foundations rollout has two blockers. First: A sensitive cloud account identifier must be tracked alongside the appropriate business and technical CSDM objects. Second: A software CI exists for an application but a procurement team assumes it represents the same thing as a purchased physical asset. Which complete two-part implementation addresses both?

  1. (1) Map the regulatory identifier to supported governed attributes or references in the correct model; (2) configure supported dependent identification or hosting relationship rules and supply the required parent reference
  2. (1) Ingest or construct relationship payloads with resolvable parent and child CIs; (2) model procurement assets and operational CIs separately and link them where the model category supports it
  3. (1) Ingest or construct relationship payloads with resolvable parent and child CIs; (2) configure supported dependent identification or hosting relationship rules and supply the required parent reference
  4. (1) Map the regulatory identifier to supported governed attributes or references in the correct model; (2) model procurement assets and operational CIs separately and link them where the model category supports it

Explanation

Correct Answer

D:

Both controls are required. For condition (1), map the regulatory identifier to supported governed attributes or references in the correct model. Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes. Verify: A compliance query retrieves the proper owned service and associated identifier. For condition (2), model procurement assets and operational CIs separately and link them where the model category supports it. Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. Verify independently: Financial tracking and service impact reports use the appropriate connected records without treating all CIs as physical assets.

Incorrect Answers

A:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: A new dependent CI class fails identification because its hosting relationship is unavailable in the payload. It should instead use: Model procurement assets and operational CIs separately and link them where the model category supports it. Both required outcomes must be verified separately.

B:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: Network switches are imported but their upstream connection relationships are missing. It should instead use: Map the regulatory identifier to supported governed attributes or references in the correct model. Both required outcomes must be verified separately.

C:

Part (1) answers a different need: Network switches are imported but their upstream connection relationships are missing. It should instead use: Map the regulatory identifier to supported governed attributes or references in the correct model. Part (2) answers a different need: A new dependent CI class fails identification because its hosting relationship is unavailable in the payload. It should instead use: Model procurement assets and operational CIs separately and link them where the model category supports it. Both required outcomes must be verified separately.

Question 383

An organization finds this data-foundation problem: A team assumes changing CI Install Status automatically updates Hardware Status for the same computer. Which approach best achieves the required outcome: A status change affects only the mapped field and not an unrelated status field?

  1. Use a controlled manual CI maintenance process with steward ownership, required fields, and review dates
  2. Stage relationships until their parent and child CIs are resolved then load them via a supported path
  3. Configure and test the distinct asset/CI status mapping appropriate to the hardware class
  4. Ingest or construct relationship payloads with resolvable parent and child CIs

Explanation

Correct Answer

C:

This is the appropriate control for the stated CI requirement. Install Status and Hardware Status are independent fields rather than automatic mirrors of each other. Implement: Configure and test the distinct asset/CI status mapping appropriate to the hardware class. Confirm effectiveness by checking: A status change affects only the mapped field and not an unrelated status field.

Incorrect Answers

A:

Non-discoverable configuration data still needs controlled creation and periodic validation. The specific problem here is that install Status and Hardware Status are independent fields rather than automatic mirrors of each other.

B:

Processing order and endpoint matching prevent dangling or mismatched relationship references. The specific problem here is that install Status and Hardware Status are independent fields rather than automatic mirrors of each other.

D:

Reliable network maps depend on relationship creation and correctly identified endpoints. The specific problem here is that install Status and Hardware Status are independent fields rather than automatic mirrors of each other.

Question 384

Two change requests must be delivered together. Requirement A: A query should include only Windows servers in a specific data center connected to a selected application service. Requirement B: A security team wants to prioritize vulnerable servers by their business criticality. Select the plan that resolves both.

  1. (1) Apply class-node attribute filters and relationship conditions in CMDB Query Builder; (2) link correctly identified server CIs to their business services and ownership data
  2. (1) Open the CI or service Dependency View or supported Unified Map; (2) link correctly identified server CIs to their business services and ownership data
  3. (1) Open the CI or service Dependency View or supported Unified Map; (2) grant the documented query-builder read role rather than the authoring role
  4. (1) Apply class-node attribute filters and relationship conditions in CMDB Query Builder; (2) grant the documented query-builder read role rather than the authoring role

Explanation

Correct Answer

A:

Both controls are required. For condition (1), apply class-node attribute filters and relationship conditions in CMDB Query Builder. Filters narrow graph results using attributes of different CI nodes. Verify: The target data-center servers are returned and unrelated servers are excluded. For condition (2), link correctly identified server CIs to their business services and ownership data. Security and vulnerability workflows gain useful prioritization from trusted service dependencies. Verify independently: A critical service server is scored higher than a noncritical isolated lab server under the tested criteria.

Incorrect Answers

B:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: A support engineer needs a visual path from an application service to its infrastructure dependencies. It should instead use: Apply class-node attribute filters and relationship conditions in CMDB Query Builder. Both required outcomes must be verified separately.

C:

Part (1) answers a different need: A support engineer needs a visual path from an application service to its infrastructure dependencies. It should instead use: Apply class-node attribute filters and relationship conditions in CMDB Query Builder. Part (2) answers a different need: A CMDB user can view saved graph queries but is not allowed to author new queries. It should instead use: Link correctly identified server CIs to their business services and ownership data. Both required outcomes must be verified separately.

D:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: A CMDB user can view saved graph queries but is not allowed to author new queries. It should instead use: Link correctly identified server CIs to their business services and ownership data. Both required outcomes must be verified separately.

Question 385

A ServiceNow Data Foundations rollout has two blockers. First: The correctness score reports numerous duplicate Linux servers created by two tools. Second: Stale active servers should first be marked retired rather than immediately removed from CMDB. Which complete two-part implementation addresses both?

  1. (1) Separate discoverable and non-discoverable populations with suitable policies and review gates; (2) verify stable identification evidence before merging a suspected duplicate pair
  2. (1) Review the Duplicate correctness metric and the applicable CI identification rules; (2) verify stable identification evidence before merging a suspected duplicate pair
  3. (1) Review the Duplicate correctness metric and the applicable CI identification rules; (2) create an active retirement definition for the server class and publish a Retire policy with reviewed staleness/owner conditions, followed by independent lifecycle verification
  4. (1) Separate discoverable and non-discoverable populations with suitable policies and review gates; (2) create an active retirement definition for the server class and publish a Retire policy with reviewed staleness/owner conditions, followed by independent lifecycle verification

Explanation

Correct Answer

C:

Both controls are required. For condition (1), review the Duplicate correctness metric and the applicable CI identification rules. Correctness duplicates indicate identity collisions or insufficient matching rather than missing optional descriptions. Verify: Consolidating verified duplicate pairs and fixing identifiers reduces duplicate correctness failures. For condition (2), create an active retirement definition for the server class and publish a Retire policy with reviewed staleness/owner conditions, followed by independent lifecycle verification. Data Manager Retire policies target not-yet-retired CIs, with active class retirement definitions; archival/deletion are later separate policy actions, not an automatic result of retirement. Verify independently: A sampled approved stale server changes to its class-defined retired state, remains recorded, and an active verified server is not retired.

Incorrect Answers

A:

Part (1) answers a different need: A governance team proposes deleting every CI not seen by a discovery scan even when some are manually maintained contracts. It should instead use: Review the Duplicate correctness metric and the applicable CI identification rules. Part (2) answers a different need: Two visually similar server names do not mean two CIs are identical physical hosts. It should instead use: Create an active retirement definition for the server class and publish a Retire policy with reviewed staleness/owner conditions, followed by independent lifecycle verification. Both required outcomes must be verified separately.

B:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: Two visually similar server names do not mean two CIs are identical physical hosts. It should instead use: Create an active retirement definition for the server class and publish a Retire policy with reviewed staleness/owner conditions, followed by independent lifecycle verification. Both required outcomes must be verified separately.

D:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: A governance team proposes deleting every CI not seen by a discovery scan even when some are manually maintained contracts. It should instead use: Review the Duplicate correctness metric and the applicable CI identification rules. Both required outcomes must be verified separately.

Question 386

A team configured: Open CMDB 360 Multisource Data Preview for the CI attribute. Its original requirement was: Two inventory tools disagree about a server's owner and the steward needs the raw source evidence. Which observation proves that the desired operational outcome was achieved?

  1. A test service with a two-hop dependency returns all expected CIs
  2. The next scheduled execution returns a comparable scoped result set
  3. The sampled incidents route more accurately after governed CI ownership remediation
  4. Both conflicting values are visible with the chosen CMDB value distinguished

Explanation

Correct Answer

D:

This observation directly validates the implemented control. Multisource preview exposes reported values alongside the current CMDB selection. The decisive expected result is: Both conflicting values are visible with the chosen CMDB value distinguished.

Incorrect Answers

A:

This checks a different technical dependency: Multihop relationship modeling is needed to evaluate complete service dependencies. The case requires proof of “Both conflicting values are visible with the chosen CMDB value distinguished”, which establishes the relevant condition: Multisource preview exposes reported values alongside the current CMDB selection.

B:

That observation would verify a control associated with: Saved queries preserve graph semantics and can support repeatable consumption. It does not establish the needed acceptance outcome. The direct evidence is “Both conflicting values are visible with the chosen CMDB value distinguished”, testing: Multisource preview exposes reported values alongside the current CMDB selection.

C:

“The sampled incidents route more accurately after governed CI ownership remediation” could occur while the stated failure remains unresolved. It tests: Dashboard measures should connect data quality to measurable operational outcomes. The required validation instead is “Both conflicting values are visible with the chosen CMDB value distinguished”, because multisource preview exposes reported values alongside the current CMDB selection.

Question 387

A CMDB program needs two changes. Requirement A: A relationship health report contains edges with missing parent CI references. Requirement B: A team wishes to clean up orphaned non-CMDB Related Entry records after their referenced CI has been deleted, without deleting arbitrary unrelated business records. Select exactly TWO actions that jointly satisfy the requirements.

  1. Configure required or recommended class fields and a scheduled quality backlog
  2. 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
  3. Investigate and repair orphan relationships in the relationship health results
  4. Review the targeted Related Entry [cmdb_related_entry] references and apply the CMDB Data Manager Delete CMDB Related Entry policy only to approved orphaned entries
  5. Configure the supported dependent-CI approval and lifecycle handling path

Explanation

Correct Answers

C:

This satisfies requirement A: Investigate and repair orphan relationships in the relationship health results. Relationship integrity is separate from a CI having complete attributes. Independently verify: The corrected edge links two valid CIs and no longer appears as orphan.

D:

This satisfies requirement B: Review the targeted Related Entry [cmdb_related_entry] references and apply the CMDB Data Manager Delete CMDB Related Entry policy only to approved orphaned entries. The separate Delete CMDB Related Entry processor handles configured related-table entries tracked in cmdb_related_entry; it is not a general-purpose delete-all-non-CMDB-table operation. Independently verify: Only the approved entries pointing to removed CIs are deleted from tracked related tables, with active CI-linked and unrelated business data intact.

Incorrect Answers

A:

This is appropriate for another technical scenario: A new principal CI class is selected for governance but its key ownership fields are unpopulated. Principal class focus enables targeted data foundation completeness work. It does not directly satisfy either stated requirement; those require investigate and repair orphan relationships in the relationship health results. and review the targeted Related Entry [cmdb_related_entry] references and apply the CMDB Data Manager Delete CMDB Related Entry policy only to approved orphaned entries.

B:

This is appropriate for another technical scenario: A duplicate set is too large for supported full wizard merging and operators plan an unrestricted bulk merge. 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 directly satisfy either stated requirement; those require investigate and repair orphan relationships in the relationship health results. and review the targeted Related Entry [cmdb_related_entry] references and apply the CMDB Data Manager Delete CMDB Related Entry policy only to approved orphaned entries.

E:

This is appropriate for another technical scenario: A Data Manager policy runs on retired records but dependent application CIs require owner approval before cascade action. Lifecycle cascades should not silently remove dependent records without approved controls. It does not directly satisfy either stated requirement; those require investigate and repair orphan relationships in the relationship health results. and review the targeted Related Entry [cmdb_related_entry] references and apply the CMDB Data Manager Delete CMDB Related Entry policy only to approved orphaned entries.

Question 388

An audit evaluates the completed action: Correct the parent-child direction using the relationship editor or supported ingestion transform. It addressed the problem: A dependency is reversed, showing the database as hosted by a frontend application. What evidence best demonstrates success?

  1. A status change affects only the mapped field and not an unrelated status field
  2. Dependency traversal follows the intended application-to-database path
  3. New cloud metadata appears but protected Discovery-owned fields remain stable
  4. An upgrade test still identifies and updates sample CIs without bypassing IRE

Explanation

Correct Answer

B:

This observation directly validates the implemented control. Relationship direction matters for accurate dependency traversals and service modeling. The decisive expected result is: Dependency traversal follows the intended application-to-database path.

Incorrect Answers

A:

“A status change affects only the mapped field and not an unrelated status field” could occur while the stated failure remains unresolved. It tests: Install Status and Hardware Status are independent fields rather than automatic mirrors of each other. The required validation instead is “Dependency traversal follows the intended application-to-database path”, because relationship direction matters for accurate dependency traversals and service modeling.

C:

That observation would verify a control associated with: The decisive expected result is: New cloud metadata appears but protected Discovery-owned fields remain stable. It does not establish the needed acceptance outcome. The direct evidence is “Dependency traversal follows the intended application-to-database path”, testing: Relationship direction matters for accurate dependency traversals and service modeling.

D:

“An upgrade test still identifies and updates sample CIs without bypassing IRE” could occur while the stated failure remains unresolved. It tests: An upgrade test still identifies and updates sample CIs without bypassing IRE. The required validation instead is “Dependency traversal follows the intended application-to-database path”, because relationship direction matters for accurate dependency traversals and service modeling.

Question 389

A CMDB program needs two changes. Requirement A: The governance team needs a recommended support group field for one class without making it universally mandatory. Requirement B: A monitoring feed overwrites the serial number populated by a more authoritative Discovery source. Select exactly TWO actions that jointly satisfy the requirements.

  1. Configure a static attribute-level reconciliation definition that authorizes Discovery above the monitoring source for the serial-number attribute of matched existing server CIs
  2. Use an appropriate CMDB 360 saved query such as Find Gap comparing the two discovery sources
  3. 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
  4. Review CMDB 360 potential issues for CIs not recently reported by configured sources
  5. Configure a class-specific recommended field through CI Class Manager health settings

Explanation

Correct Answers

A:

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.

E:

This satisfies requirement A: Configure a class-specific recommended field through CI Class Manager health settings. Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. Independently verify: The class receives a recommended-field completeness score while record creation is not globally blocked.

Incorrect Answers

B:

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 configure a class-specific recommended field through CI Class Manager health settings. 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 update payload identifies an existing CI but an administrator expects reconciliation rules to apply to first-time inserts identically. 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 directly satisfy either stated requirement; those require configure a class-specific recommended field through CI Class Manager health settings. 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: 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 class-specific recommended field through CI Class Manager health settings. 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 390

A CMDB engineer applied the control: Use scoped CMDB Health inclusion rules for the intended principal CI population. This was meant to resolve: A health dashboard shows bad scores for lab CI classes that should not be evaluated. Which result most directly confirms the implementation works?

  1. One authoritative router CI remains with agreed values and related records
  2. A task lists the intended CI identifiers and no unrelated array is included
  3. Stock items are not incorrectly represented as deployed servers and true stale CIs are remediated
  4. The target KPI excludes the approved lab class while retaining production CIs

Explanation

Correct Answer

D:

This observation directly validates the implemented control. Appropriate class inclusion keeps operational KPIs from being diluted by irrelevant CI populations. The decisive expected result is: The target KPI excludes the approved lab class while retaining production CIs.

Incorrect Answers

A:

That observation would verify a control associated with: A de-duplication task groups competing CIs for controlled consolidation. It does not establish the needed acceptance outcome. The direct evidence is “The target KPI excludes the approved lab class while retaining production CIs”, testing: Appropriate class inclusion keeps operational KPIs from being diluted by irrelevant CI populations.

B:

“A task lists the intended CI identifiers and no unrelated array is included” could occur while the stated failure remains unresolved. It tests: A task lists the intended CI identifiers and no unrelated array is included. The required validation instead is “The target KPI excludes the approved lab class while retaining production CIs”, because appropriate class inclusion keeps operational KPIs from being diluted by irrelevant CI populations.

C:

This checks a different technical dependency: A stocked asset can exist financially without a currently operating CI for production impact. The case requires proof of “The target KPI excludes the approved lab class while retaining production CIs”, which establishes the relevant condition: Appropriate class inclusion keeps operational KPIs from being diluted by irrelevant CI populations.

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