CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A ServiceNow configuration project has two acceptance conditions. The first issue is: A team configures a new custom table unrelated to cmdb_ci and expects CI Class Manager to administer it. The second is: Two sources insert separate server CIs because hostname alone is not a stable unique key. Which paired approach is suitable?
First: CI Class Manager is designed for classes in the CMDB hierarchy Second: IRE identification matches incoming payloads to existing CIs before creating new records Both verification criteria must be met: The non-CMDB table is managed correctly and no phantom CI class appears Two payloads for the same server resolve to one existing CI during the test
IRE identification matches incoming payloads to existing CIs before creating new records. The other proposed action (Route incoming CI payloads through a supported IRE-aware ingestion path) does not implement the first control. CI Class Manager is designed for classes in the CMDB hierarchy.
CI Class Manager is designed for classes in the CMDB hierarchy. IRE identification matches incoming payloads to existing CIs before creating new records. The proposed steps (Route incoming CI payloads through a supported IRE-aware ingestion path; use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value) address other capabilities instead of this required pair.
CI Class Manager is designed for classes in the CMDB hierarchy. The other proposed action (use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value) addresses a different operation. IRE identification matches incoming payloads to existing CIs before creating new records.
During a CMDB review, engineers discover: Enterprise architects maintain a business capability map and plans for applications they may buy. Which proposed action is appropriate if success is measured by: Capability reports show planned business application relationships without fictitious deployed instances?
Design and Planning represents intended enterprise architecture, separate from runtime CIs The proposed control addresses the stated problem, and its acceptance check is: Capability reports show planned business application relationships without fictitious deployed instances
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 business capabilities and business applications in Design and Planning
Incremental CSDM implementation reduces risk and enables feedback between milestones. It does not implement the specific required change for this case; the suitable control is: Model business capabilities and business applications in Design and Planning
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: Model business capabilities and business applications in Design and Planning
A CMDB change request reports: An external connector imports duplicate rows for a host across multiple scheduled runs. Select the best implementation. It must pass this acceptance test: Two imports of an identical host leave one CI with updated source data.
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle The proposed control addresses the stated problem, and its acceptance check is: Two imports of an identical host leave one CI with updated source data
Supported extension points lower technical debt from direct internal table manipulation. It does not implement the specific required change for this case; the suitable control is: Validate IRE identification configuration and stable native source IDs before increasing dedupe scripts
Hardware status mapping reflects asset lifecycle without treating unrelated CI fields as interchangeable. It does not implement the specific required change for this case; the suitable control is: Validate IRE identification configuration and stable native source IDs before increasing dedupe scripts
Non-discoverable configuration data still needs controlled creation and periodic validation. It does not implement the specific required change for this case; the suitable control is: Validate IRE identification configuration and stable native source IDs before increasing dedupe scripts
A ServiceNow configuration project has two acceptance conditions. The first issue is: A dashboard must compare two cloud inventory sources to reveal CIs absent from one feed. The second is: A CIO wants to know whether CMDB data improvements are delivering value to incident response. Which paired approach is suitable?
First: A gap query reports mismatched source coverage rather than merely comparing displayed names Second: Dashboard measures should connect data quality to measurable operational outcomes Both verification criteria must be met: The seeded one-source-only CI is returned and fully covered CIs are excluded The sampled incidents route more accurately after governed CI ownership remediation
A gap query reports mismatched source coverage rather than merely comparing displayed names. The other proposed action (align application and service entities with the CSDM model and use suitable foundation indicators) addresses a different operation. Dashboard measures should connect data quality to measurable operational outcomes.
A gap query reports mismatched source coverage rather than merely comparing displayed names. Dashboard measures should connect data quality to measurable operational outcomes. The proposed steps (Traverse CI relationships from the database to related application services using a supported dependency query or map; align application and service entities with the CSDM model and use suitable foundation indicators) address other capabilities instead of this required pair.
Dashboard measures should connect data quality to measurable operational outcomes. The other proposed action (Traverse CI relationships from the database to related application services using a supported dependency query or map) does not implement the first control. A gap query reports mismatched source coverage rather than merely comparing displayed names.
A team configured: Represent the ideas in the CSDM Ideation and Strategy domain. Its original requirement was: Product managers track strategic product ideas before any technology build is approved. Which observation proves that the desired operational outcome was achieved?
Strategy records concern proposed opportunities before detailed architecture or delivery This observation validates the required outcome, not just the presence of a configured feature.
Shared CSDM objects reduce semantic drift across workflows and reporting. It does not establish that an unapproved idea is visible in strategic planning but not misrepresented as a deployed service.
A foundation-first adoption path prevents inconsistent references spreading across later domains. It does not establish that an unapproved idea is visible in strategic planning but not misrepresented as a deployed service.
Incremental CSDM implementation reduces risk and enables feedback between milestones. It does not establish that an unapproved idea is visible in strategic planning but not misrepresented as a deployed service.
An audit evaluates the completed action: Maintain application-to-database relationships and use the change impact analysis view. It addressed the problem: A change advisory board needs to identify downstream services affected by a database replacement. What evidence best demonstrates success?
Linked CI dependencies reveal potential blast radius before infrastructure changes This observation validates the required outcome, not just the presence of a configured feature.
Multisource preview exposes reported values alongside the current CMDB selection. It does not establish that the test database change lists its genuinely dependent services for review.
Service mapping needs a starting entry point or suitable relationships to identify service infrastructure. It does not establish that the test database change lists its genuinely dependent services for review.
Dependency visualization traverses relationship edges so potential impact is easier to understand. It does not establish that the test database change lists its genuinely dependent services for review.
An implementation review finds these independent issues: (1) An enterprise application cannot be discovered by conventional infrastructure scanning but has a supported cloud API inventory. (2) A software CI exists for an application but a procurement team assumes it represents the same thing as a purchased physical asset. Which TWO controls should the team apply?
This resolves requirement B. Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies Confirm it by testing: Financial tracking and service impact reports use the appropriate connected records without treating all CIs as physical assets
This resolves requirement A. Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs Confirm it by testing: The non-scannable application CI is updated from the authoritative API inventory
A correct source mapping is needed before identifier rules can classify incoming device records.
Relationship records encode application dependencies beyond the CI attributes themselves.
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle.
A CMDB change request reports: A company starts CSDM by creating detailed service maps before standardizing departments and locations. Select the best implementation. It must pass this acceptance test: Two service teams resolve to the same authoritative company, location and support groups.
A foundation-first adoption path prevents inconsistent references spreading across later domains The proposed control addresses the stated problem, and its acceptance check is: Two service teams resolve to the same authoritative company, location and support groups
Build and Integration represents build-phase components before delivery operations. It does not implement the specific required change for this case; the suitable control is: Establish foundational reference and ownership data before expanding to advanced service maps
Service Consumption expresses what consumers request, rather than how technical systems are hosted. It does not implement the specific required change for this case; the suitable control is: Establish foundational reference and ownership data before expanding to advanced service maps
Strategy records concern proposed opportunities before detailed architecture or delivery. It does not implement the specific required change for this case; the suitable control is: Establish foundational reference and ownership data before expanding to advanced service maps
A CMDB engineer applied the control: Use a Data Manager Attestation policy assigned to the accountable reviewers. This was meant to resolve: A data owner needs quarterly human confirmation that a set of CIs is still correct. Which result most directly confirms the implementation works?
Attestation asks an accountable person to verify CI data at a defined interval This observation validates the required outcome, not just the presence of a configured feature.
Reusable templates provide consistent merge decisions across many de-duplication tasks. It does not establish that reviewers receive and complete the required attestation tasks for sampled CIs.
Archive, Retire and Delete policy types can require class-specific active retirement definitions. It does not establish that reviewers receive and complete the required attestation tasks for sampled CIs.
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. It does not establish that reviewers receive and complete the required attestation tasks for sampled CIs.
During a CMDB review, engineers discover: An analyst needs to compare the CI population connected to either Linux or Windows hosts in one graph. Which proposed action is appropriate if success is measured by: Both valid host types appear and unrelated CI pairs do not?
Graph query logic must represent OR alternatives rather than forcing both branches simultaneously The proposed control addresses the stated problem, and its acceptance check is: Both valid host types appear and unrelated CI pairs do not
ITSM workflows can use trustworthy configuration context for incident routing. It does not implement the specific required change for this case; the suitable control is: Model the required alternative relationship branches correctly in the query canvas
Multisource preview exposes reported values alongside the current CMDB selection. It does not implement the specific required change for this case; the suitable control is: Model the required alternative relationship branches correctly in the query canvas
Service mapping needs a starting entry point or suitable relationships to identify service infrastructure. It does not implement the specific required change for this case; the suitable control is: Model the required alternative relationship branches correctly in the query canvas
A configuration management team must address: A web application CI has no dependency link to its database and impact analysis misses downstream failures. What change should it implement to demonstrate this result: A dependency view now traverses from the application to the correct database CI?
Relationship records encode application dependencies beyond the CI attributes themselves The proposed control addresses the stated problem, and its acceptance check is: A dependency view now traverses from the application to the correct database CI
Processing order and endpoint matching prevent dangling or mismatched relationship references. It does not implement the specific required change for this case; the suitable control is: Create the correctly directed CI relationship with the appropriate relationship type
Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs. It does not implement the specific required change for this case; the suitable control is: Create the correctly directed CI relationship with the appropriate relationship type
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: Create the correctly directed CI relationship with the appropriate relationship type
Please check your mailbox for a message from support@examlabs.com and follow the directions.