SNOW-CSA Database Administration and CMDB Practice Test 4 — 15 Questions

Question 1

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?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Create a report with a condition where operational_status = 'In Use'. 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.

Answer

Change the 'Display condition' of the table

Answer

Create a domain separation for 'In Use' CIs

Answer

Modify the table's 'Condition Builder' to only show 'In Use' records

Question 2

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

Accepted Answer

cmdb_ci. Option B, cmdb_ci, is correct because it is the root/base class of the entire CMDB CI class hierarchy in ServiceNow, from which all other configuration item classes inherit. Option D, cmdb_ci_service, is correct because it is a defined base class representing business services within the CMDB class model. Option A, cmdb_ci_win_system, is not a valid base class but rather a specific CI class (or non-standard naming) for Windows systems, and the standard class is cmdb_ci_win_server or cmdb_ci_win_client. Option C, cmdb_ci_linux_system, is likewise not a base class but a specific platform class (standard is cmdb_ci_linux_server). Option E, cmdb_ci_computer, is a subclass of cmdb_ci used for computer CIs, not a base class itself.

Answer

cmdb_ci_win_system

Answer

cmdb_ci_linux_system

Answer

cmdb_ci_computer

Question 3

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

Accepted Answer

MAC address. MAC address (A) and serial number (D) are the two essential attributes for uniquely identifying configuration items in a CMDB because both are assigned by the manufacturer and are globally unique to a specific physical device, preventing duplicate records. A MAC address is a 48-bit hardware identifier burned into the network interface controller, making it unique per NIC, while a serial number is a manufacturer-assigned identifier unique to each individual unit, so either can reliably distinguish one CI from another. Asset tag (B) is not essential because it is a locally assigned label that can be duplicated, reused, or missing across organizations. Name (C) is not reliable for uniqueness since hostnames or CI names can be duplicated or changed. IP address (E) is not essential because it is a logical, dynamically assignable address that can change over time or be reused by different devices, so it cannot guarantee CI uniqueness.

Answer

Asset tag

Answer

Name

Answer

IP address

Question 4

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?

Accepted Answer

Modify the reconciliation rule to match on serial number instead of name and IP. 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.

Answer

Create an approval workflow for every new CI creation to manually check for duplicates

Answer

Add a unique constraint on the serial number field to prevent future duplicates

Answer

Disable the IPAM tool and cloud management platform integrations to stop duplicate creation

Question 5

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

Accepted Answer

Use the 'Archive' functionality in the Application Navigator.. ServiceNow's built-in Archive functionality is the recommended approach to reduce table size. It automatically moves old records to a separate archive table, preserving referential integrity and application logic, while freeing up space in the incident table. Option A is incorrect because the 'Delete Records' module permanently removes records, not archives them. Option C is incorrect because direct database deletion bypasses ServiceNow's safeguards and can corrupt data. Option D is incorrect because manually copying and deleting records is complex, error-prone, and not scalable; the Archive feature handles this efficiently.

Answer

Use the 'Delete Records' module to remove records older than 6 months.

Answer

Delete records older than 6 months directly from the database.

Answer

Create a scheduled job to copy records to a custom table and then delete from incident table.

Question 6

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?

Accepted Answer

The identification rule does not include custom fields.. 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.

Answer

The custom fields are not defined as 'Active' in the dictionary.

Answer

The discovery probe does not have access to the custom fields.

Answer

The custom table has a stale glide record.

Question 7

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?

Accepted Answer

Use the CI Lifecycle Manager to define a retirement business rule.. 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.

Answer

Configure a business rule on the CI class to update related CIs on state change.

Answer

Use the Relationship Viewer to manually edit each relationship.

Answer

Create a scheduled job to check for retired CIs and update dependencies.

Question 8

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

Accepted Answer

Configuring data certification policies.. Option A, configuring data certification policies, is correct because certification policies in ServiceNow CMDB Governance assign CI owners or managers to periodically review and attest that their CIs are accurate and complete, directly enforcing accountability for data quality. Option B, enabling CMDB Data Manager dashboards, is correct because CMDB Data Manager provides health dashboards and reports that surface stale, duplicate, or non-compliant CIs, giving administrators the visibility needed to remediate and maintain consistency. Option C is not effective because exporting to CSV for manual review is a one-off, error-prone process that does not enforce ongoing consistency. Option D is incorrect because CI Class Manager is used to define class hierarchy and attributes, not to enforce data quality. Option E is incorrect because reconciliation rules resolve duplicate CIs from discovery sources but do not by themselves enforce overall CMDB data consistency.

Answer

Exporting CMDB data to CSV for manual review.

Answer

Running the CI Class Manager regularly.

Answer

Setting up reconciliation rules.

Question 9

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

Accepted Answer

Adding indexes to frequently queried columns.. Option A is correct because adding indexes to frequently queried columns allows the database to locate matching CI records without scanning the entire CI table, which directly reduces query response time on large CMDB datasets. Option E is correct because archiving historical data from the CI table reduces the number of rows the database must scan, so queries against the remaining active CIs execute faster and index lookups stay efficient. Option B is not appropriate because disabling CMDB audit history removes change tracking and does not address query performance on CI tables. Option C is not correct because increasing the database heap size affects memory allocation for the Java/database process, not the query execution plan or table scan cost. Option D is not correct because the CI Cache feature caches CI data for application use and does not optimize database-level query performance on CI tables.

Answer

Disabling all CMDB audit history.

Answer

Increasing the database heap size.

Answer

Using the CI Cache feature.

Question 10

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?

Accepted Answer

Run the CMDB Data Manager to clean up empty fields and reduce index size.. 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.

Answer

Create a scheduled job to delete CIs that have not been updated in 90 days.

Answer

Disable the full-text search index and rely on basic database indexes.

Answer

Increase the database connection pool size and restart the instance.

Question 11

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?

Accepted Answer

Review the cmdb_ci table audit history to see changes.. 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.

Answer

Enable the 'Data Integrity' feature to log all web service updates.

Answer

Revert the CMDB to a previous state using a backup.

Answer

Restrict web service access to only necessary roles and review logs.

Question 12

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?

Accepted Answer

Create a business rule on the server table to update the CI when the OS is changed.. 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.

Answer

Configure the Discovery probe to re-discover the server after an OS update.

Answer

Use the CI Class Manager to set the field as 'Reconcilable'.

Answer

Use a scheduled job to query the server's actual OS version periodically.

Question 13

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?

Accepted Answer

Run the 'CMDB - Data Archiving' scheduled job to move retired CIs older than 6 months to the archive table.. 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.

Answer

Request a ServiceNow upgrade to a higher performance tier.

Answer

Create a new database view that combines cmdb_ci with other tables to improve report efficiency.

Answer

Disable all discovery sources except Service Mapping to reduce data inflow.

Question 14

A CMDB administrator needs to ensure that when a CI is retired, it is not deleted but its operational status changes to 'Retired' and it no longer appears in standard CI lists. Which feature should be configured on the CI class to achieve this?

Accepted Answer

Lifecycle stage and operational status fields with a UI policy that hides retired CIs. The correct approach uses the built-in Lifecycle Stage and Operational Status fields to mark a CI as retired without deleting it. A UI policy can then hide retired CIs from standard lists, meeting the requirement while preserving data integrity and historical relationships. This is the standard ServiceNow CMDB practice for decommissioning CIs.

Answer

Use a scheduled job to delete CIs after a certain period of inactivity

Answer

Set the CI's 'Install Status' to 'Retired' and create a filter on the CI list

Answer

Create a database view that excludes CIs with a 'Retired' flag

Question 15

A CMDB administrator needs to see which configuration items (CIs) were updated in the last 24 hours, but only wants to review changes that were made directly on the CI record, not changes to related records. Which approach should the administrator use?

Accepted Answer

Create a report on the CMDB CI table with a condition on the 'Updated' field relative to 24 hours ago.. The 'Updated' field on the CMDB CI table automatically captures the last modification timestamp for each CI record. A report with a relative date condition on this field efficiently lists all CIs changed in the last day. Other options either aggregate data or focus on relationships, not direct record updates.

Answer

Query the CMDB Health Dashboard and filter by the last 24 hours.

Answer

Check the CMDB Health Dashboard's 'CI Activity' section.

Answer

Use the CMDB Query Builder to find CIs with related audit records created in the last 24 hours.