CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
The change record states that the team will: Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path. The original defect was: A cloud infrastructure vendor has a supported Service Graph Connector and the team is considering a bespoke CMDB REST importer. Which validation finding should be accepted?
Supported connectors reduce custom upgrade debt and integrate source identification This observation validates the required outcome, not just the presence of a configured feature.
Processing order and endpoint matching prevent dangling or mismatched relationship references. It does not establish that the vendor inventory loads with mapped CI classes and no duplicate source identities.
Dependent identification may rely on relationships to identify CIs within a parent context. It does not establish that the vendor inventory loads with mapped CI classes and no duplicate source identities.
Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings. It does not establish that the vendor inventory loads with mapped CI classes and no duplicate source identities.
An implementation review finds these independent issues: (1) A policy owner changes filter conditions but does not test the effect on thousands of CIs. (2) Two integration owners disagree about the authoritative source for application environment status. Which TWO controls should the team apply?
This resolves requirement A. Evaluated policy scope helps prevent accidental mass retirement or deletion Confirm it by testing: A dry-run sample matches only the intended classes, lifecycle states and locations
This resolves requirement B. Governance decisions should translate into technical rules preventing unapproved overwrites Confirm it by testing: A lower-priority feed cannot overwrite the reviewed authoritative attribute
Traceable data changes preserve accountability for non-discoverable or manually governed CIs.
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets.
Automated lifecycle governance reconciles discovered existence with administrative approval.
A ServiceNow Data Foundations rollout has two blockers. First: A service operations team must map production application service instances and their infrastructure dependencies. Second: A service offering catalog describes customer support hours but engineers put it on a server CI. Which complete two-part implementation addresses both?
First: Service Delivery describes technology and running services used to fulfill customer-facing outcomes Second: Service offerings describe consumable business commitments, not server hardware attributes Both verification criteria must be met: The service instance maps to actual deployed infrastructure and support ownership The customer-visible offering holds the schedule and its underlying instances remain separate
Service offerings describe consumable business commitments, not server hardware attributes. 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. The other proposed action (use the CSDM Manage Portfolio cross-domain view and governed lifecycle linkages) addresses a different operation. Service offerings describe consumable business commitments, not server hardware attributes.
Service Delivery describes technology and running services used to fulfill customer-facing outcomes. Service offerings describe consumable business commitments, not server hardware attributes. The proposed steps (Establish stable service records and correct CSDM links instead of copying separate spreadsheet services; use the CSDM Manage Portfolio cross-domain view and governed lifecycle linkages) address other capabilities instead of this required pair.
During a CMDB review, engineers discover: An IRE job detects two CIs representing the same router and creates a duplicate remediation task. Which proposed action is appropriate if success is measured by: One authoritative router CI remains with agreed values and related records?
A de-duplication task groups competing CIs for controlled consolidation The proposed control addresses the stated problem, and its acceptance check is: One authoritative router CI remains with agreed values and related records
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. It does not implement the specific required change for this case; the suitable control is: Review the de-duplication task and choose the valid main CI with its associated evidence
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: Review the de-duplication task and choose the valid main CI with its associated evidence
Appropriate class inclusion keeps operational KPIs from being diluted by irrelevant CI populations. It does not implement the specific required change for this case; the suitable control is: Review the de-duplication task and choose the valid main CI with its associated evidence
A CMDB program needs two changes. Requirement A: A cloud infrastructure vendor has a supported Service Graph Connector and the team is considering a bespoke CMDB REST importer. Requirement B: A branch network has thousands of reachable devices whose hardware properties change daily. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement B. Automated discovery observes discoverable infrastructure more reliably than manual spreadsheet maintenance Confirm it by testing: A scheduled run updates the known network devices and discovers a seeded new host
This resolves requirement A. Supported connectors reduce custom upgrade debt and integrate source identification Confirm it by testing: The vendor inventory loads with mapped CI classes and no duplicate source identities
Reliable network maps depend on relationship creation and correctly identified endpoints.
Processing order and endpoint matching prevent dangling or mismatched relationship references.
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies.
A ServiceNow configuration project has two acceptance conditions. The first issue is: A team models every CI as Depends on instead of choosing the correct relationship semantics. The second is: A manual SaaS license dependency has no discovery agent and needs occasional verified updates. Which paired approach is suitable?
First: Relationship types distinguish hosting, containment, and dependencies for impact and service maps Second: Non-discoverable configuration data still needs controlled creation and periodic validation Both verification criteria must be met: A reviewed service graph shows appropriate typed edges rather than one indiscriminate relationship The owner attests that the CI has a valid class, relationship and next review date
Relationship types distinguish hosting, containment, and dependencies for impact and service maps. Non-discoverable configuration data still needs controlled creation and periodic validation. The proposed steps (Fix the source-to-target CI class mapping and verify class eligibility and identifiers; use an import set and supported transform or IntegrationHub ETL pipeline that applies CI identification controls) address other capabilities instead of this required pair.
Non-discoverable configuration data still needs controlled creation and periodic validation. The other proposed action (Fix the source-to-target CI class mapping and verify class eligibility and identifiers) does not implement the first control. Relationship types distinguish hosting, containment, and dependencies for impact and service maps.
Relationship types distinguish hosting, containment, and dependencies for impact and service maps. The other proposed action (use an import set and supported transform or IntegrationHub ETL pipeline that applies CI identification controls) addresses a different operation. Non-discoverable configuration data still needs controlled creation and periodic validation.
A team configured: Configure the supported dependent-CI approval and lifecycle handling path. Its original requirement was: A Data Manager policy runs on retired records but dependent application CIs require owner approval before cascade action. Which observation proves that the desired operational outcome was achieved?
Lifecycle cascades should not silently remove dependent records without approved controls This observation validates the required outcome, not just the presence of a configured feature.
Stewardship prevents uncoordinated changes to shared business context. It does not establish that the parent policy pauses or routes the dependent records for the designated review.
Traceable data changes preserve accountability for non-discoverable or manually governed CIs. It does not establish that the parent policy pauses or routes the dependent records for the designated review.
Governance requires clear decision rights and accountable remediation owners. It does not establish that the parent policy pauses or routes the dependent records for the designated review.
Two ServiceNow configuration issues require separate remedies. First: A query returns only the first-level server and misses downstream database dependencies. Second: A support engineer needs a visual path from an application service to its infrastructure dependencies. Select exactly TWO appropriate steps.
This resolves requirement B. Dependency visualization traverses relationship edges so potential impact is easier to understand Confirm it by testing: The view shows the application and the expected upstream infrastructure CIs
This resolves requirement A. Multihop relationship modeling is needed to evaluate complete service dependencies Confirm it by testing: A test service with a two-hop dependency returns all expected CIs
Dashboard measures should connect data quality to measurable operational outcomes.
Standardized service representation supports comparable portfolio and operations reporting.
Multisource preview exposes reported values alongside the current CMDB selection.
An audit evaluates the completed action: Apply class-node attribute filters and relationship conditions in CMDB Query Builder. It addressed the problem: A query should include only Windows servers in a specific data center connected to a selected application service. What evidence best demonstrates success?
Filters narrow graph results using attributes of different CI nodes This observation validates the required outcome, not just the presence of a configured feature.
ITSM workflows can use trustworthy configuration context for incident routing. It does not establish that the target data-center servers are returned and unrelated servers are excluded.
Compliance data requires completed audit evidence to make a trustworthy score. It does not establish that the target data-center servers are returned and unrelated servers are excluded.
Missing recent source activity can signal integration failure even when other feeds maintain the CI. It does not establish that the target data-center servers are returned and unrelated servers are excluded.
A CMDB administrator must resolve both independent failures: (1) Enterprise architects maintain a business capability map and plans for applications they may buy. (2) A service offering catalog describes customer support hours but engineers put it on a server CI. Which coordinated plan satisfies both requirements?
First: Design and Planning represents intended enterprise architecture, separate from runtime CIs Second: Service offerings describe consumable business commitments, not server hardware attributes Both verification criteria must be met: Capability reports show planned business application relationships without fictitious deployed instances The customer-visible offering holds the schedule and its underlying instances remain separate
Service offerings describe consumable business commitments, not server hardware attributes. The other proposed action (Adopt a phased approach starting with priority services and measurable outcomes) does not implement the first control. Design and Planning represents intended enterprise architecture, separate from runtime CIs.
Design and Planning represents intended enterprise architecture, separate from runtime CIs. The other proposed action (place operational application services in the Service Delivery part of CSDM) addresses a different operation. Service offerings describe consumable business commitments, not server hardware attributes.
Design and Planning represents intended enterprise architecture, separate from runtime CIs. Service offerings describe consumable business commitments, not server hardware attributes. The proposed steps (Adopt a phased approach starting with priority services and measurable outcomes; place operational application services in the Service Delivery part of CSDM) address other capabilities instead of this required pair.
After implementing the approved change — Use an import set and supported transform or IntegrationHub ETL pipeline that applies CI identification controls — the data steward needs proof that it fixed: An external inventory provides CSV files weekly and no ready connector exists. What should the steward observe?
Staging and mapping preserve input validation and can hand CI writes to supported IRE processing This observation validates the required outcome, not just the presence of a configured feature.
Hardware status mapping reflects asset lifecycle without treating unrelated CI fields as interchangeable. It does not establish that a representative file creates or updates only the intended CI records.
Reliable network maps depend on relationship creation and correctly identified endpoints. It does not establish that a representative file creates or updates only the intended CI records.
Processing order and endpoint matching prevent dangling or mismatched relationship references. It does not establish that a representative file creates or updates only the intended CI records.
Please check your mailbox for a message from support@examlabs.com and follow the directions.