SNOW-CAD Practice Test 17 — 15 Questions

Question 1

A team is using a SOAP web service integration. The response contains namespaced XML, and the script that parses it is not extracting values correctly. What is the most likely issue?

Accepted Answer

Missing or incorrect namespace prefix handling in the script. When parsing namespaced XML from a SOAP response, the script must correctly handle namespace prefixes and URIs. If the script ignores or misuses the namespace declarations (e.g., using getElementsByTagName without namespace awareness), it will fail to extract the intended values. The other options relate to connectivity or versioning, which would typically cause different errors (e.g., connection failures or SOAP faults), not silent extraction failures.

Answer

WSDL caching prevents updated endpoint

Answer

SOAP version mismatch between request and response

Answer

HTTP timeout during response retrieval

Question 2

An administrator wants to enable inbound email integration to automatically create incidents from emails sent to support@company.com. What is the first step in configuring this?

Accepted Answer

Configure an email account (mailbox) to receive emails.. The first step in configuring inbound email integration is to set up an email account (mailbox) that the instance can connect to and retrieve emails from. Without a configured mailbox, the instance has no source from which to pull incoming messages, making subsequent steps like creating inbound email actions or enabling plugins meaningless. This mailbox configuration defines the IMAP or POP3 server, credentials, and folder settings that the platform uses to poll for new emails.

Answer

Enable the Email Integration plugin.

Answer

Create an inbound email action.

Answer

Create an ACL to allow email processing.

Question 3

A Service Portal widget is not updating data on the page after the user clicks a button that calls a server-side function. The client controller uses $scope.server.get() to call the server. The server script updates a global variable in glideRecord and returns it. However, the widget view does not reflect the change. What is the most likely issue?

Accepted Answer

The client controller is not handling the promise returned by $scope.server.get(); the scope update should be inside the success callback.. `$scope.server.get()` returns a promise, and the scope variables must be updated inside the `.then()` success callback to ensure the changes are applied after the asynchronous server response is received. Without handling the promise, the client controller executes the next line immediately, and the scope update happens before the server data is available, so the widget view never reflects the change.

Answer

The widget template is not bound to the correct scope variable.

Answer

The client controller should use $scope.server.update() instead of $scope.server.get().

Answer

The server script is not allowed to modify data from a widget server script.

Question 4

A developer is designing a UI Policy that should run client-side but references a complex server-side calculation. Which approach is best?

Accepted Answer

Use a client script with GlideAjax.. The correct approach is to use a client script with GlideAjax (Option B) because UI Policies run client-side and cannot directly perform complex server-side calculations. GlideAjax allows asynchronous calls to a server-side script include, enabling the client script to retrieve the result of a complex server-side calculation without a page refresh. Option A is incorrect because Business Rules run server-side and cannot be called directly from a UI Policy; they are triggered by database operations. Option C is incorrect because UI Macros are used for reusable UI components, not for server-side logic. Option D is incorrect because UI Policy condition strings are limited to simple client-side expressions and cannot execute complex server-side calculations.

Answer

Create a Business Rule and call it from UI Policy.

Answer

Use a UI Macro.

Answer

Use a UI Policy condition string.

Question 5

A developer builds an application in Studio and wants to ensure all changes are captured in an update set. What is true?

Accepted Answer

Studio automatically creates an update set for the application scope when the application is created.. Studio automatically creates an update set for the application scope when the application is created. Option A is incorrect because the developer does not need to manually set the 'Update Set' field on each record; Studio automatically associates changes with the scope's update set. Option C is incorrect because update sets are used for scoped applications; each application scope has its own update set. Option D is incorrect because Studio automatically creates and assigns the update set; manual creation is not required.

Answer

The developer needs to set the 'Update Set' field on each record to 'Default Update Set'.

Answer

Update sets are not used for scoped applications; only for global scope.

Answer

The developer must manually create a new update set and assign it to the application scope.

Question 6

A ServiceNow instance is being integrated with an external HR system using a SOAP message. The SOAP call is failing intermittently. The developer notices that the XML payload contains special characters like '&' and '<'. What is the best practice to handle these characters in SOAP messages?

Accepted Answer

Escape the characters using XML entities (e.g., & for &).. SOAP messages are XML-based, and special characters like '&' and '<' must be escaped using XML entities (e.g., & for &, < for <) to maintain valid XML syntax. This ensures the XML parser correctly interprets the payload without breaking the message structure, which is the standard practice per the XML specification and SOAP protocol.

Answer

Wrap the payload in a CDATA section.

Answer

Encode the entire payload in Base64.

Answer

Use URL encoding for the payload.

Question 7

A business rule runs on 'before' and 'update' for the incident table. The rule sets the short_description to 'Test' only when the state changes to 'In Progress'. However, the short_description is being updated even when the state does not change. What is the most likely cause?

Accepted Answer

The business rule does not have an 'if (current.state.changes())' condition.. The business rule lacks an 'if (current.state.changes())' condition. Without this check, the script runs on every update, setting the short_description to 'Test' regardless of whether the state field actually changed. The 'before' and 'update' triggers ensure the rule executes on every update, but the conditional logic must explicitly verify the state transition.

Answer

The business rule is set to run globally.

Answer

The business rule script modifies the field directly without checking.

Answer

The business rule is using the 'cancel' action.

Question 8

During development, a developer creates a new application module and adds a table 'x_abc_incident' with a reference field to the 'sys_user' table. The developer wants to ensure that when a user is deleted, all related incident records are also deleted. What database constraint should be configured on the reference field?

Accepted Answer

Cascade delete. A cascade delete constraint ensures that when a record in the parent table (sys_user) is deleted, all child records in the referencing table (x_abc_incident) that have a foreign key pointing to that parent are automatically deleted. In ServiceNow, this is configured on the reference field's 'Delete constraint' property by selecting 'Cascade delete', which enforces referential integrity at the database level.

Answer

No action

Answer

Restrict delete

Answer

Set null on delete

Question 9

An organization has a custom table 'u_incident_task' that extends 'task'. They need to allow users to create records in this table from the 'Incidents' module. The 'u_incident_task' table should appear as a related list on the incident form. However, the related list is not showing the 'New' button. What is the most likely cause?

Accepted Answer

There is no reference field on 'u_incident_task' pointing to the incident table. The 'New' button appears on a related list only when there is a reference field on the target table (u_incident_task) that points back to the source table (incident). Without this reference field, the platform cannot automatically populate the parent record's sys_id when creating a new child record, so it suppresses the 'New' button. This is a core requirement for related list creation in ServiceNow.

Answer

The table is in a different application scope

Answer

The table does not extend 'incident'

Answer

The user does not have the required role

Question 10

After importing an update set from another instance, a scoped application shows multiple conflicts in Studio. What is the best first step to resolve?

Accepted Answer

Review each conflict and choose the correct version.. Reviewing each conflict and choosing the correct version allows the developer to selectively merge changes, preserving important modifications while discarding unwanted ones. Option A is wrong because deleting and re-importing disregards the resolution of conflicts and may lose customizations. Option C is wrong because discarding all local changes removes any work done locally without consideration. Option D is wrong because accepting all remote changes may overwrite intentional local customizations.

Answer

Delete the application and re-import.

Answer

Discard all local changes.

Answer

Accept all remote changes.

Question 11

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 12

When building a custom application using ServiceNow Studio, which of the following is NOT a recommended practice for version control?

Accepted Answer

Directly edit system tables outside of the application scope.. Directly editing system tables outside of the application scope is not a recommended version control practice because it bypasses the scoped application's change tracking, making it impossible to reliably capture, promote, or roll back those changes. ServiceNow Studio and scoped applications are designed to encapsulate customizations so they can be versioned, published, and moved between instances via update sets or application versions. Editing global system tables outside scope breaks that isolation and versioning model.

Answer

Create a new application version for each major release.

Answer

Track changes using update sets.

Answer

Use application scope to isolate changes.

Question 13

A custom table 'u_asset' stores asset data. The developer wants to add a field that calculates the depreciation value based on acquisition date and cost. Which field type should be used?

Accepted Answer

Calculated. A Calculated field type in ServiceNow computes its value dynamically from other fields using a calculation script or formula, which is exactly what is needed to derive depreciation from acquisition date and cost. Calculated fields are read-only and recalculate on display or on record update depending on configuration. This makes them ideal for derived values like depreciation.

Answer

Lookup select

Answer

Currency

Answer

Condition string

Question 14

Which TWO statements about ServiceNow UI Policies are true?

Accepted Answer

UI Policies can set fields as mandatory. UI Policies are client-side scripts that run on the browser to dynamically control form behavior, such as making fields mandatory, visible, or read-only based on conditions. Option B is correct because UI Policies can set the 'mandatory' attribute on a field, forcing users to provide a value before submitting the record.

Answer

UI Policies can enforce data integrity at the database level

Answer

UI Policies cannot be used on catalog items

Answer

UI Policies run on the server side only

Question 15

A large enterprise runs a ServiceNow instance with a heavily customized Task table. The 'Task' table has been extended to create 'u_WorkOrder', which is used by over 50,000 active records. Recently, users complain that when they open a WorkOrder record, the form takes more than 10 seconds to load. On investigation, you discover that the 'u_WorkOrder' table has 150 fields, many of which are UI policies and client scripts that trigger on load. Additionally, there is a business rule that runs 'after query' and dot-walks through multiple related tables (e.g., calling 'current.assigned_to.department.manager.email' in a loop for each record). The instance uses SQL Server as its database. Which action would most effectively reduce the form load time without losing required functionality?

Accepted Answer

Rewrite the after query business rule to use GlideAggregate or avoid dot-walking in loops, and consider caching the dot-walked data. The 10-second form load is dominated by the after-query business rule that dot-walks through related tables for each record, causing N+1 query patterns and repeated database round-trips. Rewriting it to use GlideAggregate (which performs set-based aggregation in a single query) or to avoid dot-walking in loops, plus caching the resolved data, eliminates the redundant queries while preserving functionality. This directly targets the root cause.

Answer

Change the order of the business rule to 100 so that it runs after other rules

Answer

Remove 50 of the 150 fields from the table to reduce data retrieval

Answer

Convert the after query business rule to an after update business rule