Text preview & study summary
ServiceNow CIS-DF - Certified Implementation Specialist Data Foundations
A free sample of 5 questions from this quiz, shown in full with answer choices and explanations. No interactivity — everything is visible on this page for study and review.
Want to test your knowledge? Launch the Interactive Exam Simulator
Question 1
Operations wants recurring validation that CPU count and OS version on in-scope server CIs are still accurate, with tasks auto-assigned to owning teams.
Which Data Manager policy type should the administrator create?
Explanation
Attestation is the Data Manager policy type that creates assigned review tasks for owners or groups. It fits recurring validation that selected CI attributes remain accurate.
Certification is not the CMDB Data Manager policy type to choose here. In this context the Data Manager task-based review pattern is attestation.
Retire transitions CIs toward end-of-life based on lifecycle criteria. It is not an attribute-review task cycle for active servers.
Archive moves retired records into archive storage. It does not assign owners to validate CPU count or OS version.
Question 2
Thousands of server CIs are stale for more than 90 days. The governance policy requires them to leave active operational use after review, while still preserving a restore window for historical and audit needs.
Which Data Manager automation sequence fits?
Explanation
Use a cleanup policy to target stale CIs, transition eligible records through retirement, and archive them after the defined grace period is correct. Data Manager cleanup and lifecycle automation can move stale CIs out of active use while preserving governed retention and restore options instead of hard deletion.
Create an attestation policy that asks owners to confirm the stale population, then leave confirmed records active for future reporting is incorrect. Attestation can support owner review, but leaving stale records active does not satisfy the requirement to remove eligible CIs from active operational use.
Configure a remediation policy that updates Last discovered so the stale servers no longer fail health checks is incorrect. Remediation should not mask stale data by changing freshness indicators without a real data refresh or lifecycle decision.
Build a CMDB Health audit that marks stale servers as compliant when they have linked incidents or change history is incorrect. Incident or change history does not prove the CI still represents active infrastructure, and a compliance audit is not the right automation sequence for retirement and archive handling.
Question 3
A CMDB Program Manager develops a multi-year CMDB roadmap and needs Foundation Dashboards to inform investment priorities and demonstrate progress to sponsors.
Which two ways should Foundation Dashboards inform that roadmap?
Explanation
They provide maturity indicators across foundation dimensions helps program managers identify where the CMDB program needs investment.
They track progress trends over time toward readiness targets helps sponsors see whether remediation work is improving readiness over multiple planning cycles.
They replace the CMDB with a spreadsheet export misunderstands the dashboard purpose. The dashboard informs the program; it is not the configuration system of record.
They list MID Server versions as the primary dashboard content is far too narrow. Foundation Dashboards focus on readiness dimensions, not just MID inventory.
They auto-patch operating systems on server CIs is outside dashboard scope.
Question 4
A university IT department allocates shared data-center and cloud infrastructure costs to academic departments based on actual consumption patterns documented in the CMDB.
Which two CMDB data points enable chargeback analysis?
Explanation
Leveraging CI ownership and department attributes to assign infrastructure spend supports chargeback because infrastructure can be grouped by accountable department or owner.
Following dependency paths from infrastructure CIs to business services and consuming departments also supports chargeback because shared platforms can be allocated based on the services and departments that consume them.
Posting general-ledger journal entries automatically from cmdb_ci records overstates CMDB scope. Finance systems post journals; CMDB supplies ownership and dependency context.
Replacing the finance system of record for all capital expenditures misidentifies the CMDB. It is a configuration and relationship system, not the general ledger.
Storing employee salary figures on each cmdb_ci_server record is unrelated and inappropriate for CI modeling.
Question 5
A data steward opens CMDB 360 for a CI and compares what different discovery and integration sources reported for attributes such as name, serial number, IP address, and manufacturer.
Which table is commonly used to store the raw per-source attribute data that supports this multisource comparison?
Explanation
cmdb_multisource_data is correct. This table commonly stores raw multisource attribute data reported by discovery and integration sources. CMDB 360 can use that source-specific data to show what each source contributed for a CI before or alongside the reconciled values shown on the main CI record.
sys_object_source is incorrect. This table is related to source tracking for records, but it is not the main table used to store the raw per-source CMDB attribute payloads displayed for multisource CMDB comparison.
cmdb_ci is incorrect. The cmdb_ci table stores the core CI record and its reconciled attribute values. It does not store each source’s raw reported value for every compared attribute.
cmdb_rel_ci is incorrect. This table stores CI relationships, such as dependencies or service mappings between CIs. It does not hold raw multisource attribute payloads for CMDB 360 analysis.