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: A service offering catalog describes customer support hours but engineers put it on a server CI. Select exactly TWO appropriate steps.
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
This resolves requirement B. Service offerings describe consumable business commitments, not server hardware attributes Confirm it by testing: The customer-visible offering holds the schedule and its underlying instances remain separate
Shared CSDM objects reduce semantic drift across workflows and reporting.
A foundation-first adoption path prevents inconsistent references spreading across later domains.
Accurate CSDM mapping needs collaboration between service providers and consumers.
An implementation review finds these independent issues: (1) A virtualization team created Linux servers under the generic Computer class and cannot report Linux-only attributes. (2) A trusted import is allowed to update existing storage CIs but must not create new storage CIs. Which TWO controls should the team apply?
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. A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type Confirm it by testing: Linux-specific reports include migrated server CIs without mixing desktop computers
More specialized CI class rules can be chosen to identify specific subclasses accurately.
Per-source reporting timestamps help detect coverage gaps even when a CI has historical data.
Reconciliation determines which incoming source may update each attribute on an existing CI.
A ServiceNow configuration project has two acceptance conditions. The first issue is: A saved query must be reused for monthly reporting with consistent class and relationship criteria. The second is: A service map displays duplicate relationship edges and misleading service impact chains. Which paired approach is suitable?
First: Saved queries preserve graph semantics and can support repeatable consumption Second: Map accuracy depends on relationship data rather than cosmetic icon changes Both verification criteria must be met: The next scheduled execution returns a comparable scoped result set Duplicate edges disappear and valid dependencies still appear
Saved queries preserve graph semantics and can support repeatable consumption. The other proposed action (monitor CMDB 360 'not reported by source' potential issues and reporting intervals) addresses a different operation. Map accuracy depends on relationship data rather than cosmetic icon changes.
Map accuracy depends on relationship data rather than cosmetic icon changes. The other proposed action (Link correctly identified server CIs to their business services and ownership data) does not implement the first control. Saved queries preserve graph semantics and can support repeatable consumption.
Saved queries preserve graph semantics and can support repeatable consumption. Map accuracy depends on relationship data rather than cosmetic icon changes. The proposed steps (Link correctly identified server CIs to their business services and ownership data; monitor CMDB 360 'not reported by source' potential issues and reporting intervals) address other capabilities instead of this required pair.
A ServiceNow Data Foundations rollout has two blockers. First: An executive requests one CMDB health score but support teams need practical remediation actions. Second: Cloud instances are regularly terminated but their old CMDB records are still active after three months. Which complete two-part implementation addresses both?
First: An aggregate score becomes useful when failures are traceable to actionable work items Second: Automated lifecycle governance reconciles discovered existence with administrative approval Both verification criteria must be met: Each critical failed metric has a named owner, affected CI sample and due date Confirmed terminated instances no longer appear as active configuration items
Automated lifecycle governance reconciles discovered existence with administrative approval. The other proposed action (Configure a reviewed de-duplication template and apply it through the supported dashboard) does not implement the first control. An aggregate score becomes useful when failures are traceable to actionable work items.
An aggregate score becomes useful when failures are traceable to actionable work items. The other proposed action (investigate and repair orphan relationships in the relationship health results) addresses a different operation. Automated lifecycle governance reconciles discovered existence with administrative approval.
An aggregate score becomes useful when failures are traceable to actionable work items. Automated lifecycle governance reconciles discovered existence with administrative approval. The proposed steps (Configure a reviewed de-duplication template and apply it through the supported dashboard; investigate and repair orphan relationships in the relationship health results) address other capabilities instead of this required pair.
During a CMDB review, engineers discover: A change advisory board needs to identify downstream services affected by a database replacement. Which proposed action is appropriate if success is measured by: The test database change lists its genuinely dependent services for review?
Linked CI dependencies reveal potential blast radius before infrastructure changes The proposed control addresses the stated problem, and its acceptance check is: The test database change lists its genuinely dependent services for review
Query access roles distinguish executing saved queries from creating and changing them. It does not implement the specific required change for this case; the suitable control is: Maintain application-to-database relationships and use the change impact analysis view
Saved queries preserve graph semantics and can support repeatable consumption. It does not implement the specific required change for this case; the suitable control is: Maintain application-to-database relationships and use the change impact analysis view
A single aggregate hides which technical quality condition is worsening. It does not implement the specific required change for this case; the suitable control is: Maintain application-to-database relationships and use the change impact analysis view
An implementation review finds these independent issues: (1) A CIO wants to know whether CMDB data improvements are delivering value to incident response. (2) A service portfolio manager cannot compare service reliability because applications are inconsistently represented in CMDB. Which TWO controls should the team apply?
This resolves requirement A. Dashboard measures should connect data quality to measurable operational outcomes Confirm it by testing: The sampled incidents route more accurately after governed CI ownership remediation
This resolves requirement B. Standardized service representation supports comparable portfolio and operations reporting Confirm it by testing: Two departments' equivalent services appear under consistent classes and governance definitions
Dependency visualization traverses relationship edges so potential impact is easier to understand.
A relationship-aware query traverses edges rather than filtering only a flat CI list.
ITSM workflows can use trustworthy configuration context for incident routing.
A team configured: Examine the Staleness correctness metric and the class's staleness definition. Its original requirement was: Servers remain active in CMDB although their last discovery time is older than the agreed threshold. Which observation proves that the desired operational outcome was achieved?
Staleness evaluates the recency of reported CI updates or discovery according to its rules This observation validates the required outcome, not just the presence of a configured feature.
A de-duplication task groups competing CIs for controlled consolidation. It does not establish that expired server records are flagged and newly refreshed servers clear the staleness rule.
Archive, Retire and Delete policy types can require class-specific active retirement definitions. It does not establish that expired server records are flagged and newly refreshed servers clear the staleness rule.
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets. It does not establish that expired server records are flagged and newly refreshed servers clear the staleness rule.
A CMDB program needs two changes. Requirement A: A large batch of duplicate devices needs repeatable treatment across the same CI class. Requirement B: A central team overrides business service names without approval from the service owners. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement A. Reusable templates provide consistent merge decisions across many de-duplication tasks Confirm it by testing: Sampled tasks keep their approved main CI and relationship settings after the batch
This resolves requirement B. Stewardship prevents uncoordinated changes to shared business context Confirm it by testing: An approved renaming request includes owner signoff and traceable changes
Attestation asks an accountable person to verify CI data at a defined interval.
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal.
Governance requires clear decision rights and accountable remediation owners.
Two change requests must be delivered together. Requirement A: Two visually similar server names do not mean two CIs are identical physical hosts. Requirement B: A Data Manager policy runs on retired records but dependent application CIs require owner approval before cascade action. Select the plan that resolves both.
First: Similar display names alone do not establish identical physical or logical identity Second: Lifecycle cascades should not silently remove dependent records without approved controls Both verification criteria must be met: Distinct hosts remain separate and a truly matching test pair is consolidated 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 other proposed action (Validate eligibility and publish the Data Manager policy instead of assuming drafts run) does not implement the first control. Similar display names alone do not establish identical physical or logical identity.
Similar display names alone do not establish identical physical or logical identity. The other proposed action (examine the Staleness correctness metric and the class's staleness definition) addresses a different operation. Lifecycle cascades should not silently remove dependent records without approved controls.
Similar display names alone do not establish identical physical or logical identity. Lifecycle cascades should not silently remove dependent records without approved controls. The proposed steps (Validate eligibility and publish the Data Manager policy instead of assuming drafts run; examine the Staleness correctness metric and the class's staleness definition) address other capabilities instead of this required pair.
After implementing the approved change — Map the regulatory identifier to supported governed attributes or references in the correct model — the data steward needs proof that it fixed: A sensitive cloud account identifier must be tracked alongside the appropriate business and technical CSDM objects. What should the steward observe?
Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes This observation validates the required outcome, not just the presence of a configured feature.
A correct source mapping is needed before identifier rules can classify incoming device records. It does not establish that a compliance query retrieves the proper owned service and associated identifier.
Hardware status mapping reflects asset lifecycle without treating unrelated CI fields as interchangeable. It does not establish that a compliance query retrieves the proper owned service and associated identifier.
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. It does not establish that a compliance query retrieves the proper owned service and associated identifier.
After implementing the approved change — Adopt a phased approach starting with priority services and measurable outcomes — the data steward needs proof that it fixed: An enterprise wants to demonstrate CSDM value without remapping every application in one big-bang change. What should the steward observe?
Incremental CSDM implementation reduces risk and enables feedback between milestones This observation validates the required outcome, not just the presence of a configured feature.
Design and Planning represents intended enterprise architecture, separate from runtime CIs. It does not establish that the first supported services have trustworthy models and agreed measurable improvements.
Build and Integration represents build-phase components before delivery operations. It does not establish that the first supported services have trustworthy models and agreed measurable improvements.
Strategy records concern proposed opportunities before detailed architecture or delivery. It does not establish that the first supported services have trustworthy models and agreed measurable improvements.
Please check your mailbox for a message from support@examlabs.com and follow the directions.