CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A team configured: Use CI Class Manager to classify the records under an appropriate derived Linux Server class and its class-specific attributes. Its original requirement was: A virtualization team created Linux servers under the generic Computer class and cannot report Linux-only attributes. Which observation proves that the desired operational outcome was achieved?
A derived CMDB class inherits applicable parent fields while distinguishing a more precise CI type This observation validates the required outcome, not just the presence of a configured feature.
CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. It does not establish that linux-specific reports include migrated server CIs without mixing desktop computers.
More specialized CI class rules can be chosen to identify specific subclasses accurately. It does not establish that linux-specific reports include migrated server CIs without mixing desktop computers.
Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute. It does not establish that linux-specific reports include migrated server CIs without mixing desktop computers.
An organization finds this data-foundation problem: A query returns only the first-level server and misses downstream database dependencies. Which approach best achieves the required outcome: A test service with a two-hop dependency returns all expected CIs?
Multihop relationship modeling is needed to evaluate complete service dependencies The proposed control addresses the stated problem, and its acceptance check is: A test service with a two-hop dependency returns all expected CIs
Standardized service representation supports comparable portfolio and operations reporting. It does not implement the specific required change for this case; the suitable control is: Expand the graph traversal to include the necessary intermediate and target CI relationships
Dashboard measures should connect data quality to measurable operational outcomes. It does not implement the specific required change for this case; the suitable control is: Expand the graph traversal to include the necessary intermediate and target CI relationships
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: Expand the graph traversal to include the necessary intermediate and target CI relationships
A ServiceNow configuration project has two acceptance conditions. The first issue is: A query returns only the first-level server and misses downstream database dependencies. The second is: An executive wants a quick breakdown of where CMDB stewardship should focus first. Which paired approach is suitable?
First: Multihop relationship modeling is needed to evaluate complete service dependencies Second: Foundation indicators make recurring quality gaps visible and link them to improvement actions Both verification criteria must be met: A test service with a two-hop dependency returns all expected CIs The report identifies the poorest-quality principal classes and a prioritized action
Multihop relationship modeling is needed to evaluate complete service dependencies. Foundation indicators make recurring quality gaps visible and link them to improvement actions. The proposed steps (Compare relevant health/ownership indicators with observed incident routing or impact analysis outcomes; open CMDB 360 Multisource Data Preview for the CI attribute) address other capabilities instead of this required pair.
Multihop relationship modeling is needed to evaluate complete service dependencies. The other proposed action (open CMDB 360 Multisource Data Preview for the CI attribute) addresses a different operation. Foundation indicators make recurring quality gaps visible and link them to improvement actions.
Foundation indicators make recurring quality gaps visible and link them to improvement actions. The other proposed action (Compare relevant health/ownership indicators with observed incident routing or impact analysis outcomes) does not implement the first control. Multihop relationship modeling is needed to evaluate complete service dependencies.
Two ServiceNow configuration issues require separate remedies. First: A service owner needs all database servers used by one application and their hosting Linux machines. Second: A dashboard must compare two cloud inventory sources to reveal CIs absent from one feed. Select exactly TWO appropriate steps.
This resolves requirement A. A relationship-aware query traverses edges rather than filtering only a flat CI list Confirm it by testing: The saved query returns all matching application, database and Linux server paths
This resolves requirement B. A gap query reports mismatched source coverage rather than merely comparing displayed names Confirm it by testing: The seeded one-source-only CI is returned and fully covered CIs are excluded
Compliance data requires completed audit evidence to make a trustworthy score.
Standardized service representation supports comparable portfolio and operations reporting.
Dashboard measures should connect data quality to measurable operational outcomes.
A data steward is asked to resolve: Stale active servers should first be marked retired rather than immediately removed from CMDB. Which solution meets the requirement and verifies: The stale test server reaches the retired state and is still recoverable for review?
Retire policies transition eligible active CIs before downstream archive or deletion The proposed control addresses the stated problem, and its acceptance check is: The stale test server reaches the retired state and is still recoverable for review
Fresh timestamps do not prove that a human has validated business ownership. It does not implement the specific required change for this case; the suitable control is: Use a Data Manager Retire policy with reviewed class and age conditions
Similar display names alone do not establish identical physical or logical identity. It does not implement the specific required change for this case; the suitable control is: Use a Data Manager Retire policy with reviewed class and age conditions
Direct record deletion can leave broken or incomplete related records. It does not implement the specific required change for this case; the suitable control is: Use a Data Manager Retire policy with reviewed class and age conditions
A CMDB change request reports: An administrator changes reconciliation priorities but assumes old CMDB values will instantly reflect the new rules. Select the best implementation. It must pass this acceptance test: The selected CI value changes only as justified by configured source data and the tested recomputation.
Reconciliation rule changes can require reevaluation of existing attribute choices The proposed control addresses the stated problem, and its acceptance check is: The selected CI value changes only as justified by configured source data and the tested recomputation
Suggested relationships guide consistent relationship selection without making every pairing physically true. It does not implement the specific required change for this case; the suitable control is: Use preview or recompute where supported and verify the result against source history
Child-level attributes scope specialized fields to the correct extension class. It does not implement the specific required change for this case; the suitable control is: Use preview or recompute where supported and verify the result against source history
Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported. It does not implement the specific required change for this case; the suitable control is: Use preview or recompute where supported and verify the result against source history
A ServiceNow implementation team encounters this issue: An implementation team wants the same service identifiers used in ITSM incidents and portfolio dashboards. Which control most directly resolves the issue and produces this outcome: An incident and a portfolio view reference the same authoritative service identifier?
Shared CSDM objects reduce semantic drift across workflows and reporting The proposed control addresses the stated problem, and its acceptance check is: An incident and a portfolio view reference the same authoritative service identifier
Strategy records concern proposed opportunities before detailed architecture or delivery. It does not implement the specific required change for this case; the suitable control is: Establish stable service records and correct CSDM links instead of copying separate spreadsheet services
Build and Integration represents build-phase components before delivery operations. It does not implement the specific required change for this case; the suitable control is: Establish stable service records and correct CSDM links instead of copying separate spreadsheet services
Portfolio governance spans CSDM domains rather than duplicating their objects. It does not implement the specific required change for this case; the suitable control is: Establish stable service records and correct CSDM links instead of copying separate spreadsheet services
A CMDB program needs two changes. Requirement A: The governance team needs a recommended support group field for one class without making it universally mandatory. Requirement B: The operations dashboard should list devices present in Discovery but missing from a second inventory feed. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement A. Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles Confirm it by testing: The class receives a recommended-field completeness score while record creation is not globally blocked
This resolves requirement B. Multisource gap queries identify CIs not reported by one or more participating data sources Confirm it by testing: The missing-source inventory lists the seeded device and excludes a device reported by both feeds
Per-source reporting timestamps help detect coverage gaps even when a CI has historical data.
IRE identifies a new CI for insertion while reconciliation governs source-authorized updates to an existing CI.
More specialized CI class rules can be chosen to identify specific subclasses accurately.
A CMDB administrator must resolve both independent failures: (1) Servers remain active in CMDB although their last discovery time is older than the agreed threshold. (2) A Data Manager policy runs on retired records but dependent application CIs require owner approval before cascade action. Which coordinated plan satisfies both requirements?
First: Staleness evaluates the recency of reported CI updates or discovery according to its rules Second: Lifecycle cascades should not silently remove dependent records without approved controls Both verification criteria must be met: Expired server records are flagged and newly refreshed servers clear the staleness rule The parent policy pauses or routes the dependent records for the designated review
Staleness evaluates the recency of reported CI updates or discovery according to its rules. The other proposed action (investigate and repair orphan relationships in the relationship health results) addresses a different operation. Lifecycle cascades should not silently remove dependent records without approved controls.
Staleness evaluates the recency of reported CI updates or discovery according to its rules. Lifecycle cascades should not silently remove dependent records without approved controls. The proposed steps (Define a service owner approval and change-control process for governed naming updates; investigate and repair orphan relationships in the relationship health results) address other capabilities instead of this required pair.
Lifecycle cascades should not silently remove dependent records without approved controls. The other proposed action (Define a service owner approval and change-control process for governed naming updates) does not implement the first control. Staleness evaluates the recency of reported CI updates or discovery according to its rules.
A ServiceNow configuration project has two acceptance conditions. The first issue is: CMDB health completeness is low because most Windows servers are missing a mandatory owned-by field. The second is: A new CMDB program imports every discovered object before deciding which services it supports. Which paired approach is suitable?
First: Completeness Required measures required-field population for eligible CIs Second: A scoped initial data foundation is easier to govern than an unactionable inventory Both verification criteria must be met: Required completeness improves after the sampled Windows servers receive approved owners The selected classes serve the defined use cases and have health acceptance criteria
A scoped initial data foundation is easier to govern than an unactionable inventory. The other proposed action (Use a Data Manager Attestation policy assigned to the accountable reviewers) does not implement the first control. Completeness Required measures required-field population for eligible CIs.
Completeness Required measures required-field population for eligible CIs. The other proposed action (configure a Data Manager Archive policy and the required retirement definition for eligible classes) addresses a different operation. A scoped initial data foundation is easier to govern than an unactionable inventory.
Completeness Required measures required-field population for eligible CIs. A scoped initial data foundation is easier to govern than an unactionable inventory. The proposed steps (Use a Data Manager Attestation policy assigned to the accountable reviewers; configure a Data Manager Archive policy and the required retirement definition for eligible classes) address other capabilities instead of this required pair.
After implementing the approved change — Inspect the class hierarchy and inherited attributes in CI Class Manager — the data steward needs proof that it fixed: The operations team cannot see where Database Server inherits its mandatory CI fields. What should the steward observe?
Class definitions inherit metadata from ancestor CI tables, with class-level overrides where supported This observation validates the required outcome, not just the presence of a configured feature.
Multisource gap queries identify CIs not reported by one or more participating data sources. It does not establish that the administrator identifies which parent supplies each required field before making a change.
Dynamic reconciliation can select values using multisource data and takes precedence over a static rule on the same attribute. It does not establish that the administrator identifies which parent supplies each required field before making a change.
Reconciliation rule changes can require reevaluation of existing attribute choices. It does not establish that the administrator identifies which parent supplies each required field before making a change.
Please check your mailbox for a message from support@examlabs.com and follow the directions.