SNOW-CAD Practice Test 8 — 10 Questions

Question 1

A developer wants to trigger a Business Rule on a child table when a parent record is updated. How can this be achieved?

Accepted Answer

Add a condition on the child table's Business Rule referencing the parent.. A Business Rule on the child table can include a condition that checks whether a related parent record has been updated. This is done by referencing the parent table's fields via dot-walking (e.g., `current.parent_field.changes()`) or by querying the parent record's sys_updated_on field. The Business Rule runs on the child table when a child record is inserted or updated, and the condition evaluates the parent's state, allowing the rule to trigger logic based on parent changes without requiring a direct trigger on the parent table.

Answer

Use a workaround with a scheduled job.

Answer

This is not possible in ServiceNow.

Answer

Use a before query Business Rule on the child table.

Question 2

A report on the 'incident' table shows duplicate counts due to the 'active' field being true for some records that shouldn't be counted. The report is using a simple count. How can the admin ensure only active incidents are counted?

Accepted Answer

Add a filter condition: 'active = true'.. Adding a filter condition 'active = true' in the report configuration ensures that only incidents where the active field is true are counted, eliminating duplicate counts from inactive records. Option B is incorrect because a business rule would modify data rather than filter the report. Option C is incorrect because removing the active field from the report does not filter records; it only hides the field display. Option D is incorrect because grouping by active field would separate counts by active status but still count all records including inactive ones.

Answer

Create a business rule to set active=false for certain records.

Answer

Remove the 'active' field from the report.

Answer

Group the report by the 'active' field.

Question 3

A business rule on the Task table uses 'current.assignment_group' in a condition. After cloning the application, the business rule fails with 'undefined' error for the assignment_group field. What is the most likely cause?

Accepted Answer

The field was renamed in the cloned instance.. Cloning an application copies the business rule as-is, but if the assignment_group field was renamed in the cloned instance (e.g., from 'assignment_group' to 'assignment_group_new'), the condition referencing 'current.assignment_group' will fail with an 'undefined' error. The business rule still runs, but the field name no longer matches the database column, causing the script to reference a non-existent property on the GlideRecord object.

Answer

The assignment_group field does not exist on the Task table.

Answer

The script include that defines the field is missing.

Answer

The clone process incorrectly copies business rules.

Question 4

A ServiceNow instance integrates with an external inventory system via a scheduled REST import job. Recently, the import started failing intermittently with HTTP 429 (Too Many Requests) errors. The external system enforces a rate limit of 100 requests per minute. The existing job pulls 1500 records at a time using a single REST message. Which design change would best resolve this issue while ensuring the import completes successfully?

Accepted Answer

Reduce the batch size to 50 records and add a 1-second delay between consecutive REST calls. Reducing the batch size to 50 records ensures that each REST call stays within the external system's rate limit of 100 requests per minute. Adding a 1-second delay between consecutive calls further prevents bursts that could trigger HTTP 429 errors, while still allowing the import to complete by making multiple smaller requests over time.

Answer

Increase the number of threads in the import set table loader to process records faster

Answer

Increase the batch size to 5000 records per request to reduce the number of calls

Answer

Switch the REST message to use Basic Authentication instead of OAuth to reduce overhead

Question 5

A ServiceNow administrator is responsible for setting up a custom table called 'u_incident_change' to track incidents that require a change request. Each 'u_incident_change' record must be linked to exactly one incident and one change request. The administrator creates two reference fields: 'incident_ref' pointing to the 'Incident' table, and 'change_ref' pointing to the 'Change Request' table. However, after deployment, users report that when they create a new 'u_incident_change' record from an incident form (using a related list), the 'incident_ref' field is automatically populated, but the 'change_ref' field is empty. The users want to be able to create a change request directly from that same form and have the reference automatically filled. What configuration should the administrator use to achieve this?

Accepted Answer

Create a UI Action labeled 'Create Change Request' on the incident form that runs a script to create a new 'u_incident_change' record with both references populated and then opens the change request form. A UI Action with a script creates the change request and sets the reference fields accordingly. Option B is wrong because referenced records don't auto-populate. Option C is wrong because business rules run on records, not UI. Option D is wrong because related lists don't create records with cross-reference.

Answer

Configure the related list to automatically create the 'u_incident_change' record with both references when a change request is added

Answer

Use a business rule on the 'u_incident_change' table that auto-populates the 'change_ref' when the record is created from a related list

Answer

Add a reference field on the Incident table that points to the 'u_incident_change' table

Question 6

A company uses a scheduled import from an external database to update the user table nightly. Recently, the import has been failing with a timeout error after 30 minutes. The import set contains 50,000 records. What should the administrator do to resolve this issue?

Accepted Answer

Split the import into multiple smaller batches.. The best course of action because splitting the import into smaller batches reduces the processing time per batch and avoids timeout, addressing the root cause.

Answer

Use a transform map to skip unnecessary fields.

Answer

Increase the timeout value in the scheduled import configuration.

Answer

Upgrade the instance to a larger size.

Question 7

A ServiceNow developer is working on a new application that requires a custom table to store project information. The table needs to have fields for project name, start date, end date, and project manager (reference to sys_user). The developer creates the table using the Application Creator and adds the fields. After creating the table, the developer wants to automatically generate a unique project ID in the format 'PROJ-00001' for each new record. The developer considers using a Business Rule with a script or a Default Value with a scripted function. Which approach would be the most efficient and maintainable for generating the project ID?

Accepted Answer

Create a Default Value for the project ID field using a script that calls a helper function.. A Default Value script runs before the record is saved, allowing the unique ID to be generated without an extra update. Using a helper function promotes reusability and maintainability, and the script can query the current count of records to generate the next sequential ID in the desired format.

Answer

Create an After Insert Business Rule that updates the project ID after the record is saved.

Answer

Create a Before Insert Business Rule that uses a script to query the current count of records and generate the next ID.

Answer

Create a calculated field that uses a scripted formula to generate the ID.

Question 8

A developer is building a custom application in ServiceNow Studio for IT asset management. The application includes a table 'Asset' with fields: asset_tag (string), serial_number (string), purchase_date (date), cost (currency), and status (choice: In Use, In Stock, Retired). The developer needs to create a business rule that automatically sets the status to 'Retired' when the cost is zero and the purchase_date is older than 5 years. The business rule should run before the record is saved to the database and should not prevent the save if conditions are not met. The developer writes the following business rule in Studio: Table: Asset, When: Before, Order: 100, Condition: current.cost == 0 && current.purchase_date < gs.yearsAgoStart(5). The script is: current.status = 'Retired'; However, the status is not being updated as expected. What is the most likely issue?

Accepted Answer

Replace gs.yearsAgoStart(5) with gs.yearsAgo(5) to get the exact date 5 years ago.. The issue is that `gs.yearsAgoStart(5)` returns the start of the year (January 1st) five years ago, not the exact date five years ago. This means a record with a purchase_date that is, for example, 5 years and 1 month old might still be after that start-of-year date and thus not match the condition. The correct method is `gs.yearsAgo(5)`, which returns the exact date and time five years ago, ensuring the comparison works as intended for any purchase_date older than 5 years.

Answer

Replace gs.yearsAgoStart(5) with gs.yearsAgoEnd(5) to get the end of the year 5 years ago.

Answer

Change the table from 'Asset' to 'Asset [new]' as the business rule may be on the wrong table.

Answer

Increase the order of the business rule to 200 to ensure it runs after other rules.

Question 9

Refer to the exhibit. A UI Policy is defined on the Incident table. When will the 'assigned_to' field be hidden?

Accepted Answer

When the incident state is 1.. The UI Policy in the exhibit is configured with a condition that hides the 'assigned_to' field when the 'state' field equals 1 (typically 'New'). UI Policies run client-side and evaluate the condition in real time; when the condition is true, the field is hidden. The exhibit shows the condition 'state = 1' with the 'Hidden' attribute checked, so the field is hidden only when the incident state is 1.

Answer

Never.

Answer

Always.

Answer

When the incident state is not 1.

Question 10

A ServiceNow instance has a custom table 'u_integration_log' that stores integration transactions. A flow in Flow Designer logs errors by creating records in this table. The flow is running with high volume, and the table is growing quickly causing performance issues. What is the best design to mitigate this?

Accepted Answer

Configure a scheduled job to archive and delete records older than 30 days.. It directly addresses the root cause of performance degradation—uncontrolled table growth—by implementing a scheduled job to archive and delete records older than 30 days. This reduces table size, improves query performance, and maintains the ability to retain recent logs for debugging. In ServiceNow, scheduled jobs can use GlideRecord to delete records based on a date condition, and archiving can be done via export to CSV or a separate archive table.

Answer

Disable error logging in the flow.

Answer

Use a 'Log to file' action in the flow instead of a table.

Answer

Store logs in a separate instance via MID Server.