CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
Two ServiceNow configuration issues require separate remedies. First: Developers need traceability for application components under active development and release. Second: Two stakeholder teams disagree whether a technical service should be classified under consumer or delivery concepts. Select exactly TWO appropriate steps.
This resolves requirement B. Accurate CSDM mapping needs collaboration between service providers and consumers Confirm it by testing: The revised model separates technical delivery capability from the consumer-visible business service
This resolves requirement A. Build and Integration represents build-phase components before delivery operations Confirm it by testing: 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.
CSDM distinguishes the planned business capability/application from running service instances.
Shared CSDM objects reduce semantic drift across workflows and reporting.
A configuration management team must address: A governance team proposes deleting every CI not seen by a discovery scan even when some are manually maintained contracts. What change should it implement to demonstrate this result: Manual business records remain while truly stale discoverable infrastructure enters review?
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI The proposed control addresses the stated problem, and its acceptance check is: Manual business records remain while truly stale discoverable infrastructure enters review
Orphan metrics reveal CIs no longer connected or useful under configured criteria. It does not implement the specific required change for this case; the suitable control is: Separate discoverable and non-discoverable populations with suitable policies and review gates
A de-duplication task groups competing CIs for controlled consolidation. It does not implement the specific required change for this case; the suitable control is: Separate discoverable and non-discoverable populations with suitable policies and review gates
Completeness Required measures required-field population for eligible CIs. It does not implement the specific required change for this case; the suitable control is: Separate discoverable and non-discoverable populations with suitable policies and review gates
A data governance release must meet both conditions: A: A team wants server support group to affect completeness but does not want it required by the dictionary. B: A duplicate server task contains competing IP values and two incident histories. Select the TWO necessary actions.
This resolves requirement A. Recommended completeness assesses configured helpful fields separately from mandatory creation rules Confirm it by testing: Empty support groups appear under Recommended without blocking unrelated CI creation
This resolves requirement B. Guided remediation considers source values, references and the surviving CI instead of blindly deleting the newest record Confirm it by testing: The incidents reference the surviving CI and the chosen authoritative IP is retained
An aggregate score becomes useful when failures are traceable to actionable work items.
Governance requires clear decision rights and accountable remediation owners.
A stocked asset can exist financially without a currently operating CI for production impact.
A CMDB administrator must resolve both independent failures: (1) A dashboard must compare two cloud inventory sources to reveal CIs absent from one feed. (2) An incident management team wants CIs to determine the right assignment group without manually guessing owners. Which coordinated plan satisfies both requirements?
First: A gap query reports mismatched source coverage rather than merely comparing displayed names Second: ITSM workflows can use trustworthy configuration context for incident routing Both verification criteria must be met: The seeded one-source-only CI is returned and fully covered CIs are excluded A seeded incident routes to the accountable support team using CI context
ITSM workflows can use trustworthy configuration context for incident routing. 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 gap query reports mismatched source coverage rather than merely comparing displayed names. 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.
A gap query reports mismatched source coverage rather than merely comparing displayed names. ITSM workflows can use trustworthy configuration context for incident routing. The proposed steps (Traverse CI relationships from the database to related application services using a supported dependency query or map; validate the compliance audit configuration and execution before interpreting the empty tile as clean) address other capabilities instead of this required pair.
A ServiceNow configuration project has two acceptance conditions. The first issue is: A cloud infrastructure vendor has a supported Service Graph Connector and the team is considering a bespoke CMDB REST importer. The second is: A team assumes changing CI Install Status automatically updates Hardware Status for the same computer. Which paired approach is suitable?
First: Supported connectors reduce custom upgrade debt and integrate source identification Second: Install Status and Hardware Status are independent fields rather than automatic mirrors of each other Both verification criteria must be met: The vendor inventory loads with mapped CI classes and no duplicate source identities A status change affects only the mapped field and not an unrelated status field
Supported connectors reduce custom upgrade debt and integrate source identification. The other proposed action (use a controlled manual CI maintenance process with steward ownership, required fields, and review dates) addresses a different operation. Install Status and Hardware Status are independent fields rather than automatic mirrors of each other.
Supported connectors reduce custom upgrade debt and integrate source identification. Install Status and Hardware Status are independent fields rather than automatic mirrors of each other. The proposed steps (Ingest or construct relationship payloads with resolvable parent and child CIs; use a controlled manual CI maintenance process with steward ownership, required fields, and review dates) address other capabilities instead of this required pair.
Install Status and Hardware Status are independent fields rather than automatic mirrors of each other. The other proposed action (Ingest or construct relationship payloads with resolvable parent and child CIs) does not implement the first control. Supported connectors reduce custom upgrade debt and integrate source identification.
A CMDB program needs two changes. Requirement A: Enterprise architects maintain a business capability map and plans for applications they may buy. Requirement B: Business analysts confuse a Business Application with a deployed Application Service instance. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement A. Design and Planning represents intended enterprise architecture, separate from runtime CIs Confirm it by testing: Capability reports show planned business application relationships without fictitious deployed instances
This resolves requirement B. CSDM distinguishes the planned business capability/application from running service instances Confirm it by testing: One business application is linked to relevant production service instances without duplicate application records
Incremental CSDM implementation reduces risk and enables feedback between milestones.
Accurate CSDM mapping needs collaboration between service providers and consumers.
Service offerings describe consumable business commitments, not server hardware attributes.
An audit evaluates the completed action: Configure a reviewed de-duplication template and apply it through the supported dashboard. It addressed the problem: A large batch of duplicate devices needs repeatable treatment across the same CI class. What evidence best demonstrates success?
Reusable templates provide consistent merge decisions across many de-duplication tasks This observation validates the required outcome, not just the presence of a configured feature.
Archive, Retire and Delete policy types can require class-specific active retirement definitions. It does not establish that sampled tasks keep their approved main CI and relationship settings after the batch.
Attestation asks an accountable person to verify CI data at a defined interval. It does not establish that sampled tasks keep their approved main CI and relationship settings after the batch.
CI lifecycle changes affect service dependency reporting and should be validated with owners. It does not establish that sampled tasks keep their approved main CI and relationship settings after the batch.
A ServiceNow Data Foundations rollout has two blockers. First: The security team wants a cloud account inventory imported while preserving authoritative values from existing Discovery. Second: A software CI exists for an application but a procurement team assumes it represents the same thing as a purchased physical asset. Which complete two-part implementation addresses both?
First: Additional ingestion sources should not overwrite unrelated authoritative CI attributes Second: Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies Both verification criteria must be met: New cloud metadata appears but protected Discovery-owned fields remain stable Financial tracking and service impact reports use the appropriate connected records without treating all CIs as physical assets
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. The other proposed action (Correct the parent-child direction using the relationship editor or supported ingestion transform) does not implement the first control. Additional ingestion sources should not overwrite unrelated authoritative CI attributes.
Additional ingestion sources should not overwrite unrelated authoritative CI attributes. 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.
Additional ingestion sources should not overwrite unrelated authoritative CI attributes. Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies. The proposed steps (Correct the parent-child direction using the relationship editor or supported ingestion transform; configure supported dependent identification or hosting relationship rules and supply the required parent reference) address other capabilities instead of this required pair.
A CMDB program needs two changes. Requirement A: A team sees a server icon in Dependency View but expects it to expose non-CMDB records unrelated to cmdb_ci. Requirement B: A dashboard shows empty compliance results after no audit has run. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement A. Dependency views operate on supported CMDB class and relationship information Confirm it by testing: Non-CMDB records remain outside the CI graph and modeled CIs render correctly
This resolves requirement B. Compliance data requires completed audit evidence to make a trustworthy score Confirm it by testing: A configured test audit supplies actual pass/fail results to the dashboard
Multisource records queries enable source-specific inventory reporting.
Multihop relationship modeling is needed to evaluate complete service dependencies.
Playbooks translate measured data-quality issues into actionable remediation context.
A data steward is asked to resolve: A policy owner changes filter conditions but does not test the effect on thousands of CIs. Which solution meets the requirement and verifies: A dry-run sample matches only the intended classes, lifecycle states and locations?
Evaluated policy scope helps prevent accidental mass retirement or deletion The proposed control addresses the stated problem, and its acceptance check is: A dry-run sample matches only the intended classes, lifecycle states and locations
Governance decisions should translate into technical rules preventing unapproved overwrites. It does not implement the specific required change for this case; the suitable control is: Preview or evaluate policy targets and approval requirements before publishing the change
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets. It does not implement the specific required change for this case; the suitable control is: Preview or evaluate policy targets and approval requirements before publishing the change
Traceable data changes preserve accountability for non-discoverable or manually governed CIs. It does not implement the specific required change for this case; the suitable control is: Preview or evaluate policy targets and approval requirements before publishing the change
A ServiceNow implementation team encounters this issue: A health score deteriorates after devices stop reporting but engineers blame the dashboard formula. Which control most directly resolves the issue and produces this outcome: A restored source feed refreshes the relevant CIs and improves the calculated score?
Data-source coverage failures can cause stale CI results that should not be hidden by score adjustments The proposed control addresses the stated problem, and its acceptance check is: A restored source feed refreshes the relevant CIs and improves the calculated score
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: Compare freshness and actual ingestion history before altering health thresholds
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: Compare freshness and actual ingestion history before altering health thresholds
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal. It does not implement the specific required change for this case; the suitable control is: Compare freshness and actual ingestion history before altering health thresholds
Please check your mailbox for a message from support@examlabs.com and follow the directions.