CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A CMDB engineer applied the control: Use scoped CMDB Health inclusion rules for the intended principal CI population. This was meant to resolve: A health dashboard shows bad scores for lab CI classes that should not be evaluated. Which result most directly confirms the implementation works?
Appropriate class inclusion keeps operational KPIs from being diluted by irrelevant CI populations 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 the target KPI excludes the approved lab class while retaining production CIs.
Manual tasks allow reviewed consolidation when automatic detection does not create a task. It does not establish that the target KPI excludes the approved lab class while retaining production CIs.
A stocked asset can exist financially without a currently operating CI for production impact. It does not establish that the target KPI excludes the approved lab class while retaining production CIs.
After implementing the approved change — Restrict the policy to approved retired CI classes with prerequisite retirement definitions and review its evaluation — the data steward needs proof that it fixed: A Data Manager Delete policy unexpectedly targets active production databases. What should the steward observe?
Lifecycle deletion policies require eligibility and governance gates to avoid destructive bulk removal This observation validates the required outcome, not just the presence of a configured feature.
Orphan metrics reveal CIs no longer connected or useful under configured criteria. It does not establish that no active database is selected and only approved retired test records are eligible.
A stocked asset can exist financially without a currently operating CI for production impact. It does not establish that no active database is selected and only approved retired test records are eligible.
Fresh timestamps do not prove that a human has validated business ownership. It does not establish that no active database is selected and only approved retired test records are eligible.
A configuration management team must address: An enterprise application cannot be discovered by conventional infrastructure scanning but has a supported cloud API inventory. What change should it implement to demonstrate this result: The non-scannable application CI is updated from the authoritative API inventory?
Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs The proposed control addresses the stated problem, and its acceptance check is: The non-scannable application CI is updated from the authoritative API inventory
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: Use a supported connector or governed API-based ingestion to populate that CI type
Relationship records encode application dependencies beyond the CI attributes themselves. It does not implement the specific required change for this case; the suitable control is: Use a supported connector or governed API-based ingestion to populate that CI type
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 supported connector or governed API-based ingestion to populate that CI type
A ServiceNow Data Foundations rollout has two blockers. First: A dependency is reversed, showing the database as hosted by a frontend application. Second: A sensitive cloud account identifier must be tracked alongside the appropriate business and technical CSDM objects. Which complete two-part implementation addresses both?
First: Relationship direction matters for accurate dependency traversals and service modeling Second: Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes Both verification criteria must be met: Dependency traversal follows the intended application-to-database path A compliance query retrieves the proper owned service and associated identifier
Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes. 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 (ingest or construct relationship payloads with resolvable parent and child CIs) addresses a different operation. Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes.
Relationship direction matters for accurate dependency traversals and service modeling. Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes. The proposed steps (Configure the appropriate Asset State to CI Hardware Status mapping and permitted sync direction; ingest or construct relationship payloads with resolvable parent and child CIs) address other capabilities instead of this required pair.
A data governance release must meet both conditions: A: A query returns only the first-level server and misses downstream database dependencies. B: A change advisory board needs to identify downstream services affected by a database replacement. Select the TWO necessary actions.
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
This resolves requirement B. Linked CI dependencies reveal potential blast radius before infrastructure changes Confirm it by testing: The test database change lists its genuinely dependent services for review
Standardized service representation supports comparable portfolio and operations reporting.
Multisource preview exposes reported values alongside the current CMDB selection.
Dashboard measures should connect data quality to measurable operational outcomes.
The change record states that the team will: Apply the appropriate Delete CMDB Related Entry policy after checking related table references. The original defect was: A team wishes to delete non-CMDB records orphaned after retired CI cleanup. Which validation finding should be accepted?
Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself This observation validates the required outcome, not just the presence of a configured feature.
Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI. It does not establish that only the approved dangling related entries are deleted while active references remain.
Similar display names alone do not establish identical physical or logical identity. It does not establish that only the approved dangling related entries are deleted while active references remain.
Compliance results depend on audit conditions and executed evidence rather than field population alone. It does not establish that only the approved dangling related entries are deleted while active references remain.
An implementation review finds these independent issues: (1) A team wants server support group to affect completeness but does not want it required by the dictionary. (2) The same hardware CI alternates between In Use and Retired after two different feeds run. Which TWO controls should the team apply?
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. Lifecycle governance must coordinate source reconciliation and asset state to prevent conflicting updates Confirm it by testing: Repeated import cycles preserve the reviewed hardware lifecycle state
An aggregate score becomes useful when failures are traceable to actionable work items.
A stocked asset can exist financially without a currently operating CI for production impact.
Governance requires clear decision rights and accountable remediation owners.
A CMDB program needs two changes. Requirement A: An orphan correctness indicator flags decommissioned CIs still in scope. Requirement B: A governance team proposes deleting every CI not seen by a discovery scan even when some are manually maintained contracts. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement B. Absence from infrastructure scanning alone is insufficient evidence for deleting a governed manual CI Confirm it by testing: Manual business records remain while truly stale discoverable infrastructure enters review
This resolves requirement A. Orphan metrics reveal CIs no longer connected or useful under configured criteria Confirm it by testing: Confirmed orphan CIs are assigned to remediation without deleting needed active objects
Reusable templates provide consistent merge decisions across many de-duplication tasks.
Fresh timestamps do not prove that a human has validated business ownership.
Direct record deletion can leave broken or incomplete related records.
During a CMDB review, engineers discover: A weekly review shows one inventory feed stopped sending data without deleting the existing CIs. Which proposed action is appropriate if success is measured by: The stopped feed appears in the issue list while current feeds remain healthy?
Missing recent source activity can signal integration failure even when other feeds maintain the CI The proposed control addresses the stated problem, and its acceptance check is: The stopped feed appears in the issue list while current feeds remain healthy
Standardized service representation supports comparable portfolio and operations reporting. It does not implement the specific required change for this case; the suitable control is: Monitor CMDB 360 'not reported by source' potential issues and reporting intervals
Impact analysis uses directed dependencies to identify affected services. It does not implement the specific required change for this case; the suitable control is: Monitor CMDB 360 'not reported by source' potential issues and reporting intervals
Multihop relationship modeling is needed to evaluate complete service dependencies. It does not implement the specific required change for this case; the suitable control is: Monitor CMDB 360 'not reported by source' potential issues and reporting intervals
During a CMDB review, engineers discover: An executive wants a quick breakdown of where CMDB stewardship should focus first. Which proposed action is appropriate if success is measured by: The report identifies the poorest-quality principal classes and a prioritized action?
Foundation indicators make recurring quality gaps visible and link them to improvement actions The proposed control addresses the stated problem, and its acceptance check is: The report identifies the poorest-quality principal classes and a prioritized action
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: Review the CMDB Data Foundations Dashboard indicators and associated remediation guidance
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: Review the CMDB Data Foundations Dashboard indicators and associated remediation guidance
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: Review the CMDB Data Foundations Dashboard indicators and associated remediation guidance
A data steward is asked to resolve: A team models every CI as Depends on instead of choosing the correct relationship semantics. Which solution meets the requirement and verifies: A reviewed service graph shows appropriate typed edges rather than one indiscriminate relationship?
Relationship types distinguish hosting, containment, and dependencies for impact and service maps The proposed control addresses the stated problem, and its acceptance check is: A reviewed service graph shows appropriate typed edges rather than one indiscriminate relationship
Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes. It does not implement the specific required change for this case; the suitable control is: Apply suitable suggested relationship types and governance review for each involved CI class
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: Apply suitable suggested relationship types and governance review for each involved CI class
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: Apply suitable suggested relationship types and governance review for each involved CI class
Please check your mailbox for a message from support@examlabs.com and follow the directions.