CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
After implementing the approved change — Use an import set and supported transform or IntegrationHub ETL pipeline that applies CI identification controls — the data steward needs proof that it fixed: An external inventory provides CSV files weekly and no ready connector exists. What should the steward observe?
Staging and mapping preserve input validation and can hand CI writes to supported IRE processing This observation validates the required outcome, not just the presence of a configured feature.
Hardware status mapping reflects asset lifecycle without treating unrelated CI fields as interchangeable. It does not establish that a representative file creates or updates only the intended CI records.
Reliable network maps depend on relationship creation and correctly identified endpoints. It does not establish that a representative file creates or updates only the intended CI records.
Processing order and endpoint matching prevent dangling or mismatched relationship references. It does not establish that a representative file creates or updates only the intended CI records.
A CMDB change request reports: A new dependent CI class fails identification because its hosting relationship is unavailable in the payload. Select the best implementation. It must pass this acceptance test: The dependent CI matches its existing record when the required parent relationship is supplied.
Dependent identification may rely on relationships to identify CIs within a parent context The proposed control addresses the stated problem, and its acceptance check is: The dependent CI matches its existing record when the required parent relationship is supplied
A correct source mapping is needed before identifier rules can classify incoming device records. It does not implement the specific required change for this case; the suitable control is: Configure supported dependent identification or hosting relationship rules and supply the required parent reference
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. It does not implement the specific required change for this case; the suitable control is: Configure supported dependent identification or hosting relationship rules and supply the required parent reference
A governed ETL pipeline maps source schemas to class attributes and relationships. It does not implement the specific required change for this case; the suitable control is: Configure supported dependent identification or hosting relationship rules and supply the required parent reference
A ServiceNow implementation team encounters this issue: A manual SaaS license dependency has no discovery agent and needs occasional verified updates. Which control most directly resolves the issue and produces this outcome: The owner attests that the CI has a valid class, relationship and next review date?
Non-discoverable configuration data still needs controlled creation and periodic validation The proposed control addresses the stated problem, and its acceptance check is: The owner attests that the CI has a valid class, relationship and next review date
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. It does not implement the specific required change for this case; the suitable control is: Use a controlled manual CI maintenance process with steward ownership, required fields, and review dates
Staging and mapping preserve input validation and can hand CI writes to supported IRE processing. It does not implement the specific required change for this case; the suitable control is: Use a controlled manual CI maintenance process with steward ownership, required fields, and review dates
Install Status and Hardware Status are independent fields rather than automatic mirrors of each other. It does not implement the specific required change for this case; the suitable control is: Use a controlled manual CI maintenance process with steward ownership, required fields, and review dates
A ServiceNow implementation team encounters this issue: A source stopped reporting network devices three weeks ago even though their CIs still exist. Which control most directly resolves the issue and produces this outcome: The stopped source is flagged for affected CIs while healthy sources remain current?
Per-source reporting timestamps help detect coverage gaps even when a CI has historical data The proposed control addresses the stated problem, and its acceptance check is: The stopped source is flagged for affected CIs while healthy sources remain current
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. It does not implement the specific required change for this case; the suitable control is: Review CMDB 360 potential issues for CIs not recently reported by configured sources
Suggested relationships guide consistent relationship selection without making every pairing physically true. It does not implement the specific required change for this case; the suitable control is: Review CMDB 360 potential issues for CIs not recently reported by configured sources
Child-level attributes scope specialized fields to the correct extension class. It does not implement the specific required change for this case; the suitable control is: Review CMDB 360 potential issues for CIs not recently reported by configured sources
After implementing the approved change — Set an attribute-level static reconciliation rule with authorized sources and source priority — the data steward needs proof that it fixed: A monitoring feed overwrites the serial number populated by a more authoritative Discovery source. What should the steward observe?
Reconciliation determines which incoming source may update each attribute on an existing CI This observation validates the required outcome, not just the presence of a configured feature.
Attribute-level history identifies the source of accepted updates after applicable rules are enabled. It does not establish that discovery keeps the trusted serial number after the lower-priority feed runs.
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. It does not establish that discovery keeps the trusted serial number after the lower-priority feed runs.
Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported. It does not establish that discovery keeps the trusted serial number after the lower-priority feed runs.
An audit evaluates the completed action: Prioritize principal CI classes and agreed service outcomes before onboarding large volumes. It addressed the problem: A new CMDB program imports every discovered object before deciding which services it supports. What evidence best demonstrates success?
A scoped initial data foundation is easier to govern than an unactionable inventory This observation validates the required outcome, not just the presence of a configured feature.
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets. It does not establish that the selected classes serve the defined use cases and have health acceptance criteria.
Recommended completeness assesses configured helpful fields separately from mandatory creation rules. It does not establish that the selected classes serve the defined use cases and have health acceptance criteria.
Automated lifecycle governance reconciles discovered existence with administrative approval. It does not establish that the selected classes serve the defined use cases and have health acceptance criteria.
The change record states that the team will: Review the service impact and relationship dependencies before retiring or archiving its CI. The original defect was: A retired application server is still linked as actively hosting an important service. Which validation finding should be accepted?
CI lifecycle changes affect service dependency reporting and should be validated with owners This observation validates the required outcome, not just the presence of a configured feature.
Continuous KPI governance detects regressions after point-in-time remediation. It does not establish that only the truly decommissioned server is retired and the service map points to its replacement.
Reliable CI ownership fields enable routing and operational accountability. It does not establish that only the truly decommissioned server is retired and the service map points to its replacement.
A scoped initial data foundation is easier to govern than an unactionable inventory. It does not establish that only the truly decommissioned server is retired and the service map points to its replacement.
A ServiceNow configuration project has two acceptance conditions. The first issue is: A compliance tile shows no results despite multiple mandatory fields being filled. The second is: A Data Manager policy runs on retired records but dependent application CIs require owner approval before cascade action. Which paired approach is suitable?
First: Compliance results depend on audit conditions and executed evidence rather than field population alone Second: Lifecycle cascades should not silently remove dependent records without approved controls Both verification criteria must be met: The compliance score reflects the seeded pass and fail conditions after the audit runs The parent policy pauses or routes the dependent records for the designated review
Compliance results depend on audit conditions and executed evidence rather than field population alone. The other proposed action (examine the Staleness correctness metric and the class's staleness definition) addresses a different operation. Lifecycle cascades should not silently remove dependent records without approved controls.
Compliance results depend on audit conditions and executed evidence rather than field population alone. Lifecycle cascades should not silently remove dependent records without approved controls. The proposed steps (Remediate existing duplicate records separately and test the revised IRE rule for future ingests; examine the Staleness correctness metric and the class's staleness definition) address other capabilities instead of this required pair.
Lifecycle cascades should not silently remove dependent records without approved controls. 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.
Two ServiceNow configuration issues require separate remedies. First: A virtualization team created Linux servers under the generic Computer class and cannot report Linux-only attributes. Second: Cloud inventory and Discovery report different operating system versions for the same CI. Select exactly TWO appropriate steps.
This resolves requirement A. A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type Confirm it by testing: Linux-specific reports include migrated server CIs without mixing desktop computers
This resolves requirement B. CMDB 360 retains visibility into competing reported attributes rather than showing only the final field Confirm it by testing: The reviewer sees both source values and identifies the currently selected value
Reconciliation determines which incoming source may update each attribute on an existing CI.
More specialized CI class rules can be chosen to identify specific subclasses accurately.
Per-source reporting timestamps help detect coverage gaps even when a CI has historical data.
An audit evaluates the completed action: Create a CMDB 360 Find Gap saved query across the selected sources. It addressed the problem: A dashboard must compare two cloud inventory sources to reveal CIs absent from one feed. What evidence best demonstrates success?
A gap query reports mismatched source coverage rather than merely comparing displayed names This observation validates the required outcome, not just the presence of a configured feature.
Foundation indicators make recurring quality gaps visible and link them to improvement actions. It does not establish that the seeded one-source-only CI is returned and fully covered CIs are excluded.
Query access roles distinguish executing saved queries from creating and changing them. It does not establish that the seeded one-source-only CI is returned and fully covered CIs are excluded.
Compliance data requires completed audit evidence to make a trustworthy score. It does not establish that the seeded one-source-only CI is returned and fully covered CIs are excluded.
A ServiceNow configuration project has two acceptance conditions. The first issue is: The governance team needs a recommended support group field for one class without making it universally mandatory. The second is: A data steward needs to know which source last updated a reconciled CI attribute. Which paired approach is suitable?
First: Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles Second: Attribute-level history identifies the source of accepted updates after applicable rules are enabled Both verification criteria must be met: The class receives a recommended-field completeness score while record creation is not globally blocked The steward traces the selected CI value to the permitted discovery source
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. The other proposed action (define and validate a child-class identification rule instead of relying on an unsuitable inherited parent rule) addresses a different operation. Attribute-level history identifies the source of accepted updates after applicable rules are enabled.
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. Attribute-level history identifies the source of accepted updates after applicable rules are enabled. The proposed steps (Review CMDB 360 potential issues for CIs not recently reported by configured sources; define and validate a child-class identification rule instead of relying on an unsuitable inherited parent rule) address other capabilities instead of this required pair.
Attribute-level history identifies the source of accepted updates after applicable rules are enabled. The other proposed action (Review CMDB 360 potential issues for CIs not recently reported by configured sources) does not implement the first control. Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles.
Please check your mailbox for a message from support@examlabs.com and follow the directions.