CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A ServiceNow Data Foundations rollout has two blockers. First: A relationship health report contains edges with missing parent CI references. Second: A duplicate set is too large for supported full wizard merging and operators plan an unrestricted bulk merge. Which complete two-part implementation addresses both?
First: Relationship integrity is separate from a CI having complete attributes Second: Remediation tooling can restrict available reconciliation functions for oversized duplicate sets Both verification criteria must be met: The corrected edge links two valid CIs and no longer appears as orphan The large set is processed within supported limits with auditable relationship handling
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets. The other proposed action (Configure the supported dependent-CI approval and lifecycle handling path) does not implement the first control. Relationship integrity is separate from a CI having complete attributes.
Relationship integrity is separate from a CI having complete attributes. The other proposed action (validate eligibility and publish the Data Manager policy instead of assuming drafts run) addresses a different operation. Remediation tooling can restrict available reconciliation functions for oversized duplicate sets.
Relationship integrity is separate from a CI having complete attributes. Remediation tooling can restrict available reconciliation functions for oversized duplicate sets. The proposed steps (Configure the supported dependent-CI approval and lifecycle handling path; validate eligibility and publish the Data Manager policy instead of assuming drafts run) address other capabilities instead of this required pair.
Two change requests must be delivered together. Requirement A: The system reports probable duplicate storage arrays but no de-duplication task was automatically generated. Requirement B: A retired application server is still linked as actively hosting an important service. Select the plan that resolves both.
First: Manual tasks allow reviewed consolidation when automatic detection does not create a task Second: CI lifecycle changes affect service dependency reporting and should be validated with owners Both verification criteria must be met: A task lists the intended CI identifiers and no unrelated array is included Only the truly decommissioned server is retired and the service map points to its replacement
Manual tasks allow reviewed consolidation when automatic detection does not create a task. The other proposed action (use a Data Manager Attestation policy assigned to the accountable reviewers) addresses a different operation. CI lifecycle changes affect service dependency reporting and should be validated with owners.
Manual tasks allow reviewed consolidation when automatic detection does not create a task. CI lifecycle changes affect service dependency reporting and should be validated with owners. The proposed steps (Review class scope, asset linkage and deployment lifecycle before mass remediation; use a Data Manager Attestation policy assigned to the accountable reviewers) address other capabilities instead of this required pair.
CI lifecycle changes affect service dependency reporting and should be validated with owners. The other proposed action (Review class scope, asset linkage and deployment lifecycle before mass remediation) does not implement the first control. Manual tasks allow reviewed consolidation when automatic detection does not create a task.
A team configured: Review service owner intent and use CSDM model definitions to map delivery versus consumption appropriately. Its original requirement was: Two stakeholder teams disagree whether a technical service should be classified under consumer or delivery concepts. Which observation proves that the desired operational outcome was achieved?
Accurate CSDM mapping needs collaboration between service providers and consumers This observation validates the required outcome, not just the presence of a configured feature.
Build and Integration represents build-phase components before delivery operations. It does not establish that the revised model separates technical delivery capability from the consumer-visible business service.
Foundation provides common organizational and reference data reused by other CSDM domains. It does not establish that the revised model separates technical delivery capability from the consumer-visible business service.
Service Delivery describes technology and running services used to fulfill customer-facing outcomes. It does not establish that the revised model separates technical delivery capability from the consumer-visible business service.
After implementing the approved change — Grant the documented query-builder read role rather than the authoring role — the data steward needs proof that it fixed: A CMDB user can view saved graph queries but is not allowed to author new queries. What should the steward observe?
Query access roles distinguish executing saved queries from creating and changing them This observation validates the required outcome, not just the presence of a configured feature.
Dependency views operate on supported CMDB class and relationship information. It does not establish that the analyst runs approved queries but cannot modify their definitions.
Dependency visualization traverses relationship edges so potential impact is easier to understand. It does not establish that the analyst runs approved queries but cannot modify their definitions.
A gap query reports mismatched source coverage rather than merely comparing displayed names. It does not establish that the analyst runs approved queries but cannot modify their definitions.
A ServiceNow implementation team encounters this issue: A Data Manager Delete policy unexpectedly targets active production databases. Which control most directly resolves the issue and produces this outcome: No active database is selected and only approved retired test records are eligible?
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal The proposed control addresses the stated problem, and its acceptance check is: No active database is selected and only approved retired test records are eligible
A de-duplication task groups competing CIs for controlled consolidation. It does not implement the specific required change for this case; the suitable control is: Restrict the policy to approved retired CI classes with prerequisite retirement definitions and review its evaluation
CI lifecycle changes affect service dependency reporting and should be validated with owners. It does not implement the specific required change for this case; the suitable control is: Restrict the policy to approved retired CI classes with prerequisite retirement definitions and review its evaluation
Orphan metrics reveal CIs no longer connected or useful under configured criteria. It does not implement the specific required change for this case; the suitable control is: Restrict the policy to approved retired CI classes with prerequisite retirement definitions and review its evaluation
A data governance release must meet both conditions: A: A customer-impact report needs the set of services that depend on a failed database CI. B: A service portfolio manager cannot compare service reliability because applications are inconsistently represented in CMDB. Select the TWO necessary actions.
This resolves requirement B. Standardized service representation supports comparable portfolio and operations reporting Confirm it by testing: Two departments' equivalent services appear under consistent classes and governance definitions
This resolves requirement A. Impact analysis uses directed dependencies to identify affected services Confirm it by testing: The report lists the affected services while excluding unrelated workloads
A relationship-aware query traverses edges rather than filtering only a flat CI list.
Multisource records queries enable source-specific inventory reporting.
Missing recent source activity can signal integration failure even when other feeds maintain the CI.
An implementation review finds these independent issues: (1) One source API has nested device properties requiring repeatable transformations into several CMDB classes. (2) Finance changes asset acquisition cost and expects manual reversal from the CI to rewrite the purchase ledger. Which TWO controls should the team apply?
This resolves requirement B. Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings Confirm it by testing: Asset cost updates the CI view but CI-only changes do not overwrite authoritative asset cost
This resolves requirement A. A governed ETL pipeline maps source schemas to class attributes and relationships Confirm it by testing: A sample nested payload creates the correct CI types and associated relationship records
Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes.
Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance.
Dependent identification may rely on relationships to identify CIs within a parent context.
A data steward is asked to resolve: A team configures a new custom table unrelated to cmdb_ci and expects CI Class Manager to administer it. Which solution meets the requirement and verifies: The non-CMDB table is managed correctly and no phantom CI class appears?
CI Class Manager is designed for classes in the CMDB hierarchy The proposed control addresses the stated problem, and its acceptance check is: The non-CMDB table is managed correctly and no phantom CI class appears
More specialized CI class rules can be chosen to identify specific subclasses accurately. It does not implement the specific required change for this case; the suitable control is: Use normal table-definition administration for the non-CMDB table rather than CI Class Manager
Per-source reporting timestamps help detect coverage gaps even when a CI has historical data. It does not implement the specific required change for this case; the suitable control is: Use normal table-definition administration for the non-CMDB table rather than CI Class Manager
Direct table writes can evade identification and reconciliation controls designed to prevent duplicates. It does not implement the specific required change for this case; the suitable control is: Use normal table-definition administration for the non-CMDB table rather than CI Class Manager
After implementing the approved change — Remediate existing duplicate records separately and test the revised IRE rule for future ingests — the data steward needs proof that it fixed: A duplicate task was created before an identification rule was fixed, and the team assumes fixing the rule auto-merges historical records. What should the steward observe?
Improved identification prevents future collisions but does not retroactively merge every old duplicate This observation validates the required outcome, not just the presence of a configured feature.
Staleness evaluates the recency of reported CI updates or discovery according to its rules. It does not establish that existing task is closed appropriately and repeat ingestion does not produce a new duplicate.
Completeness Required measures required-field population for eligible CIs. It does not establish that existing task is closed appropriately and repeat ingestion does not produce a new duplicate.
Principal class focus enables targeted data foundation completeness work. It does not establish that existing task is closed appropriately and repeat ingestion does not produce a new duplicate.
A CMDB program needs two changes. Requirement A: An import succeeds but all devices appear as generic cmdb_ci records rather than servers. Requirement B: A software CI exists for an application but a procurement team assumes it represents the same thing as a purchased physical asset. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement A. A correct source mapping is needed before identifier rules can classify incoming device records Confirm it by testing: Subsequent imports identify the expected server subclasses instead of generic CI entries
This resolves requirement B. Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies Confirm it by testing: Financial tracking and service impact reports use the appropriate connected records without treating all CIs as physical assets
Relationship types distinguish hosting, containment, and dependencies for impact and service maps.
Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs.
Reliable network maps depend on relationship creation and correctly identified endpoints.
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?
First: Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported Second: Reconciliation rule changes can require reevaluation of existing attribute choices Both verification criteria must be met: The administrator identifies which parent supplies each required field before making a change The selected CI value changes only as justified by configured source data and the tested recomputation
Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported. Reconciliation rule changes can require reevaluation of existing attribute choices. The proposed steps (Use an appropriate CMDB 360 saved query such as Find Gap comparing the two discovery sources; add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition) address other capabilities instead of this required pair.
Reconciliation rule changes can require reevaluation of existing attribute choices. The other proposed action (Use an appropriate CMDB 360 saved query such as Find Gap comparing the two discovery sources) does not implement the first control. Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported.
Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported. The other proposed action (add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition) addresses a different operation. Reconciliation rule changes can require reevaluation of existing attribute choices.
Please check your mailbox for a message from support@examlabs.com and follow the directions.