CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
Two change requests must be delivered together. Requirement A: An external connector imports duplicate rows for a host across multiple scheduled runs. Requirement B: A hardware laptop has both an asset record and CI record, but the two reference fields are not paired. Select the plan that resolves both.
First: Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle Second: Asset synchronization requires logical linkage between a physical asset and its technical CI Both verification criteria must be met: Two imports of an identical host leave one CI with updated source data A serial-number or location update reaches the associated record where the mapping permits
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. Asset synchronization requires logical linkage between a physical asset and its technical CI. The proposed steps (Replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal; use a properly credentialed Discovery schedule covering the intended address ranges) address other capabilities instead of this required pair.
Asset synchronization requires logical linkage between a physical asset and its technical CI. The other proposed action (Replace bypass scripts with supported import and IRE-aware mappings and keep custom transformations minimal) does not implement the first control. Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle.
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. The other proposed action (use a properly credentialed Discovery schedule covering the intended address ranges) addresses a different operation. Asset synchronization requires logical linkage between a physical asset and its technical CI.
An audit evaluates the completed action: Correct the underlying CMDB relationship records then refresh the dependency visualization. It addressed the problem: A service map displays duplicate relationship edges and misleading service impact chains. What evidence best demonstrates success?
Map accuracy depends on relationship data rather than cosmetic icon changes This observation validates the required outcome, not just the presence of a configured feature.
Security and vulnerability workflows gain useful prioritization from trusted service dependencies. It does not establish that duplicate edges disappear and valid dependencies still appear.
Missing recent source activity can signal integration failure even when other feeds maintain the CI. It does not establish that duplicate edges disappear and valid dependencies still appear.
Query access roles distinguish executing saved queries from creating and changing them. It does not establish that duplicate edges disappear and valid dependencies still appear.
An audit evaluates the completed action: Inspect the data-source history and relevant reconciliation records for that CI attribute. It addressed the problem: A data steward needs to know which source last updated a reconciled CI attribute. What evidence best demonstrates success?
Attribute-level history identifies the source of accepted updates after applicable rules are enabled 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 steward traces the selected CI value to the permitted discovery source.
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type. It does not establish that the steward traces the selected CI value to the permitted discovery source.
Reconciliation determines which incoming source may update each attribute on an existing CI. It does not establish that the steward traces the selected CI value to the permitted discovery source.
During a CMDB review, engineers discover: A branch network has thousands of reachable devices whose hardware properties change daily. Which proposed action is appropriate if success is measured by: A scheduled run updates the known network devices and discovers a seeded new host?
Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance The proposed control addresses the stated problem, and its acceptance check is: A scheduled run updates the known network devices and discovers a seeded new host
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: Use a properly credentialed Discovery schedule covering the intended address ranges
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: Use a properly credentialed Discovery schedule covering the intended address ranges
Reliable network maps depend on relationship creation and correctly identified endpoints. It does not implement the specific required change for this case; the suitable control is: Use a properly credentialed Discovery schedule covering the intended address ranges
An organization finds this data-foundation problem: A service offering catalog describes customer support hours but engineers put it on a server CI. Which approach best achieves the required outcome: The customer-visible offering holds the schedule and its underlying instances remain separate?
Service offerings describe consumable business commitments, not server hardware attributes The proposed control addresses the stated problem, and its acceptance check is: The customer-visible offering holds the schedule and its underlying instances remain separate
Service Delivery describes technology and running services used to fulfill customer-facing outcomes. It does not implement the specific required change for this case; the suitable control is: Model the consumer-facing commitment on the appropriate business service offering
Portfolio governance spans CSDM domains rather than duplicating their objects. It does not implement the specific required change for this case; the suitable control is: Model the consumer-facing commitment on the appropriate business service offering
Design and Planning represents intended enterprise architecture, separate from runtime CIs. It does not implement the specific required change for this case; the suitable control is: Model the consumer-facing commitment on the appropriate business service offering
A CMDB administrator must resolve both independent failures: (1) A dependency is reversed, showing the database as hosted by a frontend application. (2) A software CI exists for an application but a procurement team assumes it represents the same thing as a purchased physical asset. Which coordinated plan satisfies both requirements?
First: Relationship direction matters for accurate dependency traversals and service modeling Second: Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies Both verification criteria must be met: Dependency traversal follows the intended application-to-database path Financial tracking and service impact reports use the appropriate connected records without treating all CIs as physical assets
Relationship direction matters for accurate dependency traversals and service modeling. Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. The proposed steps (Configure the appropriate Asset State to CI Hardware Status mapping and permitted sync direction; configure supported dependent identification or hosting relationship rules and supply the required parent reference) address other capabilities instead of this required pair.
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. 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 (configure supported dependent identification or hosting relationship rules and supply the required parent reference) addresses a different operation. Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies.
The change record states that the team will: Use a controlled manual CI maintenance process with steward ownership, required fields, and review dates. The original defect was: A manual SaaS license dependency has no discovery agent and needs occasional verified updates. Which validation finding should be accepted?
Non-discoverable configuration data still needs controlled creation and periodic validation This observation validates the required outcome, not just the presence of a configured feature.
Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings. It does not establish that the owner attests that the CI has a valid class, relationship and next review date.
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. It does not establish that the owner attests that the CI has a valid class, relationship and next review date.
Asset synchronization requires logical linkage between a physical asset and its technical CI. It does not establish that the owner attests that the CI has a valid class, relationship and next review date.
A CMDB administrator must resolve both independent failures: (1) A trusted import is allowed to update existing storage CIs but must not create new storage CIs. (2) An attribute priority based solely on source ordering gives a poor result when most sources agree on another value. Which coordinated plan satisfies both requirements?
First: IRE data-source rules can control CI insertion separately from updating existing identified records Second: Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute Both verification criteria must be met: The import updates the matched storage CI but does not insert an unmatched device The recomputed CI attribute follows the tested dynamic selection logic
Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute. 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. IRE data-source rules can control CI insertion separately from updating existing identified records.
IRE data-source rules can control CI insertion separately from updating existing identified records. The other proposed action (inspect the class hierarchy and inherited attributes in CI Class Manager) addresses a different operation. Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute.
IRE data-source rules can control CI insertion separately from updating existing identified records. Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute. The proposed steps (Use an appropriate CMDB 360 saved query such as Find Gap comparing the two discovery sources; inspect the class hierarchy and inherited attributes in CI Class Manager) address other capabilities instead of this required pair.
The change record states that the team will: Report the appropriate KPI submetrics, including Required/Recommended, Duplicate/Stale/Orphan and audit compliance. The original defect was: A CMDB manager wants to distinguish correctness, completeness and compliance in a monthly report. Which validation finding should be accepted?
The six familiar CI metrics explain why an aggregate health score changes, while relationship metrics can be analyzed separately This observation validates the required outcome, not just the presence of a configured feature.
Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself. It does not establish that the report identifies the specific failed metric rather than presenting only a total percentage.
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. It does not establish that the report identifies the specific failed metric rather than presenting only a total percentage.
Continuous KPI governance detects regressions after point-in-time remediation. It does not establish that the report identifies the specific failed metric rather than presenting only a total percentage.
A team configured: Fix the source-to-target CI class mapping and verify class eligibility and identifiers. Its original requirement was: An import succeeds but all devices appear as generic cmdb_ci records rather than servers. Which observation proves that the desired operational outcome was achieved?
A correct source mapping is needed before identifier rules can classify incoming device records 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 subsequent imports identify the expected server subclasses instead of generic CI entries.
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. It does not establish that subsequent imports identify the expected server subclasses instead of generic CI entries.
Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes. It does not establish that subsequent imports identify the expected server subclasses instead of generic CI entries.
After implementing the approved change — Model appropriate development or SDLC components in Build and Integration — the data steward needs proof that it fixed: Developers need traceability for application components under active development and release. What should the steward observe?
Build and Integration represents build-phase components before delivery operations This observation validates the required outcome, not just the presence of a configured feature.
Incremental CSDM implementation reduces risk and enables feedback between milestones. It does not establish that component links point to owned development work without claiming a running production service.
Accurate CSDM mapping needs collaboration between service providers and consumers. It does not establish that 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 establish that component links point to owned development work without claiming a running production service.
Please check your mailbox for a message from support@examlabs.com and follow the directions.