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

Question 1

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

Accepted Answer

cmdb_ci. 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`.

Answer

cmdb_ci_storage

Answer

cmdb_ci_server

Answer

cmdb_ci_network

Question 2

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?

Accepted Answer

CMDB Health Verification. 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.

Answer

CMDB Data Manager

Answer

Discovery

Answer

CI Change Request

Question 3

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?

Accepted Answer

The identification rule is incorrectly configured to map to the base table.. 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.

Answer

The administrator manually changed the class field to 'cmdb_ci'.

Answer

The CI was created by Discovery and the sensor failed to classify it.

Answer

The CI has been retired and the class was reset.

Question 4

What is the purpose of the 'cmdb_rel_ci' table?

Accepted Answer

It stores the actual relationships between CIs.. 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.

Answer

It stores the CI classification rules.

Answer

It stores the CI hierarchy tree.

Answer

It stores the list of all relationship types.

Question 5

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

Accepted Answer

CI Class Manager. 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).

Answer

System Definition > Tables

Answer

CMDB Data Manager

Answer

Studio

Question 6

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?

Accepted Answer

The 'sys_class_name' field was not set to 'u_cmdb_ci_application' during import.. The 'Configuration Items' module filters records based on the 'sys_class_name' field to display only those belonging to the cmdb_ci class or its subclasses. When importing data into a custom table that extends cmdb_ci, if the 'sys_class_name' field is not explicitly set to 'u_cmdb_ci_application', the records will inherit a default value (often the base class name) and thus be excluded from the module's view. This is a common requirement for CMDB extension tables to ensure proper classification and visibility.

Answer

The import set used the wrong transform map.

Answer

The table was created in the wrong application scope.

Answer

The user does not have access to the custom table.

Question 7

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

Accepted Answer

Use CI Change Request to link CIs to change requests.. Running CMDB Health Verification helps identify stale or incorrect CIs, ensuring accuracy. Using CI Change Request links CIs to change requests, automatically updating status. Option B (creating a business rule) is a custom approach, not a standard best practice. Option C (Data Manager) is for bulk updates, not accuracy. Option D (CI Class Manager) enforces class hierarchy but does not directly ensure accuracy after change management.

Answer

Create a business rule to update CI status when a change request is approved.

Answer

Set up CMDB Data Manager to automatically update CIs based on change requests.

Answer

Enable CMDB CI Class Manager to enforce class hierarchy.

Question 8

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

Accepted Answer

cmdb_rel_type. 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.

Answer

cmdb_ci_service

Answer

cmdb_ci

Answer

cmdb_ci_relationship

Question 9

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.)

Accepted Answer

Reviewing CI last discovered date.. 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.

Answer

Checking CI status field for 'Retired'.

Answer

Manually auditing each CI in the CMDB.

Question 10

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?

Accepted Answer

The transform map is referencing a table that hasn't been created.. 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.

Answer

The import set has incorrect column mappings.

Answer

The user does not have permission to write to the table.

Answer

The CMDB is locked for maintenance.

Question 11

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?

Accepted Answer

The administrator does not have read access to the cmdb_ci table.. The script runs without errors but returns no records, indicating a permission issue. In ServiceNow, if the administrator lacks read access to the 'cmdb_ci' table (or the specific table being queried), GlideRecord will not return any records even if they exist. The other options are incorrect: A is wrong because 'cmdb_ci_server' is the correct sys_class_name value for server CIs; B is false because the script runs without errors, so initialization is fine; D is false because the condition is not necessary for record output—the query itself would return all records without a condition.

Answer

The sys_class_name should be 'Server' instead of 'cmdb_ci_server'.

Answer

The GlideRecord is not properly initialized.

Answer

The script does not have a condition to check the number of records.

Question 12

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?

Accepted Answer

There is already a CI with the same serial number.. 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.

Answer

The class 'Network Gear' is invalid.

Answer

The identification rule is misconfigured.

Answer

The serial number field is missing from the payload.

Question 13

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?

Accepted Answer

Add the field to the 'cmdb_ci' table directly. 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.

Answer

Add the field to a child class like 'cmdb_ci_computer'

Answer

Use the 'Include Table' configuration to add the field

Answer

Create a new extension table for the field

Question 14

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?

Accepted Answer

Set a 'unique' constraint on the Serial Number field. 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.

Answer

Configure a reconciliation rule to merge duplicates automatically

Answer

Use a data certification rule to validate serial numbers

Answer

Instruct the discovery teams to manually de-duplicate

Question 15

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?

Accepted Answer

The 'vendor' field has a reference qualifier that filters companies. 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.

Answer

The 'display field' property is incorrectly configured

Answer

The 'vendor' field is marked as mandatory

Answer

The database view permission is set to 'none' for some users