CIS-DF Governance Practice Test 3 — 15 Questions

Question 1

What is the primary purpose of the 'Audit' functionality within ServiceNow Asset and CMDB management?

Accepted Answer

To verify physical or logical existence and accuracy of CI data through scheduled campaigns. The Audit functionality in ServiceNow Asset and CMDB management is designed to verify the physical or logical existence and accuracy of CI data through scheduled audit campaigns. Auditors are assigned CIs to confirm, and results feed back into the CMDB to correct discrepancies, mark missing assets, or validate data quality. This directly supports CMDB governance and compliance.

Answer

To scan network ports for security vulnerabilities

Answer

To automatically approve emergency change requests

Answer

To track user login attempts and password resets

Question 2

A governance team wants to ensure that no CI is created without a populated 'Environment' field (e.g., Production, Test, Development). Which feature should be used to enforce this rule at the point of data entry or integration?

Accepted Answer

CMDB Data Governance completeness policy with strict enforcement. A CMDB Data Governance completeness policy with strict enforcement is the feature designed to ensure required fields like 'Environment' are populated before a CI is created or updated. Strict enforcement blocks the insert or update if the field is missing, enforcing the rule at the point of data entry or integration. This is exactly the governance mechanism for mandatory CI attributes.

Answer

UI Actions

Answer

Service Level Agreement (SLA) definition

Answer

Access Control Lists (ACLs)

Question 3

An administrator needs to configure score weightings on the CMDB Health Dashboard so that Correctness carries 50% weight, Completeness carries 30%, and Compliance carries 20%. Where is this configured?

Accepted Answer

CMDB Health Dashboard > Metric Settings / Weightings. Score weightings for CMDB Health (Correctness, Completeness, Compliance, and Relationship) are configured in the CMDB Health Dashboard under Metric Settings / Weightings. This is where administrators set the percentage contribution each health metric makes to the overall health score. Setting Correctness to 50%, Completeness to 30%, and Compliance to 20% is done there.

Answer

Performance Analytics > Widgets

Answer

CI Class Manager > Health Properties

Answer

System Properties > CMDB > Governance

Question 4

Which TWO metrics are categorized under CMDB Health Correctness? (Choose two.)

Accepted Answer

Orphans. In ServiceNow CMDB Health, the Correctness KPI measures data quality problems that make CIs inaccurate or improperly related, and it includes the Orphans metric (C), which flags CIs that lack required relationships to other CIs, and the Duplicates metric (D), which flags multiple CI records that appear to represent the same real-world item. Both Orphans and Duplicates are scored under Correctness because they directly indicate incorrect or unreliable CMDB data rather than completeness or compliance issues. Unauthorized software installations (A) belong to CMDB Health compliance-type checks (e.g., unauthorized CI/software detection), not Correctness. Mandatory fields missing (B) is a Completeness metric, since it measures whether required attributes are populated. Support group population status (E) is also a Completeness concern, because it checks whether the support group field is filled in, not whether the CI data is correct.

Answer

Unauthorized software installations

Answer

Mandatory fields missing

Answer

Support group population status

Question 5

Which TWO actions can be performed directly from the CMDB Health Dashboard when investigating health metrics? (Choose two.)

Accepted Answer

View remediation tasks associated with data health failures. Option C is correct because the CMDB Health Dashboard provides access to remediation tasks that are generated for failed health checks, allowing administrators to view and act on the tasks associated with data health failures directly from the dashboard. Option D is correct because the dashboard supports drill-down navigation, enabling users to click into a failing metric (such as completeness) and see the specific CIs that are contributing to the poor score. Option A is incorrect because IRE Identification Rules are configured in the Identification and Reconciliation engine settings, not modified from the CMDB Health Dashboard. Option B is incorrect because bulk permanent deletion of all duplicate CIs across the enterprise is not a one-click action available from the dashboard and would require de-duplication processes and careful review. Option E is incorrect because MID Server cluster configuration is managed in MID Server properties and settings, not from the CMDB Health Dashboard.

Answer

Directly modify core IRE Identification Rules for hardware classes

Answer

Permanently delete all duplicate CIs across the entire enterprise with a single click

Answer

Modify MID Server cluster configurations

Question 6

A company discovers that multiple discovery sources are overwriting authoritative manual updates to server asset tags. Which governance mechanism should be configured to protect specific attributes from being updated by automated discovery?

Accepted Answer

Reconciliation Definition (Data Precedence). Reconciliation Definitions (Data Precedence) in the CMDB control which data source wins when multiple sources update the same CI attribute. By configuring a reconciliation rule that gives manual/authoritative sources higher precedence than discovery sources for specific attributes, you protect manual updates from being overwritten by automated discovery.

Answer

Discovery Schedule Exclude filters

Answer

Access Control Lists (ACLs)

Answer

Business Rules on the cmdb_ci table

Question 7

When configuring CMDB Data Governance policies, which THREE rule criteria types can be evaluated against CI records? (Choose three.)

Accepted Answer

Attribute value validation (checking pattern or lookup criteria). Option A is correct because CMDB data governance rules can evaluate CI attribute values against validation criteria such as regex patterns, allowed lookup values, or reference tables to flag non-conforming records. Option B is correct because governance policies can include relationship checks that verify required parent/child or dependency connections exist for a CI class, ensuring the CMDB graph is structurally valid. Option E is correct because completeness checks are a core governance criterion, verifying that mandatory attributes for a given CI class are populated and not null or empty. Option C is not correct because network latency ping response is an operational monitoring/availability metric, not a CMDB data governance rule criterion evaluated against CI records. Option D is not correct because synchronizing hardware warranty expiration dates with vendor APIs is an external data integration/enrichment activity, not a governance rule criteria type evaluated against CI records.

Answer

Network latency ping response check

Answer

Hardware warranty expiration date synchronization with vendor APIs

Question 8

Which TWO practices represent effective CMDB governance strategies for maintaining data quality? (Choose two.)

Accepted Answer

Assigning clear data ownership (Managed by / Support Group) for every CI class. Option D is correct because assigning clear data ownership through fields such as Managed by and Support Group for every CI class establishes accountability, ensuring that each configuration item has a responsible party who validates and maintains its accuracy, which is a foundational CMDB governance control. Option E is correct because implementing automated remediation tasks for CMDB health and data governance violations enforces data quality continuously, detecting and correcting issues like orphan CIs, stale records, or missing attributes without relying solely on manual effort. Options A, B, and C do not belong: unrestricted modification by any authenticated user destroys change control and data integrity, relying entirely on end-users to manually update server attributes produces inconsistent and unverified data, and disabling audit logging removes the traceability needed to detect and investigate unauthorized or erroneous CI changes while offering negligible performance benefit.

Answer

Allowing any authenticated user to modify production CI configurations without restriction

Answer

Relying entirely on end-users to manually update all server attributes via service portal requests

Answer

Disabling all audit logging to improve table insert performance

Question 9

What is the main benefit of establishing CMDB data stewardship roles within an enterprise?

Accepted Answer

To ensure continuous data quality, accountability, and ownership of CMDB assets. CMDB data stewardship roles establish clear ownership and accountability for CMDB data quality, ensuring that designated stewards maintain accurate, complete, and timely CI records. This governance model is the primary benefit because it assigns responsibility for data integrity across the enterprise.

Answer

To approve all software license purchases

Answer

To write custom JavaScript business rules for system performance

Answer

To manage network switch VLAN configurations

Question 10

A security audit reveals that unauthorized users are modifying critical CI attributes directly on form views. Which ServiceNow platform governance feature can restrict write access to specific CI attributes based on user roles and data classification?

Accepted Answer

Access Control Lists (ACLs) on cmdb_ci fields. Access Control Lists (ACLs) on cmdb_ci fields are the platform's native mechanism for restricting read and write access to specific CI attributes based on user roles, conditions, and data classification. By creating field-level ACLs with write rules tied to roles, administrators can prevent unauthorized users from modifying critical CI attributes directly on form views. This is the standard governance control for attribute-level write protection in the CMDB.

Answer

Data Certification read restrictions

Answer

Discovery credential filters

Answer

CMDB Data Governance read-only policies

Question 11

Which TWO types of metrics are evaluated under the CMDB Health framework? (Choose two.)

Accepted Answer

Correctness. Under the CMDB Health framework, Correctness (C) is evaluated because it measures whether CI records contain accurate and valid data, such as ensuring required fields have valid values and that CIs conform to their class definitions. Completeness (D) is also evaluated because it measures whether required attributes and relationships are populated for each CI, identifying records that are missing mandatory data. These two metrics are part of the standard CMDB Health KPIs, along with compliance and duplicate metrics. Availability (A), Scalability (B), and Performance (E) are not CMDB Health metric types; they are operational or infrastructure characteristics rather than data-quality dimensions assessed by the CMDB Health framework.

Answer

Availability

Answer

Scalability

Answer

Performance

Question 12

Which dashboard component in the CMDB Health Dashboard displays the ratio of CIs that have missing mandatory attributes?

Accepted Answer

Completeness Score Widget. The Completeness Score Widget on the CMDB Health Dashboard displays the ratio of CIs that have missing mandatory attributes. Completeness measures whether required fields are populated, and the widget visualizes the percentage of CIs that meet completeness criteria versus those that do not. This directly answers the question about missing mandatory attributes.

Answer

Correctness Duplicate Widget

Answer

Orphaned CI Widget

Answer

Compliance Audit Widget

Question 13

What is the primary function of the CI Class Manager in relation to CMDB governance?

Accepted Answer

To manage CI class definitions, identification rules, and health inclusions. The CI Class Manager is the ServiceNow interface for managing CI class definitions, including identification rules, health inclusions, and class hierarchy. It is the central place where administrators configure how CIs are identified and which classes participate in CMDB Health. This makes it a key tool for CMDB governance because it controls the structure and rules that govern CI data.

Answer

To generate user satisfaction surveys

Answer

To run network discovery scans

Answer

To approve emergency change requests

Question 14

An administrator notices that the CMDB Health background jobs are running during peak business hours and impacting performance. Where can the schedule for CMDB Health metric calculations be modified?

Accepted Answer

System Definition > Scheduled Jobs (searching for CMDB Health jobs). CMDB Health metric calculations are executed by scheduled jobs, which can be modified in the System Definition > Scheduled Jobs module. Administrators can search for CMDB Health-related jobs and adjust their schedules to run during off-peak hours, reducing performance impact.

Answer

Discovery Schedules > CMDB Health

Answer

CMDB Health Dashboard > Schedule Settings

Answer

Data Governance > Job Execution

Question 15

An organization wants to ensure that no duplicate CIs are ever inserted into the cmdb_ci table by API integrations or manual imports. Which ServiceNow engine natively enforces this governance rule?

Accepted Answer

Identification and Reconciliation Engine (IRE). The Identification and Reconciliation Engine (IRE) is a native ServiceNow engine that enforces data governance by identifying and reconciling duplicate CIs before they are inserted into the CMDB. It uses identification rules and reconciliation rules to ensure that only unique CIs are created, even from multiple sources.

Answer

Data Policy Enforcement Engine

Answer

CMDB Health Duplicate Engine

Answer

Transform Map Unique Key matching