SNOW-CAD Practice Test 9 — 10 Questions

Question 1

Which THREE factors should be considered when designing a Business Rule for optimal performance? (Select THREE)

Accepted Answer

Limit the use of gs.log() statements in production.. Excessive gs.log() statements in production can degrade performance by writing to the system log, which consumes I/O resources and can fill up the database. In ServiceNow, logging should be minimized or removed in production scripts to avoid unnecessary overhead, especially in high-volume Business Rules.

Answer

Avoid using synchronous GlideAjax calls.

Answer

Set the Business Rule to run on 'before' if possible.

Question 2

Match each ServiceNow scripting API to its function.

Accepted Answer

GlideRecord: Perform CRUD operations on database tables. The correct matches are: GlideRecord for CRUD operations, GlideSystem for system properties/IDs, and GlideAggregate for aggregate calculations. Common confusions involve swapping the functions of GlideAggregate, GlideDateTime, and GlideUser.

Answer

GlideRecord: Used to perform aggregate calculations

Answer

GlideSystem: Used to manipulate date and time values

Answer

GlideAggregate: Used to access user session information

Question 3

A developer needs to invoke a third-party SOAP web service from a business rule. The WSDL is imported and the SOAP message is created. What is the correct way to send the request?

Accepted Answer

Create a SOAPMessage object and use the send() method.. The SOAPMessage object, part of the javax.xml.soap API, provides a send() method that handles the entire SOAP request-response cycle over HTTP. This method automatically marshals the SOAP message, sends it to the endpoint defined in the WSDL, and returns the response as a SOAPMessage object, making it the appropriate choice for invoking a SOAP web service from a business rule.

Answer

Use the XMLDocument object to parse the response only.

Answer

Use a GlideRecord insert to write the SOAP envelope to a table.

Answer

Use the RESTMessageV2 object to send the request as a POST.

Question 4

A developer is building a flow in Flow Designer as part of a scoped application. The flow needs to trigger when a record is created in a specific table. Which trigger should be used?

Accepted Answer

'Record Created' trigger with a condition. The 'Record Created' trigger fires when a new record is created in a specified table, which matches the requirement. Option B is incorrect because an 'Event' trigger requires a custom event to be published, not a record creation. Option C is incorrect because 'Application Record Created' is not a standard trigger in Flow Designer; the correct trigger for record creation is 'Record Created'. Option D is incorrect because 'Scheduled' triggers are time-based and are not triggered by record creation.

Answer

'Event' trigger

Answer

'Application Record Created' trigger

Answer

'Scheduled' trigger

Question 5

A developer needs to create a new application scope. Which of the following is a best practice when defining the scope?

Accepted Answer

Set the application's access level to 'Protected' to prevent other applications from modifying its records.. When defining a new application scope, setting the application's access level to 'Protected' is considered a best practice. This restricts access to the application's resources, preventing other applications from modifying its records. The scope name should be unique and not changed after creation. Using the global scope (B) should be avoided for custom applications, reusing an existing scope name (C) is not allowed, and changing the scope name after creation (D) can cause configuration issues.

Answer

Use the global scope to avoid access restrictions.

Answer

Use a scope name that is already in use to leverage existing configurations.

Answer

Create the scope and later change the name if needed.

Question 6

A script include is defined as a public static function and is called from multiple business rules. After an upgrade, some business rules start failing with 'undefined' errors. What is the most likely cause?

Accepted Answer

The script include's function signature changed.. If the function signature changed (e.g., parameters or return type), existing calls to the script include would fail with 'undefined' errors. Option A would cause 'not found' errors, not undefined. Option B: ACLs do not affect server-side execution. Option D: scope change could cause access errors or 'not found', not typically 'undefined'.

Answer

The script include was made private.

Answer

The script include's ACLs changed.

Answer

The script include's scope changed.

Question 7

A developer is creating a new custom table for tracking software licenses. The table must inherit the core fields (sys_id, sys_created_by, etc.) and support extensibility for future sub-tables. Which base table should be used?

Accepted Answer

Create a new table that extends directly from sys_db_object. None of the provided options are correct. For a custom table that needs to inherit core system fields (sys_id, sys_created_by, etc.) and support future extensibility, the table should extend from the **Base table** (sys_object). The Base table provides the fundamental record structure and is the recommended starting point for custom tables not tied to specific functionality like tasks or CIs. Extending from sys_db_object (a meta-table for table definitions), cmdb_ci, Task, or cloning Incident all introduce unnecessary overhead or are architecturally incorrect.

Answer

Use the Configuration Item (cmdb_ci) table as a base

Answer

Extend from the Task table

Answer

Clone the Incident table and remove unnecessary fields

Question 8

Refer to the exhibit. This script is placed in a business rule on the 'incident' table with the 'When to run' set to 'before' and 'Update' action. The incident table has an ACL that also prevents updates. The business rule runs and shows the error message but the record is still updated. What is the most likely cause?

Accepted Answer

The business rule condition is not met for this specific record.. The business rule condition is not met for this specific record. In a 'before' business rule, the script runs before the database operation. The setAbortAction(true) method should prevent the update. However, if the condition defined in the business rule (or a condition within the script) is not satisfied, the setAbortAction may not be called, allowing the update to proceed. The error message shown may come from a different part of the script (e.g., gs.addErrorMessage) that runs regardless, but the abort action is conditional. Option B is incorrect because setAbortAction works on existing records, not new ones; the exhibit likely shows an update. Option C is incorrect because ACLs do not override setAbortAction; setAbortAction is a server-side abort that prevents the database operation. Option D is incorrect because 'after' business rules cannot abort the operation; 'before' is correct for aborting.

Answer

The setAbortAction method is being called on a new record.

Answer

The ACL is overriding the business rule's setAbortAction.

Answer

The business rule should be set to 'after' instead of 'before'.

Question 9

A developer wants to restrict access to a specific record in the incident table so that only members of the 'ITIL' group can read it. Which type of ACL should be created?

Accepted Answer

Create a record-level ACL with a condition that checks group membership.. A record-level ACL with a condition that checks group membership is the correct approach because it controls read access to the entire record based on the user's group membership. In ServiceNow, record-level ACLs evaluate conditions against the user's session and the record's data, and if the condition (e.g., 'member of ITIL group') is false, the record is hidden from the user entirely. This directly meets the requirement to restrict read access to a specific incident record for only the 'ITIL' group.

Answer

Create a field-level ACL on the sys_id field.

Answer

Create a business rule to delete the record for unauthorized users.

Answer

Create a UI policy to hide the record.

Question 10

A developer is writing a scripted REST API endpoint that returns a list of users. The requirement is to return only users who are in the 'IT' department and have a role of 'itil' or 'admin'. The endpoint uses GlideRecord. Which query condition is most efficient?

Accepted Answer

gr.addQuery('department', 'IT'); gr.addQuery('role', 'itil'); gr.addOrCondition('role', 'admin');. It uses addQuery('department', 'IT') to filter by department, then addQuery('role', 'itil') and addOrCondition('role', 'admin') to create an OR condition for roles. This ensures only users in the IT department with either the itil or admin role are returned efficiently using GlideRecord's built-in OR logic. Option B is wrong because it only returns users with both department IT and role itil, missing those with role admin. Option C is wrong because it's inefficient to query all IT department users then iterate to check role in script; better to use an encoded query or OR condition directly. Option D is wrong because passing 'itil,admin' as a single string would be interpreted as a literal value, not an OR condition; GlideRecord would look for users whose role field equals exactly 'itil,admin', which is incorrect.

Answer

gr.addQuery('department', 'IT'); gr.addQuery('role', 'itil');

Answer

gr.addQuery('department', 'IT'); gr.query(); then iterate and check role.

Answer

gr.addQuery('department', 'IT'); gr.addQuery('role', 'itil,admin');