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

Question 1

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

Accepted Answer

The field 'u_environment' does not exist on records with sys_class_name='cmdb_ci_server'.. 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.

Answer

The table 'cmdb_ci' has no records with sys_class_name='cmdb_ci_server'.

Answer

The orderByDesc method is misspelled (should be orderByDescending).

Answer

The script lacks point number of rows (no rows with condition).

Question 2

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

Accepted Answer

It filters which discovered CIs should be updated by this probe.. 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.

Answer

It defines the condition under which the probe triggers.

Answer

It specifies the condition for identifying duplicates.

Answer

It limits the probe to only query the database for existing records matching the condition.

Question 3

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

Accepted Answer

Configure a data certification policy with required fields.. 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.

Answer

Use a scheduled job to populate common fields with default values.

Answer

Manually edit each CI that has missing fields.

Answer

Increase the CMDB Health weight for completeness.

Question 4

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 5

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 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.. Option A is correct because CI Change Request (the CI change request relationship/related list) links configuration items to change requests, so when a change is implemented the affected CIs are traceable and their records can be updated, keeping the CMDB aligned with the change process. Option E is correct because CMDB Health Verification (CMDB Health dashboards and scheduled health jobs) runs checks such as completeness, correctness, compliance, and orphan rules on CIs, and running it daily surfaces stale or inaccurate CI data so remediation keeps the CMDB accurate. Option B is not correct because a business rule that merely flips CI status on change approval does not by itself ensure CMDB accuracy and is not the standard mechanism for reconciling CIs with change records. Option C is not correct because CMDB Data Manager is used for data certification, attestation, and lifecycle/policy-based CI management, not for automatically updating CIs from change requests. Option D is not correct because CMDB CI Class Manager governs class hierarchy and class definitions, which affects data modeling rather than post-change CMDB accuracy.

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 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.. Option A is correct because the CI last discovered date (the most recent discovery/update timestamp) directly reveals CIs that have not been seen by discovery for a long period, which is a primary signal of an outdated or unused CI. Option B is correct because the CMDB Health 'Stale CI' indicator is a built-in metric that flags CIs whose last discovered/updated date exceeds a defined staleness threshold, precisely identifying CIs no longer in use. Option C is correct because running a CMDB Health report on compliance evaluates CIs against health/compliance rules (including staleness and required-attribute checks), surfacing outdated CIs that fail those criteria. Option D is not correct because the status field showing 'Retired' only reflects CIs already formally retired, not CIs that are outdated but still marked active or in use. Option E is not correct because manually auditing every CI is impractical and not a scalable, systematic method for identifying outdated CIs in a CMDB cleanup strategy.

Answer

Checking CI status field for 'Retired'.

Answer

Manually auditing each CI in the CMDB.

Question 9

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 10

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 11

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 12

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

Accepted Answer

Use the 'Archive Old Records' functionality in CMDB Workspace. 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.

Answer

Increase the 'CMDB History Pruning Frequency' property

Answer

Manually delete rows from the 'cmdb_ci_history' table using SQL

Answer

Run a scheduled report to export and then delete records

Question 13

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?

Accepted Answer

The table is not included in the 'CMDB Base Class' report definition. The CMDB dashboard reports are typically configured to display records from specific base classes or tables. If 'u_custom_infrastructure' is a child of 'cmdb_ci' but is not explicitly included in the 'CMDB Base Class' report definition, the report will not query that table, so its records will not appear. This is a common configuration oversight when extending the CMDB schema.

Answer

The table has permissions that restrict report access

Answer

The records have not passed data certification

Answer

The table's 'Display in CMDB dashboard' property is disabled

Question 14

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?

Accepted Answer

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

Answer

sys_journal_field

Answer

sys_audit

Answer

cmdb_ci

Question 15

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?

Accepted Answer

Create a data policy that requires a pattern. A data policy can enforce that the 'Asset Tag' field does not contain the specific string 'No asset tag' by using a condition script. Default values only populate the field at creation but do not prevent users from manually entering unwanted values like 'No asset tag' later. A data policy with a pattern requirement can block such invalid entries, ensuring data integrity.

Answer

Set the 'Asset Tag' field as mandatory

Answer

Use a workflow to populate the field

Answer

Configure a default value for the 'Asset Tag' field