CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
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.
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?
First: Compliance results depend on audit conditions and executed evidence rather than field population alone Second: Guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record Both verification criteria must be met: The compliance score reflects the seeded pass and fail conditions after the audit runs The incidents reference the surviving CI and the chosen authoritative IP is retained
Guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record. The other proposed action (Remediate existing duplicate records separately and test the revised IRE rule for future ingests) does not implement the first control. Compliance results depend on audit conditions and executed evidence rather than field population alone.
Compliance results depend on audit conditions and executed evidence rather than field population alone. Guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record. The proposed steps (Remediate existing duplicate records separately and test the revised IRE rule for future ingests; review class scope, asset linkage and deployment lifecycle before mass remediation) address other capabilities instead of this required pair.
Compliance results depend on audit conditions and executed evidence rather than field population alone. The other proposed action (review class scope, asset linkage and deployment lifecycle before mass remediation) addresses a different operation. Guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record.
After implementing the approved change — Validate the compliance audit configuration and execution before interpreting the empty tile as clean — the data steward needs proof that it fixed: A dashboard shows empty compliance results after no audit has run. What should the steward observe?
Compliance data requires completed audit evidence to make a trustworthy score This observation validates the required outcome, not just the presence of a configured feature.
Multisource records queries enable source-specific inventory reporting. It does not establish that a configured test audit supplies actual pass/fail results to the dashboard.
Filters narrow graph results using attributes of different CI nodes. It does not establish that a configured test audit supplies actual pass/fail results to the dashboard.
A relationship-aware query traverses edges rather than filtering only a flat CI list. It does not establish that a configured test audit supplies actual pass/fail results to the dashboard.
A CMDB engineer applied the control: Evaluate a supported dynamic reconciliation rule backed by CMDB 360 for that attribute. 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?
Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute This observation validates the required outcome, not just the presence of a configured feature.
More specialized CI class rules can be chosen to identify specific subclasses accurately. It does not establish that the recomputed CI attribute follows the tested dynamic selection logic.
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type. It does not establish that the recomputed CI attribute follows the tested dynamic selection logic.
IRE identifies a new CI for insertion while reconciliation governs source-authorized updates to an existing CI. It does not establish that the recomputed CI attribute follows the tested dynamic selection logic.
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?
Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance This observation validates the required outcome, not just the presence of a configured feature.
Reliable network maps depend on relationship creation and correctly identified endpoints. It does not establish that a scheduled run updates the known network devices and discovers a seeded new host.
A correct source mapping is needed before identifier rules can classify incoming device records. It does not establish that a scheduled run updates the known network devices and discovers a seeded new host.
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. It does not establish that a scheduled run updates the known network devices and discovers a seeded new host.
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.
This resolves requirement B. Reconciliation rule changes can require reevaluation of existing attribute choices Confirm it by testing: The selected CI value changes only as justified by configured source data and the tested recomputation
This resolves requirement A. IRE identification matches incoming payloads to existing CIs before creating new records Confirm it by testing: Two payloads for the same server resolve to one existing CI during the test
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles.
Per-source reporting timestamps help detect coverage gaps even when a CI has historical data.
CMDB 360 retains visibility into competing reported attributes rather than showing only the final field.
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?
Relationship integrity is separate from a CI having complete attributes The proposed control addresses the stated problem, and its acceptance check is: The corrected edge links two valid CIs and no longer appears as orphan
Principal class focus enables targeted data foundation completeness work. It does not implement the specific required change for this case; the suitable control is: Investigate and repair orphan relationships in the relationship health results
Lifecycle cascades should not silently remove dependent records without approved controls. It does not implement the specific required change for this case; the suitable control is: Investigate and repair orphan relationships in the relationship health results
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets. It does not implement the specific required change for this case; the suitable control is: Investigate and repair orphan relationships in the relationship health results
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?
Portfolio governance spans CSDM domains rather than duplicating their objects The proposed control addresses the stated problem, and its acceptance check is: Portfolio review traces a service from planning through delivery to consumption
CSDM distinguishes the planned business capability/application from running service instances. It does not implement the specific required change for this case; the suitable control is: Use the CSDM Manage Portfolio cross-domain view and governed lifecycle linkages
Service offerings describe consumable business commitments, not server hardware attributes. It does not implement the specific required change for this case; the suitable control is: Use the CSDM Manage Portfolio cross-domain view and governed lifecycle linkages
Shared CSDM objects reduce semantic drift across workflows and reporting. It does not implement the specific required change for this case; the suitable control is: Use the CSDM Manage Portfolio cross-domain view and governed lifecycle linkages
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?
First: Reliable CI ownership fields enable routing and operational accountability Second: Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI Both verification criteria must be met: A test incident is directed to the intended database support group Manual business records remain while truly stale discoverable infrastructure enters review
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. The other proposed action (Review the de-duplication task and choose the valid main CI with its associated evidence) does not implement the first control. Reliable CI ownership fields enable routing and operational accountability.
Reliable CI ownership fields enable routing and operational accountability. Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. The proposed steps (Review the de-duplication task and choose the valid main CI with its associated evidence; review Required completeness failures and correct the missing mandatory ownership data) address other capabilities instead of this required pair.
Reliable CI ownership fields enable routing and operational accountability. The other proposed action (review Required completeness failures and correct the missing mandatory ownership data) addresses a different operation. Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI.
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.
This resolves requirement A. Dependent identification may rely on relationships to identify CIs within a parent context Confirm it by testing: The dependent CI matches its existing record when the required parent relationship is supplied
This resolves requirement B. Supported connectors reduce custom upgrade debt and integrate source identification Confirm it by testing: The vendor inventory loads with mapped CI classes and no duplicate source identities
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies.
A correct source mapping is needed before identifier rules can classify incoming device records.
A governed ETL pipeline maps source schemas to class attributes and relationships.
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 report identifies the specific failed metric rather than presenting only a total percentage.
The six familiar CI metrics explain why an aggregate health score changes, while relationship metrics can be analyzed separately The proposed control addresses the stated problem, and its acceptance check is: The report identifies the specific failed metric rather than presenting only a total percentage
Stewardship prevents uncoordinated changes to shared business context. It does not implement the specific required change for this case; the suitable control is: Report the appropriate KPI submetrics, including Required/Recommended, Duplicate/Stale/Orphan and audit compliance
Published policies, not simply saved drafts, are processed by the applicable scheduled framework. It does not implement the specific required change for this case; the suitable control is: Report the appropriate KPI submetrics, including Required/Recommended, Duplicate/Stale/Orphan and audit compliance
Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates. It does not implement the specific required change for this case; the suitable control is: Report the appropriate KPI submetrics, including Required/Recommended, Duplicate/Stale/Orphan and audit compliance
Please check your mailbox for a message from support@examlabs.com and follow the directions.