SNOW-CSA Practice Test 24 — 15 Questions

Question 1

A before business rule on the Change Request table is supposed to set the 'risk' field based on the 'impact' and 'urgency' fields. The rule uses the current.update() method. However, when the rule runs, it causes a recursive loop. What is the best solution?

Accepted Answer

Use current.setValue() instead of current.update().. Option A is correct because current.update() triggers the business rule again on the same record, causing a recursive loop. Using current.setValue() only modifies the field in memory without writing to the database, so it does not re-trigger the business rule. This is the standard pattern for avoiding recursion in before business rules when setting field values.

Answer

Use current.update() with a query to avoid recursion.

Answer

Add a condition to check if the risk field is already set.

Answer

Set the business rule to run after instead of before.

Question 2

A user reports that they are unable to see any records in the 'incident' table, even though they have the itil role. The administrator checks the ACLs and finds that there are no read ACLs defined for the incident table. What will happen?

Accepted Answer

No users can read any incident records.. In ServiceNow, if no read ACLs are defined for a table, the system defaults to a 'deny all' behavior. This means that no users, including those with the itil role, can read any records in the incident table. The itil role grants access to incident records only when a read ACL explicitly allows it; without any read ACL, the implicit denial takes effect.

Answer

The system will create a default read ACL that grants access to the itil role.

Answer

All users can read all incident records.

Answer

Only users with the admin role can read incident records.

Question 3

A catalog client script is supposed to show a variable when another variable equals 'Yes'. The script runs on 'onChange' of the first variable. However, the second variable does not appear. What is a possible cause?

Accepted Answer

The client script is not set to 'All' catalog items.. Option B is correct because a client script that is not set to run on 'All' catalog items will only execute on the specific catalog item it was created for. If the script is scoped to a different item, the onChange event for the first variable on the current item will not trigger the script, so the second variable will never be shown. In ServiceNow, catalog client scripts must be explicitly associated with the correct catalog item or set to 'All' to apply globally.

Answer

The g_form.setDisplay() method is used incorrectly.

Answer

The condition is written with 'g_form.getValue' for the wrong variable.

Answer

The script is set to 'onLoad' instead of 'onChange'.

Question 4

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?

Accepted Answer

A scheduled job from the Discovery application marked CIs as unverified.. 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.

Answer

The IRE was reconfigured during upgrade.

Answer

The CMDB Data Manager job ran with incorrect parameters.

Answer

The identification and reconciliation rules were updated.

Question 5

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

Accepted Answer

It can be used to restrict access to CI records based on user criteria.. 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.

Answer

It can be applied to individual CI fields.

Answer

It is configured in the Data Segmentation module under System Security.

Answer

It requires the subscription of a separate CMDB product license.

Question 6

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?

Accepted Answer

The class is marked as 'abstract'.. 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.

Answer

The class is retired.

Answer

The class has no parent.

Answer

The class has a missing table extension.

Question 7

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?

Accepted Answer

Use the Database Views module to create a view with join conditions.. 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.

Answer

Use the CMDB Explorer to merge CI classes.

Answer

Write a custom script to join tables and store results in a new table.

Answer

Create a report and save it as a view.

Question 8

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

Accepted Answer

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

Answer

sys_user

Answer

sys_ci

Answer

sys_metadata

Question 9

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?

Accepted Answer

Check the sys_audit table for delete records.. 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.

Answer

Query the sys_archive table.

Answer

Use the CMDB Rollback feature.

Answer

Restore from backup.

Question 10

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?

Accepted Answer

Add an index on the fields used in the encoded query conditions.. 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.

Answer

Create a database view on the cmdb_ci table and query the view instead.

Answer

Convert the glide query to a direct database query using System SQL.

Answer

Add an index on the sys_created_on field.

Question 11

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

Accepted Answer

Add an index on the task table's cmdb_ci field.. 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.

Answer

Increase the database connection pool size.

Answer

Replace the JOIN with a glide query using query().

Answer

Use a glide aggregate query to reduce data returned.

Question 12

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?

Accepted Answer

A new CI will be created because the business_service is different.. 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.

Answer

The discovery will fail and not create or update any CI.

Answer

The existing CI will be updated with the new business_service.

Answer

The identification rule will match based on name only, ignoring business_service.

Question 13

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

Accepted Answer

To indicate the CI's current operational health.. 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.

Answer

To track the CI's maintenance schedule.

Answer

To define the CI's business criticality.

Answer

To record the CI's last discovery date.

Question 14

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

Accepted Answer

Reconcile only. 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.

Answer

Fuzzy match

Answer

Update only

Question 15

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?

Accepted Answer

The join is defined as an INNER JOIN, excluding servers without a matching OS record.. 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.

Answer

The view is missing a required field.

Answer

The view is not refreshed.

Answer

The server's OS field is null.