Courseiva

CCNA Db Admin Cmdb Questions

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

Practice these questionsExam hubAll questions
76
MCQmedium

An administrator wants to ensure that CI relationship data is accurate. Which tool should be used to identify CIs that have missing or invalid relationships?

A.CMDB Data Manager
B.CMDB Health Verification
C.Discovery
D.CI Change Request
AnswerB

CMDB Health Verification runs checks on CI data including relationships.

Why this answer

CMDB Health Verification is the correct tool because it specifically evaluates the completeness and accuracy of CI relationships by running health checks that flag CIs with missing or invalid relationships. It provides a dashboard and reports that highlight relationship gaps, enabling administrators to remediate data quality issues directly.

Exam trap

The trap here is that candidates often confuse Discovery (which creates relationships) with CMDB Health Verification (which validates existing relationships), leading them to choose Discovery as the tool for identifying missing relationships.

How to eliminate wrong answers

Option A is wrong because CMDB Data Manager is used for importing and updating CI data from external sources (e.g., spreadsheets or APIs), not for validating the quality of existing relationships. Option C is wrong because Discovery identifies CIs and their relationships by probing the network, but it does not retrospectively analyze or flag missing/invalid relationships in the CMDB. Option D is wrong because CI Change Request is a process for requesting changes to CI records, not a tool for auditing relationship accuracy.

Practice this question →
77
Matchingmedium

Match each database table type to its description.

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

Concepts
Matches

Top-level table in a class hierarchy

Table that inherits fields from a parent table

Parent table for work-related records like incidents and changes

Stores system configuration data

Stores audit trail and activity log entries

Why these pairings

Understanding table types is key for data modeling in ServiceNow.

Practice this question →
78
MCQhard

A large financial institution uses ServiceNow CMDB to manage their IT infrastructure. They have a complex environment with multiple data sources: Discovery, SCCM, and a custom integration from their cloud provider. The CMDB contains over 100,000 CIs. Recently, the CMDB team noticed that for a specific set of Windows servers, the 'os_version' attribute is being updated to an incorrect value every night. The value comes from the SCCM integration, which is supposed to be the authoritative source for software-related attributes. However, the 'os_version' attribute should be authoritative from Discovery. The IRE is configured with reconciliation rules, but the issue persists. The team also finds that the Discovery job for these servers runs at 2:00 AM, and the SCCM integration runs at 3:00 AM. The incorrect value appears after the SCCM run. The reconciliation rules are set so that Discovery is authoritative for 'os_version', but the SCCM integration still overwrites it. What is the most likely cause and recommended action?

A.Enable the IRE 'Strict' mode to prevent any updates from non-authoritative sources.
B.Disable the SCCM integration for these servers and rely solely on Discovery.
C.Change the order of the integrations so that SCCM runs before Discovery.
D.Review and correct the reconciliation rule to ensure Discovery is the authoritative source for 'os_version' and that the rule is active.
AnswerD

If the rule is misconfigured or inactive, SCCM may overwrite the attribute.

Why this answer

Option D is correct because the reconciliation rule is the mechanism that dictates which data source is authoritative for a specific attribute. If the rule is misconfigured, inactive, or not properly scoped, the IRE will allow the SCCM integration to overwrite the 'os_version' attribute even though Discovery is intended to be authoritative. Reviewing and correcting the rule ensures that the IRE enforces the correct source priority for that attribute.

Exam trap

The trap here is that candidates assume changing the order of integrations (Option C) will fix the issue, but the IRE's reconciliation rules, not the sequence of data ingestion, determine which source is authoritative for a given attribute.

How to eliminate wrong answers

Option A is wrong because enabling IRE 'Strict' mode would block all updates from non-authoritative sources, but the SCCM integration is still an authorized data source; the issue is a misconfigured reconciliation rule, not the IRE mode. Option B is wrong because disabling the SCCM integration removes a valuable authoritative source for software attributes and does not address the root cause of the reconciliation rule misconfiguration. Option C is wrong because changing the order of integrations does not affect which source is authoritative; the IRE uses reconciliation rules to determine source priority, not the order of data ingestion.

Practice this question →
79
MCQmedium

You are responsible for the CMDB at a large enterprise. The CMDB is used for change management and incident management. Recently, during a major incident, it was found that several critical CIs were missing from the CMDB, causing delays in troubleshooting. Further analysis reveals that the Discovery probes were not running on those devices due to schedule conflicts. You need to ensure that all critical devices are discovered regularly. What is the most effective solution?

A.Manually add the missing CIs and set a reminder to check every week.
B.Use horizontal discovery to prioritize critical devices.
C.Create a dedicated Discovery schedule for critical devices with a higher frequency.
D.Increase the frequency of Discovery schedules for all devices.
AnswerC

A dedicated schedule ensures critical devices are discovered consistently regardless of other schedules.

Why this answer

Option C is correct because creating a dedicated Discovery schedule for critical devices ensures they are discovered at a higher frequency without being affected by schedule conflicts that impact the general discovery schedule. This approach guarantees that critical CIs are consistently updated in the CMDB, which is essential for effective change and incident management. By isolating critical devices into their own schedule, you avoid the overhead of increasing frequency for all devices while meeting the specific requirement for regular discovery of critical assets.

Exam trap

The trap here is that candidates may confuse 'horizontal discovery' (which expands discovery scope) with 'prioritization' or 'scheduling,' leading them to select Option B, when in fact horizontal discovery does not address frequency or schedule conflicts.

How to eliminate wrong answers

Option A is wrong because manually adding missing CIs and setting a weekly reminder is a reactive, labor-intensive approach that does not address the root cause of schedule conflicts and does not ensure ongoing, automated discovery of critical devices. Option B is wrong because horizontal discovery is a pattern used to discover devices across multiple network segments or IP ranges, not a mechanism to prioritize or schedule discovery for specific critical devices; it does not resolve schedule conflicts or guarantee regular discovery. Option D is wrong because increasing the frequency of Discovery schedules for all devices would unnecessarily consume system resources and network bandwidth, and it may still not resolve schedule conflicts if the same schedule is shared; it is not a targeted solution for critical devices.

Practice this question →
80
MCQmedium

A CMDB administrator runs a report and finds that the count of CIs in a certain class is unexpectedly low. They suspect that some CIs were deleted accidentally. How can they verify this?

A.Check the sys_audit table for delete records.
B.Query the sys_archive table.
C.Use the CMDB Rollback feature.
D.Restore from backup.
AnswerA

sys_audit records all deletions, providing user and timestamp.

Why this answer

The sys_audit table records all insert, update, and delete operations on CMDB CIs. By querying this table for records with the operation type 'delete' and the affected CI class, the administrator can confirm whether CIs were deleted and identify when and by whom. This is the standard method for auditing historical changes in ServiceNow.

Exam trap

The trap here is that candidates confuse the sys_archive table (which stores retired CIs) with the sys_audit table (which logs deletions), leading them to choose Option B instead of the correct audit trail approach.

How to eliminate wrong answers

Option B is wrong because the sys_archive table stores archived (retired) CIs, not deleted records; deletion removes the record entirely, whereas archiving preserves it. Option C is wrong because the CMDB Rollback feature restores a CI to a previous state from a snapshot, but it does not provide a log of deletions or verify that deletions occurred. Option D is wrong because restoring from backup is a disaster recovery procedure that would overwrite current data and is not a targeted method to verify specific accidental deletions.

Practice this question →
81
Multi-Selecthard

A company wants to ensure that only authorized changes to the CMDB are allowed. Which THREE of the following mechanisms can help enforce this?

Select 3 answers
A.The Identification and Reconciliation Engine (IRE)
B.CMDB Health Definitions with remediation tasks
C.Scheduled Discovery jobs
D.Access Control Lists (ACLs) on CMDB tables
E.Business rules on the cmdb_ci table
AnswersB, D, E

Health rules can detect and correct unauthorized changes.

Why this answer

Option B is correct because CMDB Health Definitions can include remediation tasks that automatically or manually enforce compliance by correcting unauthorized changes to CI attributes. These tasks are triggered when a health score falls below a threshold, ensuring that only authorized modifications persist in the CMDB.

Exam trap

The trap here is that candidates often confuse the IRE's role in data reconciliation with change authorization, or assume that Discovery jobs inherently enforce change control, when in fact neither mechanism validates whether a change is authorized before applying it.

Practice this question →
82
MCQeasy

Your organization uses multiple data sources to populate the CMDB, including ServiceNow Discovery, manual imports, and integrations with an external asset management system. Recently, you have noticed that some CIs appear to be duplicated despite having identification rules configured. Investigation reveals that the identification rules are not correctly matching CIs from the external system. What should you do to resolve the duplication without losing existing relationships?

A.Delete all CIs from the external system and re-import.
B.Manually merge all duplicate CIs using the UI.
C.Disable the external integration to prevent further duplicates.
D.Modify the identification rule to include a unique identifier from the external system.
AnswerD

This ensures that the IRE can match CIs from the external system to existing records.

Why this answer

Option C is correct because modifying the identification rule to include a unique identifier from the external system will allow the IRE to correctly match existing CIs. Option A is wrong because manual merging is time-consuming and may not prevent recurrence. Option B is wrong because deleting and re-importing could remove change history and relationships.

Option D is wrong because disabling the integration stops data flow and does not fix the existing duplicates.

Practice this question →
83
MCQmedium

An administrator notices that a CMDB CI class is not visible in the class hierarchy. The class exists in the database but cannot be selected when creating a new CI. What is the likely cause?

A.The class is retired.
B.The class is marked as 'abstract'.
C.The class has no parent.
D.The class has a missing table extension.
AnswerB

Abstract classes cannot be instantiated, so they are not available for creating new CIs.

Why this answer

In ServiceNow, a CI class marked as 'abstract' exists in the database but is not intended for direct instantiation. Abstract classes serve as templates for inheritance and are hidden from the 'New CI' selection list, which is why the administrator cannot select it when creating a new CI.

Exam trap

The trap here is that candidates often confuse 'abstract' with 'retired' or assume a missing parent causes visibility issues, but ServiceNow specifically uses the abstract flag to hide classes from selection while keeping them in the database for inheritance purposes.

How to eliminate wrong answers

Option A is wrong because a retired class is typically removed from the class hierarchy and may not appear in the database at all, whereas the question states the class exists in the database. Option C is wrong because a class without a parent would still be visible in the hierarchy (as a root class) and selectable for new CI creation. Option D is wrong because a missing table extension would cause the class to not function properly or throw errors, but it would not hide the class from the selection list; the class would still appear in the hierarchy.

Practice this question →
84
Drag & Dropmedium

Drag and drop the steps to configure a new Catalog Item 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

Catalog items define service request forms for the service catalog.

Practice this question →
85
Multi-Selecteasy

An administrator needs to enforce data consistency in the CMDB. Which two methods are effective for ensuring CI data quality? (Choose two.)

Select 2 answers
A.Configuring data certification policies.
B.Enabling CMDB Data Manager dashboards.
C.Exporting CMDB data to CSV for manual review.
D.Running the CI Class Manager regularly.
E.Setting up reconciliation rules.
AnswersA, B

Certification policies require CI owners to regularly attest to the accuracy of their data.

Why this answer

Data certification policies in ServiceNow allow administrators to define rules that automatically validate CI data against specified criteria, such as mandatory fields or value ranges, and flag or correct non-compliant records. This proactive enforcement ensures ongoing data consistency without manual intervention, making it a core method for maintaining CMDB data quality.

Exam trap

The trap here is that candidates often confuse reconciliation rules (which handle data source conflicts) with data certification policies (which enforce quality standards), leading them to select option E instead of A.

Practice this question →
86
Multi-Selecteasy

Which TWO are valid methods to populate the CMDB with configuration items?

Select 2 answers
A.Using the 'CMDB Import' application to upload data from external tools.
B.Running ServiceNow Discovery to automatically identify and populate CIs.
C.Manually creating CIs using the 'New' button on the CMDB module.
D.Configuring LDAP integration to synchronize user and computer objects.
E.Importing a CSV file directly into the cmdb_ci table using the Import Set feature.
AnswersB, C

Discovery is a primary method for automated CI population.

Why this answer

Option B is correct because ServiceNow Discovery uses probes and sensors to scan the network, identify running services and applications, and automatically create or update CIs in the CMDB without manual intervention. This is a primary, supported method for populating the CMDB with accurate, up-to-date configuration data.

Exam trap

The trap here is that candidates may confuse the 'Import Set' feature (which requires a staging table and transform map) with a direct CSV import, or mistakenly think LDAP integration can populate CIs when it is designed for user and group synchronization.

Practice this question →
87
MCQhard

Refer to the exhibit. The script runs but no output is produced. What is the most likely cause?

A.The table 'cmdb_ci' has no records with sys_class_name='cmdb_ci_server'.
B.The orderByDesc method is misspelled (should be orderByDescending).
C.The script lacks point number of rows (no rows with condition).
D.The field 'u_environment' does not exist on records with sys_class_name='cmdb_ci_server'.
AnswerD

A missing field causes the query to return no results.

Why this answer

Option D is correct because the script uses `getValue('u_environment')` on a GlideRecord query for `cmdb_ci` with `sys_class_name='cmdb_ci_server'`. If the field `u_environment` does not exist on that table or class, `getValue` returns null, and the `gs.print` statement outputs nothing (or an empty string). The script runs without error, but no output is produced because the field is missing, not because the query returns zero rows.

Exam trap

The trap here is that candidates assume 'no output' means 'no records matched the query' (Option A), but the real issue is that the script runs successfully yet prints nothing because the field being accessed does not exist on the queried records.

How to eliminate wrong answers

Option A is wrong because if the table had no records, the `while` loop would never execute, and no output would be produced — but the question states the script runs, implying the loop iterates; the issue is that `getValue` returns null for each record, not that there are no records. Option B is wrong because `orderByDesc` is a valid GlideRecord method in ServiceNow (it sorts descending); there is no `orderByDescending` method — this is a common confusion with .NET or other languages. Option C is wrong because 'point number of rows' is not a ServiceNow concept; the script does not use `setLimit` or any row-limiting method, so the query returns all matching rows; the lack of output is due to the missing field, not a row limit.

Practice this question →
88
MCQhard

Refer to the exhibit. An administrator runs Discovery on a switch and receives this payload. However, the CI is not created in the CMDB. The Discovery log shows 'Identification rule did not match any CI. Creating new CI failed because of duplicate serial number?'. What is the most likely cause?

A.The class 'Network Gear' is invalid.
B.There is already a CI with the same serial number.
C.The identification rule is misconfigured.
D.The serial number field is missing from the payload.
AnswerB

The log explicitly states 'duplicate serial number', indicating a serial conflict.

Why this answer

The error message 'Creating new CI failed because of duplicate serial number' directly indicates that a CI with the same serial number already exists in the CMDB. ServiceNow enforces uniqueness on the serial number field for hardware CIs; when Discovery attempts to create a new CI but finds a matching serial number, the operation fails. This is why option B is correct.

Exam trap

ServiceNow often tests the distinction between identification rule failures (which produce 'no match' or 'multiple match' errors) and database constraint violations (like duplicate serial numbers), leading candidates to incorrectly blame the identification rule configuration when the real issue is a unique key conflict.

How to eliminate wrong answers

Option A is wrong because if the class 'Network Gear' were invalid, Discovery would fail earlier with a class-not-found error, not a duplicate serial number error. Option C is wrong because a misconfigured identification rule would cause a 'no match' or 'multiple match' error, not a duplicate serial number failure; the identification rule itself is working (it found no match), but the creation attempt fails due to the serial number constraint. Option D is wrong because if the serial number field were missing from the payload, Discovery would not be able to check for duplicates and would likely create the CI without a serial number, or log a different error about missing mandatory fields.

Practice this question →
89
MCQmedium

Refer to the exhibit. An administrator runs this script in a background script. The script runs without errors but does not output any CI names. All servers exist in the CMDB. What could be the issue?

A.The sys_class_name should be 'Server' instead of 'cmdb_ci_server'.
B.The GlideRecord is not properly initialized.
C.The administrator does not have read access to the cmdb_ci table.
D.The script does not have a condition to check the number of records.
AnswerA

In the base table cmdb_ci, the 'sys_class_name' field stores the table name, but the 'Class' field stores the display name 'Server'. The filter should use the display value or query the child table directly.

Why this answer

The correct answer is A because the script uses 'cmdb_ci_server' as the table name in the GlideRecord constructor, but the CMDB stores server records under the 'cmdb_ci' table with a sys_class_name of 'cmdb_ci_server'. The GlideRecord API expects the actual table name (cmdb_ci), not the sys_class_name value. Using 'cmdb_ci_server' as the table name will result in an empty query, as no table with that name exists in the database schema.

Exam trap

The trap here is that candidates confuse the sys_class_name (e.g., 'cmdb_ci_server') with the actual database table name ('cmdb_ci'), leading them to incorrectly use the class name in the GlideRecord constructor.

How to eliminate wrong answers

Option B is wrong because the GlideRecord is properly initialized with 'new GlideRecord('cmdb_ci_server')' — the syntax is correct, but the table name is invalid. Option C is wrong because if the administrator lacked read access to the cmdb_ci table, the script would either throw a security exception or return zero records silently, but the question states the script runs without errors, implying access is granted. Option D is wrong because checking the number of records is not required for the script to output CI names; a query that returns records will iterate correctly without an explicit count check.

Practice this question →
90
MCQeasy

An administrator needs to archive old incident records to reduce the size of the incident table. Which approach is recommended for optimal performance?

A.Use the 'Delete Records' module to remove records older than 6 months.
B.Use the 'Archive' functionality in the Application Navigator.
C.Delete records older than 6 months directly from the database.
D.Create a scheduled job to copy records to a custom table and then delete from incident table.
AnswerB

Archive is the recommended method to safely move old records to an archive table.

Why this answer

Option C is correct because ServiceNow's built-in Archive functionality is designed to move old records efficiently while maintaining referential integrity. Option A is wrong because direct database deletion bypasses application logic and can cause data corruption. Option B is wrong because the 'Delete Records' module is for deletion, not archival.

Option D is wrong because manual copy-and-delete is error-prone and not scalable.

Practice this question →
91
MCQhard

Your organization has implemented ServiceNow CMDB with multiple data sources including ServiceNow Discovery, SCCM, and manual imports. You notice that for a critical group of Windows servers, the 'os_version' attribute is being overwritten frequently. Upon investigation, you find that Discovery reports the correct version, but SCCM imports an older version that overwrites it. The Discovery source runs daily at 2 AM, and SCCM imports run at 4 AM. Currently, all data sources have equal priority. You need to ensure that the Discovery value is the authoritative source for os_version on these servers, but you do not want to block SCCM from updating other attributes. What is the best course of action?

A.Remove SCCM as a data source for these servers.
B.Disable reconciliation for the Windows Server CI class.
C.Set the 'Preserve manual changes' flag on the CI class.
D.Create a reconciliation rule that gives Discovery higher priority than SCCM for the os_version attribute on the Windows Server CI class.
AnswerD

This targets the specific attribute and source priority.

Why this answer

Option D is correct because reconciliation rules allow you to define attribute-level priority between data sources without blocking SCCM from updating other attributes. By creating a rule that gives Discovery higher priority than SCCM specifically for the os_version attribute on the Windows Server CI class, Discovery's value will be authoritative for that attribute while SCCM can still update other attributes. This approach preserves the multi-source CMDB integrity without disabling reconciliation or removing SCCM entirely.

Exam trap

The trap here is that candidates may confuse reconciliation rules with disabling reconciliation entirely or assume that removing a data source is the only way to prevent overwrites, missing the attribute-level granularity that reconciliation rules provide.

How to eliminate wrong answers

Option A is wrong because removing SCCM as a data source would prevent it from updating any attributes on these servers, which is overly restrictive and contradicts the requirement to allow SCCM to update other attributes. Option B is wrong because disabling reconciliation for the Windows Server CI class would stop all conflict resolution, meaning the last data source to write (SCCM at 4 AM) would always win, which does not solve the overwrite issue. Option C is wrong because the 'Preserve manual changes' flag only protects manually entered data from being overwritten by automated sources; it does not affect priority between automated sources like Discovery and SCCM.

Practice this question →
92
MCQeasy

What is the purpose of the 'cmdb_rel_ci' table?

A.It stores the actual relationships between CIs.
B.It stores the CI classification rules.
C.It stores the CI hierarchy tree.
D.It stores the list of all relationship types.
AnswerA

Each record in cmdb_rel_ci represents a relationship between two CIs.

Why this answer

The 'cmdb_rel_ci' table in ServiceNow stores the actual relationships between Configuration Items (CIs). Each row in this table represents a specific instance of a relationship, linking a parent CI to a child CI via a defined relationship type, enabling the CMDB to model dependencies and connectivity in the infrastructure.

Exam trap

The trap here is that candidates confuse the 'cmdb_rel_ci' table (which stores actual relationship instances) with the 'cmdb_rel_type' table (which stores relationship definitions), leading them to select option D.

How to eliminate wrong answers

Option B is wrong because CI classification rules are stored in the 'cmdb_class' table, not 'cmdb_rel_ci'. Option C is wrong because the CI hierarchy tree is derived from the 'cmdb_rel_ci' table but is not stored as a separate tree structure; the hierarchy is built dynamically from the relationship records. Option D is wrong because the list of all relationship types is stored in the 'cmdb_rel_type' table, not 'cmdb_rel_ci'.

Practice this question →
93
MCQeasy

A ServiceNow administrator wants to archive old CMDB history records that are older than 12 months to improve performance. Which approach should be used?

A.Increase the 'CMDB History Pruning Frequency' property
B.Manually delete rows from the 'cmdb_ci_history' table using SQL
C.Use the 'Archive Old Records' functionality in CMDB Workspace
D.Run a scheduled report to export and then delete records
AnswerC

This is the designed feature to safely archive old history records.

Why this answer

Option C is correct because the CMDB Workspace provides a built-in 'Archive Old Records' functionality specifically designed to move old CMDB history records (e.g., from the `cmdb_ci_history` table) to an archive table, improving performance without data loss. This approach is supported by ServiceNow's recommended best practices for managing CMDB history data, as it preserves records for compliance while reducing the active table size.

Exam trap

The trap here is that candidates often confuse 'pruning' (which deletes records) with 'archiving' (which moves records to a separate table), leading them to choose Option A, or they incorrectly assume that manual SQL operations are acceptable in ServiceNow, which is a common anti-pattern tested on the CSA exam.

How to eliminate wrong answers

Option A is wrong because increasing the 'CMDB History Pruning Frequency' property only controls how often the system checks for records to prune (delete), not the archival of old records; it does not archive data and may lead to permanent deletion if combined with pruning rules. Option B is wrong because manually deleting rows from the `cmdb_ci_history` table using SQL violates ServiceNow's supported practices, bypasses the platform's audit and security controls, and can cause data integrity issues or break application logic. Option D is wrong because running a scheduled report to export and then delete records is a manual, error-prone process that does not leverage ServiceNow's native archival capabilities, risks incomplete or inconsistent data removal, and lacks the automated tracking and rollback features of the Archive Old Records functionality.

Practice this question →
94
MCQhard

During a CMDB audit, an administrator discovers that some CIs have a 'sys_class_name' of 'cmdb_ci' instead of a specific subclass like 'cmdb_ci_server'. What is the most likely cause?

A.The administrator manually changed the class field to 'cmdb_ci'.
B.The CI was created by Discovery and the sensor failed to classify it.
C.The identification rule is incorrectly configured to map to the base table.
D.The CI has been retired and the class was reset.
AnswerC

If identification rules or scripts directly create records in cmdb_ci without subclass, the CI will have sys_class_name 'cmdb_ci'.

Why this answer

The most likely cause is an incorrectly configured identification rule that maps the CI to the base table 'cmdb_ci' instead of a specific subclass. Identification rules determine how CIs are matched and created; if the rule's 'Table' field is set to 'cmdb_ci' rather than a subclass like 'cmdb_ci_server', all new CIs matching that rule will be created at the base class level, losing subclass-specific attributes and relationships.

Exam trap

The trap here is that candidates often assume Discovery sensors are solely responsible for classification, but the identification rule's table setting is the primary driver for the CI's class assignment, and a misconfigured rule can override sensor classification.

How to eliminate wrong answers

Option A is wrong because manually changing the class field to 'cmdb_ci' would require explicit user action and is not a typical cause for multiple CIs having the base class; the administrator is discovering the issue, not causing it. Option B is wrong because Discovery sensors classify CIs based on identification and classification rules; if a sensor fails to classify, the CI would typically remain unclassified or get a default class, not specifically 'cmdb_ci' — the base class assignment is driven by the identification rule's table mapping. Option D is wrong because retiring a CI does not reset its class; retirement only changes the 'Install Status' field to 'Retired' and does not alter the 'sys_class_name'.

Practice this question →
95
MCQeasy

A junior administrator wants to see which CIs have been updated in the last 24 hours. Which table contains the change log for CMDB CIs?

A.sys_journal_field
B.sys_audit
C.cmdb_ci
D.cmdb_ci_history
AnswerD

This table tracks all CMDB CI updates.

Why this answer

The `cmdb_ci_history` table is specifically designed to track changes to CMDB CIs, including updates made in the last 24 hours. It stores historical snapshots of CI attribute changes, making it the correct table for a junior administrator to query for recent CI updates.

Exam trap

The trap here is that candidates often confuse the `sys_audit` table (which logs changes to any record) with the dedicated `cmdb_ci_history` table, not realizing that CMDB has its own specialized history table for CIs.

How to eliminate wrong answers

Option A is wrong because `sys_journal_field` stores journal entries (like work notes or comments) attached to records, not the change log for CMDB CIs. Option B is wrong because `sys_audit` tracks changes to any table's records via audit rules, but it is a generic auditing table, not the dedicated CMDB CI history table. Option C is wrong because `cmdb_ci` is the main table that stores the current state of CIs, not the historical change log.

Practice this question →
96
MCQeasy

A CMDB administrator notices that duplicate CIs are being created for the same server from different discovery sources. What is the most likely cause?

A.The identification rules for the CI class are not correctly defined.
B.The 'Prevent duplicates' flag is not enabled.
C.The reconciliation rules are misconfigured.
D.The CMDB is set to read-only mode.
AnswerA

Identification rules determine how CIs are uniquely identified; misconfiguration leads to duplicates.

Why this answer

Duplicate CIs occur when multiple discovery sources (e.g., Service Mapping, Discovery, or cloud APIs) identify the same server but the identification rules fail to reconcile them into a single CI. Identification rules define which attributes (such as serial number, MAC address, or FQDN) uniquely identify a CI class. If these rules are missing, incomplete, or incorrectly prioritized, the system treats each discovery event as a new CI, leading to duplicates.

Exam trap

The trap here is that candidates confuse 'identification rules' (which prevent duplicates by uniquely matching CIs) with 'reconciliation rules' (which resolve attribute conflicts after matching), leading them to incorrectly select option C.

How to eliminate wrong answers

Option B is wrong because the 'Prevent duplicates' flag is a UI-level setting that prevents manual creation of duplicate CIs in the CMDB interface, but it does not control duplicate creation from automated discovery sources. Option C is wrong because reconciliation rules handle conflict resolution (e.g., which source's attribute values to trust) after identification has already matched CIs; they do not prevent the initial creation of duplicate CIs. Option D is wrong because read-only mode prevents all CI creation and modification, so no duplicates would be created at all; the administrator would see errors or no changes, not duplicates.

Practice this question →
97
MCQhard

Refer to the exhibit. What is the primary purpose of this Business Rule?

A.To update a timestamp field on the parent CI whenever a child CI is updated.
B.To prevent updates to child CIs if the parent CI has not been updated recently.
C.To log all changes made to a CI in a custom table.
D.To delete child CIs when the parent CI is deleted.
AnswerA

The script retrieves the parent and sets a timestamp field.

Why this answer

The Business Rule shown is an 'After' update rule that triggers on the 'cmdb_ci' table. It uses a 'setValue' call on the parent record (via 'current.parent') to update the 'sys_updated_on' field, which is the system timestamp. This ensures that whenever a child CI is updated, the parent CI's timestamp is refreshed, maintaining an accurate audit trail of changes in the CMDB hierarchy.

Exam trap

ServiceNow often tests the misconception that a Business Rule updating a related record's timestamp is for logging or deletion, when in fact it is purely for maintaining a freshness indicator in a parent-child CI relationship.

How to eliminate wrong answers

Option B is wrong because the rule does not check any timestamps or prevent updates; it only updates the parent's timestamp after a child update. Option C is wrong because the rule does not write to a custom table or use any logging mechanism like 'gs.log' or 'GlideRecord.insert' to a separate table. Option D is wrong because the rule does not perform any delete operations; it only updates a timestamp field on the parent, and there is no cascading delete logic.

Practice this question →
98
MCQeasy

What is the purpose of the CMDB Health Dashboard?

A.To manage user roles and permissions for CMDB
B.To monitor the completeness and compliance of CI data in the CMDB
C.To visualize relationships between CIs
D.To configure discovery schedules and probes
AnswerB

The Health Dashboard tracks data quality metrics.

Why this answer

The CMDB Health Dashboard is designed to monitor the completeness and compliance of Configuration Item (CI) data within the CMDB. It provides metrics and visualizations that help administrators identify data quality issues, such as missing mandatory fields, stale CIs, or violations of CMDB rules, ensuring the CMDB remains a reliable source of truth for IT operations.

Exam trap

The trap here is that candidates often confuse the CMDB Health Dashboard with the CI Relationship Map or Discovery configuration, but the dashboard is strictly a monitoring tool for data quality, not for managing relationships or discovery schedules.

How to eliminate wrong answers

Option A is wrong because managing user roles and permissions for the CMDB is handled through the Role Administration module and Access Controls (ACLs), not the CMDB Health Dashboard. Option C is wrong because visualizing relationships between CIs is the purpose of the Service Graph Connector or the CI Relationship Map, not the Health Dashboard. Option D is wrong because configuring discovery schedules and probes is done within the Discovery module, specifically in the Discovery Schedules and Probe configurations, not the CMDB Health Dashboard.

Practice this question →
99
Multi-Selectmedium

A ServiceNow administrator is configuring Data Segmentation for CMDB. Which TWO statements are true about Data Segmentation? (Select exactly 2)

Select 2 answers
A.It can be applied to individual CI fields.
B.It can be used to restrict access to CI records based on user criteria.
C.It is configured in the Data Segmentation module under System Security.
D.It requires the subscription of a separate CMDB product license.
E.It can be combined with standard ACLs for granular control.
AnswersB, E

Data Segmentation allows record-level access based on user attributes.

Why this answer

Data Segmentation in ServiceNow restricts access to CI records based on user criteria, such as business unit or location, by evaluating conditions against the user's session. This is a row-level security mechanism that filters which CI records a user can see, making Option B correct. It works alongside standard ACLs, which handle field- and record-level permissions, allowing administrators to layer both for granular control, confirming Option E.

Exam trap

The trap here is that candidates often confuse Data Segmentation with field-level ACLs or assume it requires an additional license, when in fact it is a row-level security feature that is part of the base CMDB and works in conjunction with, not instead of, standard ACLs.

Practice this question →
← PreviousPage 2 of 2 · 99 questions total

Ready to test yourself?

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

Start 20-question session