Courseiva

CCNA Db Admin Cmdb Questions

75 of 99 questions · Page 1/2 · Db Admin Cmdb topic · Answers revealed

Practice these questionsExam hubAll questions
1
MCQhard

A custom table 'u_custom_server' extends 'cmdb_ci_server' and has additional fields. The admin notices that while regular attribute updates on the parent table propagate correctly to the child, some custom fields are not being updated during discovery. What is the most likely cause?

A.The custom fields are not defined as 'Active' in the dictionary.
B.The discovery probe does not have access to the custom fields.
C.The identification rule does not include custom fields.
D.The custom table has a stale glide record.
AnswerC

If custom fields are not part of the identification rule, discovery will not update them.

Why this answer

Option C is correct because ServiceNow's CMDB identification and reconciliation framework uses identification rules to determine which fields are used to match CI records during discovery. Custom fields on a child table like 'u_custom_server' are not automatically included in the parent table's identification rule; they must be explicitly added to the identification rule for the CI class. Without this, the discovery probe may create duplicate CIs or fail to update those custom fields, as the system does not consider them part of the unique identifier or update set.

Exam trap

The trap here is that candidates often assume discovery updates all fields on a table automatically, but ServiceNow's CMDB requires explicit configuration of identification rules to control which fields are used for matching and updating, especially for custom fields on extended tables.

How to eliminate wrong answers

Option A is wrong because if a custom field is not marked as 'Active' in the dictionary, it would not appear in the form or be available for data entry, but discovery updates are driven by the identification and reconciliation engine, not the field's active state. Option B is wrong because discovery probes operate at the system level and do not have field-level access controls; they use MID servers and credentials to collect data, and any field that exists in the table can be populated if the probe is configured to collect it. Option D is wrong because a 'stale glide record' is not a standard ServiceNow concept; records can be stale due to reconciliation rules or update failures, but this is a symptom, not a root cause, and the issue is specifically about identification rules not including custom fields.

Practice this question →
2
MCQhard

An organization uses ServiceNow Discovery to populate the CMDB. They notice that some CIs are missing required relationships after discovery. What is the most likely reason?

A.The discovered CIs are in different classes that do not have relationship rules.
B.The discovery probes and sensors are not configured to create relationships.
C.The IRE is set to 'reconcile only' and not 'create'.
D.The relationship type is not defined in the CMDB.
AnswerB

Probes and sensors must be designed to identify and create relationships during discovery.

Why this answer

Discovery probes and sensors are responsible for collecting data from devices, but they do not automatically create relationships unless specifically configured to do so. If the probes and sensors lack the necessary configuration to identify and record relationships, the discovered CIs will remain isolated in the CMDB. This is the most common cause of missing relationships after a Discovery run.

Exam trap

The trap here is that candidates often confuse the IRE's role (which handles CI creation and reconciliation) with the role of Discovery probes/sensors (which handle relationship creation), leading them to incorrectly select Option C.

How to eliminate wrong answers

Option A is wrong because relationship rules are defined between CI classes, and if the discovered CIs belong to classes that do not have relationship rules, the IRE would still create the CIs but simply not populate relationships; the question states that relationships are missing, not that the CIs themselves are missing. Option C is wrong because the IRE's 'reconcile only' mode prevents creation of new CIs but does not affect relationship creation; relationships are created by Discovery probes/sensors, not by the IRE. Option D is wrong because if the relationship type were not defined in the CMDB, Discovery would still create the CIs and the relationship would simply be stored with a generic or default type, not be entirely absent.

Practice this question →
3
MCQhard

During a CMDB health review, an administrator finds that many CI records have the same serial number but different names and IP addresses. What is the most likely root cause?

A.The CMDB has a scheduled job that deletes old CIs.
B.The CI class has a unique constraint on the name field.
C.The identification rule for the CI class does not include the serial number.
D.The reconciliation rule is set to 'Create' instead of 'Update'.
AnswerC

Without serial number as an identifier, the system creates new records instead of updating existing ones.

Why this answer

The correct answer is C because the identification rule determines which fields are used to uniquely identify a CI. If the serial number is not included in the identification rule, the CMDB cannot detect duplicates based on serial number, allowing multiple CIs with the same serial number but different names and IP addresses to be created. This is a common misconfiguration that leads to CI proliferation and data inconsistency.

Exam trap

The trap here is that candidates often confuse identification rules with reconciliation rules, assuming that reconciliation settings control duplicate detection, when in fact identification rules define the uniqueness criteria that trigger reconciliation.

How to eliminate wrong answers

Option A is wrong because a scheduled job that deletes old CIs would remove CIs based on age or last updated time, not cause duplicate serial numbers with different names and IP addresses. Option B is wrong because a unique constraint on the name field would prevent duplicate names, but the issue here is duplicate serial numbers with different names, so a name constraint would not cause or prevent this problem. Option D is wrong because setting the reconciliation rule to 'Create' instead of 'Update' would cause new CIs to be created on every import, but it would not specifically result in the same serial number appearing on multiple CIs with different names and IPs; the identification rule is what controls how duplicates are detected.

Practice this question →
4
MCQmedium

Given the IRE identification rule shown, what will happen when a Discovery probe sends a CI with a name that already exists in the CMDB but with a different business_service?

A.The discovery will fail and not create or update any CI.
B.The existing CI will be updated with the new business_service.
C.A new CI will be created because the business_service is different.
D.The identification rule will match based on name only, ignoring business_service.
AnswerC

Since the combination of name and business_service does not match, IRE creates a new CI.

Why this answer

The IRE (Identification and Reconciliation Engine) rule in ServiceNow uses the 'name' field as the primary identifier for CIs. When a Discovery probe sends a CI with a name that already exists but a different business_service, the IRE treats the business_service as a separate attribute, not part of the identification key. Therefore, it creates a new CI because the combination of identification attributes (name alone) does not match any existing CI when the business_service differs, as the rule does not include business_service in the match criteria.

Exam trap

The trap here is that candidates assume the 'name' field is a unique identifier across all attributes, but ServiceNow's IRE treats each identification rule independently, and a different non-key attribute like business_service forces a new CI creation, not an update or failure.

How to eliminate wrong answers

Option A is wrong because Discovery does not fail; the IRE processes the CI and either creates or updates based on the identification rule, not failing due to a name match with a different attribute. Option B is wrong because the existing CI will not be updated with the new business_service; the IRE only updates CIs when all identification attributes match, and since business_service is not part of the identification rule, a name match alone does not trigger an update. Option D is wrong because the identification rule does not match based on name only; it matches based on the defined identification attributes (name), but the rule's behavior is to create a new CI when the business_service differs, not to ignore it.

Practice this question →
5
MCQmedium

A company wants to ensure that when a server CI is retired, all its associated running services are automatically updated to reflect the retirement. What is the best practice?

A.Configure a business rule on the CI class to update related CIs on state change.
B.Use the CI Lifecycle Manager to define a retirement business rule.
C.Use the Relationship Viewer to manually edit each relationship.
D.Create a scheduled job to check for retired CIs and update dependencies.
AnswerB

CI Lifecycle Manager offers built-in capabilities to trigger updates on related CIs when a CI is retired.

Why this answer

The CI Lifecycle Manager provides a dedicated framework for defining lifecycle states and automating actions when a CI transitions between states, such as retirement. By configuring a retirement business rule within the CI Lifecycle Manager, you can automatically update or retire all associated running services when a server CI is retired, ensuring consistency without manual intervention.

Exam trap

The trap here is that candidates often assume a simple business rule on the CI class is sufficient, but the SNOW-CSA exam emphasizes the CI Lifecycle Manager as the best practice for managing CI state transitions and their cascading effects on related records.

How to eliminate wrong answers

Option A is wrong because a business rule on the CI class can trigger on state change, but it lacks the lifecycle-aware context and built-in relationship handling that the CI Lifecycle Manager provides; it would require custom scripting to manage all related services. Option C is wrong because manually editing each relationship via the Relationship Viewer is not scalable and contradicts the goal of automation. Option D is wrong because a scheduled job introduces latency and complexity, and it does not provide real-time, event-driven updates when a CI is retired, unlike the lifecycle framework.

Practice this question →
6
Multi-Selectmedium

Which TWO attributes are essential for identifying configuration items in the CMDB to ensure uniqueness? (Choose exactly 2.)

Select 2 answers
A.MAC address
B.Asset tag
C.Name
D.Serial number
E.IP address
AnswersA, D

Network interface MAC addresses are globally unique.

Why this answer

Option A (MAC address) is correct because a MAC address is a globally unique hardware identifier assigned to network interfaces by the manufacturer, making it a reliable and immutable attribute for uniquely identifying configuration items (CIs) such as servers, switches, and workstations in the CMDB. In ServiceNow, the MAC address is often used as a deduplication key to prevent duplicate CIs, especially when discovered via network probes or agents. Its uniqueness is guaranteed at the hardware level, unlike attributes that can be changed or reassigned.

Exam trap

The trap here is that candidates often confuse 'uniqueness' with 'common usage' and select IP address or name because they are frequently used in daily operations, but the exam specifically tests the understanding that MAC addresses and serial numbers are hardware-level, immutable identifiers that guarantee uniqueness across the entire CMDB.

Practice this question →
7
Multi-Selectmedium

An administrator is troubleshooting issues with the CMDB identification and reconciliation engine. Which three components are part of the identification and reconciliation process? (Choose three.)

Select 3 answers
A.Transform maps
B.Reconciliation rules
C.Data source
D.Identification rules
E.CI Class Manager
AnswersB, C, D

These rules specify how to handle CI merging and conflict resolution.

Why this answer

Reconciliation rules (B) are a core component of the CMDB identification and reconciliation process because they define how to handle duplicate or conflicting CIs during the reconciliation phase. These rules determine which data source takes precedence, whether to merge or overwrite attributes, and how to resolve conflicts between multiple sources. Without reconciliation rules, the system cannot maintain a single authoritative view of each CI.

Exam trap

The trap here is that candidates confuse the data import pipeline (transform maps, data sources) with the identification and reconciliation engine, which only includes identification rules, reconciliation rules, and data sources as the three core components.

Practice this question →
8
MCQhard

An organization is planning to implement CMDB for a large-scale environment with multiple data sources. They need to ensure that the most trustworthy data source takes precedence when conflicts occur. Which feature should they use?

A.Identification & Reconciliation engine
B.Reconciliation
C.Set source precedence in the CI class manager for each CI
D.Data Source Priority
AnswerD

This feature allows setting precedence for data sources.

Why this answer

Data Source Priority (Option D) is the correct feature because it allows administrators to define a hierarchy of data sources in the CMDB, ensuring that when multiple sources provide conflicting attribute values for the same CI, the source with the highest priority (lowest numeric value) is trusted and its data is used. This directly addresses the requirement to make the most trustworthy data source take precedence in a large-scale, multi-source environment.

Exam trap

The trap here is that candidates often confuse the Identification & Reconciliation engine (which performs the conflict detection) with the Data Source Priority feature (which dictates which source wins), leading them to select Option A instead of D.

How to eliminate wrong answers

Option A is wrong because the Identification & Reconciliation engine is responsible for identifying CIs and reconciling them against existing records, but it does not itself set a priority order among data sources; it relies on the Data Source Priority configuration to resolve conflicts. Option B is wrong because 'Reconciliation' is a broad process within the CMDB that includes identification, merging, and conflict resolution, but it is not a specific feature that assigns precedence to data sources. Option C is wrong because setting source precedence in the CI class manager for each CI is not a valid operation; source precedence is configured globally or per data source in the Data Source Priority settings, not per CI class or individual CI.

Practice this question →
9
MCQmedium

A company has a custom application that automatically updates the CMDB via web services. After a recent update, several CI records were incorrectly modified, causing incorrect relationships. The administrator does not know exactly which web service calls caused the issue. What is the best way to identify the source of the incorrect updates and prevent future occurrences?

A.Enable the 'Data Integrity' feature to log all web service updates.
B.Revert the CMDB to a previous state using a backup.
C.Review the cmdb_ci table audit history to see changes.
D.Restrict web service access to only necessary roles and review logs.
AnswerC

Audit logs capture who or what changed each field, enabling identification of the problematic web service calls.

Why this answer

Option C is correct because the cmdb_ci table audit history captures detailed records of all changes made to CI records, including the source of the update (e.g., web service call, user, or script). By reviewing this audit trail, the administrator can identify which specific web service calls modified the CIs incorrectly, even without prior logging enabled. This approach leverages ServiceNow's built-in auditing for CMDB tables, which is enabled by default for critical CI tables.

Exam trap

The trap here is that candidates may confuse the 'Data Integrity' feature with auditing or logging, assuming it captures change history, when in fact it only validates data quality rules and does not record transactional changes.

How to eliminate wrong answers

Option A is wrong because the 'Data Integrity' feature in ServiceNow is designed to detect and report data quality issues (e.g., missing mandatory fields, orphaned CIs) but does not log web service updates or provide a historical record of changes. Option B is wrong because reverting the CMDB to a previous backup would undo all changes, including legitimate updates, and does not help identify the source of the incorrect modifications; it is a reactive measure, not a diagnostic one. Option D is wrong because restricting web service access and reviewing logs is a preventive measure that does not help identify which specific past web service calls caused the issue; it addresses future occurrences but not the immediate need to trace the source of the incorrect updates.

Practice this question →
10
MCQmedium

An administrator needs to create a new CI class for 'Database Instance' that extends the existing 'cmdb_ci' table. Which tool should be used?

A.System Definition > Tables
B.CMDB Data Manager
C.CI Class Manager
D.Studio
AnswerC

CI Class Manager is designed to create and manage CI classes.

Why this answer

The CI Class Manager is the dedicated tool in ServiceNow for creating and managing Configuration Item (CI) classes, including extending existing tables like 'cmdb_ci' to create a new 'Database Instance' class. It provides a guided interface to define class hierarchy, attributes, and relationships specific to CMDB, ensuring proper alignment with the Common Service Data Model (CSDM).

Exam trap

The trap here is that candidates confuse general table creation (System Definition > Tables) with CMDB-specific class creation, not realizing that CI Class Manager enforces CSDM compliance and proper CI lifecycle management.

How to eliminate wrong answers

Option A is wrong because System Definition > Tables is used for creating or modifying database tables in general, not specifically for CMDB CI class hierarchy or CSDM-compliant CI class creation. Option B is wrong because CMDB Data Manager is a tool for importing, exporting, and reconciling CI data, not for defining new CI class structures or extending the cmdb_ci table. Option D is wrong because Studio is an application development environment for building scoped applications and customizing modules, but it is not the recommended or direct tool for creating a new CI class that extends cmdb_ci; that task is specifically handled by CI Class Manager.

Practice this question →
11
MCQeasy

In the CMDB, what is the purpose of the 'cmdb_ci' table?

A.It stores the discovery schedule and probes.
B.It is the base table for all hardware and software CI classes.
C.It contains the CMDB health rules.
D.It stores relationships between configuration items.
AnswerB

cmdb_ci is the parent table for all CI classes.

Why this answer

The 'cmdb_ci' table is the base (or parent) table for all hardware and software Configuration Item (CI) classes in the ServiceNow CMDB. It defines common fields such as name, serial number, and operational status, which are inherited by all child CI tables (e.g., cmdb_ci_server, cmdb_ci_software_product). This design follows a single-table inheritance model, ensuring consistency across all CI types.

Exam trap

The trap here is that candidates often confuse the 'cmdb_ci' base table with the 'cmdb_rel_ci' relationship table, assuming that the base table stores relationships rather than being the parent for all CI classes.

How to eliminate wrong answers

Option A is wrong because discovery schedules and probes are stored in the 'discovery_schedule' and 'discovery_probe' tables, not in 'cmdb_ci'. Option C is wrong because CMDB health rules are stored in the 'cmdb_health_rule' table, which defines conditions for CI health scoring. Option D is wrong because relationships between CIs are stored in the 'cmdb_rel_ci' table, which links two CIs via a relationship type defined in 'cmdb_rel_type'.

Practice this question →
12
MCQeasy

What is the purpose of the 'Operational Status' field on a CMDB CI?

A.To indicate the CI's current operational health.
B.To track the CI's maintenance schedule.
C.To define the CI's business criticality.
D.To record the CI's last discovery date.
AnswerA

Operational Status reflects whether the CI is functioning properly.

Why this answer

The 'Operational Status' field on a CMDB CI in ServiceNow indicates the current operational health of the configuration item, such as whether it is functioning normally, in a degraded state, or down. This field is used to quickly assess the real-time status of a CI, enabling IT operations to prioritize incident response and change management based on the CI's operational condition.

Exam trap

The trap here is that candidates confuse 'Operational Status' with 'Business Criticality' or 'Maintenance Schedule', as all three fields relate to CI management but serve distinct purposes in the CMDB.

How to eliminate wrong answers

Option B is wrong because the 'Operational Status' field does not track maintenance schedules; maintenance schedules are managed via the 'Maintenance Schedule' related list or a separate field on the CI form. Option C is wrong because business criticality is defined by the 'Business Criticality' field, not the 'Operational Status' field, which focuses on technical health rather than business impact. Option D is wrong because the last discovery date is recorded in the 'Last Discovered' field, which is separate from the 'Operational Status' field that reflects the CI's current operational state.

Practice this question →
13
Multi-Selectmedium

Which two statements are true about CMDB relationships? (Select two.)

Select 2 answers
A.Relationship types are defined in the cmdb_rel_type table.
B.Relationships are stored in the cmdb_rel_ci table.
C.Relationships can only be created manually.
D.A CI can have only one relationship of a given type.
E.The 'Depends on' relationship is default for all CIs.
AnswersA, B

The cmdb_rel_type table defines all relationship types.

Why this answer

Option A is correct because the `cmdb_rel_type` table stores the definitions of all relationship types in the ServiceNow CMDB, such as 'Depends on' and 'Used by'. Each record in this table defines a unique relationship type with its name, direction, and cardinality constraints. This table is the authoritative source for the relationship types available in the system.

Exam trap

The trap here is that candidates often confuse the `cmdb_rel_type` table (which defines relationship types) with the `cmdb_rel_ci` table (which stores actual relationships), and mistakenly think relationships are stored in the type table or that all CIs automatically have a 'Depends on' relationship.

Practice this question →
14
Multi-Selecthard

A CMDB administrator is planning to use the CMDB Data Manager to perform data imports. Which THREE statements about the Data Manager are true? (Select exactly 3)

Select 3 answers
A.It can create relationships between CIs during import.
B.It automatically reconciles imported CIs with existing CIs.
C.It can transform data using transform maps.
D.It can directly import data from external databases.
E.It supports scheduled imports from CSV files.
AnswersA, C, E

Transform maps can populate relationship fields, creating relationships.

Why this answer

Option A is correct because the CMDB Data Manager can create relationships between Configuration Items (CIs) during the import process. When importing data, you can specify relationship definitions in the import source or transform map, allowing the Data Manager to automatically link CIs (e.g., 'Runs on', 'Depends on') based on the imported data, which is essential for maintaining a complete and accurate CMDB.

Exam trap

The trap here is that candidates confuse the Data Manager's ability to create relationships during import (which is true) with automatic reconciliation (which is a separate process), leading them to incorrectly select Option B.

Practice this question →
15
MCQhard

An administrator inspects the IRE log and sees the exhibit. The IRE created a new CI despite finding a match on serial_number. What is the most likely reason?

A.The identification rule for cmdb_ci_server includes serial_number.
B.The IRE is configured to always create new records regardless of matches.
C.The identification rule for cmdb_ci_server does NOT include serial_number.
D.The existing CI has a different name, so IRE considers it a different CI.
AnswerC

Without serial_number in the rule, the IRE treats it as a new CI.

Why this answer

Option C is correct because the IRE uses identification rules to determine which attributes are used for matching CIs. If the identification rule for cmdb_ci_server does NOT include serial_number, then even though a match on serial_number exists, the IRE will not consider it a match and will create a new CI. The IRE only reconciles based on the attributes defined in the identification rule.

Exam trap

The trap here is that candidates assume the IRE automatically uses all unique fields (like serial_number) for matching, but in reality, only the attributes explicitly listed in the identification rule are used for reconciliation.

How to eliminate wrong answers

Option A is wrong because if the identification rule for cmdb_ci_server included serial_number, the IRE would have matched the incoming CI to the existing one and would not have created a new CI. Option B is wrong because the IRE does not have a global setting to always create new records; its behavior is governed by identification and reconciliation rules. Option D is wrong because the IRE does not consider the CI name as a matching attribute unless it is explicitly included in the identification rule; the name alone does not cause the IRE to treat it as a different CI.

Practice this question →
16
MCQeasy

A large enterprise has implemented ServiceNow CMDB with multiple discovery sources including Service Mapping, Cloud Management, and manual imports. Over the past six months, the CMDB has grown to over 2 million CI records, and users are reporting that CMDB queries and reports take a long time to load. The administrator checks the database and finds that the cmdb_ci table has over 1.5 million records, including many retired and historical CIs. The average query time for reports on active hardware CIs is 30 seconds. The instance is hosted on a standard mid-range node. The administrator has verified that no duplicate CIs exist and that all CI classes are properly configured. The instance's performance dashboard shows high database contention. Which action should the administrator take first to improve CMDB performance?

A.Request a ServiceNow upgrade to a higher performance tier.
B.Create a new database view that combines cmdb_ci with other tables to improve report efficiency.
C.Disable all discovery sources except Service Mapping to reduce data inflow.
D.Run the 'CMDB - Data Archiving' scheduled job to move retired CIs older than 6 months to the archive table.
AnswerD

Archiving reduces the active table size, directly improving query performance.

Why this answer

Option D is correct because the primary issue is high database contention caused by an excessive number of historical and retired CI records in the active cmdb_ci table. Running the 'CMDB - Data Archiving' scheduled job moves retired CIs older than 6 months to the archive table, reducing the active table size and query load. This directly addresses the root cause without requiring infrastructure changes or disabling critical discovery sources.

Exam trap

The trap here is that candidates often jump to scaling the infrastructure (Option A) or modifying discovery (Option C) without recognizing that CMDB performance degradation is typically caused by data bloat in the active table, which is resolved by archiving rather than by hardware or process changes.

How to eliminate wrong answers

Option A is wrong because requesting a ServiceNow upgrade to a higher performance tier treats the symptom (slow queries) rather than the cause (bloated active table), and is an expensive, unnecessary step when data archiving can resolve the issue. Option B is wrong because creating a new database view that combines cmdb_ci with other tables would likely increase query complexity and execution time, worsening performance rather than improving it. Option C is wrong because disabling all discovery sources except Service Mapping would stop data inflow but does nothing to address the existing 1.5 million records causing contention, and would break critical CMDB population processes.

Practice this question →
17
MCQmedium

A company uses ServiceNow CMDB and wants to ensure that CI attribute updates from a discovery tool are not overwritten by manual changes made by administrators. Which configuration best achieves this?

A.Set the CI source to 'Manual' to prevent discovery updates.
B.Create a business rule to prevent updates from discovery.
C.Configure the 'Preserve manual changes' setting in the CMDB CI Class Manager.
D.Disable the reconciliation process for the affected CIs.
AnswerC

This setting ensures that manual changes are not overwritten by automated updates.

Why this answer

Option C is correct because the 'Preserve manual changes' setting in the CMDB CI Class Manager ensures that when a CI attribute is manually updated by an administrator, subsequent discovery runs will not overwrite that specific attribute. This setting works at the class level and compares the source of the last update; if the source is 'Manual', the attribute is preserved even if the discovery tool reports a different value. This directly addresses the requirement to prevent discovery from overwriting manual changes without disabling discovery entirely.

Exam trap

The trap here is that candidates often confuse the 'Preserve manual changes' setting with the 'Ignore changes' flag or assume that disabling reconciliation is the only way to stop overwrites, when in fact the setting is a granular, attribute-level protection mechanism built into the CMDB CI Class Manager.

How to eliminate wrong answers

Option A is wrong because setting the CI source to 'Manual' prevents discovery from updating the CI at all, which is too restrictive and would block legitimate automated updates from the discovery tool. Option B is wrong because creating a business rule to prevent updates from discovery would require custom scripting and maintenance, and it is not the recommended or supported approach for preserving manual changes in the CMDB. Option D is wrong because disabling the reconciliation process would stop all CI attribute updates from discovery, not just preserve manual changes, and it would break the intended CMDB data flow and identification/reconciliation rules.

Practice this question →
18
MCQeasy

An administrator wants to ensure that when a user deletes a CI, all its relationships are also deleted to maintain data integrity. What should the administrator configure?

A.A cascade delete rule on the relationship table
B.An ACL that denies delete unless relationships are removed first
C.A CMDB health rule that flags orphaned relationships
D.A business rule on the CI table that deletes relationships on delete
AnswerA

Cascade delete rules are designed for this purpose.

Why this answer

Option A is correct because a cascade delete rule on the relationship table (sys_cmdb_rel_ci) ensures that when a CI is deleted, all associated relationship records are automatically removed. This maintains referential integrity in the CMDB without requiring custom scripting or manual cleanup.

Exam trap

The trap here is that candidates often choose a business rule (Option D) because it seems logical, but ServiceNow's native cascade delete on reference fields is the correct and simpler approach, avoiding the need for custom scripting.

How to eliminate wrong answers

Option B is wrong because an ACL that denies delete unless relationships are removed first would prevent the deletion entirely, not automate the cleanup, and would require manual intervention. Option C is wrong because a CMDB health rule can only flag orphaned relationships after they exist, not prevent them from occurring. Option D is wrong because a business rule on the CI table that deletes relationships on delete would work but is not the recommended or native approach; cascade delete rules are the built-in, declarative mechanism for this purpose.

Practice this question →
19
MCQmedium

An administrator wants to improve the performance of a report that aggregates data from a large custom table. Which database administration technique is most effective?

A.Use a glide aggregate query with a group by clause.
B.Create a database view that pre-aggregates the data.
C.Schedule a job to archive old records.
D.Add an index on the table's sys_updated_by field.
AnswerA

GlideAggregate processes the aggregation efficiently on the server.

Why this answer

Option D is correct because GlideAggregate performs aggregation server-side, reducing data transfer and improving performance. Option A is incorrect because indexing sys_updated_by may not help aggregation. Option B is incorrect because a view pre-aggregates but is static and may not reflect live data.

Option C is incorrect because archiving reduces table size but is not a performance optimization for current queries.

Practice this question →
20
Multi-Selecteasy

A new administrator needs to view the relationships between CIs. Which TWO tables store information about CI relationships? (Select two.)

Select 2 answers
A.cmdb_ci_service
B.cmdb_rel_type
C.cmdb_rel_ci
D.cmdb_ci
E.cmdb_ci_relationship
AnswersB, C

Stores the types of relationships (e.g., 'Connected to', 'Depends on').

Why this answer

Option B is correct because the `cmdb_rel_type` table defines the types of relationships that can exist between configuration items (CIs), such as 'Depends on' or 'Runs on'. Option C is correct because the `cmdb_rel_ci` table stores the actual relationship instances, linking two CIs together with a specific relationship type. Together, these two tables provide the schema and data for CI relationships in the ServiceNow CMDB.

Exam trap

The trap here is that candidates often confuse the `cmdb_ci_relationship` table (which does not exist) with the correct `cmdb_rel_ci` table, or they mistakenly think that `cmdb_ci` itself stores relationship data instead of just CI attributes.

Practice this question →
21
Multi-Selectmedium

Which TWO statements about ServiceNow CMDB identification and reconciliation are correct?

Select 2 answers
A.The 'Source' field on a CI can be set per attribute.
B.The Identification and Reconciliation (IRE) engine processes incoming CI data.
C.Reconciliation rules are used to identify duplicate CIs.
D.Reconciliation rules define which source has priority for updating CI attributes.
E.The CMDB automatically deletes duplicate CIs when detected.
AnswersB, D

The IRE handles identification and reconciliation of CI data.

Why this answer

Option B is correct because the Identification and Reconciliation (IRE) engine is the ServiceNow component responsible for processing incoming CI data from sources like Discovery, Service Mapping, or integrations. It applies identification rules to determine if a CI already exists and reconciliation rules to resolve attribute conflicts, ensuring data integrity in the CMDB.

Exam trap

The trap here is that candidates often confuse the roles of identification rules (which find duplicates) with reconciliation rules (which resolve attribute conflicts), leading them to incorrectly select option C as correct.

Practice this question →
22
MCQhard

A scheduled job runs a transform map to import data into the CMDB from an external asset management system. The transform map has a field mapping that uses script to derive the CI class based on asset type. Recently, imports have been failing with a 'GlideRecord: Invalid table name' error. What is the most likely cause?

A.The external system is sending malformed data.
B.The scheduled job does not have the right roles.
C.The script in the field mapping is returning a value that does not correspond to an existing table name.
D.The target table name in the transform map is misspelled.
AnswerC

If the script sets sys_class_name to a non-existent table, GlideRecord will throw 'Invalid table name'.

Why this answer

Option C is correct because the error 'GlideRecord: Invalid table name' indicates that the script in the field mapping is returning a string that does not match any existing table (class) in the CMDB. When a transform map uses a script to derive the CI class, the returned value must be a valid table name (e.g., 'cmdb_ci_server'). If the script returns a misspelled, malformed, or non-existent table name, GlideRecord fails to instantiate the record, causing the import to fail.

Exam trap

The trap here is that candidates often confuse 'Invalid table name' with a data quality issue (Option A) or a configuration error in the transform map target (Option D), but the error is specifically tied to the dynamic table name returned by the script, not static configuration or external data format.

How to eliminate wrong answers

Option A is wrong because malformed data from the external system would typically cause parsing or validation errors, not a 'GlideRecord: Invalid table name' error, which is specific to table name resolution within ServiceNow. Option B is wrong because role issues would result in security or permission errors (e.g., 'Security restricted'), not a table name error; the scheduled job runs with the system's privileges, not a specific user's roles. Option D is wrong because the target table name in the transform map is used only for the overall import target; the error occurs during field mapping script execution, not at the transform map level, and a misspelled target table would cause a different error at import configuration time.

Practice this question →
23
MCQhard

You are a ServiceNow administrator for a healthcare organization. The CMDB contains sensitive patient data under strict compliance rules. You need to ensure that only authorized users can view the full details of certain CIs, while still allowing change management to reference the CIs. What is the best practice to achieve this?

A.Move the sensitive CIs to a separate CMDB instance.
B.Use Access Controls (ACLs) to restrict read access to the sensitive CI records.
C.Encrypt the fields containing sensitive data.
D.Remove the sensitive CIs from the CMDB and maintain them externally.
AnswerB

ACLs can grant selective read access, ensuring only authorized users see sensitive details.

Why this answer

Access Controls (ACLs) are the correct mechanism to restrict read access to sensitive CI records while still allowing Change Management to reference them. ACLs can be configured to grant read access only to authorized users or roles, and the cmdb_ci table or specific CI records can be targeted. This ensures compliance with data privacy rules without removing the CIs from the CMDB or breaking downstream processes like change requests that need to link to those CIs.

Exam trap

The trap here is that candidates often confuse encryption with access control, assuming that encrypting sensitive fields prevents unauthorized viewing, but encryption in ServiceNow does not enforce read permissions—it only protects data at rest, and users with read access can still decrypt and view the data unless ACLs are applied.

How to eliminate wrong answers

Option A is wrong because moving sensitive CIs to a separate CMDB instance would break the single CMDB architecture, requiring complex cross-instance integrations and potentially violating the principle of a single source of truth for configuration data. Option C is wrong because field-level encryption in ServiceNow is primarily for data at rest and does not control user-level read permissions; encrypted fields can still be visible to users with read access unless combined with ACLs, and encryption alone does not prevent authorized users from viewing the data. Option D is wrong because removing sensitive CIs from the CMDB and maintaining them externally would break Change Management's ability to reference those CIs, as change records require CI relationships to be tracked within the CMDB for impact analysis and compliance.

Practice this question →
24
MCQhard

An administrator discovers that a scheduled discovery job is creating duplicate CI records for the same physical server. The server has two IP addresses (one for management, one for production). What is the most likely cause?

A.The discovery schedule is set to run too frequently.
B.The discovery job is configured to scan only the management IP.
C.The identification rule for the CI class does not include a unique hardware identifier like serial number.
D.The server has too many IP addresses for discovery to handle.
AnswerC

Without a unique identifier, each IP may create a separate CI.

Why this answer

Option C is correct because ServiceNow's CMDB uses identification rules to determine whether a discovered CI is new or matches an existing record. For a physical server with multiple IP addresses, the identification rule must include a unique hardware identifier such as a serial number (e.g., from SMBIOS) to prevent duplicate CIs. Without that, the system may treat each IP address as a separate CI, even though they belong to the same server.

Exam trap

The trap here is that candidates often assume duplicate CIs are caused by scheduling or scanning frequency, when the real issue is the absence of a proper unique identifier in the identification rule, which is a core CMDB concept tested in the SNOW-CSA exam.

How to eliminate wrong answers

Option A is wrong because the frequency of the discovery schedule does not cause duplicate CI records; it only affects how often the scan runs. Option B is wrong because scanning only the management IP would not create duplicates—it would simply discover one IP, not two. Option D is wrong because ServiceNow discovery can handle multiple IP addresses on a single server; the issue is not the number of IPs but the lack of a unique identifier in the identification rule.

Practice this question →
25
MCQeasy

A company wants to ensure that critical servers in the CMDB have accurate operational status. Which CMDB feature should the administrator configure to automatically update the operational status based on monitoring tools?

A.CI Relationships
B.Application Services
C.CMDB Health Score
D.Identification and Reconciliation
AnswerD

This feature automatically updates CI attributes from authorized sources.

Why this answer

Option C is correct because Identification and Reconciliation rules can update CI attributes using data from discovery and monitoring sources. Option A is incorrect because CI Relationships define connections between CIs, not status updates. Option B is incorrect because Application Services model business services, not operational status.

Option D is incorrect because CMDB Health Score measures data quality, not updates.

Practice this question →
26
Multi-Selectmedium

An administrator wants to ensure that the CMDB remains accurate after a change management process. Which TWO actions should the administrator take? (Select two.)

Select 2 answers
A.Use CI Change Request to link CIs to change requests.
B.Create a business rule to update CI status when a change request is approved.
C.Set up CMDB Data Manager to automatically update CIs based on change requests.
D.Enable CMDB CI Class Manager to enforce class hierarchy.
E.Configure CMDB Health Verification to run daily on all CIs.
AnswersA, E

CI Change Request automatically associates CIs with changes, helping keep relationships accurate.

Why this answer

Running CMDB Health Verification helps identify stale or incorrect CIs. Enabling CI Change Request links CIs to change requests, automatically updating status. Option A (CI Class Manager) is for structure, not accuracy.

Option C (Data Manager) is for bulk updates. Option D (business rule) is a custom approach, not a standard best practice.

Practice this question →
27
MCQeasy

Refer to the exhibit. An administrator is trying to import data into a custom CI table but receives this error. What is the most likely cause?

A.The transform map is referencing a table that hasn't been created.
B.The import set has incorrect column mappings.
C.The user does not have permission to write to the table.
D.The CMDB is locked for maintenance.
AnswerA

The error indicates the target table is missing; the table must be created first.

Why this answer

The error indicates that the transform map is trying to populate a custom CI table that does not yet exist in the CMDB. In ServiceNow, a transform map must reference an existing target table; if the table has not been created (e.g., via the 'Create Table' module), the import will fail with this specific error. This is the most likely cause because the error message directly points to a missing table reference.

Exam trap

ServiceNow often tests the distinction between transform map errors (missing table) versus import set row errors (column mapping or permission issues), and the trap here is that candidates confuse a missing table error with a column mapping problem.

How to eliminate wrong answers

Option B is wrong because incorrect column mappings would produce a different error, such as 'Column not found' or 'Invalid field', not a missing table error. Option C is wrong because permission errors typically result in 'Access denied' or 'Insufficient rights' messages, not a table-not-found error. Option D is wrong because a locked CMDB would prevent all imports with a maintenance lock message, not a table-specific error.

Practice this question →
28
Multi-Selecthard

An administrator is investigating a performance issue where a script that queries the task table with a JOIN to the cmdb_ci table is slow. Which two actions can improve query performance? (Select two.)

Select 2 answers
A.Increase the database connection pool size.
B.Add an index on the task table's cmdb_ci field.
C.Replace the JOIN with a glide query using query().
D.Create a database view that combines the two tables.
E.Use a glide aggregate query to reduce data returned.
AnswersB, D

Indexing the join field speeds up the JOIN operation.

Why this answer

Option B is correct because adding an index on the `cmdb_ci` field of the `task` table allows the database to quickly locate matching rows without scanning the entire table, significantly speeding up the JOIN operation. In ServiceNow, indexes are database-level structures that reduce I/O and improve query performance for filtered or joined columns.

Exam trap

ServiceNow often tests the misconception that application-layer changes (like using `query()` or aggregate queries) can replace database-level optimizations, but the correct approach is always to address the root cause at the database layer, such as adding proper indexes.

Practice this question →
29
MCQhard

Based on the exhibit, why did the identification rule fail?

A.The serial_number field is empty, but the rule requires it to be non-empty.
B.The name field is missing from the payload.
C.The rule has a dependency that is not satisfied.
D.The ip_address field is not included in the identification rule.
AnswerA

The rule condition demands a non-empty serial_number.

Why this answer

The identification rule fails because the serial_number field, which is defined as a required identifier field in the rule configuration, is empty in the incoming payload. ServiceNow CMDB identification rules use a set of fields to uniquely identify CI records; if any required field is missing or null, the rule cannot match or create a record, resulting in a failure. In this case, the payload contains the serial_number field but with no value, which the rule treats as a violation of its non-empty constraint.

Exam trap

The trap here is that candidates assume a field being 'present' in the payload is sufficient, but ServiceNow requires the field to be non-empty for identification rules, and an empty string is treated as a missing value.

How to eliminate wrong answers

Option B is wrong because the name field is present in the payload (as shown in the exhibit), and the identification rule does not require it to be non-empty for matching. Option C is wrong because the exhibit shows no dependency conditions configured on the rule; dependencies are used for CI relationships, not for field-level identification. Option D is wrong because the ip_address field is not listed as a required identifier in the rule; the rule only requires serial_number and possibly other fields, but ip_address is optional or used elsewhere.

Practice this question →
30
MCQhard

Based on the sys_audit output, which CI has undergone the most recent change to its operational_status?

A.Both CI001 and CI002
B.CI002
C.Cannot be determined
D.CI001
AnswerB

Record 5 is the most recent and shows a change to CI002.

Why this answer

The sys_audit table records the timestamp of each change to a CI's operational_status field. CI002 has the most recent sys_audit record for operational_status, indicating it was changed last. The correct answer is B because the audit trail shows CI002's status was updated after CI001's.

Exam trap

The trap here is that candidates may assume the most recently created CI (based on sys_created_on) is the most recently changed, but the question specifically asks about changes to operational_status, which requires checking the sys_audit table for that field's update history.

How to eliminate wrong answers

Option A is wrong because both CIs did not have their operational_status changed at the same time; the audit records show different timestamps, with CI002 being more recent. Option C is wrong because the sys_audit table provides clear timestamps for each change, so the most recent change can be determined. Option D is wrong because CI001's last operational_status change occurred before CI002's, making CI002 the most recently changed.

Practice this question →
31
MCQhard

A custom table called 'u_cmdb_ci_application' has been created to extend cmdb_ci. After importing data into this table, the new records do not appear in the 'Configuration Items' module. What is the most likely reason?

A.The 'sys_class_name' field was not set to 'u_cmdb_ci_application' during import.
B.The import set used the wrong transform map.
C.The table was created in the wrong application scope.
D.The user does not have access to the custom table.
AnswerA

Without the correct sys_class_name, the records may appear in the base table or not be recognized as the proper class.

Why this answer

The Configuration Items module typically shows records from the base cmdb_ci table and its children. If the new table is not properly defined as an extension of cmdb_ci, or if it lacks the required fields like 'sys_class_name', it may not be recognized. However, the most common issue is that the import did not set the 'sys_class_name' field correctly, so the records are seen as base table entries or not at all.

Practice this question →
32
MCQeasy

Refer to the exhibit. What action should the administrator take to improve the completeness score?

A.Use a scheduled job to populate common fields with default values.
B.Manually edit each CI that has missing fields.
C.Configure a data certification policy with required fields.
D.Increase the CMDB Health weight for completeness.
AnswerC

Data certification enforces completeness by requiring those fields during periodic review.

Why this answer

Option C is correct because a data certification policy in ServiceNow allows administrators to define required fields for CI classes. When a data certification policy is configured with required fields, the system automatically validates that those fields are populated during certification runs, directly improving the completeness score by ensuring critical data is present. This is a proactive, automated approach that aligns with CMDB Health best practices.

Exam trap

The trap here is that candidates often confuse adjusting the CMDB Health weight (a scoring mechanism) with actually fixing data quality issues, leading them to select option D instead of recognizing that a data certification policy directly enforces data population.

How to eliminate wrong answers

Option A is wrong because using a scheduled job to populate common fields with default values does not address missing fields that require specific, context-dependent data; it only fills generic defaults, which may not improve the actual completeness of meaningful attributes. Option B is wrong because manually editing each CI that has missing fields is not scalable for large CMDBs and does not provide a sustainable, automated mechanism to prevent future completeness gaps. Option D is wrong because increasing the CMDB Health weight for completeness only changes the scoring impact of completeness in the overall health score, but does not actually populate missing fields or enforce data population; it merely adjusts the metric's importance without fixing the underlying data quality issue.

Practice this question →
33
MCQhard

A company has an enterprise ServiceNow instance with a CMDB that contains over 50,000 CIs. The instance is integrated with multiple discovery tools: ServiceNow Discovery, a third-party IPAM tool, and a cloud management platform. Recently, the CMDB health score dropped significantly due to an increase in duplicate CIs. Upon investigation, you find that many CIs from the IPAM tool have the same serial number as CIs discovered by ServiceNow Discovery, but with slight differences in the hardware model field. Also, the cloud management platform creates CIs with the same name but different serial numbers. The business requires that each physical device should have only one CI record, and the serial number is the authoritative identifier. The current reconciliation rules are set to merge based on name and IP address, but they are not effectively resolving duplicates. What should the administrator do to resolve this issue most effectively?

A.Create an approval workflow for every new CI creation to manually check for duplicates
B.Add a unique constraint on the serial number field to prevent future duplicates
C.Modify the reconciliation rule to match on serial number instead of name and IP
D.Disable the IPAM tool and cloud management platform integrations to stop duplicate creation
AnswerC

Serial number is the authoritative identifier; matching on it will accurately identify duplicates across sources.

Why this answer

Option C is correct because the business requirement states that serial number is the authoritative identifier for physical devices. By modifying the reconciliation rule to match on serial number instead of name and IP, the system will correctly identify and merge duplicate CIs that share the same serial number, even if other fields like hardware model differ. This directly addresses the root cause of the duplicate CIs from the IPAM tool and cloud management platform.

Exam trap

The trap here is that candidates may think adding a unique constraint (Option B) is sufficient, but they overlook that existing duplicates must be resolved first, and a unique constraint alone does not handle the reconciliation of CIs from multiple discovery sources with differing non-key attributes.

How to eliminate wrong answers

Option A is wrong because creating an approval workflow for every new CI creation is not scalable for over 50,000 CIs and would introduce manual overhead without fixing the underlying reconciliation logic. Option B is wrong because adding a unique constraint on the serial number field would prevent future duplicates but would not resolve the existing duplicate CIs that are already causing the health score drop. Option D is wrong because disabling the IPAM tool and cloud management platform integrations would stop duplicate creation but also eliminate valuable data sources, violating the business requirement for integrated discovery.

Practice this question →
34
MCQmedium

A company is using multiple data sources (Discovery, SCCM, and manual imports) to populate the CMDB. They notice that some CI attributes are being overwritten incorrectly. Which feature should be used to define which data source is authoritative for specific attributes?

A.Identification and Reconciliation Engine (IRE) with reconciliation rules
B.CMDB Data Source rules
C.Import set transform maps
D.Business rules with condition on source field
AnswerA

IRE reconciliation rules define which source is authoritative for each attribute.

Why this answer

The Identification and Reconciliation Engine (IRE) with reconciliation rules is the correct feature because it allows administrators to define which data source is authoritative for specific CI attributes. When multiple sources populate the CMDB, reconciliation rules determine the priority of data sources, ensuring that attributes from a higher-priority source overwrite those from lower-priority sources, preventing incorrect overwrites.

Exam trap

The trap here is that candidates confuse 'Data Source' configuration with reconciliation rules, assuming that simply defining a data source will automatically resolve conflicts, when in fact the IRE's reconciliation rules are required to explicitly set attribute-level authority.

How to eliminate wrong answers

Option B is wrong because CMDB Data Source rules do not exist as a feature in ServiceNow; the correct term is 'Data Source' definitions, which are used to configure import sources but not to define attribute-level authority. Option C is wrong because Import set transform maps handle data transformation and mapping during import, but they do not resolve conflicts between multiple data sources for attribute authority. Option D is wrong because Business rules with condition on source field can modify data during transactions but are not designed to manage authoritative source priority for CI attributes in the CMDB reconciliation process.

Practice this question →
35
Multi-Selecteasy

Which TWO of the following are valid CI relationship types in ServiceNow?

Select 2 answers
A.Uses
B.Connects to
C.Member of
D.Owns
E.Depends on
AnswersC, E

'Member of' is a standard membership relationship.

Why this answer

Option C is correct because 'Member of' is a predefined CI relationship type in ServiceNow's CMDB, used to indicate that a CI belongs to a group or cluster, such as a server being a member of a cluster. This relationship is part of the standard CMDB relationship model and is commonly used for grouping CIs like applications, clusters, or business services.

Exam trap

The trap here is that candidates often confuse 'Uses' or 'Connects to' with valid relationship types, but ServiceNow strictly uses 'Depends on' and 'Connected to' (with 'Connected to' being a valid type, not 'Connects to'), and 'Owns' is a field attribute, not a relationship type.

Practice this question →
36
Multi-Selecthard

A company is implementing a CMDB cleanup strategy and needs to identify CIs that are no longer in use. Which THREE methods can help identify outdated CIs? (Select three.)

Select 3 answers
A.Reviewing CI last discovered date.
B.Using the 'Stale CI' indicator in CMDB Health.
C.Running a CMDB Health report on compliance.
D.Checking CI status field for 'Retired'.
E.Manually auditing each CI in the CMDB.
AnswersA, B, C

A very old last discovered date suggests the CI may be out of use.

Why this answer

Option A is correct because the 'Last Discovered' date field on a CI record indicates when the CI was last seen by a discovery probe. If this date is significantly old, it suggests the CI may no longer be active or in use, making it a reliable method for identifying outdated CIs during a CMDB cleanup.

Exam trap

The trap here is that candidates confuse the 'Retired' status (a manual state) with an automated detection method, or think manual auditing is a valid scalable approach, when the exam expects automated, health-based indicators like last discovered date, stale CI flags, and compliance reports.

Practice this question →
37
MCQeasy

A ServiceNow administrator notices that a CI record in the CMDB is not being updated by a scheduled discovery job. The CI is a Linux server that is reachable on the network. Which is the most likely cause?

A.The discovery source is not configured for this IP range.
B.The Identification and Reconciliation Engine (IRE) is disabled.
C.The cmdb_ci table ACL is set to private.
D.The CI is classified under a different CI class in the CMDB.
AnswerD

If the CI is misclassified, discovery may update a different record or create a duplicate.

Why this answer

When a CI is classified under a different CI class in the CMDB, the scheduled discovery job may not update it because discovery uses the IRE to match incoming data against existing CIs based on identification rules. If the CI's class differs from what the discovery payload expects, the IRE may fail to reconcile the record, or the update may be directed to a different class table, leaving the original CI unchanged. This is a common cause of apparent update failures when the CI is reachable and the discovery source is correctly configured.

Exam trap

The trap here is that candidates assume a reachable CI with a configured discovery source guarantees updates, overlooking how the IRE's class-specific identification rules can prevent reconciliation when the CI class in the CMDB does not match the discovery payload.

How to eliminate wrong answers

Option A is wrong because if the discovery source were not configured for the IP range, the CI would not be discovered at all, but the question states the CI is reachable and the discovery job is scheduled, implying the source is configured. Option B is wrong because disabling the IRE would prevent all CI identification and reconciliation, causing discovery to fail for all CIs, not just this specific one. Option C is wrong because the cmdb_ci table ACL set to private would block user access to view or modify the table, but discovery runs with system-level privileges and is not affected by table ACLs.

Practice this question →
38
MCQmedium

A ServiceNow CSA is tasked with ensuring that all CIs in the CMDB have an accurate 'Asset Tag' field. Some records show 'No asset tag' as a value. Which method can prevent this in the future?

A.Set the 'Asset Tag' field as mandatory
B.Use a workflow to populate the field
C.Configure a default value for the 'Asset Tag' field
D.Create a data policy that requires a pattern
AnswerC

A default value can be blank or a meaningful value, preventing placeholder entries.

Why this answer

Option C is correct because configuring a default value for the 'Asset Tag' field ensures that when a new CI is created without an explicit asset tag, the system automatically populates the field with a predefined value (e.g., 'No asset tag' or a placeholder). This prevents the field from being left empty or showing an unintended value, as the default is applied at record creation. In ServiceNow, default values are set in the dictionary configuration for the field, making this a simple and effective preventive measure.

Exam trap

The trap here is that candidates often confuse 'mandatory' with 'preventing incorrect values,' but mandatory only ensures a value is entered, not that it is the correct or intended value, while a default value proactively sets the field to a desired state.

How to eliminate wrong answers

Option A is wrong because setting the 'Asset Tag' field as mandatory would require users to enter a value, but it does not prevent them from entering 'No asset tag' as a manual entry, nor does it address the existing records with that value. Option B is wrong because using a workflow to populate the field is an over-engineered solution; workflows are typically used for complex business processes, not for simple field population, and they add unnecessary overhead and maintenance. Option D is wrong because creating a data policy that requires a pattern would enforce a specific format (e.g., regex), but the issue is that 'No asset tag' is a valid string that could match a pattern; a data policy does not prevent the entry of that specific text unless the pattern explicitly excludes it, which is not the goal here.

Practice this question →
39
Multi-Selecteasy

Which three are components of CMDB Reconciliation? (Select three.)

Select 3 answers
A.Identification rules
B.Data Source definitions
C.Reconciliation rules
D.CMDB Health Score
E.CI Class Manager
AnswersA, B, C

Identification rules determine how CIs are matched to data sources.

Why this answer

Identification rules are a core component of CMDB Reconciliation because they define how ServiceNow uniquely identifies CIs across multiple data sources. They use specific attributes (like serial number or MAC address) to match CIs and prevent duplicates during the reconciliation process.

Exam trap

The trap here is that candidates confuse CMDB Health Score (a reporting feature) with an active reconciliation component, or assume CI Class Manager is involved in reconciliation when it only handles class structure, not data matching.

Practice this question →
40
MCQeasy

A CMDB administrator wants to identify which user last updated a CI record. Which table contains this information?

A.sys_user
B.sys_audit
C.sys_ci
D.sys_metadata
AnswerB

sys_audit records all changes to records including the user.

Why this answer

The sys_audit table stores the audit history of all field-level changes made to CI records, including the user who made the update, the timestamp, and the old and new values. When a CMDB administrator needs to identify the last user to update a CI, querying sys_audit with the appropriate filter on the record's sys_id and ordering by the 'sys_created_on' field descending will reveal the most recent change and its author.

Exam trap

The trap here is that candidates often confuse the table storing the CI record (sys_ci) with the table storing the change history (sys_audit), mistakenly thinking the record itself contains the last updated user field, whereas ServiceNow stores that metadata in the audit trail.

How to eliminate wrong answers

Option A is wrong because sys_user is the table that stores user account records (e.g., login credentials, roles), not the history of CI updates. Option C is wrong because sys_ci is the table that stores the CI records themselves, not the audit trail of who modified them. Option D is wrong because sys_metadata is the table that stores system metadata definitions (e.g., table schemas, field definitions), not user-driven change history.

Practice this question →
41
MCQhard

An administrator is managing a CMDB that contains both physical and virtual servers. The company uses a custom field 'u_os_version' to track the operating system version. When new servers are discovered, the field is populated correctly. However, when the operating system is updated manually by the IT team, the field is not updated. The administrator wants the CMDB to automatically reflect manual changes made to server operating systems. Which approach should be taken?

A.Configure the Discovery probe to re-discover the server after an OS update.
B.Create a business rule on the server table to update the CI when the OS is changed.
C.Use the CI Class Manager to set the field as 'Reconcilable'.
D.Use a scheduled job to query the server's actual OS version periodically.
AnswerB

A business rule can trigger on update events and populate the custom CMDB field accordingly.

Why this answer

Option B is correct because a business rule on the server table can detect when the 'u_os_version' field is manually updated and automatically update the corresponding CI record. This ensures that changes made outside of Discovery are reflected in the CMDB without requiring re-discovery or scheduled jobs, leveraging ServiceNow's event-driven architecture.

Exam trap

The trap here is that candidates often confuse 'Reconcilable' fields with automatic update propagation, but reconciliation only resolves conflicts during data source merges, not for manual changes.

How to eliminate wrong answers

Option A is wrong because re-discovering the server after an OS update would only work if Discovery runs again, but it does not automatically trigger on manual changes; it requires manual intervention or a scheduled job, making it inefficient and not real-time. Option C is wrong because setting a field as 'Reconcilable' in CI Class Manager affects how conflicts are resolved during reconciliation processes, not how manual updates are captured or propagated. Option D is wrong because a scheduled job to query the server's actual OS version periodically introduces latency and overhead, and it does not provide immediate synchronization when the OS is manually updated.

Practice this question →
42
MCQhard

During a CMDB audit, an administrator discovers duplicate CI records for the same network switch. The switch is identified by its serial number. The identification rule currently uses IP address and MAC address as identifiers. What is the most likely cause of the duplicate records?

A.There is a conflict in the class hierarchy.
B.The discovery source is set to ServiceNow Discovery only, but multiple sources exist.
C.The reconciliation rule is set to manual mode.
D.The serial number is not included in the identification rule.
AnswerD

Without a unique identifier like serial number, duplicates can occur.

Why this answer

The duplicate CI records exist because the identification rule does not include the serial number, which is the unique hardware identifier for the switch. Without it, the system cannot reliably match the discovered switch to an existing CI, so a new record is created each time the switch is discovered with a different IP or MAC address. Including the serial number in the identification rule ensures that the same physical device is always reconciled to the same CI record.

Exam trap

The trap here is that candidates often assume reconciliation rules (Option C) prevent duplicates, but duplicates are actually created during the identification phase, before reconciliation is ever applied.

How to eliminate wrong answers

Option A is wrong because a class hierarchy conflict would cause issues with CI classification or inheritance, not duplicate records for the same device. Option B is wrong because the discovery source setting does not cause duplicates; multiple sources are handled by identification and reconciliation rules. Option C is wrong because manual reconciliation mode affects how conflicts are resolved, not the creation of duplicate records; duplicates are created during identification, before reconciliation is applied.

Practice this question →
43
MCQmedium

A company's CMDB has been populated with configuration items (CIs) from various discovery sources. However, when querying the CMDB for all Windows servers, the result set is missing some servers that are known to exist. The administrator has verified that the servers are discovered and appear in the discovery logs. What is the most likely cause of this issue?

A.The missing servers are duplicates and have been merged into other CIs.
B.The missing servers have a status of 'Retired' in the CMDB.
C.The user running the query does not have the cmdb_read role.
D.The missing servers are classified under a different CMDB class than the one being queried.
AnswerD

Class hierarchy and classification determine query results.

Why this answer

Option D is correct because the CMDB organizes CIs into a hierarchical class structure (e.g., cmdb_ci_server, cmdb_ci_win_server). If a Windows server is classified under a different parent class (e.g., cmdb_ci_linux_server due to misclassification or a custom class), a query filtering specifically on the Windows server class will exclude it. Discovery populates the CI with the correct class based on the identification and classification rules, but manual reclassification or an incorrect identification rule can place the CI in a different class, making it invisible to class-specific queries.

Exam trap

The trap here is that candidates assume discovery success guarantees the CI is in the expected class, but ServiceNow's CMDB class hierarchy and classification rules can place discovered CIs into a different class, making them invisible to class-specific queries even though they exist in the CMDB.

How to eliminate wrong answers

Option A is wrong because duplicate CIs are handled by identification and reconciliation rules, which may merge or update CIs, but the merged CI retains the original CI's class and is still queryable; it would not be missing from the result set. Option B is wrong because a 'Retired' status does not remove the CI from the CMDB; it remains in the table and is still returned by queries unless the query explicitly filters on status. Option C is wrong because the cmdb_read role grants read access to the CMDB tables; if the user lacked this role, they would receive a security error or see no results at all, not a partial set of missing servers.

Practice this question →
44
MCQeasy

A system administrator receives a request to add a new field called 'Business Impact' to the 'cmdb_ci' table. Which method should be used to ensure the field is available to all CI classes?

A.Add the field to the 'cmdb_ci' table directly
B.Add the field to a child class like 'cmdb_ci_computer'
C.Use the 'Include Table' configuration to add the field
D.Create a new extension table for the field
AnswerA

This adds the field to the base table and all its descendants.

Why this answer

The 'cmdb_ci' table is the base table for all Configuration Items (CIs) in the CMDB. Adding a field directly to this table ensures it is inherited by all child CI classes (e.g., cmdb_ci_computer, cmdb_ci_server) through the table hierarchy. This is the standard method for making a field universally available across all CI types without creating redundant or inconsistent data structures.

Exam trap

The trap here is that candidates often assume adding a field to a specific child class is sufficient for all CIs, overlooking the inheritance hierarchy and the base table's role in universal field availability.

How to eliminate wrong answers

Option B is wrong because adding the field to a child class like 'cmdb_ci_computer' would only make it available to that specific class and its descendants, not to all CI classes. Option C is wrong because the 'Include Table' configuration is used to extend a table's schema by including fields from another table, not to add a new field directly to the base table. Option D is wrong because creating a new extension table would isolate the field to that table and require additional configuration to associate it with the base CI classes, defeating the purpose of universal availability.

Practice this question →
45
MCQmedium

A consultant is designing a CMDB for a large enterprise. The data from multiple discovery tools is being imported into the CMDB. Some CIs are being duplicated due to minor differences in serial numbers. Which approach best prevents duplicates without losing data integrity?

A.Set a 'unique' constraint on the Serial Number field
B.Configure a reconciliation rule to merge duplicates automatically
C.Use a data certification rule to validate serial numbers
D.Instruct the discovery teams to manually de-duplicate
AnswerA

Prevents insertion of duplicate serial numbers, enforcing uniqueness at the database level.

Why this answer

Setting a 'unique' constraint on the Serial Number field prevents duplicate CIs by enforcing that no two records can have the same serial number at the database level. This approach preserves data integrity because it blocks insertion of duplicates rather than merging or overwriting existing data, which could cause loss of attribute history or relationships.

Exam trap

The trap here is that candidates often confuse reconciliation rules (which handle existing duplicates) with prevention mechanisms, leading them to choose Option B instead of understanding that a unique constraint blocks duplicates at the database level before they can occur.

How to eliminate wrong answers

Option B is wrong because reconciliation rules merge duplicates after they are created, which can lead to data loss if attributes conflict or if relationships are incorrectly consolidated; they do not prevent duplicates at the point of import. Option C is wrong because data certification rules validate data quality (e.g., format or completeness) but do not enforce uniqueness or prevent duplicate serial numbers from being inserted. Option D is wrong because manual de-duplication is error-prone, unscalable, and does not provide a systematic, automated prevention mechanism; it also risks human error and inconsistent application across large datasets.

Practice this question →
46
Drag & Dropmedium

Drag and drop the steps to create a new user in ServiceNow into the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order

Why this order

User records require mandatory fields like user ID and email.

Practice this question →
47
Matchingmedium

Match each ServiceNow update set state to its meaning.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Update set is being worked on

All changes have been captured and are ready to commit

Update set has been applied to the target instance

Update set will not be processed

Changes are reviewed before committing

Why these pairings

Update sets track and migrate customizations between instances.

Practice this question →
48
MCQmedium

A consultant is designing the CMDB for a large enterprise. The company wants to track relationships between business services, applications, and infrastructure components. Which relationship model should be used to represent that a business service depends on an application, which in turn depends on a server?

A.Dependency relationship (structural)
B.Membership relationship
C.Ownership relationship
D.Connectivity relationship
AnswerA

Structural dependency is the correct type for service-dependency modeling.

Why this answer

A dependency relationship (structural) is the correct model because it explicitly captures the directional 'depends on' nature of the chain: a business service relies on an application, which in turn relies on a server. In ServiceNow CMDB, structural dependency relationships (e.g., 'Depends on' or 'Used by') are designed to represent these hierarchical, transitive dependencies between CIs, enabling impact analysis and root cause mapping.

Exam trap

The trap here is that candidates confuse 'dependency' with 'connectivity' because both involve links between CIs, but connectivity only describes physical or logical network links without the directional 'depends on' semantics required for service impact chains.

How to eliminate wrong answers

Option B is wrong because a membership relationship (e.g., 'Member of' or 'Contains') groups CIs into a logical collection (like a cluster or a business service group) but does not express directional dependency or transitive chaining between individual CIs. Option C is wrong because an ownership relationship (e.g., 'Owned by') defines administrative or financial responsibility for a CI, not technical dependency or service impact flow. Option D is wrong because a connectivity relationship (e.g., 'Connects to' or 'Communicates with') models network or physical links between CIs (like a server connected to a switch) but lacks the directional 'depends on' semantics needed to represent service-to-application-to-infrastructure chains.

Practice this question →
49
MCQeasy

A company wants to restrict access to CI records based on the business service they belong to. What feature should they use?

A.ACLs on cmdb_ci table
B.CMDB Application Access Control
C.CMDB Data Segmentation
D.Condition-based ACLs
AnswerC

Data Segmentation allows record-level access based on defined conditions.

Why this answer

CMDB Data Segmentation (option C) is the correct feature because it allows administrators to restrict access to CI records based on the business service they belong to, using a segmentation rule that filters CIs by their 'business_service' field. This is specifically designed for multi-tenant or service-based access control in the CMDB, ensuring users only see CIs associated with their assigned business services.

Exam trap

The trap here is that candidates confuse CMDB Data Segmentation with standard ACLs or condition-based ACLs, not realizing that Data Segmentation is a purpose-built feature for business service-based CI filtering, whereas ACLs require more manual and less maintainable configuration.

How to eliminate wrong answers

Option A is wrong because ACLs on the cmdb_ci table apply globally to all CI records without the ability to dynamically filter by business service; they would require complex condition scripts for each service, which is not scalable. Option B is wrong because CMDB Application Access Control is a legacy feature that controls access to the CMDB application module itself, not to individual CI records based on business service. Option D is wrong because condition-based ACLs, while powerful, are a general ACL type that can filter records, but they are not the dedicated, out-of-box feature designed specifically for business service-based CI segmentation; CMDB Data Segmentation provides a simpler, declarative approach without custom scripting.

Practice this question →
50
Multi-Selectmedium

A ServiceNow administrator notices that the CMDB contains duplicate CI records for the same server. The duplicates were created by different discovery sources. Which TWO actions should the administrator take to resolve this issue and prevent future duplicates? (Choose two.)

Select 2 answers
A.Use the 'Reconcile' operation in the CMDB Workspace to manually merge the duplicates.
B.Run the 'Remove Duplicate CIs' scheduled job with the 'Delete' flag enabled.
C.Set the 'Identification Engine' to automatically merge duplicate CIs based on serial number.
D.Update the discovery source rules to exclude the duplicate server from future discovery.
E.Configure the CI Class Manager to require a unique combination of serial number and model ID.
AnswersA, E

The Reconcile operation allows administrators to manually merge duplicate CI records, resolving the immediate issue.

Why this answer

Option A is correct because the 'Reconcile' operation in the CMDB Workspace allows an administrator to manually review and merge duplicate CI records, which is necessary when duplicates are created by different discovery sources and automatic rules cannot resolve the conflict. This action directly resolves the existing duplicate records by consolidating them into a single authoritative CI.

Exam trap

The trap here is that candidates often confuse the 'Remove Duplicate CIs' scheduled job (which deletes duplicates automatically) with the 'Reconcile' operation (which merges them manually), leading to the misconception that automatic deletion is a safe and complete solution when it can cause data loss.

Practice this question →
51
Multi-Selectmedium

Which THREE of the following are required for ServiceNow Discovery to successfully populate the CMDB?

Select 3 answers
A.The CMDB CI tables with open ACLs
B.Valid credentials for the target devices
C.A discovery schedule configured for the IP range
D.A MID Server that can reach the target devices
E.The Identification and Reconciliation Engine (IRE) enabled
AnswersB, C, D

Credentials are necessary for authentication.

Why this answer

Valid credentials (Option B) are required because ServiceNow Discovery uses SNMP, SSH, WMI, or REST to probe target devices. Without correct credentials, the MID Server cannot authenticate to the device, so it cannot read configuration data or populate CI attributes in the CMDB.

Exam trap

ServiceNow often tests that candidates confuse the IRE as a hard requirement for Discovery, when in fact Discovery can function with the legacy identification engine, making Option E a tempting but incorrect choice.

Practice this question →
52
MCQhard

An administrator notices that a custom table 'u_custom_infrastructure' was created as a child of 'cmdb_ci'. However, records in this table are not appearing in the CMDB dashboard reports that show all CIs. What is the likely reason?

A.The table has permissions that restrict report access
B.The records have not passed data certification
C.The table's 'Display in CMDB dashboard' property is disabled
D.The table is not included in the 'CMDB Base Class' report definition
AnswerD

Reports may need to be configured to include all child classes.

Why this answer

CMDB reports typically use the 'cmdb_ci' base table. Custom child classes must be included in report definitions if they are not automatically included. The table might be excluded due to class hierarchy filtering.

Table permissions would prevent viewing but not necessarily reporting. Data certification would flag data quality. Sharing settings do not affect reporting.

Practice this question →
53
MCQmedium

An administrator needs to delete a large number of records from the cmdb_ci table based on a condition. Which method is recommended for bulk deletion to ensure data integrity and performance?

A.Use a script that iterates and deletes each record using glideRecord.delete().
B.Use a direct SQL DELETE statement in a background script.
C.Use a GlideRecord script with deleteMultiple() to delete all matching records in one transaction.
D.Use the 'Delete all records in this table' option in the table configuration.
AnswerC

deleteMultiple() is efficient and safe for bulk deletions.

Why this answer

Option C is correct because deleteMultiple() processes all matching records in a single database transaction, ensuring data integrity by respecting business rules, ACLs, and database constraints while offering better performance than iterating individual deletes. This method is specifically designed for bulk deletion in ServiceNow, balancing efficiency with platform safety.

Exam trap

The trap here is that candidates often choose Option A (iterative delete) because it seems safer, but they overlook the severe performance penalty and risk of transaction log overflow when deleting large volumes of records individually.

How to eliminate wrong answers

Option A is wrong because iterating and deleting each record with glideRecord.delete() in a loop is inefficient for large datasets, causing excessive database round-trips and potential timeouts. Option B is wrong because direct SQL DELETE statements bypass ServiceNow's business logic, ACLs, and audit trails, risking data integrity and violating platform best practices. Option D is wrong because the 'Delete all records in this table' option removes every record unconditionally, ignoring the specified condition and potentially deleting unintended data.

Practice this question →
54
Multi-Selecthard

Which THREE of the following are best practices for CMDB data maintenance? (Choose exactly 3.)

Select 3 answers
A.Scheduled reconciliation to identify and merge duplicates
B.Disabling discovery for all CIs to prevent changes
C.Manually updating all CI attributes
D.Regular data certification to ensure data quality
E.Setting up data refresh schedules for imported data
AnswersA, D, E

Reconciliation keeps the CMDB clean.

Why this answer

Option A is correct because scheduled reconciliation is a core CMDB best practice that uses identification rules to automatically detect and merge duplicate CIs, ensuring a single source of truth. This process relies on the CMDB's reconciliation engine, which compares CI attributes against defined identification and reconciliation rules to resolve conflicts without manual intervention.

Exam trap

ServiceNow often tests the misconception that disabling discovery is a valid maintenance strategy, when in fact it is the opposite; the trap here is confusing 'maintenance' with 'preventing change' rather than 'ensuring data accuracy through automation'.

Practice this question →
55
MCQhard

An administrator is troubleshooting why a CMDB CI's last discovered date is not updating after a successful discovery run. The CI is in a valid state and the discovery schedule runs. What could be the cause?

A.The CMDB identification rule has a condition that excludes this CI from updates.
B.The discovery source is set to 'ServiceNow' but the CI was created manually.
C.The reconciliation rule is set to 'Manual' and the discovered data conflicts with existing data.
D.The CI is a parent class and child class discovery is updating child records.
AnswerC

Manual reconciliation prevents automatic updates when conflicts arise, so the date stays unchanged.

Why this answer

Option C is correct because when a reconciliation rule is set to 'Manual', the CMDB will not automatically update CI attributes with discovered data if there is a conflict with existing data. The CI remains in its last discovered state until a manual reconciliation is performed, even if the discovery run succeeds and the CI is valid.

Exam trap

The trap here is that candidates often confuse reconciliation rules with identification rules or assume that a successful discovery run always updates the last discovered date, overlooking the impact of manual reconciliation settings on attribute updates.

How to eliminate wrong answers

Option A is wrong because identification rules determine how CIs are matched and identified, not whether updates are applied after identification; a condition that excludes a CI would prevent it from being identified or updated at all, not just the last discovered date. Option B is wrong because the discovery source being set to 'ServiceNow' is the correct source for ServiceNow discovery, and a manually created CI can still be updated by discovery if the identification rule matches it; the issue is not about the source value. Option D is wrong because parent-child class relationships do not prevent the parent CI's last discovered date from updating; discovery of child records typically updates the parent's last discovered date as part of the hierarchy update logic.

Practice this question →
56
MCQmedium

An administrator runs a CMDB health report for the CI class cmdb_ci_server and sees the exhibit. Which attribute is the highest priority to populate first?

A.Operating system (os)
B.Serial number (serial_number)
C.Model ID (model_id)
D.Manufacturer
AnswerB

800 missing, the highest number, and critical for identification.

Why this answer

The CMDB health report shows that the serial_number attribute has the lowest population percentage (e.g., 45%) compared to other attributes. Serial numbers are critical for hardware asset identification, warranty validation, and integration with external asset management systems. Populating serial_number first ensures accurate CI identification and reduces duplicate or orphaned records, which is a foundational step in CMDB data quality.

Exam trap

The trap here is that candidates often prioritize attributes like operating system or manufacturer because they seem more relevant to server operations, but the CMDB health report specifically highlights population gaps, and serial_number is the most critical for unique CI identification and deduplication.

How to eliminate wrong answers

Option A is wrong because operating system (os) is a software attribute that, while important for server management, is often dynamically discovered and can be populated later without impacting CI uniqueness. Option C is wrong because model_id, though useful for hardware categorization, is not a unique identifier and can be derived from manufacturer and other attributes. Option D is wrong because manufacturer is a broad classification attribute that, like model_id, does not provide unique CI identification and is typically populated via discovery or manual entry without affecting record deduplication.

Practice this question →
57
MCQeasy

A report using the 'server_by_os' database view is expected to show a record for each server. However, a server without an operating system entry is not appearing in the report. What is the most likely reason?

A.The view is missing a required field.
B.The view is not refreshed.
C.The server's OS field is null.
D.The join is defined as an INNER JOIN, excluding servers without a matching OS record.
AnswerD

INNER JOIN requires matching records in both tables.

Why this answer

The report is built on a database view that joins the server table with the operating system table. If the join is an INNER JOIN, only records with matching rows in both tables are returned. A server with a null OS field has no matching OS record, so it is excluded from the result set.

This is the most likely reason the server is missing from the report.

Exam trap

The trap here is that candidates assume a null field value is the direct cause of the missing record, when in fact the underlying join type (INNER JOIN) is the mechanism that excludes rows with null foreign keys.

How to eliminate wrong answers

Option A is wrong because a missing required field would typically cause an error or prevent the view from being created, not silently exclude a row. Option B is wrong because views in ServiceNow are dynamic and reflect the underlying data in real time; they do not require manual refresh. Option C is wrong because a null OS field alone does not cause a row to be excluded; it is the join type (INNER JOIN) that filters out rows with null foreign keys.

Practice this question →
58
Multi-Selecteasy

Which TWO of the following are valid CMDB base classes? (Choose exactly 2.)

Select 2 answers
A.cmdb_ci_win_system
B.cmdb_ci
C.cmdb_ci_linux_system
D.cmdb_ci_service
E.cmdb_ci_computer
AnswersB, D

This is the root CMDB CI table.

Why this answer

In ServiceNow, the CMDB base classes are the top-level classes from which all other configuration items (CIs) inherit. `cmdb_ci` is the root base class for all CIs, and `cmdb_ci_service` is a base class specifically for business and technical services. Both are defined in the CMDB data model as foundation classes that cannot be deleted and serve as parents for more specific CI types.

Exam trap

The trap here is that candidates often mistake common CI types like `cmdb_ci_win_system` or `cmdb_ci_computer` for base classes because they appear frequently in CMDB tables, but ServiceNow defines only a few true base classes (e.g., `cmdb_ci`, `cmdb_ci_service`, `cmdb_ci_infrastructure`) from which all others inherit.

Practice this question →
59
MCQeasy

Which CMDB relationship type should be used to represent that a server is physically installed in a rack?

A.Depends on
B.Contains
C.Runs on
D.Connected to
AnswerB

Contains is used for physical hierarchy like rack and server.

Why this answer

The 'Contains' relationship type is correct because it models a parent-child containment hierarchy in the CMDB, where the rack is the container and the server is the contained item. This aligns with the CMDB's ability to represent physical location and dependencies, ensuring accurate service mapping and impact analysis.

Exam trap

ServiceNow often tests the confusion between 'Contains' and 'Depends on' by presenting scenarios where physical location is implied but candidates mistakenly choose a dependency relationship due to misinterpreting 'installed in' as a functional reliance.

How to eliminate wrong answers

Option A is wrong because 'Depends on' indicates a functional dependency (e.g., a server depends on a power source), not a physical containment relationship. Option C is wrong because 'Runs on' is used for software or application relationships (e.g., an application runs on a server), not for physical placement. Option D is wrong because 'Connected to' describes a network or cable connection (e.g., a server connected to a switch), not physical installation within a rack.

Practice this question →
60
MCQmedium

A ServiceNow administrator needs to create a database view that combines data from the cmdb_ci_server table and the cmdb_ci_netgear table. What is the correct method to achieve this?

A.Use the CMDB Explorer to merge CI classes.
B.Write a custom script to join tables and store results in a new table.
C.Create a report and save it as a view.
D.Use the Database Views module to create a view with join conditions.
AnswerD

Database Views is the correct feature for creating views.

Why this answer

Option D is correct because the Database Views module in ServiceNow allows administrators to create a view that combines data from multiple tables using SQL-like join conditions. This is the standard, no-code method to create a virtual table that merges fields from cmdb_ci_server and cmdb_ci_netgear without modifying the underlying schema or duplicating data.

Exam trap

The trap here is that candidates confuse the Database Views module with reporting features or CMDB tools, assuming a report or CMDB Explorer can produce a queryable table, when only Database Views creates a true SQL-level join view.

How to eliminate wrong answers

Option A is wrong because the CMDB Explorer is used to visualize and manage CI class hierarchies and relationships, not to create database views that join tables. Option B is wrong because writing a custom script to join tables and store results in a new table is inefficient, bypasses platform best practices, and creates data redundancy rather than a live view. Option C is wrong because reports in ServiceNow can be saved as report views or dashboards, but they do not create a database view that can be queried like a table in the platform.

Practice this question →
61
MCQeasy

An administrator needs to identify which CI(s) are affected by a recent network outage. Which table should be queried to find the relationship between CIs and incidents?

A.task_ci
B.cmdb_ci
C.sys_ci_relation
D.cmdb_rel_ci
AnswerA

task_ci links tasks (like incidents) to CIs.

Why this answer

The task_ci table stores the direct relationship between tasks (including incidents) and configuration items (CIs). When an administrator needs to identify which CIs are affected by a specific incident, querying task_ci with the incident's sys_id will return the associated CIs. This table is the standard ServiceNow junction table for linking any task record (such as an incident) to CIs.

Exam trap

The trap here is that candidates often confuse the table for CI-to-CI relationships (cmdb_rel_ci) with the table for task-to-CI relationships (task_ci), leading them to select cmdb_rel_ci when the question specifically asks about incidents and CIs.

How to eliminate wrong answers

Option B (cmdb_ci) is wrong because it is the base table for all configuration items, storing CI attributes and not the relationship between incidents and CIs. Option C (sys_ci_relation) is wrong because it is not a standard ServiceNow table; the correct table for CI-to-CI relationships is cmdb_rel_ci. Option D (cmdb_rel_ci) is wrong because it stores relationships between CIs (e.g., 'runs on', 'connects to'), not the association between incidents and CIs.

Practice this question →
62
MCQhard

An administrator is asked to design a solution to prevent unauthorized changes to the CMDB. The requirement is that any update to a CI's critical attributes (e.g., serial number, model) must be logged and require an approval. Which approach should be taken?

A.Configure the CMDB to use 'Data Certification' and require approval for attribute changes.
B.Use a database trigger that captures changes and creates a change request.
C.Create a business rule that fires on update, checks the previous values, and sends an approval request.
D.Set field-level audit on the critical fields and use the 'Audit' module to report changes.
AnswerC

A business rule with approval workflow can prevent unauthorized updates in real time.

Why this answer

Option C is correct because a business rule that fires 'on update' with a condition checking previous values of critical attributes (e.g., serial number, model) can trigger an approval request via an approval engine or flow. This approach directly enforces the requirement that updates to those specific fields require approval before the change is committed, without relying on external modules or triggers that may bypass ServiceNow's native approval framework.

Exam trap

The trap here is that candidates often confuse 'audit' (which only logs changes) with 'approval' (which prevents changes), leading them to select Option D, or they mistakenly think database triggers (Option B) are a valid ServiceNow mechanism when the platform explicitly prohibits direct database operations.

How to eliminate wrong answers

Option A is wrong because 'Data Certification' is designed for periodic verification of CI accuracy by designated certifiers, not for real-time approval of attribute changes. Option B is wrong because database triggers are not supported in ServiceNow's platform architecture; they would require direct database manipulation, which is prohibited and would bypass all business logic and security rules. Option D is wrong because field-level audit only logs changes for reporting purposes and does not enforce an approval workflow; it provides visibility after the fact but does not prevent unauthorized changes.

Practice this question →
63
MCQeasy

You are a ServiceNow administrator at a mid-sized company. The CMDB currently has over 100,000 CIs, and end users report that the CI search results are slow, often taking more than 10 seconds. The database has been optimized, but the issue persists. You have noticed that many CIs have empty or outdated fields. What is the best course of action to improve search performance without impacting data integrity?

A.Create a scheduled job to delete CIs that have not been updated in 90 days.
B.Disable the full-text search index and rely on basic database indexes.
C.Increase the database connection pool size and restart the instance.
D.Run the CMDB Data Manager to clean up empty fields and reduce index size.
AnswerD

Data Manager can identify and remove empty fields, shrinking the table and improving performance.

Why this answer

Option D is correct because the CMDB Data Manager can identify and remove empty or outdated fields from CI records, which reduces the size of the database indexes. Smaller indexes improve search query performance without deleting entire CIs, thus preserving data integrity. This directly addresses the root cause—bloated indexes due to unnecessary data—rather than masking the issue with connection pool changes or risking data loss.

Exam trap

The trap here is that candidates confuse 'data integrity' with 'keeping all data,' leading them to choose Option A (deleting old CIs) instead of recognizing that cleaning empty fields preserves CIs while improving performance.

How to eliminate wrong answers

Option A is wrong because deleting CIs that haven't been updated in 90 days would remove potentially critical configuration items, violating data integrity and breaking dependencies like relationships or CI-based workflows. Option B is wrong because disabling the full-text search index would force searches to rely solely on basic database indexes, which are less efficient for partial or fuzzy matches, likely making search performance worse, not better. Option C is wrong because increasing the database connection pool size and restarting the instance only addresses connection bottlenecks, not the underlying index bloat caused by empty fields; it would not improve search query execution time.

Practice this question →
64
MCQmedium

A company is implementing ServiceNow CMDB and wants to ensure that all CIs in the 'Production' environment are backed up daily. What is the best practice to achieve this?

A.Set the 'cmdb_ci' table's 'Backup' field to true
B.Use the 'Export to XML' feature every night for production CIs
C.Configure the instance's automatic daily backup
D.Create a scheduled data export for only production CMDB records
AnswerC

ServiceNow provides automatic daily backups of the entire instance.

Why this answer

Option C is correct because ServiceNow instances have a built-in automatic daily backup feature that captures the entire instance, including all CMDB records and CIs, regardless of environment. This ensures that production CIs are backed up daily without requiring manual configuration or selective exports, aligning with best practices for data protection and disaster recovery.

Exam trap

The trap here is that candidates may confuse CMDB-specific data management (like exporting records) with instance-level backup, or assume that a field or table-level setting can control backup behavior, when ServiceNow's backup is an all-or-nothing instance feature.

How to eliminate wrong answers

Option A is wrong because the 'cmdb_ci' table does not have a 'Backup' field; backup is managed at the instance level, not per CI or table. Option B is wrong because 'Export to XML' is a manual, one-time export tool, not an automated daily backup solution, and it does not guarantee consistent, scheduled backups for production CIs. Option D is wrong because creating a scheduled data export for only production CMDB records is an inefficient, custom approach that bypasses the native, comprehensive instance backup mechanism, and it may miss related data or dependencies.

Practice this question →
65
MCQeasy

Which table is the base table for all configuration items in the CMDB?

A.cmdb_ci
B.cmdb_ci_storage
C.cmdb_ci_server
D.cmdb_ci_network
AnswerA

cmdb_ci is the base table for all CIs.

Why this answer

The `cmdb_ci` table is the base (parent) table for all configuration items in the CMDB. It contains common attributes such as name, sys_class_name, and operational status, and all specialized CI tables (like `cmdb_ci_server`, `cmdb_ci_storage`, and `cmdb_ci_network`) extend from it via class inheritance. This hierarchical structure ensures that any CI record, regardless of its specific type, has a corresponding row in `cmdb_ci`.

Exam trap

The trap here is that candidates often confuse the base table with a commonly used child table like `cmdb_ci_server` or `cmdb_ci_network`, thinking that because those tables are frequently referenced, they are the root of the CMDB hierarchy.

How to eliminate wrong answers

Option B is wrong because `cmdb_ci_storage` is a child table that extends `cmdb_ci` and is used specifically for storage devices (e.g., SAN, NAS), not as the base table for all CIs. Option C is wrong because `cmdb_ci_server` is a child table that extends `cmdb_ci` and is used specifically for server hardware and virtual machines, not as the base table. Option D is wrong because `cmdb_ci_network` is a child table that extends `cmdb_ci` and is used specifically for network devices (e.g., routers, switches), not as the base table.

Practice this question →
66
Multi-Selecthard

A company has a large CMDB and wants to improve query performance on CI tables. Which two actions would help achieve this? (Choose two.)

Select 2 answers
A.Adding indexes to frequently queried columns.
B.Disabling all CMDB audit history.
C.Increasing the database heap size.
D.Using the CI Cache feature.
E.Archiving historical data from the CI table.
AnswersA, E

Indexes improve query performance by allowing faster data retrieval.

Why this answer

Adding indexes to frequently queried columns (Option A) improves query performance by allowing the database to locate rows more efficiently, reducing full table scans. This is a standard database optimization technique that directly addresses slow CI table queries in ServiceNow.

Exam trap

The trap here is that candidates often confuse application-layer caching (CI Cache) with database-level query optimization, leading them to select Option D instead of recognizing that indexes and archiving are the correct database-focused actions.

Practice this question →
67
MCQhard

After upgrading to a new version, a CMDB administrator notices that many CI records have been flagged as 'unverified' and their operational status changed. What is the most likely cause?

A.A scheduled job from the Discovery application marked CIs as unverified.
B.The IRE was reconfigured during upgrade.
C.The CMDB Data Manager job ran with incorrect parameters.
D.The identification and reconciliation rules were updated.
AnswerA

Discovery can flag CIs as unverified if it fails to identify them.

Why this answer

After a version upgrade, the Discovery application's scheduled jobs (e.g., 'Discovery Status Update' or 'Operational Status Update') automatically flag CIs as 'unverified' and reset their operational status to 'In Use' or 'Unverified' to force re-validation. This is a built-in safety mechanism to ensure that CIs discovered under the old version's logic are re-assessed under the new version's rules, preventing stale or incorrectly reconciled data from persisting.

Exam trap

The trap here is that candidates assume the IRE or CMDB Data Manager is responsible for status changes, when in fact the Discovery application's post-upgrade scheduled job is the specific mechanism that resets verification and operational status to force re-validation.

How to eliminate wrong answers

Option B is wrong because the Identification and Reconciliation Engine (IRE) is not reconfigured during an upgrade; its configuration is preserved, and changes to IRE behavior require explicit manual updates to identification rules or reconciliation engine properties. Option C is wrong because the CMDB Data Manager job does not set CIs as 'unverified' or change operational status; it handles data normalization, duplicate detection, and CI relationship maintenance, not status flags. Option D is wrong because updating identification and reconciliation rules would affect how CIs are matched and merged, but would not directly cause a bulk flagging of existing CIs as 'unverified' or change their operational status; that behavior is specific to Discovery's post-upgrade validation jobs.

Practice this question →
68
MCQmedium

A company uses Discovery to populate the CMDB. After a recent change, some CIs are incorrectly classified as 'Network Gear' instead of 'Server'. What is the most efficient way to correct the classification for these specific CIs?

A.Delete the CIs and let Discovery recreate them.
B.Manually change the 'Class' field on each CI.
C.Update the Discovery classification pattern and re-run Discovery on the affected IPs.
D.Run the 'Identify CI' probe again.
AnswerC

Correcting the pattern and re-running Discovery will reclassify the CIs correctly and prevent future issues.

Why this answer

Option C is correct because Discovery classification patterns define how CIs are categorized based on probe results. Updating the pattern to correctly identify the affected CIs and re-running Discovery on their IPs ensures that the classification is corrected at the source, preventing future misclassification without manual intervention or data loss.

Exam trap

The trap here is that candidates may think re-running the 'Identify CI' probe (Option D) will fix classification, but that probe only identifies CIs based on existing patterns and does not correct misclassification caused by a flawed pattern.

How to eliminate wrong answers

Option A is wrong because deleting CIs removes their relationships and historical data, and Discovery may recreate them with the same incorrect classification if the pattern is not fixed. Option B is wrong because manually changing the 'Class' field on each CI is inefficient for multiple CIs and does not address the root cause, so the misclassification will recur on the next Discovery run. Option D is wrong because the 'Identify CI' probe only identifies CIs but does not correct classification patterns; it would re-apply the same incorrect logic.

Practice this question →
69
MCQmedium

A CMDB administrator wants to ensure that all changes to CI records are tracked with the user who made the change. What system property must be set to true?

A.glide.record.audit
B.glide.cmdb.track.ci.changes
C.glide.cmdb.audit.enable
D.glide.sys.audit.all
AnswerA

Setting glide.record.audit to true enables auditing for all tables, including CMDB.

Why this answer

The correct answer is A because the `glide.record.audit` system property, when set to true, enables auditing for all records in the system, including Configuration Items (CIs) in the CMDB. This ensures that any change to a CI record is tracked with the user who made the modification, as required by the CMDB administrator. The property is a global audit toggle that applies to all tables, making it the appropriate choice for tracking CI changes.

Exam trap

The trap here is that candidates often confuse the global audit property with non-existent CMDB-specific properties like `glide.cmdb.audit.enable` or `glide.cmdb.track.ci.changes`, assuming that CI auditing requires a separate setting rather than the global `glide.record.audit` property.

How to eliminate wrong answers

Option B is wrong because `glide.cmdb.track.ci.changes` is not a valid system property in ServiceNow; there is no such property for tracking CI changes specifically. Option C is wrong because `glide.cmdb.audit.enable` is also not a valid system property; ServiceNow does not have a CMDB-specific audit property, as auditing is controlled at the table or global level. Option D is wrong because `glide.sys.audit.all` is not a valid system property; the correct global audit property is `glide.record.audit`, and `glide.sys.audit.*` properties do not exist in the platform.

Practice this question →
70
MCQmedium

Refer to the exhibit. What is the purpose of the 'condition' field in this discovery probe?

A.It defines the condition under which the probe triggers.
B.It specifies the condition for identifying duplicates.
C.It filters which discovered CIs should be updated by this probe.
D.It limits the probe to only query the database for existing records matching the condition.
AnswerC

The condition restricts the probe's updates to CIs matching the criteria.

Why this answer

In ServiceNow discovery probes, the 'condition' field is used to filter which discovered CIs should be updated by the probe. It acts as a predicate that evaluates against the discovered CI's attributes; only CIs that match the condition will have their fields updated by the probe's actions. This prevents the probe from overwriting CIs that do not meet specific criteria, ensuring targeted and accurate CI updates.

Exam trap

The trap here is that candidates often confuse the 'condition' field with the probe's trigger condition or with the identification rule, leading them to select option A or B, when in fact it is a post-discovery filter for updates.

How to eliminate wrong answers

Option A is wrong because the condition field does not define when the probe triggers; that is controlled by the probe's trigger schedule or the discovery process itself. Option B is wrong because duplicate identification is handled by the identification and reconciliation engine (IRE) using CI identifiers, not by the probe's condition field. Option D is wrong because the condition field does not limit database queries; it filters which discovered CIs are updated after the probe has already retrieved data from the target source.

Practice this question →
71
Multi-Selectmedium

Which THREE of the following are valid options when configuring an Identification and Reconciliation (IRE) rule? (Select exactly 3)

Select 3 answers
A.Reconcile only
B.Create only
C.Fuzzy match
D.Exact match
E.Update only
AnswersA, B, D

Reconcile only is a valid action that updates existing CIs without creating new ones.

Why this answer

Option A is correct because the 'Reconcile only' option in an IRE rule instructs the IRE engine to only reconcile existing CI records against incoming data, without creating new CIs. This is used when you want to ensure existing CIs are updated or validated but no new records should be created from the data source.

Exam trap

The trap here is that candidates confuse 'Reconcile only' with 'Update only' or think 'Fuzzy match' is a valid IRE option, but ServiceNow IRE only supports exact matching and the three specific actions: Reconcile only, Create only, and Exact match.

Practice this question →
72
MCQhard

During a CMDB health assessment, an administrator finds that the 'cmdb_ci_computer' table has 5000 records, but only 3000 have an 'operational_status' of 'In Use'. The administrator wants to view only the records with 'In Use' status in the CMDB reports. What is the most efficient approach?

A.Change the 'Display condition' of the table
B.Create a domain separation for 'In Use' CIs
C.Create a report with a condition where operational_status = 'In Use'
D.Modify the table's 'Condition Builder' to only show 'In Use' records
AnswerC

The report builder supports conditions to filter records.

Why this answer

Option C is correct because the most efficient approach to view only records with 'In Use' status in CMDB reports is to apply a condition directly within the report definition. This method filters the data at query time without altering the underlying table structure or affecting other users, ensuring that the report shows only the desired subset of records while preserving the full dataset for other purposes.

Exam trap

The trap here is that candidates may confuse table-level configuration (like display conditions or condition builders) with report-level filtering, leading them to choose options that would globally alter the table instead of applying a simple, non-destructive filter in the report itself.

How to eliminate wrong answers

Option A is wrong because changing the 'Display condition' of the table would alter the default view for all users and all interactions with the table, which is not appropriate for a report-specific filter and could hide records needed for other operations. Option B is wrong because domain separation is used to isolate data for different business units or tenants, not to filter records based on a specific field value like operational_status; it would introduce unnecessary complexity and overhead. Option D is wrong because the 'Condition Builder' is used to define conditions for table-level behaviors such as business rules or UI policies, not for filtering records in reports; modifying it would affect the entire table's behavior rather than just the report output.

Practice this question →
73
MCQmedium

A company's CMDB has duplicate CIs for the same server due to conflicting identification rules. The admin notices that some CIs are being merged incorrectly. What is the best practice to resolve this issue?

A.Increase the reconciliation engine's timeout value.
B.Run the CI Class Manager to delete duplicate CIs.
C.Review and refine the identification rules to ensure uniqueness criteria are correctly defined.
D.Disable all identification rules and use manual reconciliation.
AnswerC

This addresses the root cause by correcting the rules that cause misidentification.

Why this answer

Option C is correct because duplicate CIs in the CMDB arise from conflicting or poorly defined identification rules. The best practice is to review and refine these rules to ensure each CI has a unique set of identifying attributes (e.g., serial number, MAC address, or FQDN). This prevents incorrect merges and maintains data integrity without relying on manual cleanup or timeout adjustments.

Exam trap

The trap here is that candidates often confuse symptom fixes (like increasing timeouts or deleting duplicates) with the root cause solution, which is correcting the identification rules that govern CI uniqueness.

How to eliminate wrong answers

Option A is wrong because increasing the reconciliation engine's timeout value only affects how long the system waits for data sources to respond; it does not address the root cause of duplicate CIs or incorrect merges. Option B is wrong because running the CI Class Manager to delete duplicates is a reactive, manual fix that does not prevent future duplicates and can lead to data loss if CIs are merged incorrectly. Option D is wrong because disabling all identification rules and using manual reconciliation removes automation entirely, which is inefficient, error-prone, and defeats the purpose of a CMDB.

Practice this question →
74
MCQmedium

An administrator notices that a scheduled job that queries the cmdb_ci table is taking longer than expected. The job uses a glide query with multiple encoded queries. What is the best approach to improve performance without altering the job's results?

A.Create a database view on the cmdb_ci table and query the view instead.
B.Add an index on the fields used in the encoded query conditions.
C.Convert the glide query to a direct database query using System SQL.
D.Add an index on the sys_created_on field.
AnswerB

Indexing the filter fields accelerates query execution.

Why this answer

Adding an index on the fields used in the encoded query conditions directly reduces the number of rows scanned by the database engine when executing the GlideRecord query. This improves query performance without changing the logic or results of the scheduled job, as indexes only affect data access speed, not the data returned.

Exam trap

The trap here is that candidates often assume creating a view or using direct SQL will magically speed up queries, but ServiceNow's architecture requires proper indexing on the filtered columns to achieve performance gains without breaking platform security or result integrity.

How to eliminate wrong answers

Option A is wrong because creating a database view does not improve performance; views are just saved queries and still require scanning the underlying table unless the view is materialized (which ServiceNow does not support natively). Option C is wrong because converting to a direct System SQL bypasses ServiceNow's ACL and business logic, potentially altering results and violating platform best practices. Option D is wrong because adding an index on sys_created_on is irrelevant unless the encoded queries filter on that field; indexing the wrong columns provides no performance benefit.

Practice this question →
75
MCQhard

An administrator notices that a reference field on the cmdb_ci table, 'vendor', points to the 'core_company' table. However, some users report that they cannot select certain companies in the reference field. What is the most likely cause?

A.The 'display field' property is incorrectly configured
B.The 'vendor' field is marked as mandatory
C.The 'vendor' field has a reference qualifier that filters companies
D.The database view permission is set to 'none' for some users
AnswerC

Reference qualifiers limit the selectable records in a reference field.

Why this answer

Option C is correct because reference qualifiers are used to filter the records displayed in a reference field. If the 'vendor' field has a reference qualifier condition (e.g., 'active=true' or 'vendor_type=hardware'), only companies meeting that condition will appear in the dropdown, preventing users from selecting certain companies. This is the most likely cause when users cannot see specific records in a reference field.

Exam trap

The trap here is that candidates often confuse reference qualifiers (which filter available records) with display fields (which control what is shown in the field) or mandatory settings (which enforce data entry), leading them to pick option A or B instead of C.

How to eliminate wrong answers

Option A is wrong because the 'display field' property controls which column from the referenced table is shown in the field (e.g., 'name' vs 'u_number'), not which records are available for selection. Option B is wrong because marking a field as mandatory only requires a value to be entered before the record can be saved; it does not restrict which values can be selected. Option D is wrong because database view permissions control whether a user can see the table at all (e.g., via ACLs), not which specific records are filtered within a reference field; if permission were 'none', the field would likely show no results or an error, not a partial list.

Practice this question →
Page 1 of 2 · 99 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Db Admin Cmdb questions.

Start 20-question session