CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A data steward is asked to resolve: The same hardware CI alternates between In Use and Retired after two different feeds run. Which solution meets the requirement and verifies: Repeated import cycles preserve the reviewed hardware lifecycle state?
Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates The proposed control addresses the stated problem, and its acceptance check is: Repeated import cycles preserve the reviewed hardware lifecycle state
Similar display names alone do not establish identical physical or logical identity. It does not implement the specific required change for this case; the suitable control is: Align lifecycle attribute source authority and the asset-CI status mapping
Direct record deletion can leave broken or incomplete related records. It does not implement the specific required change for this case; the suitable control is: Align lifecycle attribute source authority and the asset-CI status mapping
Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself. It does not implement the specific required change for this case; the suitable control is: Align lifecycle attribute source authority and the asset-CI status mapping
Two change requests must be delivered together. Requirement A: A new dependent CI class fails identification because its hosting relationship is unavailable in the payload. Requirement B: An import succeeds but all devices appear as generic cmdb_ci records rather than servers. Select the plan that resolves both.
First: Dependent identification may rely on relationships to identify CIs within a parent context Second: A correct source mapping is needed before identifier rules can classify incoming device records Both verification criteria must be met: The dependent CI matches its existing record when the required parent relationship is supplied Subsequent imports identify the expected server subclasses instead of generic CI entries
Dependent identification may rely on relationships to identify CIs within a parent context. The other proposed action (use a supported connector or governed API-based ingestion to populate that CI type) addresses a different operation. A correct source mapping is needed before identifier rules can classify incoming device records.
A correct source mapping is needed before identifier rules can classify incoming device records. The other proposed action (Model procurement assets and operational CIs separately and link them where the model category supports it) does not implement the first control. Dependent identification may rely on relationships to identify CIs within a parent context.
Dependent identification may rely on relationships to identify CIs within a parent context. A correct source mapping is needed before identifier rules can classify incoming device records. The proposed steps (Model procurement assets and operational CIs separately and link them where the model category supports it; use a supported connector or governed API-based ingestion to populate that CI type) address other capabilities instead of this required pair.
A CMDB engineer applied the control: Apply suitable suggested relationship types and governance review for each involved CI class. This was meant to resolve: A team models every CI as Depends on instead of choosing the correct relationship semantics. Which result most directly confirms the implementation works?
Relationship types distinguish hosting, containment, and dependencies for impact and service maps This observation validates the required outcome, not just the presence of a configured feature.
Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance. It does not establish that a reviewed service graph shows appropriate typed edges rather than one indiscriminate relationship.
Supported extension points lower technical debt from direct internal table manipulation. It does not establish that a reviewed service graph shows appropriate typed edges rather than one indiscriminate relationship.
Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs. It does not establish that a reviewed service graph shows appropriate typed edges rather than one indiscriminate relationship.
A configuration management team must address: A Data Manager policy runs on retired records but dependent application CIs require owner approval before cascade action. What change should it implement to demonstrate this result: The parent policy pauses or routes the dependent records for the designated review?
Lifecycle cascades should not silently remove dependent records without approved controls The proposed control addresses the stated problem, and its acceptance check is: The parent policy pauses or routes the dependent records for the designated review
An aggregate score becomes useful when failures are traceable to actionable work items. It does not implement the specific required change for this case; the suitable control is: Configure the supported dependent-CI approval and lifecycle handling path
Relationship integrity is separate from a CI having complete attributes. It does not implement the specific required change for this case; the suitable control is: Configure the supported dependent-CI approval and lifecycle handling path
Staleness evaluates the recency of reported CI updates or discovery according to its rules. It does not implement the specific required change for this case; the suitable control is: Configure the supported dependent-CI approval and lifecycle handling path
Two change requests must be delivered together. Requirement A: A service operations team must map production application service instances and their infrastructure dependencies. Requirement B: A program measures CSDM success by number of created rows alone despite low service ownership coverage. Select the plan that resolves both.
First: Service Delivery describes technology and running services used to fulfill customer-facing outcomes Second: CSDM's value is service context and usability, not raw CI volume Both verification criteria must be met: The service instance maps to actual deployed infrastructure and support ownership The adoption report shows verified owners and valid links for the priority services
CSDM's value is service context and usability, not raw CI volume. The other proposed action (Establish stable service records and correct CSDM links instead of copying separate spreadsheet services) does not implement the first control. Service Delivery describes technology and running services used to fulfill customer-facing outcomes.
Service Delivery describes technology and running services used to fulfill customer-facing outcomes. CSDM's value is service context and usability, not raw CI volume. The proposed steps (Establish stable service records and correct CSDM links instead of copying separate spreadsheet services; represent the ideas in the CSDM Ideation and Strategy domain) address other capabilities instead of this required pair.
Service Delivery describes technology and running services used to fulfill customer-facing outcomes. The other proposed action (represent the ideas in the CSDM Ideation and Strategy domain) addresses a different operation. CSDM's value is service context and usability, not raw CI volume.
An audit evaluates the completed action: Use IntegrationHub ETL with documented transformation mappings and supported IRE integration. It addressed the problem: One source API has nested device properties requiring repeatable transformations into several CMDB classes. What evidence best demonstrates success?
A governed ETL pipeline maps source schemas to class attributes and relationships This observation validates the required outcome, not just the presence of a configured feature.
Supported extension points lower technical debt from direct internal table manipulation. It does not establish that a sample nested payload creates the correct CI types and associated relationship records.
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. It does not establish that a sample nested payload creates the correct CI types and associated relationship records.
Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs. It does not establish that a sample nested payload creates the correct CI types and associated relationship records.
A data steward is asked to resolve: One source API has nested device properties requiring repeatable transformations into several CMDB classes. Which solution meets the requirement and verifies: A sample nested payload creates the correct CI types and associated relationship records?
A governed ETL pipeline maps source schemas to class attributes and relationships The proposed control addresses the stated problem, and its acceptance check is: A sample nested payload creates the correct CI types and associated relationship records
Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings. It does not implement the specific required change for this case; the suitable control is: Use IntegrationHub ETL with documented transformation mappings and supported IRE integration
Dependent identification may rely on relationships to identify CIs within a parent context. It does not implement the specific required change for this case; the suitable control is: Use IntegrationHub ETL with documented transformation mappings and supported IRE integration
Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance. It does not implement the specific required change for this case; the suitable control is: Use IntegrationHub ETL with documented transformation mappings and supported IRE integration
A CMDB administrator must resolve both independent failures: (1) An application service has no defined entry points and automatic service mapping misses its runtime. (2) An incident management team wants CIs to determine the right assignment group without manually guessing owners. Which coordinated plan satisfies both requirements?
First: Service mapping needs a starting entry point or suitable relationships to identify service infrastructure Second: ITSM workflows can use trustworthy configuration context for incident routing Both verification criteria must be met: The service visualization contains the expected application hosts after entry-point correction A seeded incident routes to the accountable support team using CI context
Service mapping needs a starting entry point or suitable relationships to identify service infrastructure. The other proposed action (validate the compliance audit configuration and execution before interpreting the empty tile as clean) addresses a different operation. ITSM workflows can use trustworthy configuration context for incident routing.
ITSM workflows can use trustworthy configuration context for incident routing. The other proposed action (Read the indicator's problem overview, business impact and fix/improve guidance) does not implement the first control. Service mapping needs a starting entry point or suitable relationships to identify service infrastructure.
Service mapping needs a starting entry point or suitable relationships to identify service infrastructure. ITSM workflows can use trustworthy configuration context for incident routing. The proposed steps (Read the indicator's problem overview, business impact and fix/improve guidance; validate the compliance audit configuration and execution before interpreting the empty tile as clean) address other capabilities instead of this required pair.
During a CMDB review, engineers discover: An auditor asks how CMDB quality improvement will be measured rather than relying on a one-time cleanup. Which proposed action is appropriate if success is measured by: Monthly measurements show trend, responsible owner and completed corrective actions?
Continuous KPI governance detects regressions after point-in-time remediation The proposed control addresses the stated problem, and its acceptance check is: Monthly measurements show trend, responsible owner and completed corrective actions
Guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record. It does not implement the specific required change for this case; the suitable control is: Define baseline health metrics and scheduled KPIs with owners and achievable thresholds
Similar display names alone do not establish identical physical or logical identity. It does not implement the specific required change for this case; the suitable control is: Define baseline health metrics and scheduled KPIs with owners and achievable thresholds
Fresh timestamps do not prove that a human has validated business ownership. It does not implement the specific required change for this case; the suitable control is: Define baseline health metrics and scheduled KPIs with owners and achievable thresholds
A ServiceNow Data Foundations rollout has two blockers. First: Developers need traceability for application components under active development and release. Second: Business analysts confuse a Business Application with a deployed Application Service instance. Which complete two-part implementation addresses both?
First: Build and Integration represents build-phase components before delivery operations Second: CSDM distinguishes the planned business capability/application from running service instances Both verification criteria must be met: Component links point to owned development work without claiming a running production service One business application is linked to relevant production service instances without duplicate application records
Build and Integration represents build-phase components before delivery operations. The other proposed action (use the CSDM Manage Portfolio cross-domain view and governed lifecycle linkages) addresses a different operation. CSDM distinguishes the planned business capability/application from running service instances.
CSDM distinguishes the planned business capability/application from running service instances. The other proposed action (Establish foundational reference and ownership data before expanding to advanced service maps) does not implement the first control. Build and Integration represents build-phase components before delivery operations.
Build and Integration represents build-phase components before delivery operations. CSDM distinguishes the planned business capability/application from running service instances. The proposed steps (Establish foundational reference and ownership data before expanding to advanced service maps; use the CSDM Manage Portfolio cross-domain view and governed lifecycle linkages) address other capabilities instead of this required pair.
A team configured: Use CI Class Manager to classify the records under an appropriate derived Linux Server class and its class-specific attributes. Its original requirement was: A virtualization team created Linux servers under the generic Computer class and cannot report Linux-only attributes. Which observation proves that the desired operational outcome was achieved?
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type This observation validates the required outcome, not just the presence of a configured feature.
CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. It does not establish that linux-specific reports include migrated server CIs without mixing desktop computers.
More specialized CI class rules can be chosen to identify specific subclasses accurately. It does not establish that linux-specific reports include migrated server CIs without mixing desktop computers.
Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute. It does not establish that linux-specific reports include migrated server CIs without mixing desktop computers.
Please check your mailbox for a message from support@examlabs.com and follow the directions.