McAfee Secure

Exam Code: CIS-DF

Exam Name: Certified Implementation Specialist - Data Foundations (CMDB and CSDM)

Certification Provider: ServiceNow

Corresponding Certification: CIS-DF (CMDB and CSDM)

ServiceNow CIS-DF Questions & Answers

Study with Up-To-Date REAL Exam Questions and Answers from the ACTUAL Test

283 Questions & Answers with Testing Engine

"Certified Implementation Specialist - Data Foundations (CMDB and CSDM) Exam", also known as CIS-DF exam, is a ServiceNow certification exam.

Pass your tests with the always up-to-date CIS-DF Exam Engine. Your CIS-DF training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

ServiceNow CIS-DF Practice Test 34

Question 330

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?

  1. (1) Configure a class-specific recommended field through CI Class Manager health settings; (2) define and validate a child-class identification rule instead of relying on an unsuitable inherited parent rule
  2. (1) Review CMDB 360 potential issues for CIs not recently reported by configured sources; (2) define and validate a child-class identification rule instead of relying on an unsuitable inherited parent rule
  3. (1) Configure a class-specific recommended field through CI Class Manager health settings; (2) review the CMDB 360 Multisource Data Preview and the configured reconciliation/data-source history records under the CI and relevant attribute
  4. (1) Review CMDB 360 potential issues for CIs not recently reported by configured sources; (2) review the CMDB 360 Multisource Data Preview and the configured reconciliation/data-source history records under the CI and relevant attribute

Explanation

Correct Answer

C:

Both controls are required. For condition (1), configure a class-specific recommended field through CI Class Manager health settings. Recommended completeness checks and dictionary-level mandatory fields have different enforcement roles. Verify: The class receives a recommended-field completeness score while record creation is not globally blocked. For condition (2), review the CMDB 360 Multisource Data Preview and the configured reconciliation/data-source history records under the CI and relevant attribute. CMDB 360 shows per-source reported values and the current CMDB selection; data-source history depends on actual source reporting and reconciliation configuration, not merely on a populated CI display field. Verify independently: The steward can inspect the competing reported attribute values, identify the selected CMDB value and corroborate its source history.

Incorrect Answers

A:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: A child network-device class needs stricter identification than its broad parent network class. It should instead use: Review the CMDB 360 Multisource Data Preview and the configured reconciliation/data-source history records under the CI and relevant attribute. Both required outcomes must be verified separately.

B:

Part (1) answers a different need: A source stopped reporting network devices three weeks ago even though their CIs still exist. It should instead use: Configure a class-specific recommended field through CI Class Manager health settings. Part (2) answers a different need: A child network-device class needs stricter identification than its broad parent network class. It should instead use: Review the CMDB 360 Multisource Data Preview and the configured reconciliation/data-source history records under the CI and relevant attribute. Both required outcomes must be verified separately.

D:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: A source stopped reporting network devices three weeks ago even though their CIs still exist. It should instead use: Configure a class-specific recommended field through CI Class Manager health settings. Both required outcomes must be verified separately.

Question 331

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?

  1. The target class accepts the valid Archive policy after retirement definition activation, and an unretired test CI remains outside archival eligibility
  2. Sampled tasks keep their approved main CI and relationship settings after the batch
  3. The monthly scorecard attributes changes to individual CI submetrics and distinct relationship-health failures rather than hiding both in a single blended score
  4. A test incident is directed to the intended database support group

Explanation

Correct Answer

D:

This observation directly validates the implemented control. Reliable CI ownership fields enable routing and operational accountability. The decisive expected result is: A test incident is directed to the intended database support group.

Incorrect Answers

A:

“The target class accepts the valid Archive policy after retirement definition activation, and an unretired test CI remains outside archival eligibility” could occur while the stated failure remains unresolved. It tests: Data Manager Retire, Archive and Delete policy types require an active class retirement definition; Archive further acts on records evaluated as retired before policy filters are applied. The required validation instead is “A test incident is directed to the intended database support group”, because reliable CI ownership fields enable routing and operational accountability.

B:

This checks a different technical dependency: Reusable templates provide consistent merge decisions across many de-duplication tasks. The case requires proof of “A test incident is directed to the intended database support group”, which establishes the relevant condition: Reliable CI ownership fields enable routing and operational accountability.

C:

That observation would verify a control associated with: The monthly scorecard attributes changes to individual CI submetrics and distinct relationship-health failures rather than hiding both in a single blended score. It does not establish the needed acceptance outcome. The direct evidence is “A test incident is directed to the intended database support group”, testing: Reliable CI ownership fields enable routing and operational accountability.

Question 332

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?

  1. (1) Use a supported connector or governed API-based ingestion to populate that CI type; (2) stage relationships until their parent and child CIs are resolved then load them via a supported path
  2. (1) Use a supported connector or governed API-based ingestion to populate that CI type; (2) maintain acquisition Cost as the authoritative asset value and validate the supported one-way Asset-to-CI Cost synchronization instead of editing the CI to overwrite the purchase record
  3. (1) Create the correctly directed CI relationship with the appropriate relationship type; (2) maintain acquisition Cost as the authoritative asset value and validate the supported one-way Asset-to-CI Cost synchronization instead of editing the CI to overwrite the purchase record
  4. (1) Create the correctly directed CI relationship with the appropriate relationship type; (2) stage relationships until their parent and child CIs are resolved then load them via a supported path

Explanation

Correct Answer

C:

Both controls are required. For condition (1), create the correctly directed CI relationship with the appropriate relationship type. Relationship records encode application dependencies beyond the CI attributes themselves. Verify: A dependency view now traverses from the application to the correct database CI. For condition (2), maintain acquisition Cost as the authoritative asset value and validate the supported one-way Asset-to-CI Cost synchronization instead of editing the CI to overwrite the purchase record. ServiceNow Asset–CI synchronization permits many mapped attributes in both directions, but the Cost field is informational on the CI and is synchronized only from Asset to CI. Verify independently: Changing asset Cost updates the linked CI cost display; editing the CI cost does not change the authoritative asset Cost.

Incorrect Answers

A:

Part (1) answers a different need: An enterprise application cannot be discovered by conventional infrastructure scanning but has a supported cloud API inventory. It should instead use: Create the correctly directed CI relationship with the appropriate relationship type. Part (2) answers a different need: CI relationships are sourced from an external dependency feed but endpoints arrive in a later batch. It should instead use: Maintain acquisition Cost as the authoritative asset value and validate the supported one-way Asset-to-CI Cost synchronization instead of editing the CI to overwrite the purchase record. Both required outcomes must be verified separately.

B:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: An enterprise application cannot be discovered by conventional infrastructure scanning but has a supported cloud API inventory. It should instead use: Create the correctly directed CI relationship with the appropriate relationship type. Both required outcomes must be verified separately.

D:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: CI relationships are sourced from an external dependency feed but endpoints arrive in a later batch. It should instead use: Maintain acquisition Cost as the authoritative asset value and validate the supported one-way Asset-to-CI Cost synchronization instead of editing the CI to overwrite the purchase record. Both required outcomes must be verified separately.

Question 333

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?

  1. (1) Use preview or recompute where supported and verify the result against source history; (2) use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value
  2. (1) Use preview or recompute where supported and verify the result against source history; (2) add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition
  3. (1) Configure the appropriate suggested relationships for the class in CI Class Manager; (2) use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value
  4. (1) Configure the appropriate suggested relationships for the class in CI Class Manager; (2) add the appropriate class-specific column in CI Class Manager rather than changing the shared parent definition

Explanation

Correct Answer

C:

Both controls are required. For condition (1), configure the appropriate suggested relationships for the class in CI Class Manager. Suggested relationships guide consistent relationship selection without making every pairing physically true. Verify: The relationship editor proposes the intended type for a compatible parent-child pair. For condition (2), use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value. CMDB 360 retains visibility into competing reported attributes rather than showing only the final field. Verify independently: The reviewer sees both source values and identifies the currently selected value.

Incorrect Answers

A:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: An administrator changes reconciliation priorities but assumes old CMDB values will instantly reflect the new rules. It should instead use: Configure the appropriate suggested relationships for the class in CI Class Manager. Both required outcomes must be verified separately.

B:

Part (1) answers a different need: An administrator changes reconciliation priorities but assumes old CMDB values will instantly reflect the new rules. It should instead use: Configure the appropriate suggested relationships for the class in CI Class Manager. Part (2) answers a different need: A child CI class requires a new application build field but sibling classes must remain unaffected. It should instead use: Use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value. Both required outcomes must be verified separately.

D:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: A child CI class requires a new application build field but sibling classes must remain unaffected. It should instead use: Use CMDB 360 multisource data preview to compare per-source values and the selected CMDB value. Both required outcomes must be verified separately.

Question 334

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?

  1. (1) Represent the ideas in the CSDM Ideation and Strategy domain; (2) model shared reference entities in the CSDM Foundation domain
  2. (1) Establish foundational reference and ownership data before expanding to advanced service maps; (2) model shared reference entities in the CSDM Foundation domain
  3. (1) Establish foundational reference and ownership data before expanding to advanced service maps; (2) define adoption KPIs for correctly mapped services, owners and relationships
  4. (1) Represent the ideas in the CSDM Ideation and Strategy domain; (2) define adoption KPIs for correctly mapped services, owners and relationships

Explanation

Correct Answer

D:

Both controls are required. For condition (1), represent the ideas in the CSDM Ideation and Strategy domain. Strategy records concern proposed opportunities before detailed architecture or delivery. Verify: An unapproved idea is visible in strategic planning but not misrepresented as a deployed service. For condition (2), define adoption KPIs for correctly mapped services, owners and relationships. CSDM's value is service context and usability, not raw CI volume. Verify independently: The adoption report shows verified owners and valid links for the priority services.

Incorrect Answers

A:

Part (1) is relevant, but the pair is incomplete. Part (2) answers a different need: The organizational chart lists departments, companies and locations that several service teams share. It should instead use: Define adoption KPIs for correctly mapped services, owners and relationships. Both required outcomes must be verified separately.

B:

Part (1) answers a different need: A company starts CSDM by creating detailed service maps before standardizing departments and locations. It should instead use: Represent the ideas in the CSDM Ideation and Strategy domain. Part (2) answers a different need: The organizational chart lists departments, companies and locations that several service teams share. It should instead use: Define adoption KPIs for correctly mapped services, owners and relationships. Both required outcomes must be verified separately.

C:

Part (2) is relevant, but the pair is incomplete. Part (1) answers a different need: A company starts CSDM by creating detailed service maps before standardizing departments and locations. It should instead use: Represent the ideas in the CSDM Ideation and Strategy domain. Both required outcomes must be verified separately.

Question 335

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?

  1. Preview or evaluate policy targets and approval requirements before publishing the change
  2. Check glide.duplicate_ci_remediator.max.cis (default 1000, never above 5000) and the wizard limited-remediation behavior for larger duplicate sets, then plan an approved staged or alternate remediation
  3. Require change records, source metadata and reviewer ownership for manual CI updates
  4. Link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks
  5. Establish an attribute-level source-of-truth decision and enforce it through reconciliation

Explanation

Correct Answers

A:

This satisfies requirement A: Preview or evaluate policy targets and approval requirements before publishing the change. Evaluated policy scope helps prevent accidental mass retirement or deletion. Independently verify: A dry-run sample matches only the intended classes, lifecycle states and locations.

D:

This satisfies requirement B: Link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks. An aggregate score becomes useful when failures are traceable to actionable work items. Independently verify: Each critical failed metric has a named owner, affected CI sample and due date.

Incorrect Answers

B:

This is appropriate for another technical scenario: A duplicate set is too large for supported full wizard merging and operators plan an unrestricted bulk merge. When a de-duplication task exceeds its configured threshold the wizard restricts main-CI selection and does not reconcile conflicting attributes or relationships; raising the setting above 5000 cannot restore those functions. It does not directly satisfy either stated requirement; those require preview or evaluate policy targets and approval requirements before publishing the change. and link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks.

C:

This is appropriate for another technical scenario: A compliance reviewer cannot distinguish who approved a CI's manual changes from who loaded it. Traceable data changes preserve accountability for non-discoverable or manually governed CIs. It does not directly satisfy either stated requirement; those require preview or evaluate policy targets and approval requirements before publishing the change. and link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks.

E:

This is appropriate for another technical scenario: Two integration owners disagree about the authoritative source for application environment status. Governance decisions should translate into technical rules preventing unapproved overwrites. It does not directly satisfy either stated requirement; those require preview or evaluate policy targets and approval requirements before publishing the change. and link KPI dashboards and issue lists to assigned remediation tasks and data quality playbooks.

Question 336

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.

  1. Validate IRE identification configuration and stable native source IDs before increasing dedupe scripts
  2. Configure and test the distinct asset/CI status mapping appropriate to the hardware class
  3. Configure the appropriate Asset State to CI Hardware Status mapping and permitted sync direction
  4. Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path
  5. Correct the parent-child direction using the relationship editor or supported ingestion transform

Explanation

Correct Answers

B:

This satisfies requirement B: Configure and test the distinct asset/CI status mapping appropriate to the hardware class. Install Status and Hardware Status are independent fields rather than automatic mirrors of each other. Independently verify: A status change affects only the mapped field and not an unrelated status field.

E:

This satisfies requirement A: Correct the parent-child direction using the relationship editor or supported ingestion transform. Relationship direction matters for accurate dependency traversals and service modeling. Independently verify: Dependency traversal follows the intended application-to-database path.

Incorrect Answers

A:

This is appropriate for another technical scenario: An external connector imports duplicate rows for a host across multiple scheduled runs. Repeatable ingestion must identify the existing CI rather than creating a new object on every cycle. It does not directly satisfy either stated requirement; those require correct the parent-child direction using the relationship editor or supported ingestion transform. and configure and test the distinct asset/CI status mapping appropriate to the hardware class.

C:

This is appropriate for another technical scenario: A hardware asset moves to pending disposal but its technical CI still reports the old hardware status. Hardware status mapping reflects asset lifecycle without treating unrelated CI fields as interchangeable. It does not directly satisfy either stated requirement; those require correct the parent-child direction using the relationship editor or supported ingestion transform. and configure and test the distinct asset/CI status mapping appropriate to the hardware class.

D:

This is appropriate for another technical scenario: A cloud infrastructure vendor has a supported Service Graph Connector and the team is considering a bespoke CMDB REST importer. Supported connectors reduce custom upgrade debt and integrate source identification. It does not directly satisfy either stated requirement; those require correct the parent-child direction using the relationship editor or supported ingestion transform. and configure and test the distinct asset/CI status mapping appropriate to the hardware class.

Question 337

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.

  1. Create the correctly directed CI relationship with the appropriate relationship type
  2. Stage relationships until their parent and child CIs are resolved then load them via a supported path
  3. Maintain acquisition Cost as the authoritative asset value and validate the supported one-way Asset-to-CI Cost synchronization instead of editing the CI to overwrite the purchase record
  4. Establish the correct asset-to-CI association and model category mapping
  5. Prefer the supported Service Graph Connector with its documented mapping and IRE-aware ingestion path

Explanation

Correct Answers

B:

This satisfies requirement A: Stage relationships until their parent and child CIs are resolved then load them via a supported path. Processing order and endpoint matching prevent dangling or mismatched relationship references. Independently verify: All staged edges resolve to existing CIs after both ingestion batches complete.

C:

This satisfies requirement B: Maintain acquisition Cost as the authoritative asset value and validate the supported one-way Asset-to-CI Cost synchronization instead of editing the CI to overwrite the purchase record. ServiceNow Asset–CI synchronization permits many mapped attributes in both directions, but the Cost field is informational on the CI and is synchronized only from Asset to CI. Independently verify: Changing asset Cost updates the linked CI cost display; editing the CI cost does not change the authoritative asset Cost.

Incorrect Answers

A:

This is appropriate for another technical scenario: A web application CI has no dependency link to its database and impact analysis misses downstream failures. Relationship records encode application dependencies beyond the CI attributes themselves. It does not directly satisfy either stated requirement; those require stage relationships until their parent and child CIs are resolved then load them via a supported path. and maintain acquisition Cost as the authoritative asset value and validate the supported one-way Asset-to-CI Cost synchronization instead of editing the CI to overwrite the purchase record.

D:

This is appropriate for another technical scenario: A hardware laptop has both an asset record and CI record, but the two reference fields are not paired. Asset synchronization requires logical linkage between a physical asset and its technical CI. It does not directly satisfy either stated requirement; those require stage relationships until their parent and child CIs are resolved then load them via a supported path. and maintain acquisition Cost as the authoritative asset value and validate the supported one-way Asset-to-CI Cost synchronization instead of editing the CI to overwrite the purchase record.

E:

This is appropriate for another technical scenario: A cloud infrastructure vendor has a supported Service Graph Connector and the team is considering a bespoke CMDB REST importer. Supported connectors reduce custom upgrade debt and integrate source identification. It does not directly satisfy either stated requirement; those require stage relationships until their parent and child CIs are resolved then load them via a supported path. and maintain acquisition Cost as the authoritative asset value and validate the supported one-way Asset-to-CI Cost synchronization instead of editing the CI to overwrite the purchase record.

Question 338

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.

  1. Review Required completeness failures and correct the missing mandatory ownership data
  2. Use an appropriate certification or attestation control requiring explicit confirmation of that value
  3. Review the targeted Related Entry [cmdb_related_entry] references and apply the CMDB Data Manager Delete CMDB Related Entry policy only to approved orphaned entries
  4. Schedule a CMDB Data Manager Attestation policy for selected CIs and assign existence-verification tasks to accountable owners; route rejected items to the governed retirement review
  5. Define a service owner approval and change-control process for governed naming updates

Explanation

Correct Answers

A:

This satisfies requirement A: Review Required completeness failures and correct the missing mandatory ownership data. Completeness Required measures required-field population for eligible CIs. Independently verify: Required completeness improves after the sampled Windows servers receive approved owners.

B:

This satisfies requirement B: Use an appropriate certification or attestation control requiring explicit confirmation of that value. Fresh timestamps do not prove that a human has validated business ownership. Independently verify: The responsible person signs off on the current owner value with dated evidence.

Incorrect Answers

C:

This is appropriate for another technical scenario: A team wishes to clean up orphaned non-CMDB Related Entry records after their referenced CI has been deleted, without deleting arbitrary unrelated business records. The separate Delete CMDB Related Entry processor handles configured related-table entries tracked in cmdb_related_entry; it is not a general-purpose delete-all-non-CMDB-table operation. It does not directly satisfy either stated requirement; those require review Required completeness failures and correct the missing mandatory ownership data. and use an appropriate certification or attestation control requiring explicit confirmation of that value.

D:

This is appropriate for another technical scenario: A data owner needs quarterly human confirmation that the servers represented by selected CIs still physically exist, before deciding whether to retire records for missing equipment. Attestation is a human confirmation of the represented real infrastructure or application, not equivalent to automatic correctness of every attribute or to a Certification policy for a specified field. It does not directly satisfy either stated requirement; those require review Required completeness failures and correct the missing mandatory ownership data. and use an appropriate certification or attestation control requiring explicit confirmation of that value.

E:

This is appropriate for another technical scenario: A central team overrides business service names without approval from the service owners. Stewardship prevents uncoordinated changes to shared business context. It does not directly satisfy either stated requirement; those require review Required completeness failures and correct the missing mandatory ownership data. and use an appropriate certification or attestation control requiring explicit confirmation of that value.

Question 339

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?

  1. Remediate existing duplicate records separately and test the revised IRE rule for future ingests
  2. Check glide.duplicate_ci_remediator.max.cis (default 1000, never above 5000) and the wizard limited-remediation behavior for larger duplicate sets, then plan an approved staged or alternate remediation
  3. Define a stale-to-retired lifecycle process using source absence, owner verification and Data Manager policy
  4. Preview or evaluate policy targets and approval requirements before publishing the change
  5. Require change records, source metadata and reviewer ownership for manual CI updates

Explanation

Correct Answers

C:

This satisfies requirement B: Define a stale-to-retired lifecycle process using source absence, owner verification and Data Manager policy. Automated lifecycle governance reconciles discovered existence with administrative approval. Independently verify: Confirmed terminated instances no longer appear as active configuration items.

D:

This satisfies requirement A: Preview or evaluate policy targets and approval requirements before publishing the change. Evaluated policy scope helps prevent accidental mass retirement or deletion. Independently verify: A dry-run sample matches only the intended classes, lifecycle states and locations.

Incorrect Answers

A:

This is appropriate for another technical scenario: A duplicate task was created before an identification rule was fixed, and the team assumes fixing the rule auto-merges historical records. Improved identification prevents future collisions but does not retroactively merge every old duplicate. It does not directly satisfy either stated requirement; those require preview or evaluate policy targets and approval requirements before publishing the change. and define a stale-to-retired lifecycle process using source absence, owner verification and Data Manager policy.

B:

This is appropriate for another technical scenario: A duplicate set is too large for supported full wizard merging and operators plan an unrestricted bulk merge. When a de-duplication task exceeds its configured threshold the wizard restricts main-CI selection and does not reconcile conflicting attributes or relationships; raising the setting above 5000 cannot restore those functions. It does not directly satisfy either stated requirement; those require preview or evaluate policy targets and approval requirements before publishing the change. and define a stale-to-retired lifecycle process using source absence, owner verification and Data Manager policy.

E:

This is appropriate for another technical scenario: A compliance reviewer cannot distinguish who approved a CI's manual changes from who loaded it. Traceable data changes preserve accountability for non-discoverable or manually governed CIs. It does not directly satisfy either stated requirement; those require preview or evaluate policy targets and approval requirements before publishing the change. and define a stale-to-retired lifecycle process using source absence, owner verification and Data Manager policy.

Question 340

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.

  1. Verify compliance activation, audit definition and last completed run before treating a blank CMDB Health compliance indicator as meaningful
  2. Traverse CI relationships from the database to related application services using a supported dependency query or map
  3. Populate and maintain accurate support group and service ownership fields on the relevant CIs
  4. Use a CMDB 360 Get Records saved query with appropriate source and attribute filters

Explanation

Correct Answer

D:

This is the appropriate control for the stated CI requirement. Multisource records queries enable source-specific inventory reporting. Implement: Use a CMDB 360 Get Records saved query with appropriate source and attribute filters. Confirm effectiveness by checking: The report lists matching discovered servers while excluding other sources.

Incorrect Answers

A:

CMDB compliance scores require the latest completed audit evidence; scripted audits lacking a recorded Last run date can be skipped rather than counted as a passing score. The specific problem here is that multisource records queries enable source-specific inventory reporting.

B:

Impact analysis uses directed dependencies to identify affected services. The specific problem here is that multisource records queries enable source-specific inventory reporting.

C:

ITSM workflows can use trustworthy configuration context for incident routing. The specific problem here is that multisource records queries enable source-specific inventory reporting.

Certified Implementation Specialist - Data Foundations (CMDB and CSDM) (CIS-DF) Practice Tests