Courseiva

CCNA Governance Questions

56 questions · Governance topic · All types, answers revealed

1
MCQmedium

An enterprise wants to ensure that data stewards are automatically notified when duplicate CIs are detected by the Identification and Reconciliation Engine (IRE). How can this governance requirement be streamlined?

A.Set up a scheduled data import transform map script
B.Modify the Identification Engine processor script directly
C.Configure CMDB Duplicate Remediation rules
D.Write a custom Business Rule on the sys_object_source table
AnswerC

CMDB Duplicate Remediation rules generate tasks automatically when IRE detects duplicate CIs, assigning them to the relevant data stewards. This satisfies the governance requirement for automatic notification without manual monitoring, since the rules run as part of the duplicate remediation workflow.

Why this answer

Configuring CMDB Duplicate Remediation rules allows the system to automatically detect duplicate CIs and notify data stewards based on predefined conditions. These rules can trigger notifications, assign tasks, or even merge duplicates, streamlining governance. This approach leverages out-of-the-box functionality rather than custom scripting, ensuring maintainability and scalability.

Exam trap

CIS-DF often tests the misconception that custom scripts or direct modifications are needed for governance, but the correct answer is to use built-in CMDB Duplicate Remediation rules.

How to eliminate wrong answers

Option A is wrong because a scheduled data import transform map script is for data loading, not for duplicate detection and notification. Option B is wrong because modifying the Identification Engine processor script directly is risky, unsupported, and not a streamlined governance approach; it could break IRE functionality. Option D is wrong because writing a custom Business Rule on the sys_object_source table is a custom solution that may not be triggered by IRE duplicate detection and is not the recommended streamlined method.

2
MCQhard

An organization wants to configure remediation rules so that when a CMDB Health Correctness anomaly (such as a duplicate CI) is identified, a remediation task is automatically generated and assigned to the correct data owner. Where are these remediation rules configured?

A.Inside Data Certification definition forms
B.In the CMDB Health Dashboard configuration settings
C.Through Data Policies on the cmdb_ci table
D.In the CI Class Manager under the Remediation tab
AnswerB

Remediation rules live within the CMDB Health Dashboard configuration, where each health metric's task generation and assignment logic is defined. Configuring them there lets a detected correctness anomaly, such as a duplicate CI, automatically spawn a remediation task routed to the appropriate data owner.

Why this answer

CMDB Health remediation rules are configured within the CMDB Health Dashboard configuration, where administrators define which health failures (correctness, completeness, compliance, duplicate) trigger remediation tasks and how those tasks are assigned. This is the centralized location for mapping a health anomaly to a task generation and assignment policy. The rules reference the CI's support group or owner to route the task to the correct data owner.

Exam trap

The trap is confusing Data Certification (periodic attestation campaigns) with CMDB Health remediation (event-driven task generation) — both involve 'data quality tasks' but live in different configuration areas.

How to eliminate wrong answers

Option A is wrong because Data Certification definitions are used to schedule certification campaigns where CI owners attest to data accuracy — they do not generate remediation tasks for CMDB Health anomalies. Option C is wrong because Data Policies enforce attribute-level validation on insert/update (e.g., mandatory fields, regex) but do not create remediation tasks for health scan findings like duplicates. Option D is wrong because the CI Class Manager manages class schema, attributes, and identification rules — it has no Remediation tab for health-based task generation.

3
MCQmedium

An administrator needs to ensure that historical changes to data governance remediation tasks are easily tracked. Which platform feature automatically tracks changes to task work notes, state transitions, and assignments?

A.CMDB Health Audit Table
B.Discovery History Table
C.Task Activity Stream and Audit Log
D.Data Certification Log
AnswerC

The Task Activity Stream records field-level changes and work note additions chronologically on the task record, while the Audit Log captures state transitions and assignment changes, together providing the automatic historical traceability the administrator requires without manual logging.

Why this answer

The Task Activity Stream and Audit Log is the platform feature that automatically records field-level changes, work note additions, state transitions, and assignment changes on task records, including governance remediation tasks. It provides a chronological, filterable history without any custom configuration. This is the native mechanism for tracking who changed what and when on a task.

Exam trap

The trap is confusing CMDB health or certification logs with task-level audit history — candidates pick the 'audit-sounding' option without checking whether it actually tracks task field changes.

How to eliminate wrong answers

Option A is wrong because the CMDB Health Audit Table stores results of CMDB health audits (completeness, correctness, compliance), not task-level change history. Option B is wrong because the Discovery History Table logs discovery runs and their outcomes, not changes to task records. Option D is wrong because the Data Certification Log tracks certification task outcomes and attestation results, not the granular field-level change history of remediation tasks.

4
MCQmedium

Which CMDB Health metric category evaluates whether CIs have mandatory fields populated, such as Assigned to, Managed by, and Support Group?

A.Freshness
B.Completeness
C.Correctness
D.Compliance
AnswerB

Completeness evaluates whether mandatory fields such as Assigned to, Managed by and Support Group are populated on CIs. It therefore directly satisfies the scenario's requirement to measure missing required attribute values in the CMDB health assessment.

Why this answer

Completeness is the CMDB Health metric category that specifically checks whether mandatory fields on a CI are populated — such as Assigned to, Managed by, and Support Group. It measures the presence of required attribute values rather than their accuracy or timeliness. This is distinct from Correctness (which validates values against expected patterns) and Freshness (which checks update recency).

Exam trap

CIS-DF often tests the distinction between Completeness (fields are populated) and Correctness (fields contain valid values) — candidates frequently swap these two because both sound like 'data quality' checks.

How to eliminate wrong answers

Option A is wrong because Freshness measures how recently a CI was updated or discovered, not whether mandatory fields are populated. Option C is wrong because Correctness evaluates whether populated values are valid/accurate (e.g., matching expected formats or reference data), not whether fields are filled. Option D is wrong because Compliance in CMDB Health refers to adherence to defined audit/validation rules and policy checks, not the presence of mandatory field values.

5
MCQhard

An auditor requires proof that all discovered Linux servers have a validated business justification attribute. The team uses CMDB Data Governance to enforce this. How can the administrator prove to the auditor that the policy is actively running and enforcing this rule?

A.Show the CMDB Data Governance Policy execution history and generated remediation task metrics
B.Provide a screenshot of the Discovery Schedule configuration
C.Export the entire sys_audit table to CSV
D.Display the baseline CI Class Manager JSON payload definition
AnswerA

Policy execution history records each governance run, showing which CIs were evaluated and which failed the business justification rule. Remediation task metrics evidence that non-compliant records generated enforcement actions, giving the auditor verifiable proof the policy actively runs rather than existing as documentation only.

Why this answer

CMDB Data Governance policies maintain execution history and generate remediation task metrics that serve as auditable evidence. By showing the policy's execution history (when it ran, what it evaluated) and the generated remediation tasks (with timestamps, assignees, and statuses), the administrator can prove the policy is actively running and enforcing the business justification rule. This is the direct, purpose-built evidence an auditor needs.

Exam trap

CIS-DF often tests the difference between configuration evidence (screenshots of schedules or schemas) and operational evidence (execution history and task metrics), so candidates who pick Discovery Schedule or CI Class Manager miss that auditors require proof of active enforcement.

How to eliminate wrong answers

Option B is wrong because a Discovery Schedule screenshot only proves discovery is configured — it says nothing about whether the business justification policy is running or enforcing. Option C is wrong because exporting the entire sys_audit table is overbroad, noisy, and does not specifically demonstrate policy execution or enforcement of the business justification attribute. Option D is wrong because the baseline CI Class Manager JSON payload defines the class schema — it shows the attribute exists but not that the policy is actively enforcing it.

6
MCQhard

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?

A.Performance Analytics > Widgets
B.CI Class Manager > Health Properties
C.CMDB Health Dashboard > Metric Settings / Weightings
D.System Properties > CMDB > Governance
AnswerC

Weightings are set under CMDB Health Dashboard metric settings, where each health metric — Correctness, Completeness, Compliance — receives a percentage that must total 100. This satisfies the stem's exact 50/30/20 split, since the dashboard reads those configured values when calculating the aggregate health score.

Why this answer

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.

Exam trap

The trap is confusing class-level Health Properties (which metrics apply to a class) with global Metric Settings/Weightings (how much each metric counts) — candidates often pick CI Class Manager when the question asks about weighting percentages.

How to eliminate wrong answers

Option A is wrong because Performance Analytics > Widgets is for building and configuring PA dashboards and widgets, not for CMDB Health score weighting. Option B is wrong because CI Class Manager > Health Properties controls which health metrics and KPIs apply to a specific CI class, not the global weighting percentages across metrics. Option D is wrong because System Properties > CMDB > Governance holds governance-related properties (e.g., task creation behavior), not the health score weighting configuration.

7
Multi-Selectmedium

Which TWO actions can be taken from the CMDB Data Governance application interface? (Choose two.)

Select 2 answers
A.Defining and editing data quality policies
B.Writing custom web server Apache configurations
C.Managing ITIL change request CAB approval boards
D.Monitoring and reviewing generated remediation tasks
E.Configuring MID Server SSL encryption keys
AnswersA, D

Defining and editing data quality policies is performed directly within the CMDB Data Governance application interface, satisfying the stem's requirement for actions available there. This interface governs data quality rules centrally, letting administrators create and modify policies without leaving the application, which matches the scenario's constraint of interface-native actions.

Why this answer

Option A is correct because the CMDB Data Governance application provides the interface for creating, defining, and editing data quality policies that specify the rules and thresholds used to evaluate CMDB data health. Option D is correct because the same application lets administrators monitor data quality results and review the remediation tasks that are generated when policy violations are detected, so owners can act on them. The other options do not belong: writing custom Apache web server configurations (B) is a web-tier administration task unrelated to CMDB governance, managing ITIL change request CAB approval boards (C) is done in Change Management, and configuring MID Server SSL encryption keys (E) is handled through MID Server and certificate/key management, not the CMDB Data Governance interface.

8
MCQmedium

A governance team wants to ensure that CIs without valid IP addresses or MAC addresses are flagged in network-connected classes. Where can this specific validation rule be configured?

A.Discovery Definition > Behaviors
B.CI Class Manager > Identifiers
C.CMDB Data Governance > Policies
D.System Properties > Network Settings
AnswerC

CMDB Data Governance > Policies holds configurable data policies, including validation rules that flag CIs missing required attributes such as IP or MAC addresses in network-connected classes. This is the specific location where such attribute validation is defined and enforced.

Why this answer

CMDB Data Governance > Policies allows administrators to define validation rules that flag CIs with missing or invalid attributes, such as IP addresses or MAC addresses for network-connected classes. These policies can be configured to run on-demand or on schedule, providing governance over data quality.

Exam trap

CIS-DF often tests the location of data governance policy configuration, and candidates may confuse it with identification rules or discovery behaviors.

How to eliminate wrong answers

Option A is wrong because Discovery Definition > Behaviors is used to configure discovery behavior, not data validation rules. Option B is wrong because CI Class Manager > Identifiers is used to define identification rules for IRE, not for flagging invalid attributes. Option D is wrong because System Properties > Network Settings contains system-wide network configurations, not CI-specific validation rules.

9
MCQeasy

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

A.To verify physical or logical existence and accuracy of CI data through scheduled campaigns
B.To scan network ports for security vulnerabilities
C.To automatically approve emergency change requests
D.To track user login attempts and password resets
AnswerA

Audit campaigns schedule verification of CI records against physical or logical reality, reconciling discovered data with the CMDB. This satisfies the stem's requirement to confirm existence and accuracy of CI data through scheduled campaigns rather than ad hoc checks.

Why this answer

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.

Exam trap

The trap is confusing the CMDB Audit module with security auditing or change auditing — candidates see 'Audit' and think of vulnerability scans or login logs, but in ServiceNow Asset/CMDB context, Audit specifically means scheduled CI verification campaigns.

How to eliminate wrong answers

Option B is wrong because network port scanning for vulnerabilities is performed by security tools (e.g., Vulnerability Response, third-party scanners), not by the CMDB Audit module — Audit is about data verification, not security scanning. Option C is wrong because emergency change request approval is handled by the Change Management workflow and CAB/ECAB processes, not by Audit. Option D is wrong because tracking user login attempts and password resets is a platform security/authentication function (login audit records, password policy logs), not the Asset/CMDB Audit module.

10
MCQmedium

A CMDB administrator notices that multiple CIs have duplicate records with identical serial numbers due to conflicting integration sources. Which CMDB Health metric evaluates this specific condition?

A.Freshness
B.Completeness
C.Compliance
D.Correctness
AnswerD

Correctness evaluates whether CI records contain accurate, non-duplicate data, including conflicting values from multiple sources. Duplicate records sharing identical serial numbers from clashing integrations are precisely the data integrity defect this metric detects and reports.

Why this answer

The CMDB Health Correctness metric evaluates the accuracy of CI data by checking for duplicates, orphans, and other data quality issues. Duplicate CIs with identical serial numbers are specifically flagged under the Correctness metric, which includes duplicate checks.

Exam trap

CIS-DF often tests the distinction between CMDB Health metrics, and candidates may incorrectly associate duplicates with Completeness or Compliance instead of Correctness.

How to eliminate wrong answers

Option A is wrong because Freshness measures how recently CIs were updated, not duplicates. Option B is wrong because Completeness checks for missing required attributes, not duplicates. Option C is wrong because Compliance checks adherence to defined policies, which may include duplicates but is broader; the specific duplicate condition is part of Correctness.

11
Multi-Selecthard

Which THREE actions occur when a Data Certification task is assigned to a CI owner? (Choose three.)

Select 3 answers
A.The CI is automatically retired from the database immediately
B.The reviewer can update incorrect attribute values directly from the task interface
C.A high-priority incident is automatically created for the IT service desk
D.The reviewer submits the certification response, completing the task
E.The reviewer is asked to verify if the CI data is accurate and up to date
AnswersB, D, E

Reviewers can correct inaccurate attribute values inline from the certification task, satisfying the requirement that remediation happens without leaving the task. This direct edit capability distinguishes certification tasks from read-only access reviews, letting the CI owner fix data quality issues during review rather than raising a separate change request.

Why this answer

Option B is correct because the Data Certification task interface lets the assigned CI owner (reviewer) correct inaccurate attribute values directly on the CI record while performing the certification. Option D is correct because the reviewer must submit a certification response (for example, certified or not certified), and that submission completes the task. Option E is correct because the core purpose of assigning a Data Certification task to a CI owner is to have that reviewer verify whether the CI's data is accurate and up to date.

Option A is incorrect because certification does not automatically retire a CI; retirement is a separate lifecycle action. Option C is incorrect because Data Certification does not automatically generate a high-priority incident for the service desk.

Exam trap

The trap here is assuming that Data Certification triggers automatic lifecycle changes or incident creation; candidates may confuse it with other CMDB processes like retirement workflows or incident management, but certification is strictly about verifying and updating CI data.

12
Multi-Selectmedium

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

Select 2 answers
A.Availability
B.Scalability
C.Correctness
D.Completeness
E.Performance
AnswersC, D

Correctness is one of the two metric types evaluated under the CMDB Health framework, alongside completeness. It measures whether configuration item attributes hold accurate, valid values, satisfying the stem's requirement for a metric type assessed by the framework rather than a compliance or audit score.

Why this answer

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.

13
MCQeasy

When setting up CMDB data ownership, which field on a CI record is typically used to designate the individual accountable for the physical or logical asset's data quality?

A.Managed by
B.Caller ID
C.Reported by
D.Opened by
AnswerA

Managed by designates the person accountable for the CI's data quality, satisfying the ownership requirement. Owned by denotes the group responsible for support, and Supported by is operational, so Managed by is the field that maps to individual accountability for the physical or logical asset.

Why this answer

The 'Managed by' field on a CI record designates the individual accountable for the physical or logical asset's data quality. It is used to assign ownership and responsibility for maintaining accurate information about the CI. This field is typically populated with a user reference and is distinct from fields like 'Caller ID' or 'Reported by', which are used in incident or request contexts.

Exam trap

CIS-DF often tests the confusion between fields used for CI ownership versus those used in incident management, leading candidates to select 'Caller ID' or 'Reported by' incorrectly.

How to eliminate wrong answers

Option B is wrong because 'Caller ID' is used in incident, problem, or change records to identify the person who reported the issue, not for CI ownership. Option C is wrong because 'Reported by' is similar to 'Caller ID' and is used in task-based records, not for CI data stewardship. Option D is wrong because 'Opened by' is used in records like incidents or changes to indicate who created the record, not for CI accountability.

14
MCQeasy

An auditor needs to verify when a critical business application CI was last updated by an authorized discovery source versus a manual update. Which CMDB feature tracks the provenance and history of attribute updates for governance review?

A.CMDB Baseline
B.Reconciliation Engine Simulator
C.Audit Log and CI History
D.CMDB Data Manager
AnswerC

Audit Log and CI History retain each attribute change with its source, timestamp and user, distinguishing discovery-driven updates from manual edits. This provenance trail gives auditors the evidence needed to verify who last modified the application CI and through which channel.

Why this answer

The Audit Log and CI History feature in the CMDB records every change made to a configuration item, including the source of the update (e.g., discovery, manual, import) and the timestamp. This provides the provenance and historical record needed for governance and audit reviews. It allows auditors to distinguish between authorized discovery updates and manual modifications.

Exam trap

CIS-DF often tests the confusion between features that manage data quality (like CMDB Data Manager) and those that provide audit trails (like Audit Log and CI History). Candidates may mistakenly choose CMDB Data Manager thinking it tracks provenance, but it focuses on data certification and bulk updates, not historical audit.

How to eliminate wrong answers

Option A is wrong because CMDB Baseline is used to compare the current state of a CI against a known good baseline, not to track the history or source of individual attribute updates. Option B is wrong because Reconciliation Engine Simulator is a tool for testing reconciliation rules and does not store historical update data. Option D is wrong because CMDB Data Manager is used for bulk data operations and governance of data quality, but it does not provide the detailed audit trail of attribute-level changes with source information.

15
MCQmedium

A CMDB administrator is configuring a Data Certification campaign to verify the accuracy of CI attributes. The administrator wants to ensure that only CIs that have not been certified in the last 6 months are included in the campaign. Which ServiceNow feature should be used to filter the CIs?

A.CMDB Data Manager policies
B.Data Certification filter conditions
C.CMDB Data Governance policies
D.CMDB Health Dashboard filters
AnswerB

When creating a Data Certification campaign, you can define filter conditions to specify which CIs are included. You can use conditions based on fields such as 'Last certified date' to exclude CIs certified within the last 6 months. This allows precise targeting of CIs that require re-certification.

Why this answer

Data Certification filter conditions allow the administrator to specify criteria for including CIs in a campaign. By setting a condition on the 'Last certified' field to be older than 6 months, only those CIs are included. Other options do not provide this filtering capability for certification campaigns.

Exam trap

The trap here is confusing governance policies with certification filters; only the certification campaign configuration includes filter conditions.

16
MCQhard

An organization notices that custom application CIs are failing compliance checks because the governance policy checks standard fields that do not apply to custom apps. How should an administrator resolve this while maintaining governance standards?

A.Disable CMDB Data Governance globally
B.Create a class-specific governance policy targeting the custom application table
C.Add mandatory fields to the base configuration item table (cmdb_ci)
D.Ignore the failed tasks permanently
AnswerB

A class-specific governance policy applies audit criteria only to the custom application table, so standard fields irrelevant to custom apps are no longer enforced while governance remains intact for other classes. This resolves the failures without weakening overall standards.

Why this answer

ServiceNow CMDB Data Governance policies are applied per CI class, so the correct fix is to create a class-specific governance policy that targets the custom application table (a child of cmdb_ci_appl) and defines only the fields relevant to that class. This preserves governance for standard CIs while allowing custom apps to be evaluated against appropriate rules. It maintains compliance standards rather than bypassing them.

Exam trap

The trap is assuming governance is global and all-or-nothing — candidates pick 'disable globally' or 'add fields to base table' instead of recognizing that governance policies are class-scoped and should be tailored per CI class.

How to eliminate wrong answers

Option A is wrong because disabling CMDB Data Governance globally removes all compliance enforcement across every CI class, which destroys governance rather than fixing the custom-app mismatch. Option C is wrong because adding mandatory fields to the base cmdb_ci table would force those fields onto every CI class, causing widespread false failures and polluting the base schema. Option D is wrong because permanently ignoring failed tasks suppresses the symptom without resolving the policy mismatch, leaving the CMDB non-compliant and unauditable.

17
MCQhard

An organization wants to configure CMDB Data Governance remediation tasks so that when a completeness policy fails for a high-priority server, a task is automatically assigned to the data owner. Where are these remediation workflows and task generation parameters configured?

A.CMDB Health > Dashboard Settings
B.Data Certification > Definitions
C.CMDB Data Governance > Policies
D.System Policy > Rules > Data Policy
AnswerC

Remediation workflows and task generation parameters are defined within CMDB Data Governance policies. Each policy specifies the task assignment and scheduling behaviour triggered on failure, so configuring the completeness policy there produces the automatic task for the data owner.

Why this answer

CMDB Data Governance > Policies is where administrators define the health policies (completeness, correctness, compliance, duplicates) and configure the remediation workflow, task assignment rules, and task generation parameters such as the assignee (data owner), priority, and due date. The policy record itself contains the 'Remediation' related list and task generation settings that drive automatic task creation when a high-priority server fails the completeness check.

Exam trap

CIS-DF often tests the confusion between CMDB Health dashboard configuration (display only) and CMDB Data Governance policies (which actually generate remediation tasks), so candidates who pick the dashboard option miss the task-generation capability.

How to eliminate wrong answers

Option A is wrong because CMDB Health > Dashboard Settings only controls which health KPIs and scores are displayed on the CMDB Health dashboard — it does not create remediation tasks or assign them. Option B is wrong because Data Certification > Definitions is used to schedule certification campaigns where CI owners attest to the accuracy of their CIs, not to auto-generate remediation tasks from health policy failures. Option D is wrong because System Policy > Rules > Data Policy governs field-level data policy rules (mandatory/read-only fields) at the platform level, not CMDB health remediation workflows.

18
MCQeasy

An administrator needs to track overall CMDB data quality using standardized metrics out of the box. Which specific dashboard should they access in ServiceNow to view scores for Completeness, Correctness, Compliance, and Freshness?

A.CSDM Framework Dashboard
B.CMDB Health Dashboard
C.Data Certification Dashboard
D.CI Class Manager Dashboard
AnswerB

The CMDB Health Dashboard provides out-of-the-box scores for Completeness, Correctness, Compliance, and Freshness, exactly the four standardised metrics the administrator must track. It aggregates these across the CMDB without custom reporting, satisfying the requirement for overall data quality visibility using standardised metrics.

Why this answer

The CMDB Health Dashboard provides out-of-the-box scores for Completeness, Correctness, Compliance, and Freshness to help administrators measure data quality.

19
MCQeasy

An enterprise wants to establish clear data ownership and automate the lifecycle management tasks of archiving and retiring old hardware servers. Which native ServiceNow tool should be implemented to govern this process?

A.Service Graph Connector
B.CMDB Data Manager
C.Discovery Schedule
D.Identification and Reconciliation Engine (IRE)
AnswerB

CMDB Data Manager enforces ownership through CI class policies and automates lifecycle transitions, including archiving and retiring hardware CIs, directly satisfying the stem's requirement to govern ownership and automate archiving and retirement of old servers.

Why this answer

CMDB Data Manager is the native application designed to automate lifecycle operations such as backup, retire, delete, and attest for CIs based on policy rules.

20
MCQhard

An administrator is reviewing the Correctness score on the CMDB Health Dashboard and notices a low score caused by multiple CIs having no relationships to any business services. Which specific Correctness metric is flagging this issue?

A.Duplicate CIs
B.Orphans
C.Unassigned CIs
D.Stale CIs
AnswerB

Orphans are CIs lacking any relationship to a business service, so they directly reduce the Correctness score. This metric flags exactly the condition described, distinguishing it from duplicate or stale metrics that measure different correctness failures.

Why this answer

The Orphans metric under CMDB Health Correctness flags CIs that have no relationships to any business services or other CIs, indicating they are disconnected from the service model. A low Correctness score caused by CIs lacking business-service relationships is precisely what the Orphans KPI measures. This helps identify CIs that need to be related or retired.

Exam trap

CIS-DF often tests the specific definitions of Correctness KPIs, confusing candidates between Orphans (no relationships), Unassigned (no owner/group), Stale (no recent update), and Duplicate (multiple records).

How to eliminate wrong answers

Option A is wrong because Duplicate CIs measures CIs that appear more than once due to failed identification/reconciliation, not CIs lacking relationships. Option C is wrong because Unassigned CIs refers to CIs without an assigned support group or owner, not CIs missing business-service relationships. Option D is wrong because Stale CIs measures CIs that have not been updated or discovered within a threshold, which is a different correctness dimension than missing relationships.

21
Multi-Selecthard

A CMDB administrator is configuring CMDB Data Governance policies to enforce data quality. The administrator wants to define actions that occur when a policy is violated. Which two actions can be configured in a CMDB Data Governance policy? (Choose two.)

Select 2 answers
A.Block the CI from being saved
B.Assign the CI to a different class
C.Create a remediation task
D.Send an email notification
E.Automatically delete the CI
AnswersC, D

CMDB Data Governance policies can be configured to create a remediation task when a violation occurs. This task is assigned to a responsible user or group to correct the data. This action helps ensure that data quality issues are addressed in a timely manner.

Why this answer

CMDB Data Governance policies support actions such as creating remediation tasks and sending email notifications. These actions help enforce data quality by alerting and assigning work to correct issues. Other actions like deleting, blocking saves, or reclassifying are not native to Data Governance policies.

Exam trap

The trap here is assuming that Data Governance policies can delete or reclassify CIs, but those are outside its scope; it focuses on remediation and notification.

22
MCQeasy

A CMDB manager wants to review the overall health of the CMDB across Completeness, Correctness, and Compliance. Which ServiceNow module should they navigate to first?

A.Configuration > Data Governance > Dashboard
B.Configuration > CMDB Health > Dashboard
C.System Definition > CMDB Dashboard
D.Reports > View > CMDB Health
AnswerB

The CMDB Health Dashboard aggregates Completeness, Correctness and Compliance scores into one view, letting the manager assess overall health across all three pillars simultaneously. Navigating there first satisfies the stem's requirement to review the combined health state before drilling into individual metrics.

Why this answer

The CMDB Health Dashboard is the dedicated ServiceNow module that aggregates the three health pillars — Completeness, Correctness, and Compliance — into a single view with scores, KPIs, and drill-downs. It is accessed via Configuration > CMDB Health > Dashboard, which is the standard navigation path in the CMDB Health plugin (com.snc.cmdb.health). This module is purpose-built for the exact review the manager needs.

Exam trap

CIS-DF often tests whether candidates know the exact navigation path for CMDB Health, baiting them with plausible-sounding but non-existent menu items like 'Data Governance Dashboard' or 'System Definition > CMDB Dashboard'.

How to eliminate wrong answers

Option A is wrong because 'Configuration > Data Governance > Dashboard' is not a real ServiceNow navigation path — Data Governance is a concept, not a module with its own dashboard under Configuration. Option C is wrong because 'System Definition > CMDB Dashboard' does not exist; System Definition contains tables, business rules, and scheduled jobs, not CMDB health dashboards. Option D is wrong because 'Reports > View > CMDB Health' is not a valid navigation; CMDB Health is not surfaced as a report view but as a dedicated dashboard module.

23
MCQeasy

What is the primary role of a 'Data Owner' in the context of ServiceNow CMDB governance?

A.Accountability for the accuracy, completeness, and quality of data within their assigned CI domain
B.Approving financial balance sheets for the enterprise
C.Configuring network switch routing tables
D.Writing custom Java code for MID server extensions
AnswerA

The Data Owner holds accountability for accuracy, completeness and quality of CIs within their assigned domain, approving governance decisions rather than performing daily data entry. This satisfies the stem's governance-role requirement by placing ownership at the domain level.

Why this answer

A Data Owner in ServiceNow CMDB governance is accountable for the accuracy, completeness, and quality of data within their assigned CI domain. They are responsible for validating CIs, approving remediation, and ensuring data meets governance standards. This role is central to the CMDB data governance framework.

Exam trap

CIS-DF often tests governance role definitions, baiting candidates with unrelated responsibilities like financial approvals or network configuration that do not belong to a Data Owner.

How to eliminate wrong answers

Option B is wrong because approving financial balance sheets is a finance function, not a CMDB data governance responsibility. Option C is wrong because configuring network switch routing tables is a network engineering task, not a data ownership role. Option D is wrong because writing custom Java code for MID server extensions is a development task, unrelated to data ownership and governance.

24
MCQmedium

An administrator needs to configure a Data Certification schedule to ensure that Application owners review their respective records quarterly. Which module is used to set up these recurring certification campaigns?

A.Configuration > Governance > Audits
B.CMDB Health > Certification Rules
C.Data Certification > Certification Definitions
D.Service Level Management > Certification
AnswerC

Certification Definitions holds the schedule, filter and scope that generate recurring certification tasks. Configuring it here satisfies the quarterly requirement, because the definition drives task creation for Application owners at the specified interval, unlike the Certification Tasks module, which only shows generated instances.

Why this answer

Data Certification campaigns are configured through the Data Certification module, where administrators create Certification Definitions that specify the target table, filter conditions, certification schedule (e.g., quarterly), and the certifier assignment (such as CI owner or application owner). The Certification Definition is the reusable template that drives each recurring campaign, so it is the correct place to set up quarterly reviews of Application owner records.

Exam trap

CIS-DF often tests the distinction between configuring certification definitions versus reviewing certification tasks, causing candidates to select audit or CMDB Health options that sound governance-related but do not schedule campaigns.

How to eliminate wrong answers

Option A is wrong because Configuration > Governance > Audits is used for audit records and attestation tracking, not for defining recurring certification campaigns. Option B is wrong because CMDB Health > Certification Rules does not exist as a certification scheduling module; CMDB Health focuses on completeness, correctness, and compliance metrics. Option D is wrong because Service Level Management deals with SLAs and OLAs, not data certification scheduling.

25
Multi-Selecthard

When planning a CMDB Governance strategy, which THREE key stakeholder groups should be actively involved in defining data ownership and data quality rules? (Choose three.)

Select 3 answers
A.CMDB / Platform Administrators
B.Compliance and Audit Officers
C.End-users submitting self-service catalog requests
D.Data Owners / CI Stewards
E.External third-party hardware component manufacturers
AnswersA, B, D

CMDB and platform administrators hold technical ownership of the CMDB schema, identification rules and data ingestion pipelines, so they must define enforceable data quality rules and assign CI ownership consistent with platform capabilities and constraints.

Why this answer

Option A (CMDB / Platform Administrators) is correct because these administrators own the technical implementation of the CMDB, including the CI class model, attribute definitions, reconciliation and normalization rules, and health dashboards, so they must help define enforceable data quality rules and ownership workflows. Option B (Compliance and Audit Officers) is correct because they translate regulatory and internal control requirements (e.g., SOX, ISO 27001, ITIL audit criteria) into data retention, accuracy, and evidence standards that the governance strategy must satisfy. Option D (Data Owners / CI Stewards) is correct because they are accountable for the accuracy, completeness, and lifecycle of specific CI classes and attributes, making them the primary parties who assign ownership and approve data quality thresholds.

Option C is not correct because end-users submitting self-service catalog requests are consumers of CMDB data, not stakeholders responsible for defining ownership or quality rules. Option E is not correct because external hardware manufacturers supply component data but have no governance authority over the organization's CMDB data ownership or quality standards.

26
Multi-Selectmedium

Which TWO configurations can be adjusted within CMDB Health Dashboard metric settings? (Choose two.)

Select 2 answers
A.Adjusting metric weightings to influence overall health scoring
B.Configuring SMTP email server relay settings
C.Enabling or disabling specific metric evaluations (e.g., toggling Stale CIs on or off)
D.Defining firewall zone routing rules
E.Modifying underlying hardware CPU core clock speeds
AnswersA, C

Metric weightings are configurable within CMDB Health Dashboard metric settings, letting administrators control how much each metric contributes to the composite health score. Adjusting them aligns scoring with business priorities without altering the underlying metric definitions or evaluation logic.

Why this answer

Option A is correct because the CMDB Health Dashboard metric settings allow administrators to adjust metric weightings, which determine how much each health metric (such as completeness, correctness, or compliance) contributes to the overall CMDB health score. Option C is correct because these settings also let you enable or disable individual metric evaluations, for example toggling the Stale CIs metric on or off, so you can control which checks run and affect the dashboard results. Options B, D, and E are not part of CMDB Health Dashboard metric configuration: SMTP relay settings belong to email/notification configuration, firewall zone routing rules are network security settings, and CPU core clock speeds are hardware/firmware parameters, none of which are adjustable within the CMDB Health metric settings.

Exam trap

The trap here is selecting options that sound like general system configurations but are unrelated to CMDB Health; candidates might pick SMTP settings because they are configurable elsewhere, but the question specifically asks about CMDB Health Dashboard metric settings.

27
Multi-Selectmedium

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

Select 2 answers
A.Unauthorized software installations
B.Mandatory fields missing
C.Orphans
D.Duplicates
E.Support group population status
AnswersC, D

Orphans counts configuration items lacking required relationships, directly measuring data correctness within the CMDB. Because correctness evaluates whether CI records hold valid, complete relationship data, orphaned CIs represent failed integrity checks, satisfying the stem's requirement for a correctness-categorised health metric alongside duplicate and stale metrics.

Why this answer

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.

28
MCQhard

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?

A.Access Control Lists (ACLs) on cmdb_ci fields
B.Data Certification read restrictions
C.Discovery credential filters
D.CMDB Data Governance read-only policies
AnswerA

ACLs on cmdb_ci fields enforce field-level write restrictions, checking the user's roles against the attribute's data classification before permitting edits. This directly blocks unauthorised modification of critical CI attributes on form views, satisfying the audit requirement for role- and classification-based write control.

Why this answer

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.

Exam trap

CIS-DF often tests whether candidates confuse data quality processes (Data Certification) with access control mechanisms (ACLs), causing them to pick a governance process when the question asks for write-access restriction.

How to eliminate wrong answers

Option B is wrong because Data Certification is a process for attesting to the accuracy of CI data, not for restricting write access to attributes — it does not enforce field-level write permissions. Option C is wrong because Discovery credential filters control which credentials are used during discovery, not who can modify CI attributes on forms. Option D is wrong because 'CMDB Data Governance read-only policies' is not a real ServiceNow feature — while read-only policies exist conceptually, the actual enforcement mechanism for field-level write restriction is ACLs, not a governance policy module.

29
MCQeasy

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

A.To ensure continuous data quality, accountability, and ownership of CMDB assets
B.To approve all software license purchases
C.To write custom JavaScript business rules for system performance
D.To manage network switch VLAN configurations
AnswerA

Data stewardship assigns named individuals accountability for CMDB records, so accuracy, completeness and currency are actively maintained rather than assumed. This ownership directly delivers the continuous data quality the scenario requires across the asset estate.

Why this answer

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.

Exam trap

CIS-DF often tests whether candidates understand that CMDB stewardship is about data governance and quality ownership, so the trap is selecting operational or procurement responsibilities that are unrelated to CMDB data integrity.

How to eliminate wrong answers

Option B is wrong because approving software license purchases is a procurement/finance function, not a CMDB stewardship responsibility. Option C is wrong because writing custom JavaScript business rules is a development task, not a stewardship role. Option D is wrong because managing network switch VLAN configurations is an infrastructure operations task, not CMDB data stewardship.

30
MCQmedium

A company implements a policy where department heads must review their server assets every six months. Which module supports scheduling this periodic verification campaign?

A.Data Certification > Certification Schedules
B.Service Portfolio > Reviews
C.Governance, Risk, and Compliance > Periodic Audits
D.CMDB Health > Review Schedules
AnswerA

Certification Schedules under Data Certification lets administrators define recurring review campaigns with defined intervals, such as six-monthly cycles, and assign them to department heads. This directly supports the periodic verification requirement by automating task generation and tracking completion for each reviewer.

Why this answer

Data Certification > Certification Schedules is the ServiceNow module that lets administrators define recurring certification campaigns, including the frequency (e.g., every six months), the CI scope, and the reviewers (department heads). When the schedule fires, certification tasks are generated and assigned to the designated reviewers for attestation.

Exam trap

CIS-DF often tests the confusion between Data Certification (periodic attestation campaigns) and CMDB Health (continuous KPI monitoring), so candidates who pick a non-existent 'Review Schedules' option or GRC audits miss the specific module that schedules certification.

How to eliminate wrong answers

Option B is wrong because Service Portfolio > Reviews is not a standard ServiceNow module for periodic CI verification — Service Portfolio management deals with service offerings and lifecycle, not CI certification. Option C is wrong because Governance, Risk, and Compliance > Periodic Audits is for GRC audit engagements and control testing, not for CI data certification campaigns. Option D is wrong because CMDB Health > Review Schedules does not exist as a module — CMDB Health provides dashboards and KPIs, but scheduling periodic verification is handled by Data Certification.

31
Multi-Selecteasy

Which TWO metrics are standard components of the CMDB Health Dashboard overview? (Choose two.)

Select 2 answers
A.Network latency score
B.Help desk ticket backlog score
C.Correctness score
D.Employee satisfaction score
E.Completeness score
AnswersC, E

Correctness score measures whether CI attributes hold accurate, validated values against expected data, forming one of the standard CMDB Health Dashboard overview metrics. It aggregates rule outcomes across the CMDB, giving administrators a quantified view of data accuracy alongside completeness and compliance scores.

Why this answer

The CMDB Health Dashboard in ServiceNow is built around three standard health metrics: Correctness, Completeness, and Compliance. Option C (Correctness score) is correct because it measures whether CI records have accurate, valid data — for example, CIs that fail validation against CI class rules or have duplicate records — and it appears as a core KPI tile on the dashboard overview. Option E (Completeness score) is correct because it measures whether required CI attributes and relationships are populated, such as missing mandatory fields or missing related CIs, and it is likewise a standard dashboard component.

The other options do not belong: Network latency (A) is a performance/availability metric, Help desk ticket backlog (B) is an ITSM incident/request metric, and Employee satisfaction (D) is a survey/CSAT metric — none of these are CMDB health metrics in the dashboard.

32
MCQeasy

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

A.To generate user satisfaction surveys
B.To run network discovery scans
C.To approve emergency change requests
D.To manage CI class definitions, identification rules, and health inclusions
AnswerD

CI Class Manager governs the class hierarchy itself: it defines CI class definitions, configures identification rules that determine how CIs are uniquely matched, and sets health inclusions controlling which classes contribute to CMDB health metrics, forming the structural basis of governance.

Why this answer

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.

Exam trap

CIS-DF often tests the confusion between CI Class Manager and Discovery — candidates assume the Class Manager runs discovery, but it only configures class metadata and rules.

How to eliminate wrong answers

Option A is wrong because generating user satisfaction surveys is a function of Survey Management, not CI Class Manager. Option B is wrong because running network discovery scans is performed by Discovery, not by CI Class Manager — the Class Manager configures class metadata, not discovery execution. Option C is wrong because approving emergency change requests is a Change Management workflow function, unrelated to CI class configuration.

33
MCQhard

A company is preparing for an ISO compliance audit of its IT infrastructure. The auditor asks to see historical records of who approved changes to critical server ownership attributes over the past year. Which ServiceNow feature provides this verifiable evidence?

A.CI Class History / Audit Trails on CI records
B.Data Certification campaign results from three years ago
C.Discovery schedule run logs
D.CMDB Health Compliance Dashboard score widget
AnswerA

CI Class History captures field-level change records on CI attributes, including who made each modification and when. This directly satisfies the auditor's requirement for verifiable historical evidence of approvals to critical server ownership attributes over the past year.

Why this answer

CI Class History / Audit Trails on CI records capture every field-level change to a CI, including who made the change, when, and the before/after values. This provides the verifiable, timestamped evidence an ISO auditor needs to trace approvals of server ownership attribute changes over the past year.

Exam trap

CIS-DF often tests the difference between change history (audit trails with user attribution) and compliance/health reporting (aggregate scores or certification results) — candidates pick the dashboard or certification option because it sounds audit-related, but only the CI audit trail provides the per-change, per-user evidence an auditor demands.

How to eliminate wrong answers

Option B is wrong because Data Certification campaign results from three years ago are stale, cover a different time window than the auditor requested, and show attestation outcomes rather than the actual change history with approver identity. Option C is wrong because Discovery schedule run logs only show when discovery jobs executed and what they found — they do not record manual changes to ownership attributes or who approved them. Option D is wrong because the CMDB Health Compliance Dashboard score widget shows aggregate compliance percentages, not the granular per-record change history with user attribution that an audit requires.

34
MCQmedium

An enterprise requires that all newly discovered servers must have a valid cost center before being classified as operational. How can this requirement be automated without writing custom scripts?

A.Asset management depreciation rule
B.Discovery cost center transform script
C.CI Class Manager attribute mandatory toggle
D.CMDB Data Governance Completeness Policy
AnswerD

The CMDB Data Governance Completeness Policy enforces required attributes, such as cost center, on newly discovered CIs before they reach operational status. This satisfies the stem's no-custom-scripts constraint by using out-of-box governance rules rather than bespoke code.

Why this answer

The CMDB Data Governance Completeness Policy is the correct answer because it allows administrators to define policies that enforce data completeness requirements — such as requiring a valid cost center — on newly discovered CIs before they can be classified as operational. These policies are configured through the CMDB Data Governance module without writing custom scripts, and they can block or flag CIs that fail the completeness check.

Exam trap

The trap is confusing UI-level mandatory attributes (CI Class Manager toggle) with governance policies that enforce data completeness for operational classification — the question asks for automation without scripts, and only the Data Governance Completeness Policy provides that enforcement.

How to eliminate wrong answers

Option A is wrong because Asset management depreciation rules govern financial depreciation calculations for assets, not data completeness or operational classification of CIs. Option B is wrong because a Discovery cost center transform script is a custom script — the question explicitly requires automation without custom scripts, and transform scripts are code-based. Option C is wrong because the CI Class Manager attribute mandatory toggle only makes an attribute mandatory on the form (UI-level requirement); it does not enforce a governance policy that prevents a CI from being classified as operational based on that attribute's presence.

35
Multi-Selectmedium

Which TWO benefits are gained by scheduling regular Data Certification campaigns in a mature CMDB? (Choose two.)

Select 2 answers
A.Replacing the need for the Identification and Reconciliation Engine (IRE)
B.Maintaining audit readiness and proving data governance compliance
C.Automatically generating physical network router configurations
D.Automatically resolving all IT service desk P1 incidents
E.Engaging CI owners to regularly validate the accuracy of their assigned records
AnswersB, E

Scheduled certification campaigns create timestamped, attributable approval records for each configuration item, directly satisfying auditors' evidence requirements. This recurring attestation cycle demonstrates active governance rather than one-off cleanup, proving that data ownership and review controls operate continuously, which is precisely the audit-readiness and compliance benefit the scenario demands.

Why this answer

Option B is correct because scheduling regular Data Certification campaigns creates a documented, repeatable record of who attested to which CIs and when, which is exactly the evidence auditors and governance frameworks (e.g., COBIT, ISO 20000, SOX controls) require to demonstrate data governance compliance and audit readiness. Option E is correct because a Data Certification campaign in ServiceNow CMDB assigns certification tasks to CI owners, forcing those owners to review and attest to the accuracy of the records they are responsible for, which keeps the CMDB trustworthy over time. Option A is wrong because the Identification and Reconciliation Engine (IRE) is the service that detects and reconciles duplicate or conflicting CI data from discovery and other sources; certification validates existing records and does not replace IRE's deduplication and reconciliation functions.

Option C is wrong because generating physical router configurations is a network automation/tooling task, not a CMDB data governance activity. Option D is wrong because resolving P1 incidents is an incident management process performed by support teams; certification campaigns validate data accuracy and do not automatically resolve incidents.

Exam trap

The trap is assuming Data Certification automates technical processes like IRE or incident resolution; the exam expects recognition that certification is a governance and attestation activity, not a technical reconciliation or automation tool.

36
MCQmedium

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?

A.Discovery Schedule Exclude filters
B.Access Control Lists (ACLs)
C.Reconciliation Definition (Data Precedence)
D.Business Rules on the cmdb_ci table
AnswerC

Reconciliation definitions enforce data precedence, letting you mark manually maintained attributes as authoritative so automated discovery cannot overwrite them. This directly satisfies the stem's constraint: protecting specific server asset tags from discovery-driven updates, while still allowing discovery to populate non-authoritative fields.

Why this answer

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.

Exam trap

CIS-DF often tests the difference between excluding discovery entirely (schedule filters) and governing attribute-level source precedence (reconciliation) — candidates pick exclusion filters and inadvertently stop discovering the CI altogether.

How to eliminate wrong answers

Option A is wrong because Discovery Schedule Exclude filters prevent discovery from scanning certain IP ranges or devices entirely — they do not protect individual attributes on CIs that are still discovered. Option B is wrong because ACLs control who can read/write records at the table/field level for users, not which automated data source wins during reconciliation. Option D is wrong because Business Rules execute logic on record insert/update but are not the CMDB-native governance mechanism for source precedence; they would be a custom, fragile workaround.

37
Multi-Selectmedium

Which TWO methods can be used to assign data ownership to configuration items in the CMDB to support governance and accountability? (Choose two.)

Select 2 answers
A.Editing ACL rules on the cmdb_ci table
B.Modifying Discovery behavior patterns to inject custom firewall rules
C.Populating the 'Owned by' or 'Managed by' fields on the CI record
D.Adjusting Discovery schedule probe frequency
E.Configuring CMDB Data Manager policies to assign owners based on CI filter criteria
AnswersC, E

Populating 'Owned by' or 'Managed by' on the CI record assigns accountability directly on the configuration item itself, satisfying the governance requirement. These reference fields link the CI to a user or group, making ownership queryable and reportable without external mapping.

Why this answer

Option C is correct because the 'Owned by' and 'Managed by' fields on a CI record are the standard ServiceNow reference fields used to designate the person or group accountable for a configuration item, directly supporting governance and accountability. Option E is correct because CMDB Data Manager policies let you define CI filter criteria and then automatically assign ownership fields (such as 'Owned by' or 'Managed by') in bulk, which is the scalable, policy-driven way to enforce ownership across the CMDB. Option A is not correct because ACL rules on cmdb_ci control read/write access to records, not the assignment of ownership data.

Option B is not correct because Discovery behavior patterns are used to identify and classify CIs and their attributes during discovery, not to inject firewall rules or set ownership. Option D is not correct because adjusting Discovery schedule probe frequency only changes how often discovery runs and has no bearing on assigning CI ownership.

38
MCQmedium

A CMDB administrator needs to ensure that all Configuration Items (CIs) of class 'Server' have a value in the 'Environment' field. The administrator wants to prevent CIs from being marked as 'Operational' if this field is empty. Which ServiceNow feature should be used to enforce this requirement?

A.CMDB CI Class Models
B.CMDB Data Governance
C.CMDB Health Dashboard
D.CMDB Data Manager
AnswerB

CMDB Data Governance allows you to create policies that define required fields and can enforce them by preventing CIs from transitioning to operational status if the policy is violated. This is achieved through governance policies that include conditions and actions, such as blocking operational status until the required field is populated.

Why this answer

CMDB Data Governance is the correct feature because it enables the creation of policies that enforce data completeness and can block CI operational status until requirements are met. Other options lack enforcement capabilities; they either monitor, manage lifecycle, or define schema. Thus, only Data Governance can satisfy the requirement to prevent operational status for non-compliant CIs.

Exam trap

The trap here is confusing monitoring tools like CMDB Health Dashboard with enforcement mechanisms, which are provided by CMDB Data Governance policies.

39
MCQeasy

Which ServiceNow application houses the CMDB Health Dashboard, Data Certification, and CMDB Data Governance features?

A.HR Service Delivery
B.Project Portfolio Management
C.Customer Service Management
D.Configuration (CMDB)
AnswerD

Configuration (CMDB) hosts the CMDB Health Dashboard, Data Certification and CMDB Data Governance, satisfying the stem's requirement for a single application containing all three. These capabilities depend on CMDB tables and health scoring, so they reside within the Configuration application rather than separate modules such as Discovery or Service Mapping.

Why this answer

The CMDB Health Dashboard, Data Certification, and CMDB Data Governance features all live within the Configuration (CMDB) application in ServiceNow. This application is the central workspace for managing configuration items, health metrics, and governance policies.

Exam trap

CIS-DF often tests ServiceNow application boundaries — candidates assume CMDB governance features live in a dedicated 'Governance' or 'ITOM' module, but they are all housed under the Configuration (CMDB) application, so picking HR, PPM, or CSM reflects a misunderstanding of the platform's module organization.

How to eliminate wrong answers

Option A is wrong because HR Service Delivery manages employee lifecycle cases and HR catalog items, not CMDB health or data governance. Option B is wrong because Project Portfolio Management handles project, demand, and portfolio records, not configuration item health. Option C is wrong because Customer Service Management manages customer cases and accounts, unrelated to CMDB governance features.

40
Multi-Selecthard

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

Select 3 answers
A.Attribute value validation (checking pattern or lookup criteria)
B.Relationship check (verifying required parent/child connections)
C.Network latency ping response check
D.Hardware warranty expiration date synchronization with vendor APIs
E.Completeness check (verifying required attributes are not empty)
AnswersA, B, E

Attribute value validation lets governance policies evaluate CI records against pattern or lookup criteria, flagging values that breach the defined format or reference set. This is one of the rule criteria types available when configuring CMDB Data Governance policies.

Why this answer

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.

Exam trap

CIS-DF often tests the boundary of what Data Governance policies can evaluate — candidates may assume any data quality check (like ping latency or vendor API sync) is a governance rule, but only completeness, correctness, and relationship checks are supported.

41
MCQmedium

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?

A.CMDB Data Governance completeness policy with strict enforcement
B.UI Actions
C.Service Level Agreement (SLA) definition
D.Access Control Lists (ACLs)
AnswerA

A completeness policy with strict enforcement blocks CI creation or integration when the Environment field is empty, rejecting the record at the point of entry. This directly satisfies the governance team's requirement to prevent non-compliant CIs.

Why this answer

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.

Exam trap

CIS-DF often tests the misconception that ACLs or UI policies can enforce mandatory CI fields; candidates must know that CMDB Data Governance completeness policies with strict enforcement are the correct mechanism for required CI attributes.

How to eliminate wrong answers

Option B is wrong because UI Actions are client-side or server-side scripts that add buttons or behaviors to forms; they do not enforce data completeness policies across integrations. Option C is wrong because an SLA definition governs service level targets and timelines, not CI data quality. Option D is wrong because ACLs control access to records and fields, not whether a field must be populated.

42
MCQhard

An administrator configures a CMDB Data Governance policy to check for missing support groups on business applications. When the policy runs, it creates remediation tasks. How can the administrator ensure these tasks are automatically closed when the data is corrected by a user?

A.Requiring the user to manually email the data governance team
B.Deleting the remediation task manually from the task list
C.Writing a custom business rule on the incident table
D.Automatic re-evaluation and closure upon policy compliance restoration
AnswerD

Automatic re-evaluation detects when the missing support group is populated and closes the associated remediation task once the policy condition is satisfied. This removes manual task closure, ensuring remediation tasks close automatically after user correction.

Why this answer

CMDB Data Governance policies in ServiceNow create remediation tasks when policy violations are detected. When the underlying data is corrected and the policy is re-evaluated, the system can automatically mark the remediation task as closed because the compliance condition is now satisfied. This is the built-in lifecycle behavior of data governance remediation tasks, ensuring tasks do not remain open after the issue is resolved.

Exam trap

The trap is assuming remediation tasks require manual closure or that deleting them is equivalent; the exam expects knowledge that policy re-evaluation automatically closes tasks when compliance is restored.

How to eliminate wrong answers

Option A is wrong because requiring manual email notification is not an automated closure mechanism and defeats the purpose of the governance workflow; it also creates delays and audit gaps. Option B is wrong because manually deleting the remediation task does not close it properly, loses the audit trail, and does not reflect that the data was corrected. Option C is wrong because writing a custom business rule on the incident table is unrelated to CMDB Data Governance remediation tasks, which are not incidents; this would be a misdirected customization that does not address the task lifecycle.

43
Multi-Selectmedium

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

Select 2 answers
A.Allowing any authenticated user to modify production CI configurations without restriction
B.Relying entirely on end-users to manually update all server attributes via service portal requests
C.Disabling all audit logging to improve table insert performance
D.Assigning clear data ownership (Managed by / Support Group) for every CI class
E.Implementing automated remediation tasks for CMDB health and data governance violations
AnswersD, E

Assigning explicit ownership per CI class satisfies the accountability constraint, ensuring each configuration item has a named Managed by and Support Group. Owners validate attributes, approve changes and resolve duplicates, so stale or orphaned records are corrected at source rather than accumulating. This directly sustains data accuracy and completeness across the CMDB lifecycle.

Why this answer

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.

Exam trap

CIS-DF often tests governance by including obviously bad practices (open modification, no audit logs) alongside good ones, so candidates must recognize that governance = accountability + automation, not permissive access or manual-only updates.

44
Multi-Selecthard

When setting up CMDB Data Governance, which THREE elements must be defined for a custom data policy or rule? (Choose three.)

Select 3 answers
A.Evaluation Criteria (the condition or completeness check)
B.MID Server IP address binding range
C.Service-Level Agreement response time threshold for incident escalation
D.Remediation Configuration (task creation and assignment rules)
E.Target CI Class (e.g., cmdb_ci_appl)
AnswersA, D, E

Evaluation Criteria supply the conditional logic a custom policy tests against, such as a completeness check on a configuration item attribute. Without a defined condition, the policy engine has nothing to evaluate, so the rule cannot trigger remediation or flag non-compliant records in the CMDB.

Why this answer

In ServiceNow CMDB Data Governance, a custom data policy or rule requires three core elements: the Target CI Class (option E, e.g., cmdb_ci_appl), which scopes the rule to the specific class of CIs it governs; the Evaluation Criteria (option A), which defines the condition or completeness check that determines whether a CI passes or fails the policy; and the Remediation Configuration (option D), which specifies the task creation and assignment rules that fire when a CI violates the policy. These three together form the complete policy definition — what to check, against which CIs, and what to do when the check fails. Option B (MID Server IP address binding range) is unrelated, as MID Server binding is a discovery/connectivity concern, not a data governance policy element.

Option C (SLA response time threshold for incident escalation) belongs to SLA and incident management configuration, not CMDB data governance.

45
MCQmedium

A company requires that all production Linux servers must have an assigned owner and a valid support group before being eligible for operational use. Which CMDB governance feature can automatically evaluate these specific data requirements and fail or flag non-compliant CI inserts?

A.Discovery Schedule
B.Data Certification
C.CMDB Data Governance
D.CI Class Manager
AnswerC

CMDB Data Governance applies completeness and other data policies that evaluate CI records against defined requirements, failing or flagging inserts that lack an owner or valid support group. This enforces the mandated production-readiness conditions before operational use.

Why this answer

CMDB Data Governance in ServiceNow allows administrators to define data policies that enforce specific requirements on CI records. These policies can include mandatory fields (like owner and support group) and can be configured to run on insert or update, automatically failing or flagging non-compliant CIs. This directly addresses the need to evaluate and enforce data requirements before operational use.

Exam trap

CIS-DF often tests the distinction between data governance (enforcement) and data certification (review), so candidates may confuse Data Certification with Data Governance because both involve data quality.

How to eliminate wrong answers

Option A is wrong because Discovery Schedules are used to automate the discovery of CIs and their attributes, not to enforce data governance rules. Option B is wrong because Data Certification is a periodic review process where owners certify the accuracy of CI data, but it does not automatically evaluate and fail non-compliant CI inserts. Option D is wrong because CI Class Manager is used to manage CI class hierarchies and attributes, not to enforce data policies on CI records.

46
MCQmedium

An auditor requests evidence that all critical databases have an identified support group. Which built-in CMDB feature allows an administrator to quickly run an on-demand check for this specific completeness rule without waiting for scheduled dashboard refreshes?

A.Run a background script using GlideRecord
B.Export the cmdb_ci table to Excel and filter manually
C.Run Policy evaluation from CMDB Data Governance
D.Execute a Full Discovery Scan
AnswerC

Running policy evaluation from CMDB Data Governance executes the completeness policy on demand, immediately returning compliance results for the critical-database support-group rule. This provides the auditor with current evidence without waiting for scheduled dashboard refreshes.

Why this answer

The CMDB Data Governance module includes a Policy evaluation feature that allows administrators to run on-demand checks against defined policies, such as ensuring all critical databases have an identified support group. This bypasses the need to wait for scheduled dashboard refreshes, providing immediate compliance evidence.

Exam trap

CIS-DF often tests the distinction between on-demand policy evaluation and scheduled health jobs, causing candidates to overlook the built-in governance feature and choose custom scripting or manual methods.

How to eliminate wrong answers

Option A is wrong because a background script using GlideRecord is a custom, manual approach that requires scripting and does not leverage built-in governance features. Option B is wrong because exporting to Excel and filtering manually is a time-consuming, error-prone process that does not provide an automated check. Option D is wrong because a Full Discovery Scan is used to discover CIs and their attributes, not to validate governance rules like support group assignment.

47
MCQmedium

A company notices that hundreds of stale server records are polluting the CMDB, negatively affecting health scores. Rather than deleting them manually, what is the best practice governance workflow to handle stale CIs?

A.Initiate a review campaign or automated retirement workflow via CMDB health remediation
B.Delete all records where sys_updated_on is older than 90 days using a background script
C.Run Discovery against the entire IP range daily to force updates
D.Turn off the Stale CI metric so the score improves without action
AnswerA

CMDB health remediation drives stale CIs through a governed review campaign or automated retirement workflow, so hundreds of records are retired in bulk with auditability rather than manually deleted. This satisfies the stem's requirement for a best-practice governance workflow that fixes health scores without manual deletion.

Why this answer

The best-practice governance workflow for stale CIs is to initiate a review campaign or automated retirement workflow through CMDB Health remediation, which routes stale CIs to data owners for validation before retirement. This preserves auditability, respects data ownership, and prevents accidental deletion of CIs that may still be relevant. It also feeds back into the health score legitimately rather than masking the problem.

Exam trap

CIS-DF often tests governance best practices versus quick fixes, baiting candidates with options that delete records or disable metrics instead of following the proper remediation and review workflow.

How to eliminate wrong answers

Option B is wrong because bulk-deleting records older than 90 days via a background script bypasses governance, risks removing valid CIs, and leaves no audit trail — it also violates the principle of data-owner accountability. Option C is wrong because running Discovery daily against the entire IP range does not address stale records that are no longer discoverable; it wastes resources and may not update CIs that are genuinely decommissioned. Option D is wrong because turning off the Stale CI metric is data manipulation that hides the problem instead of remediating it, and it undermines the integrity of the CMDB health score.

48
MCQhard

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?

A.Identification and Reconciliation Engine (IRE)
B.Data Policy Enforcement Engine
C.CMDB Health Duplicate Engine
D.Transform Map Unique Key matching
AnswerA

The IRE applies identification rules and reconciliation to every insert, whether from API integrations or imports, matching incoming payloads against existing CIs and preventing duplicates. It is the native engine enforcing that governance rule on cmdb_ci.

Why this answer

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.

Exam trap

CIS-DF often tests the role of IRE in preventing duplicates, and candidates may confuse it with import set transform maps or data policies, which do not provide comprehensive duplicate prevention across all data sources.

How to eliminate wrong answers

Option B is wrong because Data Policy Enforcement Engine is not a real ServiceNow engine; data policies are used for validation but do not prevent duplicates. Option C is wrong because CMDB Health Duplicate Engine is not a native engine; CMDB Health includes duplicate metrics but does not enforce prevention. Option D is wrong because Transform Map Unique Key matching is a feature of import sets that can help avoid duplicates during imports, but it is not a comprehensive engine that covers API integrations and manual inserts; IRE is the centralized solution.

49
Multi-Selecthard

Which THREE factors should an administrator consider when configuring CMDB Health Inclusion Rules? (Choose three.)

Select 3 answers
A.Operational State (e.g., excluding retired or non-operational CIs)
B.MID Server cluster membership
C.Environment (e.g., separating production from test/lab assets)
D.Email notification retry intervals
E.CI Class (targeting specific tables like servers or databases)
AnswersA, C, E

Retired or non-operational CIs skew health scores because they are no longer actively managed, so inclusion rules must filter on operational state. Excluding them ensures the CMDB Health dashboard reports only on CIs that genuinely require data completeness and compliance validation.

Why this answer

Option A is correct because CMDB Health Inclusion Rules commonly filter CIs by Operational State, allowing administrators to exclude retired, non-operational, or otherwise inactive CIs so they are not counted in health metrics. Option C is correct because Environment is a standard inclusion criterion, letting administrators scope health calculations to production assets and exclude test or lab CIs that would otherwise skew compliance and completeness scores. Option E is correct because CI Class is a fundamental inclusion factor, enabling rules to target specific tables such as servers or databases so health metrics apply only to the relevant CI types.

Option B is not correct because MID Server cluster membership relates to discovery and data collection infrastructure, not to which CIs are included in CMDB Health calculations. Option D is not correct because email notification retry intervals are an alerting or notification setting and have no bearing on CMDB Health Inclusion Rules.

Exam trap

CIS-DF often tests the factors for inclusion rules, and candidates may incorrectly include unrelated options like MID Server membership or notification settings.

50
MCQeasy

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

A.Correctness Duplicate Widget
B.Orphaned CI Widget
C.Completeness Score Widget
D.Compliance Audit Widget
AnswerC

The Completeness Score Widget reports the proportion of CIs holding all mandatory attributes, directly surfacing records with missing required values. It satisfies the requirement to display that ratio, letting administrators target remediation at incomplete CIs affecting overall CMDB health.

Why this answer

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.

Exam trap

The trap is confusing Completeness with Correctness or Compliance; candidates may select the Duplicate Widget thinking it covers missing data, but Completeness specifically addresses missing mandatory attributes.

How to eliminate wrong answers

Option A is wrong because the Correctness Duplicate Widget focuses on duplicate CIs, not missing attributes. Option B is wrong because the Orphaned CI Widget shows CIs without relationships, not missing mandatory attributes. Option D is wrong because the Compliance Audit Widget tracks audit compliance, not completeness of mandatory attributes.

51
MCQhard

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?

A.Discovery Schedules > CMDB Health
B.System Definition > Scheduled Jobs (searching for CMDB Health jobs)
C.CMDB Health Dashboard > Schedule Settings
D.Data Governance > Job Execution
AnswerB

CMDB Health metric calculations run as scheduled jobs, so their timing is altered via System Definition > Scheduled Jobs, where the relevant CMDB Health jobs are located and their run schedule adjusted away from peak hours.

Why this answer

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.

Exam trap

CIS-DF often tests the location of scheduled jobs, and candidates may incorrectly assume that CMDB Health schedules are managed within the CMDB Health Dashboard or Data Governance modules.

How to eliminate wrong answers

Option A is wrong because Discovery Schedules are used to schedule discovery runs, not CMDB Health metric calculations. Option C is wrong because the CMDB Health Dashboard does not provide schedule settings; it displays health results. Option D is wrong because Data Governance > Job Execution is not a standard location for scheduling CMDB Health jobs; it may relate to policy evaluations but not the core health metrics.

52
MCQhard

An enterprise is audited for CSDM compliance. The CSDM Data Foundations Dashboard indicates that application services are not properly connected to technical services. What is the governance impact of this structural gap?

A.Hardware assets will automatically be marked as deprecated
B.Database replication lag will increase across MID servers
C.Discovery will fail to run network scans on IP subnets
D.Inability to accurately perform impact analysis during outages and incorrect service portfolio visibility
AnswerD

Missing technical-service relationships break the CSDM dependency chain, so application services cannot be traced to the infrastructure they consume. That gap directly prevents accurate impact analysis during outages and corrupts service portfolio visibility, satisfying the stem's requirement to identify the governance consequence of the structural disconnect.

Why this answer

In CSDM, application services must be connected to technical services to provide a complete service model. If this linkage is missing, the organization cannot accurately trace the impact of an outage from the business application down to the underlying technical components, and service portfolio visibility becomes fragmented. This directly undermines impact analysis and service health reporting, which are core governance outcomes of CSDM.

Exam trap

CIS-DF often tests the misconception that CSDM gaps affect infrastructure operations like discovery or replication; the real impact is on service visibility and impact analysis, which are governance outcomes.

How to eliminate wrong answers

Option A is wrong because hardware asset deprecation is governed by asset lifecycle policies, not by application-to-technical service relationships; a structural gap in CSDM does not automatically deprecate hardware. Option B is wrong because database replication lag is a database/infrastructure performance issue, unrelated to CSDM service modeling relationships. Option C is wrong because Discovery network scans are configured via discovery schedules and IP ranges, not by application service to technical service connections; CSDM gaps do not prevent network scanning.

53
Multi-Selectmedium

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

Select 2 answers
A.Directly modify core IRE Identification Rules for hardware classes
B.Permanently delete all duplicate CIs across the entire enterprise with a single click
C.View remediation tasks associated with data health failures
D.Drill down into specific failing CIs contributing to poor completeness scores
E.Modify MID Server cluster configurations
AnswersC, D

Remediation tasks surface directly from the dashboard's health metric drill-down, letting you trace failed data health checks to their assigned fixes without leaving the CMDB Health Dashboard. This satisfies the stem's requirement for actions performed directly from the dashboard, since remediation records are linked to the failing metric itself.

Why this answer

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.

Exam trap

CIS-DF often tests whether candidates confuse dashboard investigative actions (view/drill down) with administrative configuration actions (edit IRE rules, delete duplicates) — the exam expects you to know the dashboard is read/investigate-oriented, not a bulk-admin console.

54
MCQeasy

Which role is typically required to manage and configure CMDB Data Governance policies and remediation definitions?

A.asset
B.itil
C.discovery_admin
D.cmdb_datagovernance_admin
AnswerD

The cmdb_datagovernance_admin role grants the privileges needed to create and maintain CMDB Data Governance policies, remediation definitions and related rule configurations. It satisfies the requirement to manage governance policy setup without granting broader platform administrative rights.

Why this answer

The cmdb_datagovernance_admin role is specifically designed to manage and configure CMDB Data Governance policies and remediation definitions. This role grants the necessary permissions to define governance rules, set up remediation workflows, and oversee data integrity within the CMDB. Unlike other roles, it is purpose-built for data governance tasks, ensuring that only authorized users can modify critical governance settings.

Exam trap

CIS-DF often tests the distinction between general CMDB administration roles and specialized data governance roles, causing candidates to confuse the cmdb_datagovernance_admin with broader roles like itil or discovery_admin.

How to eliminate wrong answers

Option A is wrong because the 'asset' role is intended for asset management tasks, such as tracking and managing assets, not for configuring CMDB data governance policies. Option B is wrong because the 'itil' role is a general ITIL role that provides access to ITIL processes like incident, problem, and change management, but does not include the specific permissions required for CMDB data governance. Option C is wrong because the 'discovery_admin' role is focused on configuring and managing discovery schedules, credentials, and related settings, not on data governance policies or remediation definitions.

55
Multi-Selecteasy

Which TWO core benefits does the CSDM Data Foundations Dashboard provide to an organization? (Choose two.)

Select 2 answers
A.Direct control over firewall security policies
B.Identification of orphaned relationships and missing foundational CIs
C.Visibility into CSDM compliance and maturity stages
D.Automated network switch configuration backups
E.Real-time patch management compliance scoring
AnswersB, C

The dashboard scans the CMDB for configuration items lacking mandatory relationships or required foundational data, surfacing orphans and gaps that break dependency mapping. This directly satisfies the stem's demand for a core benefit: proactive identification of data integrity failures, enabling remediation before downstream CSDM processes and reporting are compromised.

Why this answer

Option B is correct because the CSDM Data Foundations Dashboard surfaces data-quality gaps in the CMDB, specifically orphaned relationships (CIs whose relationships point to missing or decommissioned records) and missing foundational CIs that the CSDM framework requires as prerequisites for higher-level modeling. Option C is correct because the dashboard reports on CSDM compliance and shows which maturity stages (e.g., Foundation, Crawl, Walk, Run, Fly) the organization has achieved, letting teams track adoption progress against the CSDM framework. The remaining options do not belong: A (firewall security policy control) is a network security management function, D (automated network switch configuration backups) is a network configuration/backup tool capability, and E (real-time patch management compliance scoring) is a vulnerability/patch management function — none of these are provided by the CSDM Data Foundations Dashboard, which is focused on CMDB data quality and CSDM adoption.

Exam trap

The trap is picking operational capabilities (firewall control, patch scoring, switch backups) that sound like governance but belong to other ITOM/security modules, not the CSDM Data Foundations Dashboard.

56
MCQeasy

A team wants to exclude test and lab servers from being evaluated by strict production CMDB Health completeness rules. What is the best practice method to handle this in ServiceNow?

A.Modify the baseline system properties to ignore completeness globally
B.Delete the test server CIs from the CMDB
C.Configure CMDB Health Inclusion Rules
D.Turn off Discovery for the test network
AnswerC

CMDB Health Inclusion Rules let administrators scope which CIs health calculations evaluate, so test and lab servers can be excluded from strict production completeness rules without altering the rules themselves. This directly satisfies the exclusion requirement.

Why this answer

The best practice to exclude test and lab servers from strict production CMDB Health completeness rules is to configure CMDB Health Inclusion Rules. These rules allow administrators to define conditions that determine which CIs are included in health evaluations, so test servers can be filtered out based on attributes like environment or CI class. This avoids modifying global settings or deleting CIs.

Exam trap

The trap is thinking that global system properties or deletion are viable solutions; the exam expects knowledge that CMDB Health Inclusion Rules provide a scoped, best-practice way to exclude specific CIs from health evaluations.

How to eliminate wrong answers

Option A is wrong because modifying baseline system properties to ignore completeness globally would disable completeness checks for all CIs, not just test servers, which is not a best practice. Option B is wrong because deleting test server CIs from the CMDB removes valuable data and is not a sustainable approach. Option D is wrong because turning off Discovery for the test network would stop data collection but would not exclude existing test CIs from health rules, and it could impact other discovery needs.

Ready to test yourself?

Try a timed practice session using only Governance questions.