Governance practice questions

During an internal audit, an enterprise needs to prove that all changes to server ownership are tracked and verified. Which feature provides a historical log of attribute changes specifically for governance and auditing purposes?

Trap 1: CMDB Data Governance > Audit Trail

The Audit Trail records changes to CMDB records generally, but the question asks specifically for attribute-level change history used in governance. Data Certification Results capture verification outcomes from certification tasks, which is the mechanism that proves ownership was reviewed and confirmed. Audit Trail would be correct for tracking who edited a record, not for proving certification.

Trap 2: Data Certification Results

Data Certification Results record the outcome of certification tasks, showing whether an owner confirmed or rejected a CI, but they do not log every attribute change. The Audit Trail provides the historical log of attribute changes required for governance. Certification Results would be correct when proving periodic ownership verification occurred, not when tracing individual field edits.

Trap 3: System Logs > Audit (sys_audit)

The sys_audit table records field-level changes on individual records, but it is not the governance feature designed to track and verify CI ownership changes as a managed approval process. It is tempting because sys_audit genuinely provides a historical log of attribute changes, which is its actual purpose for general record auditing.

A
CMDB Data Governance > Audit Trail
Why it fails: The Audit Trail records changes to CMDB records generally, but the question asks specifically for attribute-level change history used in governance. Data Certification Results capture verification outcomes from certification tasks, which is the mechanism that proves ownership was reviewed and confirmed. Audit Trail would be correct for tracking who edited a record, not for proving certification.
B
Data Certification Results
Why it fails: Data Certification Results record the outcome of certification tasks, showing whether an owner confirmed or rejected a CI, but they do not log every attribute change. The Audit Trail provides the historical log of attribute changes required for governance. Certification Results would be correct when proving periodic ownership verification occurred, not when tracing individual field edits.
C
System Logs > Audit (sys_audit)
Why it fails: The sys_audit table records field-level changes on individual records, but it is not the governance feature designed to track and verify CI ownership changes as a managed approval process. It is tempting because sys_audit genuinely provides a historical log of attribute changes, which is its actual purpose for general record auditing.
D
CI Class History
CI Class History records a chronological log of attribute changes on configuration items, including ownership fields, retained specifically for governance and audit evidence. This satisfies the audit requirement by providing the historical attribute-change trail that standard CI records do not preserve.

Question 2easymultiple choice

An administrator needs to track adherence to CSDM data standards across business services. Which ServiceNow workspace or dashboard natively provides out-of-the-box visibility into CSDM compliance scores and orphaned relationships?

Trap 1: Data Certification Dashboard

Data certification is used for scheduled validation campaigns, not automated CSDM structural checks.

Trap 2: CMDB Health Dashboard

The CMDB Health Dashboard reports completeness, correctness and compliance of CI records, not CSDM maturity scores or orphaned business service relationships. It is tempting as a CMDB governance tool, but CSDM adherence is surfaced through the CSDM Data Foundations Dashboard instead.

Trap 3: Service Portfolio Management Workspace

Service Portfolio Management Workspace manages service lifecycles, demand and portfolio taxonomy, not CSDM compliance scoring or orphaned relationship detection. It is tempting because it displays business services, yet it lacks the CSDM health KPIs and orphan metrics the requirement demands.

A
Data Certification Dashboard
Why it fails: Data certification is used for scheduled validation campaigns, not automated CSDM structural checks.
B
CSDM Data Foundations Dashboard
This dashboard directly evaluates CSDM maturity and compliance.
C
CMDB Health Dashboard
Why it fails: The CMDB Health Dashboard reports completeness, correctness and compliance of CI records, not CSDM maturity scores or orphaned business service relationships. It is tempting as a CMDB governance tool, but CSDM adherence is surfaced through the CSDM Data Foundations Dashboard instead.
D
Service Portfolio Management Workspace
Why it fails: Service Portfolio Management Workspace manages service lifecycles, demand and portfolio taxonomy, not CSDM compliance scoring or orphaned relationship detection. It is tempting because it displays business services, yet it lacks the CSDM health KPIs and orphan metrics the requirement demands.

Question 3hardmultiple choice

A company implements a policy stating that any server CI not updated in over 90 days should be flagged as stale. Where are the thresholds for stale CIs configured in ServiceNow?

Trap 1: Discovery Definition > Properties > Stale CIs

Discovery Definition properties govern discovery schedules, MID Server behaviour and identification rules, not staleness thresholds for CIs. Stale CI thresholds are configured in CMDB Health settings. Discovery properties would be the right place to adjust discovery ranges, credentials or probe behaviour.

Trap 2: Data Governance > Thresholds

No Data Governance thresholds menu governs stale CI ageing; Data Governance covers policy compliance, remediation and certification, not staleness calculation. Stale thresholds belong to CMDB Health configuration. Data Governance would be correct when defining completeness, correctness or compliance policies and their remediation tasks.

Trap 3: System Properties > UI Properties

UI Properties control interface behaviour such as list rendering, form defaults and display preferences; they hold no CI ageing logic. Stale CI thresholds are set in CMDB Health configuration. UI Properties would be the correct location when changing how records or fields appear to users.

A
Discovery Definition > Properties > Stale CIs
Why it fails: Discovery Definition properties govern discovery schedules, MID Server behaviour and identification rules, not staleness thresholds for CIs. Stale CI thresholds are configured in CMDB Health settings. Discovery properties would be the right place to adjust discovery ranges, credentials or probe behaviour.
B
CMDB Health Dashboard > Settings > Metric Thresholds
Stale CI thresholds are set under CMDB Health Dashboard settings, specifically the Metric Thresholds section. This defines the 90-day age limit that flags servers as stale, driving the health scorecards and remediation tasks that follow.
C
Data Governance > Thresholds
Why it fails: No Data Governance thresholds menu governs stale CI ageing; Data Governance covers policy compliance, remediation and certification, not staleness calculation. Stale thresholds belong to CMDB Health configuration. Data Governance would be correct when defining completeness, correctness or compliance policies and their remediation tasks.
D
System Properties > UI Properties
Why it fails: UI Properties control interface behaviour such as list rendering, form defaults and display preferences; they hold no CI ageing logic. Stale CI thresholds are set in CMDB Health configuration. UI Properties would be the correct location when changing how records or fields appear to users.

Question 4easymultiple choice

Which user role is typically granted to business users so they can participate in Data Certification campaigns by reviewing records assigned to them?

Trap 1: data_certification员 (data_certification)

The role name is data_certification.

Trap 2: itil

itil users manage IT service management records, not specifically data certification campaigns unless assigned.

Trap 3: cmdb_read

cmdb_read only provides read access to CMDB tables, not certification task workflow execution.

A
data_certification
The data_certification role allows users to access and complete assigned data certification tasks.
B
data_certification员 (data_certification)
Why it fails: The role name is data_certification.
C
itil
Why it fails: itil users manage IT service management records, not specifically data certification campaigns unless assigned.
D
cmdb_read
Why it fails: cmdb_read only provides read access to CMDB tables, not certification task workflow execution.

Question 5hardmulti select

Which THREE components are required when setting up a Data Certification schedule in ServiceNow? (Choose three.)

Trap 1: Automatic MID Server selection rule

MID servers are used for Discovery, not Data Certification campaigns.

A
Automatic MID Server selection rule
Why it fails: MID servers are used for Discovery, not Data Certification campaigns.
B
Assigned Reviewer or group mapping
Campaigns require designated reviewers (such as CI owners) to perform the validations.
C
Certification Filter (specifying which CIs are in scope)
Filters determine which table and records are evaluated during the certification campaign.
D
Direct integration webhook to external ERP systems
ERP webhooks are not part of core Data Certification setup.
E
Certification Schedule (defining start date, recurrence, and completion window)
Schedules control when and how often certification campaigns run.

Question 6easymulti select

Which TWO user roles are typically associated with managing and reviewing CMDB Health and Governance dashboards? (Choose two.)

Trap 1: itil

The itil role grants broad ITSM process access but carries no CMDB Health or Governance dashboard permissions; those require cmdb_read plus specific health roles. It is tempting because ITIL users own CI lifecycle tasks, so it would be the right choice for incident, change and problem management rather than dashboard governance.

Trap 2: survey_admin

survey_admin governs survey definitions, questions and responses, granting no access to CMDB Health or Governance dashboards. It is tempting because survey-style assessments resemble certification tasks, so it would be correct when building or administering survey questionnaires rather than reviewing CMDB health metrics.

Trap 3: approval_user

approval_user only permits acting on approval records routed to the user, with no CMDB Health or Governance dashboard rights. It is tempting because certification campaigns involve approvals, so it would be the right choice for approving change or catalog requests rather than managing CMDB health dashboards.

A
itil
Why it fails: The itil role grants broad ITSM process access but carries no CMDB Health or Governance dashboard permissions; those require cmdb_read plus specific health roles. It is tempting because ITIL users own CI lifecycle tasks, so it would be the right choice for incident, change and problem management rather than dashboard governance.
B
survey_admin
Why it fails: survey_admin governs survey definitions, questions and responses, granting no access to CMDB Health or Governance dashboards. It is tempting because survey-style assessments resemble certification tasks, so it would be correct when building or administering survey questionnaires rather than reviewing CMDB health metrics.
C
approval_user
Why it fails: approval_user only permits acting on approval records routed to the user, with no CMDB Health or Governance dashboard rights. It is tempting because certification campaigns involve approvals, so it would be the right choice for approving change or catalog requests rather than managing CMDB health dashboards.
D
sn_cmdb_admin
The sn_cmdb_admin role grants administrative control over CMDB configuration, including health and governance dashboard setup, so it satisfies the scenario's need to manage these dashboards. It carries the elevated privileges required to configure health metrics and governance rules across CI classes.
E
cmdb_health_dashboard_admin
The cmdb_health_dashboard_admin role is purpose-built for administering CMDB Health dashboards, directly satisfying the requirement to manage and review health and governance views. It scopes access precisely to dashboard configuration without granting broader CMDB administrative rights.

Question 7mediummultiple choice

An administrator needs to report on how many CIs were successfully certified during the latest Data Certification campaign. Where can this certification campaign result data be viewed?

Trap 1: System Logs > Certification Trail

System Logs > Certification Trail holds diagnostic and audit log entries about certification execution, not the per-CI certification outcome records needed for reporting counts. It is tempting because it sounds like a certification-specific record store, and would be correct for troubleshooting why a campaign or certification task failed.

Trap 2: CMDB Health > Audit Reports

CMDB Health > Audit Reports presents compliance and audit findings against health metrics, not the certified or rejected status of each CI from a campaign. It is tempting because it is a CMDB reporting surface, and would be correct for reviewing data compliance against audit rules rather than campaign certification results.

Trap 3: Configuration > Compliance Logs

Compliance Logs record audit events such as CI class changes and data policy violations, not campaign outcomes. Certification results live in the Data Certification module's campaign records. It is tempting because compliance auditing sounds adjacent to certification, but the log holds no per-campaign pass/fail counts.

A
System Logs > Certification Trail
Why it fails: System Logs > Certification Trail holds diagnostic and audit log entries about certification execution, not the per-CI certification outcome records needed for reporting counts. It is tempting because it sounds like a certification-specific record store, and would be correct for troubleshooting why a campaign or certification task failed.
B
CMDB Health > Audit Reports
Why it fails: CMDB Health > Audit Reports presents compliance and audit findings against health metrics, not the certified or rejected status of each CI from a campaign. It is tempting because it is a CMDB reporting surface, and would be correct for reviewing data compliance against audit rules rather than campaign certification results.
C
Configuration > Compliance Logs
Why it fails: Compliance Logs record audit events such as CI class changes and data policy violations, not campaign outcomes. Certification results live in the Data Certification module's campaign records. It is tempting because compliance auditing sounds adjacent to certification, but the log holds no per-campaign pass/fail counts.
D
Data Certification > Certification Results
Data Certification > Certification Results holds per-campaign certification outcomes, including counts of CIs successfully certified, making it the direct source for the latest campaign's figures. Unlike general reporting or audit logs, this view is scoped to certification decisions, satisfying the requirement to report successful certifications specifically.

Question 8hardmulti select

Which THREE methods can be used to resolve duplicate CIs identified by the CMDB Health Dashboard? (Choose three.)

Trap 1: Restarting all running MID servers in the cluster

MID servers are Java processes that execute discovery and integration probes; restarting them re-establishes connectivity and clears stuck jobs, but changes nothing about duplicate CI records. It is tempting because MID issues cause failed discovery, and a restart would be correct when probes stop reporting or the cluster is unhealthy.

Trap 2: Modifying inbound email actions

Inbound email actions parse received messages and create or update records; editing them alters how email-generated incidents or CIs are processed, not how existing duplicate CIs are reconciled. It is tempting because email actions do create records, and modifying them would be correct to stop a mail source generating bad data.

A
Restarting all running MID servers in the cluster
Why it fails: MID servers are Java processes that execute discovery and integration probes; restarting them re-establishes connectivity and clears stuck jobs, but changes nothing about duplicate CI records. It is tempting because MID issues cause failed discovery, and a restart would be correct when probes stop reporting or the cluster is unhealthy.
B
Modifying inbound email actions
Why it fails: Inbound email actions parse received messages and create or update records; editing them alters how email-generated incidents or CIs are processed, not how existing duplicate CIs are reconciled. It is tempting because email actions do create records, and modifying them would be correct to stop a mail source generating bad data.
C
Manually reviewing and deleting or retiring the redundant CI record
Manually reviewing and deleting or retiring the redundant CI record directly satisfies the remediation requirement, since the CMDB Health Dashboard only identifies duplicates and does not auto-merge them. Retiring preserves historical relationships and audit trails, whereas deletion suits records created in error, giving administrators granular control over each duplicate.
D
Using the CI Merge tool to combine duplicate records and remap relationships
The CI Merge tool directly satisfies the deduplication requirement by combining duplicate records into a single authoritative CI and remapping their relationships, so no dependent data is orphaned. This is the platform's native remediation path for duplicates flagged by the CMDB Health Dashboard, unlike manual deletion or exclusion rules.
E
Configuring automated duplicate remediation rules to automatically merge or task duplicates
Automated duplicate remediation rules directly address the dashboard's duplicate CI findings by merging records or generating tasks for owners, satisfying the requirement to resolve duplicates at scale rather than merely detecting them. This mechanism clears the duplicate metric without manual intervention, which the other listed methods cannot achieve.

Question 9hardmultiple choice

A company has strict compliance mandates requiring that any modification to a Business Service relationship must be authorized by the Service Owner. Which ServiceNow feature can be configured to audit and require approval for relationship changes in the CMDB?

Trap 1: Data Certification schedules for relationships

Data certification runs point-in-time reviews, not real-time approval gates for relationship creation.

Trap 2: Workflow editor on the task table

Workflow editor on the task table orchestrates approvals for task records, not cmdb_rel_ci relationship rows, so Service Owner authorisation of Business Service relationship changes cannot be enforced. It tempts because workflows commonly gate change and catalog approvals; that is the right tool when the governed record is a task, not a CMDB relationship.

Trap 3: Service Level Agreements (SLAs) on the cmdb_rel_ci table

SLAs measure and escalate against time targets on the cmdb_rel_ci table; they neither capture approval nor audit relationship modifications, so Service Owner authorisation is never enforced. It tempts because SLAs attach to any table and can trigger notifications, which is correct for tracking response or resolution deadlines, not for approval governance.

A
Data Certification schedules for relationships
Why it fails: Data certification runs point-in-time reviews, not real-time approval gates for relationship creation.
B
Workflow editor on the task table
Why it fails: Workflow editor on the task table orchestrates approvals for task records, not cmdb_rel_ci relationship rows, so Service Owner authorisation of Business Service relationship changes cannot be enforced. It tempts because workflows commonly gate change and catalog approvals; that is the right tool when the governed record is a task, not a CMDB relationship.
C
Service Level Agreements (SLAs) on the cmdb_rel_ci table
Why it fails: SLAs measure and escalate against time targets on the cmdb_rel_ci table; they neither capture approval nor audit relationship modifications, so Service Owner authorisation is never enforced. It tempts because SLAs attach to any table and can trigger notifications, which is correct for tracking response or resolution deadlines, not for approval governance.
D
CMDB Data Governance Relationship Policies
Relationship Policies let you enforce approval workflows on specific CMDB relationship types, so any change to a Business Service relationship is held pending Service Owner authorisation. This satisfies the compliance mandate by gating modifications rather than merely logging them after the fact.

Question 10mediummultiple choice

An organization wants to configure CMDB health score targets (e.g., maintaining an overall score above 85%). Where are health score targets and thresholds managed?

Trap 1: Data Governance > Scorecards

Scorecards define KPI indicators and targets for performance analytics, not CMDB Health thresholds. CMDB Health score targets are configured in the CMDB Health properties via the CI Class Manager or Health settings. It tempts because scorecards do hold targets, but they govern metric scores, not CMDB health scoring.

Trap 2: System Properties > Performance Analytics

System Properties > Performance Analytics holds analytics configuration, not CMDB Health scoring thresholds. CMDB Health targets are set within the CMDB Health property records, adjusted through the Health settings or CI Class Manager. It tempts because system properties store global settings, but CMDB Health scoring uses its own dedicated property records.

Trap 3: CI Class Manager > Scoring

CI Class Manager > Scoring configures class-specific health scoring weights and metric inclusion, not the overall health score target. The overall threshold is set in the CMDB Health properties. It tempts because class scoring does affect health scores, but the global target percentage lives in the CMDB Health configuration.

A
Data Governance > Scorecards
Why it fails: Scorecards define KPI indicators and targets for performance analytics, not CMDB Health thresholds. CMDB Health score targets are configured in the CMDB Health properties via the CI Class Manager or Health settings. It tempts because scorecards do hold targets, but they govern metric scores, not CMDB health scoring.
B
System Properties > Performance Analytics
Why it fails: System Properties > Performance Analytics holds analytics configuration, not CMDB Health scoring thresholds. CMDB Health targets are set within the CMDB Health property records, adjusted through the Health settings or CI Class Manager. It tempts because system properties store global settings, but CMDB Health scoring uses its own dedicated property records.
C
CI Class Manager > Scoring
Why it fails: CI Class Manager > Scoring configures class-specific health scoring weights and metric inclusion, not the overall health score target. The overall threshold is set in the CMDB Health properties. It tempts because class scoring does affect health scores, but the global target percentage lives in the CMDB Health configuration.
D
CMDB Health Dashboard > Settings > Score Thresholds
Health score targets and thresholds are configured in the CMDB Health Dashboard under Settings, where administrators define the overall score target and per-KPI thresholds. This satisfies the requirement to maintain an overall score above 85% by letting you set that exact percentage as the target the dashboard evaluates against.

Question 11mediummultiple choice

An enterprise wants to ensure that when a Data Certification campaign task is overdue, an escalation notification is automatically sent to the reviewer's manager. Where are task escalation rules or notifications typically configured for Data Certification?

Trap 1: CI Class Manager > Notifications

CI Class Manager > Notifications configures class-level CI notifications such as expiry or ownership alerts, not Data Certification task escalation. It is tempting because it is the notification hub for CMDB classes, so it would be correct for alerting on CI attribute changes or CI lifecycle events rather than overdue certification tasks.

Trap 2: Data Governance > Escalation Workflows

No Data Governance > Escalation Workflows module exists in the platform; escalation for certification tasks is configured through the Data Certification campaign's task reminder and escalation settings. It is tempting because the name matches governance terminology, so a dedicated escalation workflow area would be the right place if such a module existed.

Trap 3: CMDB Health > Escalation Properties

CMDB Health > Escalation Properties does not exist; CMDB Health surfaces compliance, completeness and correctness metrics but holds no escalation properties. It is tempting because CMDB Health is the governance dashboard area, so it would be correct for configuring health score thresholds and KPI exclusions rather than certification task escalation.

A
CI Class Manager > Notifications
Why it fails: CI Class Manager > Notifications configures class-level CI notifications such as expiry or ownership alerts, not Data Certification task escalation. It is tempting because it is the notification hub for CMDB classes, so it would be correct for alerting on CI attribute changes or CI lifecycle events rather than overdue certification tasks.
B
System Notification > Notifications (targeting certification task tables)
Configuring notifications against certification task tables lets the platform trigger escalation emails when a task's due date passes, satisfying the overdue-escalation requirement. Notification records evaluate conditions on those tables and route to the reviewer's manager via the task's assignment hierarchy.
C
Data Governance > Escalation Workflows
Why it fails: No Data Governance > Escalation Workflows module exists in the platform; escalation for certification tasks is configured through the Data Certification campaign's task reminder and escalation settings. It is tempting because the name matches governance terminology, so a dedicated escalation workflow area would be the right place if such a module existed.
D
CMDB Health > Escalation Properties
Why it fails: CMDB Health > Escalation Properties does not exist; CMDB Health surfaces compliance, completeness and correctness metrics but holds no escalation properties. It is tempting because CMDB Health is the governance dashboard area, so it would be correct for configuring health score thresholds and KPI exclusions rather than certification task escalation.

Question 12mediummultiple choice

An organization requires that all database CIs have their assigned support group populated before being marked as operational, failing which a compliance task should be generated. Which feature should be configured to enforce this policy?

Trap 1: Reconciliation Definition

Reconciliation Definitions resolve duplicate CIs and reconcile attribute conflicts between data sources; they do not evaluate required-field completeness or generate compliance tasks. It is tempting because reconciliation governs CI data integrity, and would be correct when merging duplicate records or enforcing authoritative source precedence.

Trap 2: CMDB Data Manager

CMDB Data Manager runs scheduled bulk lifecycle operations such as retire, archive and delete on CIs; it cannot block operational status or raise compliance tasks for missing support groups. It is tempting because it manages CI lifecycle at scale, and would be correct for automating retirement of stale records.

Trap 3: Data Certification

Data Certification issues periodic attestation tasks asking owners to confirm CI attributes remain accurate; it does not enforce mandatory-field population before a CI becomes operational. It is tempting because certification also produces tasks, and would be correct for scheduled reviews of existing CI accuracy.

A
Reconciliation Definition
Why it fails: Reconciliation Definitions resolve duplicate CIs and reconcile attribute conflicts between data sources; they do not evaluate required-field completeness or generate compliance tasks. It is tempting because reconciliation governs CI data integrity, and would be correct when merging duplicate records or enforcing authoritative source precedence.
B
CMDB Data Manager
Why it fails: CMDB Data Manager runs scheduled bulk lifecycle operations such as retire, archive and delete on CIs; it cannot block operational status or raise compliance tasks for missing support groups. It is tempting because it manages CI lifecycle at scale, and would be correct for automating retirement of stale records.
C
Data Certification
Why it fails: Data Certification issues periodic attestation tasks asking owners to confirm CI attributes remain accurate; it does not enforce mandatory-field population before a CI becomes operational. It is tempting because certification also produces tasks, and would be correct for scheduled reviews of existing CI accuracy.
D
CMDB Audit Rules
CMDB Audit Rules evaluate CI records against defined conditions and can generate compliance tasks when violations occur. Configuring a rule requiring the support group field to be populated before operational status satisfies the enforcement requirement, automatically raising tasks for non-compliant database CIs.

Question 13hardmultiple choice

A ServiceNow implementation specialist is configuring Data Certification to ensure that application owners regularly review the accuracy of their business-critical applications. Where must the filter criteria be specified to determine which CIs are included in the certification schedule?

Trap 1: Inside the CI Class Manager under Governance settings

CI Class Manager defines class hierarchy, identification and reconciliation rules, not certification filter criteria. The filter determining which CIs enter a certification schedule is set on the Data Certification schedule record itself. Class Manager tempts because it governs CI classes broadly, but it holds no certification scheduling fields.

Trap 2: On the CMDB Health Dashboard compliance settings tab

The CMDB Health Dashboard displays compliance, completeness and correctness KPIs; its settings tab configures health score thresholds and weights, not certification scope. Certification filters live on the Data Certification schedule. The dashboard tempts because both concern CI data quality, yet health scoring and certification scheduling are separate mechanisms.

Trap 3: In the CMDB Data Manager policy definition

CMDB Data Manager policies automate CI lifecycle tasks such as retirement, archival and deletion, driven by policy conditions on CI records. Certification filter criteria are defined on the Data Certification schedule instead. Data Manager tempts because it also targets CI subsets, but it executes lifecycle actions rather than review assignments.

A
Inside the CI Class Manager under Governance settings
Why it fails: CI Class Manager defines class hierarchy, identification and reconciliation rules, not certification filter criteria. The filter determining which CIs enter a certification schedule is set on the Data Certification schedule record itself. Class Manager tempts because it governs CI classes broadly, but it holds no certification scheduling fields.
B
In the Certification Filter related list of the audit definition
The Certification Filter related list on the audit definition holds the encoded query that scopes which CIs each certification task covers. This satisfies the requirement to determine inclusion in the schedule, since Data Certification generates tasks only for records matching that filter, letting application owners review their business-critical applications.
C
On the CMDB Health Dashboard compliance settings tab
Why it fails: The CMDB Health Dashboard displays compliance, completeness and correctness KPIs; its settings tab configures health score thresholds and weights, not certification scope. Certification filters live on the Data Certification schedule. The dashboard tempts because both concern CI data quality, yet health scoring and certification scheduling are separate mechanisms.
D
In the CMDB Data Manager policy definition
Why it fails: CMDB Data Manager policies automate CI lifecycle tasks such as retirement, archival and deletion, driven by policy conditions on CI records. Certification filter criteria are defined on the Data Certification schedule instead. Data Manager tempts because it also targets CI subsets, but it executes lifecycle actions rather than review assignments.

Question 14hardmulti select

An administrator is setting up CMDB Data Manager policies to govern the lifecycle of server CIs. Which THREE lifecycle stages are natively supported by CMDB Data Manager out of the box? (Choose three.)

Trap 1: Discovery

Discovery is managed via Discovery schedules and patterns, not CMDB Data Manager lifecycle policies.

Trap 2: Provision

Provisioning is handled by orchestration and catalog workflows, not CMDB Data Manager policies.

A
Attestation
CMDB Data Manager ships with attestation as a native lifecycle stage, letting administrators certify CI accuracy before retention or archival actions run. This satisfies the stem's out-of-the-box constraint: attestation is available without custom development, alongside the other natively supported stages the question requires.
B
Archive
Archiving is a supported policy action to move old CIs to archive tables.
C
Discovery
Why it fails: Discovery is managed via Discovery schedules and patterns, not CMDB Data Manager lifecycle policies.
D
Retire
Retire is one of the three natively supported CMDB Data Manager lifecycle stages, alongside operational and end-of-life states. It lets administrators schedule retirement workflows that archive or delete server CIs once they are decommissioned, satisfying the stem's requirement for out-of-the-box lifecycle governance without custom scripting.
E
Provision
Why it fails: Provisioning is handled by orchestration and catalog workflows, not CMDB Data Manager policies.

Question 15mediummulti select

Which TWO of the following metrics are included in the standard out-of-the-box CMDB Health Dashboard? (Choose two.)

Trap 1: Performance

Performance is not a calculated metric within the CMDB Health Dashboard framework.

Trap 2: Availability

CMDB Health Dashboard tracks completeness, correctness and compliance — for example orphan CIs, duplicate CIs and stale records. Availability is monitored by Event Management and service level reporting, not CMDB Health, though both concern CI state.

Trap 3: Security

CMDB Health Dashboard measures completeness, correctness and compliance of CMDB data, not security posture. Security metrics come from Security Operations or Vulnerability Response. It is tempting because CI records carry fields that security tools consume, but CMDB Health does not score them.

A
Freshness
Freshness measures whether CIs have been updated within their expected audit intervals, and it ships as a standard out-of-the-box CMDB Health metric alongside Completeness and Correctness. It satisfies the stem's requirement for a default dashboard metric.
B
Completeness
Completeness is a core out-of-the-box CMDB Health metric, tracking required attributes and relationships that are missing from CIs. It ships by default alongside Correctness and Compliance, satisfying the stem's requirement for a standard dashboard metric.
C
Performance
Why it fails: Performance is not a calculated metric within the CMDB Health Dashboard framework.
D
Availability
Why it fails: CMDB Health Dashboard tracks completeness, correctness and compliance — for example orphan CIs, duplicate CIs and stale records. Availability is monitored by Event Management and service level reporting, not CMDB Health, though both concern CI state.
E
Security
Why it fails: CMDB Health Dashboard measures completeness, correctness and compliance of CMDB data, not security posture. Security metrics come from Security Operations or Vulnerability Response. It is tempting because CI records carry fields that security tools consume, but CMDB Health does not score them.

Question 16hardmultiple choice

A global financial services company runs its CMDB on ServiceNow. The governance board has mandated that any change to the 'Environment' attribute on a Business Application CI classified as 'Mission Critical' must be reviewed and approved by the application owner before the change is committed. The Change Management process already uses standard change models, but the CMDB team wants to enforce this control directly within the CMDB itself, independent of any change request. Which ServiceNow CMDB governance feature should the implementation specialist configure to meet this requirement?

Trap 1: CMDB CI Class Manager attribute-level write ACL restricted to the…

CI Class Manager is used to define class hierarchy and attributes, not to enforce approval workflows. While an ACL could restrict who can write to the Environment attribute, it would block all other editors entirely rather than route changes for owner approval. The requirement is for review and approval, not blanket denial. This approach would break legitimate updates by administrators and does not provide an auditable approval trail.

Trap 2: CMDB Data Manager lifecycle policy

CMDB Data Manager lifecycle policies automate the archival, retirement, or deletion of CIs based on age or inactivity. They do not evaluate attribute-level changes or enforce an approval workflow before a CI update is saved. This scenario requires pre-commit review of a specific attribute, which lifecycle policies cannot provide. Using this feature would leave the Environment attribute editable without owner approval, failing the governance mandate.

Trap 3: CMDB Health completeness rule on the Environment attribute

CMDB Health completeness rules measure whether required fields are populated; they do not gate changes or require approvals. A completeness rule could flag an empty Environment value, but it cannot prevent a user from changing the value from 'Production' to 'Test' without owner consent. This option addresses data quality scoring, not change authorization, so it fails to meet the governance board's control requirement.

A
CMDB Governance attestation with a custom approval workflow triggered on CI update
CMDB Governance attestation allows you to define policies that require review and approval of CI records or specific attributes before changes are accepted. By configuring an attestation policy scoped to the 'Environment' attribute on Business Application CIs with 'Mission Critical' classification, and attaching a custom approval workflow, the system enforces owner review directly in the CMDB. This satisfies the requirement independent of Change Management, ensuring no unauthorized modification is committed.
B
CMDB CI Class Manager attribute-level write ACL restricted to the application owner
Why it fails: CI Class Manager is used to define class hierarchy and attributes, not to enforce approval workflows. While an ACL could restrict who can write to the Environment attribute, it would block all other editors entirely rather than route changes for owner approval. The requirement is for review and approval, not blanket denial. This approach would break legitimate updates by administrators and does not provide an auditable approval trail.
C
CMDB Data Manager lifecycle policy
Why it fails: CMDB Data Manager lifecycle policies automate the archival, retirement, or deletion of CIs based on age or inactivity. They do not evaluate attribute-level changes or enforce an approval workflow before a CI update is saved. This scenario requires pre-commit review of a specific attribute, which lifecycle policies cannot provide. Using this feature would leave the Environment attribute editable without owner approval, failing the governance mandate.
D
CMDB Health completeness rule on the Environment attribute
Why it fails: CMDB Health completeness rules measure whether required fields are populated; they do not gate changes or require approvals. A completeness rule could flag an empty Environment value, but it cannot prevent a user from changing the value from 'Production' to 'Test' without owner consent. This option addresses data quality scoring, not change authorization, so it fails to meet the governance board's control requirement.

Question 17hardmultiple choice

A financial services company has a strict requirement that any change to a Configuration Item (CI) that is classified as 'High Business Impact' must be approved by the Data Owner. Which ServiceNow capability should be configured to meet this requirement?

Trap 1: CMDB Health Dashboard

The CMDB Health Dashboard displays health scores and metrics but does not provide approval workflows or enforce change approval based on CI classification. It is a reporting tool, not a workflow engine. Therefore, it cannot enforce the approval requirement for changes to high-impact CIs.

Trap 2: CMDB CI Class Models

CMDB CI Class Models define the attributes and relationships for CI classes but do not include approval logic. They are used for data modeling, not for enforcing governance rules. Thus, they cannot enforce the approval requirement for changes to high-impact CIs.

Trap 3: CMDB Data Manager

CMDB Data Manager handles lifecycle operations like archiving and deletion, not change approval processes. It does not integrate with change management to require approvals. Its focus is on managing the lifecycle of CIs, not on governing changes to them.

A
CMDB Health Dashboard
Why it fails: The CMDB Health Dashboard displays health scores and metrics but does not provide approval workflows or enforce change approval based on CI classification. It is a reporting tool, not a workflow engine. Therefore, it cannot enforce the approval requirement for changes to high-impact CIs.
B
CMDB Data Governance
CMDB Data Governance can be configured with policies that trigger approval workflows when certain conditions are met, such as a CI having a 'High Business Impact' attribute. The policy can require approval from the Data Owner before the change is applied. This ensures that only authorized changes are made to critical CIs.
C
CMDB CI Class Models
Why it fails: CMDB CI Class Models define the attributes and relationships for CI classes but do not include approval logic. They are used for data modeling, not for enforcing governance rules. Thus, they cannot enforce the approval requirement for changes to high-impact CIs.
D
CMDB Data Manager
Why it fails: CMDB Data Manager handles lifecycle operations like archiving and deletion, not change approval processes. It does not integrate with change management to require approvals. Its focus is on managing the lifecycle of CIs, not on governing changes to them.

Question 18mediummultiple choice

A CMDB administrator needs to ensure that all CIs of class 'Application' have a valid 'Business Owner' assigned. The administrator wants to create a policy that checks this and, if violated, assigns a remediation task to the CIO. Which ServiceNow feature should be used?

Trap 1: CMDB CI Class Models

CMDB CI Class Models define the schema and can mark fields as mandatory, but they do not create remediation tasks or assign them to users. They enforce data entry at the form level, but not through automated tasks. Therefore, they do not fulfill the requirement.

Trap 2: CMDB Health Dashboard

The CMDB Health Dashboard shows completeness scores but does not create remediation tasks or enforce policies. It can highlight that Business Owner is missing, but it cannot automatically assign a task to the CIO. Therefore, it does not meet the requirement.

Trap 3: CMDB Data Manager

CMDB Data Manager is used for lifecycle management, such as archiving or deleting CIs, and does not create remediation tasks based on field completeness. It cannot enforce the assignment of a Business Owner. Thus, it is not the correct feature.

A
CMDB CI Class Models
Why it fails: CMDB CI Class Models define the schema and can mark fields as mandatory, but they do not create remediation tasks or assign them to users. They enforce data entry at the form level, but not through automated tasks. Therefore, they do not fulfill the requirement.
B
CMDB Health Dashboard
Why it fails: The CMDB Health Dashboard shows completeness scores but does not create remediation tasks or enforce policies. It can highlight that Business Owner is missing, but it cannot automatically assign a task to the CIO. Therefore, it does not meet the requirement.
C
CMDB Data Governance
CMDB Data Governance allows the creation of policies that check for required fields like 'Business Owner' and can create remediation tasks assigned to a specific user, such as the CIO. This directly enforces the requirement and automates task assignment.
D
CMDB Data Manager
Why it fails: CMDB Data Manager is used for lifecycle management, such as archiving or deleting CIs, and does not create remediation tasks based on field completeness. It cannot enforce the assignment of a Business Owner. Thus, it is not the correct feature.

Question 19easymultiple choice

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?

Trap 1: Modify the baseline system properties to ignore completeness…

Editing baseline system properties disables completeness evaluation for every CI class, not just test and lab servers. The correct approach is a CI class or filter-based health exclusion, or a dedicated CI class for non-production assets, so production rules remain enforced while test servers are scoped out.

Trap 2: Delete the test server CIs from the CMDB

Deleting CIs removes them from the CMDB entirely, breaking dependency mapping, incident linkage and audit history rather than merely exempting them from health rules. It is tempting because it eliminates the failing records, and would be right if the servers were genuinely decommissioned and no longer referenced.

Trap 3: Turn off Discovery for the test network

Disabling Discovery halts population and refresh of all CIs on that network, so the CMDB loses visibility rather than merely excluding those servers from health evaluation. Discovery scope control is for networks you never intend to manage, not for filtering which existing CIs a completeness rule assesses.

A
Modify the baseline system properties to ignore completeness globally
Why it fails: Editing baseline system properties disables completeness evaluation for every CI class, not just test and lab servers. The correct approach is a CI class or filter-based health exclusion, or a dedicated CI class for non-production assets, so production rules remain enforced while test servers are scoped out.
B
Delete the test server CIs from the CMDB
Why it fails: Deleting CIs removes them from the CMDB entirely, breaking dependency mapping, incident linkage and audit history rather than merely exempting them from health rules. It is tempting because it eliminates the failing records, and would be right if the servers were genuinely decommissioned and no longer referenced.
C
Configure CMDB Health Inclusion Rules
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.
D
Turn off Discovery for the test network
Why it fails: Disabling Discovery halts population and refresh of all CIs on that network, so the CMDB loses visibility rather than merely excluding those servers from health evaluation. Discovery scope control is for networks you never intend to manage, not for filtering which existing CIs a completeness rule assesses.

Question 20hardmultiple choice

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?

Trap 1: CMDB Health > Dashboard Settings

Dashboard Settings controls only CMDB Health scorecard display, weightings and KPI visibility; it generates no remediation tasks and holds no assignment parameters. Remediation workflows and task generation live under CMDB Data Governance policy configuration. Dashboard Settings would be the right place to tune how health scores appear to stakeholders.

Trap 2: Data Certification > Definitions

Data Certification Definitions schedule certification audits and assign certifiers to verify CI attributes; they do not create remediation tasks when a completeness policy fails. Remediation workflows and task generation parameters sit in CMDB Data Governance policy records. Data Certification would be correct when the requirement is periodic attestation of CI accuracy by owners.

Trap 3: System Policy > Rules > Data Policy

System Policy Data Policy rules govern field-level validation and mandatory values on forms; they do not generate remediation tasks or assign them to data owners. CMDB Data Governance policy configuration holds those workflows and parameters. Data Policy would be correct when enforcing attribute formatting or required fields during record entry.

A
CMDB Health > Dashboard Settings
Why it fails: Dashboard Settings controls only CMDB Health scorecard display, weightings and KPI visibility; it generates no remediation tasks and holds no assignment parameters. Remediation workflows and task generation live under CMDB Data Governance policy configuration. Dashboard Settings would be the right place to tune how health scores appear to stakeholders.
B
Data Certification > Definitions
Why it fails: Data Certification Definitions schedule certification audits and assign certifiers to verify CI attributes; they do not create remediation tasks when a completeness policy fails. Remediation workflows and task generation parameters sit in CMDB Data Governance policy records. Data Certification would be correct when the requirement is periodic attestation of CI accuracy by owners.
C
CMDB Data Governance > Policies
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.
D
System Policy > Rules > Data Policy
Why it fails: System Policy Data Policy rules govern field-level validation and mandatory values on forms; they do not generate remediation tasks or assign them to data owners. CMDB Data Governance policy configuration holds those workflows and parameters. Data Policy would be correct when enforcing attribute formatting or required fields during record entry.