CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
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
A configuration management team must address: A CMDB user can view saved graph queries but is not allowed to author new queries. What change should it implement to demonstrate this result: The analyst runs approved queries but cannot modify their definitions?
Query access roles distinguish executing saved queries from creating and changing them The proposed control addresses the stated problem, and its acceptance check is: The analyst runs approved queries but cannot modify their definitions
Dependency visualization traverses relationship edges so potential impact is easier to understand. It does not implement the specific required change for this case; the suitable control is: Grant the documented query-builder read role rather than the authoring role
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: Grant the documented query-builder read role rather than the authoring role
Security and vulnerability workflows gain useful prioritization from trusted service dependencies. It does not implement the specific required change for this case; the suitable control is: Grant the documented query-builder read role rather than the authoring role
The change record states that the team will: Model supported CMDB CIs and relationships rather than assuming arbitrary tables appear in CI maps. The original defect was: A team sees a server icon in Dependency View but expects it to expose non-CMDB records unrelated to cmdb_ci. Which validation finding should be accepted?
Dependency views operate on supported CMDB class and relationship information This observation validates the required outcome, not just the presence of a configured feature.
Query access roles distinguish executing saved queries from creating and changing them. It does not establish that non-CMDB records remain outside the CI graph and modeled CIs render correctly.
Missing recent source activity can signal integration failure even when other feeds maintain the CI. It does not establish that non-CMDB records remain outside the CI graph and modeled CIs render correctly.
Security and vulnerability workflows gain useful prioritization from trusted service dependencies. It does not establish that non-CMDB records remain outside the CI graph and modeled CIs render correctly.
During a CMDB review, engineers discover: Two sources insert separate server CIs because hostname alone is not a stable unique key. Which proposed action is appropriate if success is measured by: 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 proposed control addresses the stated problem, and its acceptance check is: Two payloads for the same server resolve to one existing CI during the test
CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. It does not implement the specific required change for this case; the suitable control is: Refine the applicable CI identification rule with reliable class-appropriate identifiers and test it in the IRE simulator
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. It does not implement the specific required change for this case; the suitable control is: Refine the applicable CI identification rule with reliable class-appropriate identifiers and test it in the IRE simulator
Per-source reporting timestamps help detect coverage gaps even when a CI has historical data. It does not implement the specific required change for this case; the suitable control is: Refine the applicable CI identification rule with reliable class-appropriate identifiers and test it in the IRE simulator
A data governance release must meet both conditions: A: A duplicate server task contains competing IP values and two incident histories. B: A team wishes to delete non-CMDB records orphaned after retired CI cleanup. Select the TWO necessary actions.
This resolves requirement A. 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
This resolves requirement B. Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself Confirm it by testing: Only the approved dangling related entries are deleted while active references remain
Data-source coverage failures can cause stale CI results that should not be hidden by score adjustments.
Automated lifecycle governance reconciles discovered existence with administrative approval.
A stocked asset can exist financially without a currently operating CI for production impact.
An implementation review finds these independent issues: (1) A health dashboard shows bad scores for lab CI classes that should not be evaluated. (2) An incident assignment group is missing on many production database CIs. Which TWO controls should the team apply?
This resolves requirement A. Appropriate class inclusion keeps operational KPIs from being diluted by irrelevant CI populations Confirm it by testing: The target KPI excludes the approved lab class while retaining production CIs
This resolves requirement B. Reliable CI ownership fields enable routing and operational accountability Confirm it by testing: A test incident is directed to the intended database support group
Direct record deletion can leave broken or incomplete related records.
Reusable templates provide consistent merge decisions across many de-duplication tasks.
Retire policies transition eligible active CIs before downstream archive or deletion.
A team configured: Use an appropriate CMDB 360 saved query such as Find Gap comparing the two discovery sources. Its original requirement was: The operations dashboard should list devices present in Discovery but missing from a second inventory feed. Which observation proves that the desired operational outcome was achieved?
Multisource gap queries identify CIs not reported by one or more participating data sources This observation validates the required outcome, not just the presence of a configured feature.
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type. It does not establish that the missing-source inventory lists the seeded device and excludes a device reported by both feeds.
IRE data-source rules can control CI insertion separately from updating existing identified records. It does not establish that the missing-source inventory lists the seeded device and excludes a device reported by both feeds.
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. It does not establish that the missing-source inventory lists the seeded device and excludes a device reported by both feeds.
The change record states that the team will: Compare relevant health/ownership indicators with observed incident routing or impact analysis outcomes. The original defect was: A CIO wants to know whether CMDB data improvements are delivering value to incident response. Which validation finding should be accepted?
Dashboard measures should connect data quality to measurable operational outcomes This observation validates the required outcome, not just the presence of a configured feature.
Saved queries preserve graph semantics and can support repeatable consumption. It does not establish that the sampled incidents route more accurately after governed CI ownership remediation.
Security and vulnerability workflows gain useful prioritization from trusted service dependencies. It does not establish that the sampled incidents route more accurately after governed CI ownership remediation.
Multisource preview exposes reported values alongside the current CMDB selection. It does not establish that the sampled incidents route more accurately after governed CI ownership remediation.
A configuration management team must address: A security team wants to prioritize vulnerable servers by their business criticality. What change should it implement to demonstrate this result: A critical service server is scored higher than a noncritical isolated lab server under the tested criteria?
Security and vulnerability workflows gain useful prioritization from trusted service dependencies The proposed control addresses the stated problem, and its acceptance check is: A critical service server is scored higher than a noncritical isolated lab server under the tested criteria
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: Link correctly identified server CIs to their business services and ownership data
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: Link correctly identified server CIs to their business services and ownership data
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: Link correctly identified server CIs to their business services and ownership data
A CMDB program needs two changes. Requirement A: A new dependent CI class fails identification because its hosting relationship is unavailable in the payload. Requirement B: A sensitive cloud account identifier must be tracked alongside the appropriate business and technical CSDM objects. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement B. Compliance identifiers require a controlled relationship to the relevant CI or service instead of free-form unrelated notes Confirm it by testing: A compliance query retrieves the proper owned service and associated identifier
This resolves requirement A. Dependent identification may rely on relationships to identify CIs within a parent context Confirm it by testing: The dependent CI matches its existing record when the required parent relationship is supplied
A correct source mapping is needed before identifier rules can classify incoming device records.
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies.
A governed ETL pipeline maps source schemas to class attributes and relationships.
A data governance release must meet both conditions: A: A web application CI has no dependency link to its database and impact analysis misses downstream failures. B: A branch network has thousands of reachable devices whose hardware properties change daily. Select the TWO necessary actions.
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. Relationship records encode application dependencies beyond the CI attributes themselves Confirm it by testing: A dependency view now traverses from the application to the correct database CI
Assets track financial and ownership lifecycle while CIs represent service configuration and operational dependencies.
Processing order and endpoint matching prevent dangling or mismatched relationship references.
Integration choice should reflect whether reliable source data comes from discovery protocols or product APIs.
Please check your mailbox for a message from support@examlabs.com and follow the directions.