CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A CMDB engineer applied the control: Check the Duplicate CI Remediator scale limit and use a supported safe alternate remediation strategy. This was meant to resolve: A duplicate set is too large for supported full wizard merging and operators plan an unrestricted bulk merge. Which result most directly confirms the implementation works?
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets This observation validates the required outcome, not just the presence of a configured feature.
Correctness duplicates indicate identity collisions or insufficient matching rather than missing optional descriptions. It does not establish that the large set is processed within supported limits with auditable relationship handling.
Lifecycle cascades should not silently remove dependent records without approved controls. It does not establish that the large set is processed within supported limits with auditable relationship handling.
Staleness evaluates the recency of reported CI updates or discovery according to its rules. It does not establish that the large set is processed within supported limits with auditable relationship handling.
A CMDB program needs two changes. Requirement A: The operations team cannot see where Database Server inherits its mandatory CI fields. Requirement B: A trusted import is allowed to update existing storage CIs but must not create new storage CIs. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement B. IRE data-source rules can control CI insertion separately from updating existing identified records Confirm it by testing: The import updates the matched storage CI but does not insert an unmatched device
This resolves requirement A. Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported Confirm it by testing: The administrator identifies which parent supplies each required field before making a change
Multisource gap queries identify CIs not reported by one or more participating data sources.
Reconciliation rule changes can require reevaluation of existing attribute choices.
Direct table writes can evade identification and reconciliation controls designed to prevent duplicates.
A CMDB administrator must resolve both independent failures: (1) A customer-impact report needs the set of services that depend on a failed database CI. (2) A service owner wants to understand why a foundational-data playbook recommends a change. Which coordinated plan satisfies both requirements?
First: Impact analysis uses directed dependencies to identify affected services Second: Playbooks translate measured data-quality issues into actionable remediation context Both verification criteria must be met: The report lists the affected services while excluding unrelated workloads The owner can identify the problem, impact and recommended action from the playbook
Playbooks translate measured data-quality issues into actionable remediation context. The other proposed action (Build a CMDB Query Builder graph using CI class nodes and correctly typed relationships) does not implement the first control. Impact analysis uses directed dependencies to identify affected services.
Impact analysis uses directed dependencies to identify affected services. Playbooks translate measured data-quality issues into actionable remediation context. The proposed steps (Build a CMDB Query Builder graph using CI class nodes and correctly typed relationships; save and schedule a supported CMDB Query Builder query and use its result set for reporting) address other capabilities instead of this required pair.
Impact analysis uses directed dependencies to identify affected services. The other proposed action (save and schedule a supported CMDB Query Builder query and use its result set for reporting) addresses a different operation. Playbooks translate measured data-quality issues into actionable remediation context.
A team configured: Route incoming CI payloads through a supported IRE-aware ingestion path. Its original requirement was: A custom CMDB integration uses a direct table insert and bypasses existing IRE identification logic. Which observation proves that the desired operational outcome was achieved?
Direct table writes can evade identification and reconciliation controls designed to prevent duplicates This observation validates the required outcome, not just the presence of a configured feature.
Per-source reporting timestamps help detect coverage gaps even when a CI has historical data. It does not establish that the ingest uses identification rules and does not insert another copy of a known CI.
Child-level attributes scope specialized fields to the correct extension class. It does not establish that the ingest uses identification rules and does not insert another copy of a known CI.
Attribute-level history identifies the source of accepted updates after applicable rules are enabled. It does not establish that the ingest uses identification rules and does not insert another copy of a known CI.
A ServiceNow configuration project has two acceptance conditions. The first issue is: A dependency is reversed, showing the database as hosted by a frontend application. The second is: An external connector imports duplicate rows for a host across multiple scheduled runs. Which paired approach is suitable?
First: Relationship direction matters for accurate dependency traversals and service modeling Second: Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle Both verification criteria must be met: Dependency traversal follows the intended application-to-database path Two imports of an identical host leave one CI with updated source data
Relationship direction matters for accurate dependency traversals and service modeling. Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. The proposed steps (Configure the appropriate Asset State to CI Hardware Status mapping and permitted sync direction; replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal) address other capabilities instead of this required pair.
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. The other proposed action (Configure the appropriate Asset State to CI Hardware Status mapping and permitted sync direction) does not implement the first control. Relationship direction matters for accurate dependency traversals and service modeling.
Relationship direction matters for accurate dependency traversals and service modeling. The other proposed action (replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal) addresses a different operation. Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle.
An implementation review finds these independent issues: (1) The correctness score reports numerous duplicate Linux servers created by two tools. (2) A retired application server is still linked as actively hosting an important service. Which TWO controls should the team apply?
This resolves requirement B. CI lifecycle changes affect service dependency reporting and should be validated with owners Confirm it by testing: Only the truly decommissioned server is retired and the service map points to its replacement
This resolves requirement A. Correctness duplicates indicate identity collisions or insufficient matching rather than missing optional descriptions Confirm it by testing: Consolidating verified duplicate pairs and fixing identifiers reduces duplicate correctness failures
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI.
A scoped initial data foundation is easier to govern than an unactionable inventory.
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal.
A data governance release must meet both conditions: A: A support engineer needs a visual path from an application service to its infrastructure dependencies. B: A change advisory board needs to identify downstream services affected by a database replacement. Select the TWO necessary actions.
This resolves requirement A. Dependency visualization traverses relationship edges so potential impact is easier to understand Confirm it by testing: The view shows the application and the expected upstream infrastructure CIs
This resolves requirement B. Linked CI dependencies reveal potential blast radius before infrastructure changes Confirm it by testing: The test database change lists its genuinely dependent services for review
Graph query logic must represent OR alternatives rather than forcing both branches simultaneously.
Filters narrow graph results using attributes of different CI nodes.
Multihop relationship modeling is needed to evaluate complete service dependencies.
A CMDB engineer applied the control: Apply reconciliation source priority and valid identification as the new data source is onboarded. This was meant to resolve: The security team wants a cloud account inventory imported while preserving authoritative values from existing Discovery. Which result most directly confirms the implementation works?
Additional ingestion sources should not overwrite unrelated authoritative CI attributes This observation validates the required outcome, not just the presence of a configured feature.
Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs. It does not establish that new cloud metadata appears but protected Discovery-owned fields remain stable.
Processing order and endpoint matching prevent dangling or mismatched relationship references. It does not establish that new cloud metadata appears but protected Discovery-owned fields remain stable.
Dependent identification may rely on relationships to identify CIs within a parent context. It does not establish that new cloud metadata appears but protected Discovery-owned fields remain stable.
A team configured: Link correctly identified server CIs to their business services and ownership data. Its original requirement was: A security team wants to prioritize vulnerable servers by their business criticality. Which observation proves that the desired operational outcome was achieved?
Security and vulnerability workflows gain useful prioritization from trusted service dependencies This observation validates the required outcome, not just the presence of a configured feature.
Query access roles distinguish executing saved queries from creating and changing them. It does not establish that a critical service server is scored higher than a noncritical isolated lab server under the tested criteria.
Saved queries preserve graph semantics and can support repeatable consumption. It does not establish that a critical service server is scored higher than a noncritical isolated lab server under the tested criteria.
A gap query reports mismatched source coverage rather than merely comparing displayed names. It does not establish that a critical service server is scored higher than a noncritical isolated lab server under the tested criteria.
After implementing the approved change — Define adoption KPIs for correctly mapped services, owners and relationships — the data steward needs proof that it fixed: A program measures CSDM success by number of created rows alone despite low service ownership coverage. What should the steward observe?
CSDM's value is service context and usability, not raw CI volume This observation validates the required outcome, not just the presence of a configured feature.
Foundation provides common organizational and reference data reused by other CSDM domains. It does not establish that the adoption report shows verified owners and valid links for the priority services.
Portfolio governance spans CSDM domains rather than duplicating their objects. It does not establish that the adoption report shows verified owners and valid links for the priority services.
Service Delivery describes technology and running services used to fulfill customer-facing outcomes. It does not establish that the adoption report shows verified owners and valid links for the priority services.
A configuration management team must address: Developers need traceability for application components under active development and release. What change should it implement to demonstrate this result: Component links point to owned development work without claiming a running production service?
Build and Integration represents build-phase components before delivery operations The proposed control addresses the stated problem, and its acceptance check is: Component links point to owned development work without claiming a running production service
A foundation-first adoption path prevents inconsistent references spreading across later domains. It does not implement the specific required change for this case; the suitable control is: Model appropriate development or SDLC components in Build and Integration
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: Model appropriate development or SDLC components in Build and Integration
Accurate CSDM mapping needs collaboration between service providers and consumers. It does not implement the specific required change for this case; the suitable control is: Model appropriate development or SDLC components in Build and Integration
Please check your mailbox for a message from support@examlabs.com and follow the directions.