CIS-DF Premium File
- 283 Questions & Answers
- Last Update: Nov 14, 2026
A ServiceNow configuration project has two acceptance conditions. The first issue is: The governance team needs a recommended support group field for one class without making it universally mandatory. The second is: A data steward needs to know which source last updated a reconciled CI attribute. Which paired approach is suitable?
First: Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles Second: Attribute-level history identifies the source of accepted updates after applicable rules are enabled Both verification criteria must be met: The class receives a recommended-field completeness score while record creation is not globally blocked The steward traces the selected CI value to the permitted discovery source
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. The other proposed action (define and validate a child-class identification rule instead of relying on an unsuitable inherited parent rule) addresses a different operation. Attribute-level history identifies the source of accepted updates after applicable rules are enabled.
Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. Attribute-level history identifies the source of accepted updates after applicable rules are enabled. The proposed steps (Review CMDB 360 potential issues for CIs not recently reported by configured sources; define and validate a child-class identification rule instead of relying on an unsuitable inherited parent rule) address other capabilities instead of this required pair.
Attribute-level history identifies the source of accepted updates after applicable rules are enabled. The other proposed action (Review CMDB 360 potential issues for CIs not recently reported by configured sources) does not implement the first control. Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles.
The change record states that the team will: Assign an authoritative support group or enrich it from governed relationships. The original defect was: An incident assignment group is missing on many production database CIs. Which validation finding should be accepted?
Reliable CI ownership fields enable routing and operational accountability This observation validates the required outcome, not just the presence of a configured feature.
Archive, Retire and Delete policy types can require class-specific active retirement definitions. It does not establish that a test incident is directed to the intended database support group.
Reusable templates provide consistent merge decisions across many de-duplication tasks. It does not establish that a test incident is directed to the intended database support group.
The six familiar CI metrics explain why an aggregate health score changes, while relationship metrics can be analyzed separately. It does not establish that a test incident is directed to the intended database support group.
A ServiceNow configuration project has two acceptance conditions. The first issue is: A web application CI has no dependency link to its database and impact analysis misses downstream failures. The second is: Finance changes asset acquisition cost and expects manual reversal from the CI to rewrite the purchase ledger. Which paired approach is suitable?
First: Relationship records encode application dependencies beyond the CI attributes themselves Second: Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings Both verification criteria must be met: A dependency view now traverses from the application to the correct database CI Asset cost updates the CI view but CI-only changes do not overwrite authoritative asset cost
Relationship records encode application dependencies beyond the CI attributes themselves. Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings. The proposed steps (Use a supported connector or governed API-based ingestion to populate that CI type; stage relationships until their parent and child CIs are resolved then load them via a supported path) address other capabilities instead of this required pair.
Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings. The other proposed action (Use a supported connector or governed API-based ingestion to populate that CI type) does not implement the first control. Relationship records encode application dependencies beyond the CI attributes themselves.
Relationship records encode application dependencies beyond the CI attributes themselves. The other proposed action (stage relationships until their parent and child CIs are resolved then load them via a supported path) addresses a different operation. Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings.
A ServiceNow configuration project has two acceptance conditions. The first issue is: A new service CI class needs suggested parent-child relationship types visible to its modelers. The second is: Cloud inventory and Discovery report different operating system versions for the same CI. Which paired approach is suitable?
First: Suggested relationships guide consistent relationship selection without making every pairing physically true Second: CMDB 360 retains visibility into competing reported attributes rather than showing only the final field Both verification criteria must be met: The relationship editor proposes the intended type for a compatible parent-child pair The reviewer sees both source values and identifies the currently selected value
CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. The other proposed action (Use preview or recompute where supported and verify the result against source history) does not implement the first control. Suggested relationships guide consistent relationship selection without making every pairing physically true.
Suggested relationships guide consistent relationship selection without making every pairing physically true. CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. The proposed steps (Use preview or recompute where supported and verify the result against source history; add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition) address other capabilities instead of this required pair.
Suggested relationships guide consistent relationship selection without making every pairing physically true. The other proposed action (add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition) addresses a different operation. CMDB 360 retains visibility into competing reported attributes rather than showing only the final field.
A ServiceNow configuration project has two acceptance conditions. The first issue is: Product managers track strategic product ideas before any technology build is approved. The second is: A program measures CSDM success by number of created rows alone despite low service ownership coverage. Which paired approach is suitable?
First: Strategy records concern proposed opportunities before detailed architecture or delivery Second: CSDM's value is service context and usability, not raw CI volume Both verification criteria must be met: An unapproved idea is visible in strategic planning but not misrepresented as a deployed service The adoption report shows verified owners and valid links for the priority services
Strategy records concern proposed opportunities before detailed architecture or delivery. The other proposed action (model shared reference entities in the CSDM Foundation domain) addresses a different operation. CSDM's value is service context and usability, not raw CI volume.
Strategy records concern proposed opportunities before detailed architecture or delivery. CSDM's value is service context and usability, not raw CI volume. The proposed steps (Establish foundational reference and ownership data before expanding to advanced service maps; model shared reference entities in the CSDM Foundation domain) address other capabilities instead of this required pair.
CSDM's value is service context and usability, not raw CI volume. The other proposed action (Establish foundational reference and ownership data before expanding to advanced service maps) does not implement the first control. Strategy records concern proposed opportunities before detailed architecture or delivery.
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) An executive requests one CMDB health score but support teams need practical remediation actions. 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. An aggregate score becomes useful when failures are traceable to actionable work items Confirm it by testing: Each critical failed metric has a named owner, affected CI sample and due date
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets.
Traceable data changes preserve accountability for non-discoverable or manually governed CIs.
Governance decisions should translate into technical rules preventing unapproved overwrites.
Two ServiceNow configuration issues require separate remedies. First: A dependency is reversed, showing the database as hosted by a frontend application. Second: A team assumes changing CI Install Status automatically updates Hardware Status for the same computer. Select exactly TWO appropriate steps.
This resolves requirement B. Install Status and Hardware Status are independent fields rather than automatic mirrors of each other Confirm it by testing: A status change affects only the mapped field and not an unrelated status field
This resolves requirement A. Relationship direction matters for accurate dependency traversals and service modeling Confirm it by testing: Dependency traversal follows the intended application-to-database path
Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle.
Hardware status mapping reflects asset lifecycle without treating unrelated CI fields as interchangeable.
Supported connectors reduce custom upgrade debt and integrate source identification.
A data governance release must meet both conditions: A: CI relationships are sourced from an external dependency feed but endpoints arrive in a later batch. B: Finance changes asset acquisition cost and expects manual reversal from the CI to rewrite the purchase ledger. Select the TWO necessary actions.
This resolves requirement A. Processing order and endpoint matching prevent dangling or mismatched relationship references Confirm it by testing: All staged edges resolve to existing CIs after both ingestion batches complete
This resolves requirement B. Cost synchronization is one-way from asset to CI, unlike certain bidirectional location or model mappings Confirm it by testing: Asset cost updates the CI view but CI-only changes do not overwrite authoritative asset cost
Relationship records encode application dependencies beyond the CI attributes themselves.
Asset synchronization requires logical linkage between a physical asset and its technical CI.
Supported connectors reduce custom upgrade debt and integrate source identification.
A CMDB program needs two changes. Requirement A: CMDB health completeness is low because most Windows servers are missing a mandatory owned-by field. Requirement B: A CMDB steward wants to certify a critical CI's business owner field rather than merely mark it updated recently. Select exactly TWO actions that jointly satisfy the requirements.
This resolves requirement A. Completeness Required measures required-field population for eligible CIs Confirm it by testing: Required completeness improves after the sampled Windows servers receive approved owners
This resolves requirement B. Fresh timestamps do not prove that a human has validated business ownership Confirm it by testing: The responsible person signs off on the current owner value with dated evidence
Data Manager can manage irrelevant records linked to now-removed CIs separately from CI lifecycle itself.
Attestation asks an accountable person to verify CI data at a defined interval.
Stewardship prevents uncoordinated changes to shared business context.
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) Cloud instances are regularly terminated but their old CMDB records are still active after three months. Which TWO controls should the team apply?
This resolves requirement B. Automated lifecycle governance reconciles discovered existence with administrative approval Confirm it by testing: Confirmed terminated instances no longer appear as active configuration items
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
Improved identification prevents future collisions but does not retroactively merge every old duplicate.
Remediation tooling can restrict available reconciliation functions for oversized duplicate sets.
Traceable data changes preserve accountability for non-discoverable or manually governed CIs.
A CMDB change request reports: A reporting team needs all servers last reported by a particular source with a particular OS family. Select the best implementation. It must pass this acceptance test: The report lists matching discovered servers while excluding other sources.
Multisource records queries enable source-specific inventory reporting The proposed control addresses the stated problem, and its acceptance check is: The report lists matching discovered servers while excluding other sources
Compliance data requires completed audit evidence to make a trustworthy score. It does not implement the specific required change for this case; the suitable control is: Use a CMDB 360 Get Records saved query with appropriate source and attribute filters
Impact analysis uses directed dependencies to identify affected services. It does not implement the specific required change for this case; the suitable control is: Use a CMDB 360 Get Records saved query with appropriate source and attribute filters
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: Use a CMDB 360 Get Records saved query with appropriate source and attribute filters
Please check your mailbox for a message from support@examlabs.com and follow the directions.