SNOW-CAD Exam Simulation 1 — 100 Questions

Question 1

A business rule on the Incident table should send an email notification when the state changes to 'Resolved'. Which two conditions should be checked in the business rule script? (Choose two.)

Accepted Answer

current.state.changesTo('Resolved'). The `changesTo()` method in GlideRecord checks if the specified field has changed to a specific value during the current transaction. This is the precise way to detect a state transition to 'Resolved'. Option C is also correct because it adds the `current.operation() == 'update'` condition, which ensures the business rule only fires on update operations, preventing false triggers on insert or delete. Together, these two conditions guarantee the email is sent only when an existing record's state is updated to 'Resolved'.

Answer

current.state == 'Resolved'

Answer

current.state.changes()

Answer

current.state.changesFrom() != 'Resolved'

Question 2

What happens when a user changes the state from '2' to '1' on an incident record?

Accepted Answer

The record is not saved and an error message 'State change is not allowed' is displayed.. In a 'before' business rule, calling `current.setAbortAction(true)` prevents the database operation from completing and displays the error message specified in `gs.addErrorMessage()`. When the state changes from '2' to '1', the script checks for this condition and aborts the save, showing 'State change is not allowed'. This is a standard pattern for enforcing state transition restrictions in ServiceNow.

Answer

Nothing happens because the script does not have a return statement.

Answer

The record is saved without any message because setAbortAction is ignored in 'before' rules.

Answer

The record is saved and a message 'State change is not allowed' is shown.

Question 3

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 4

A company needs to automatically update the 'Assignment group' field on the Change Request table to 'Change Management' when the 'Category' field is set to 'Network'. Which type of business rule should be used?

Accepted Answer

Before business rule. A Before business rule (Option D) is correct because it runs before the record is saved to the database, allowing you to set the 'Assignment group' field value based on the 'Category' field before the insert or update operation completes. This ensures the assignment group is correctly populated in the same database transaction, avoiding the need for a separate update.

Answer

Display business rule

Answer

Async business rule

Answer

After business rule

Question 5

The Business Rule above runs on the 'incident' table. It is set to run 'before' update. What is the most likely issue with this script?

Accepted Answer

The script will cause a recursive loop because it updates incident records within a Business Rule that runs on the same table.. Updating the same table (incident) within a 'before update' Business Rule that runs on that table creates a recursive loop. Each time the script calls gr.update() on an incident record, it triggers the same Business Rule again, leading to infinite recursion until the system enforces a governor limit or stack overflow. ServiceNow detects and prevents such loops by throwing an error, but the design is fundamentally flawed.

Answer

The script should use 'current' instead of 'gr' to update records.

Answer

The script has a syntax error: missing semicolon after the while loop.

Answer

The script does not commit the changes because it uses 'gr.update()' instead of 'current.update()'.

Question 6

Drag and drop the steps to create a new table in ServiceNow into the correct order.

Accepted Answer

Navigate to System Definition > Tables, then click New, then define table properties (label, name, etc.), then set attributes (extends, access, etc.), then submit.. The order is: navigate to tables, click new, define table properties, set attributes, then submit.

Answer

Navigate to System Definition > Tables, then click New, then set attributes (extends, access, etc.), then define table properties (label, name, etc.), then submit.

Answer

Navigate to System Definition > Tables, then define table properties (label, name, etc.), then click New, then set attributes, then submit.

Answer

Navigate to System Definition > Tables, then click New, then define table properties, then submit, then set attributes.

Question 7

A developer needs to create a service catalog variable that allows the user to select multiple values from a predefined list. Which variable type should be used?

Accepted Answer

Multiple Choice (Checkbox). The Multiple Choice (Checkbox) variable type in ServiceNow allows users to select multiple values from a predefined list. This is the only variable type that supports multi-select behavior, which is required when a user needs to choose more than one option from a set of choices.

Answer

Single Line Text

Answer

Radio Button

Answer

Select Box

Question 8

Which TWO of the following are valid ways to create a Business Rule? (Choose two.)

Accepted Answer

Navigate to 'System Definition > Business Rules' and click 'New'.. Navigating to 'System Definition > Business Rules' and clicking 'New' is the standard module-based method for creating a Business Rule in ServiceNow. This path directly accesses the Business Rule table (sys_script) and opens a new record form, which is a valid and documented approach.

Answer

From the Business Rules list, right-click and select 'New'.

Answer

Type 'business_rule.do' in the navigator filter.

Answer

Create a Client Script and convert it to a Business Rule.

Question 9

Refer to the exhibit. The script runs as a business rule on the incident table. What will happen when this script executes?

Accepted Answer

The update will trigger other business rules that run on update.. The script uses `setValue()` to update a field on the current record, which is an update operation. In ServiceNow, business rules that run on 'update' will fire when a record is updated, unless the business rule is specifically configured to run 'asynchronously' or with the 'Don't run other business rules' option. Since the exhibit does not show such configuration, the update will trigger other business rules that run on update.

Answer

The update will only occur if the business rule condition evaluates to true.

Answer

The record will be updated without triggering any other business rules.

Answer

The script will throw an error because setValue() requires a third parameter.

Question 10

Refer to the exhibit. A developer runs this script and notices it only returns 10 incidents even though there are more than 10 active priority 1 incidents. What is the reason?

Accepted Answer

The setLimit(10) method limits the number of records returned.. The script uses the setLimit(10) method, which restricts the GlideRecord query to return only 10 records, even though there are more matching records. Option A is incorrect because the script does not limit by session. Option B is incorrect because there is no filter for created today. Option C is incorrect because the issue is about the limit, not joins.

Answer

The script only gets incidents from the current session.

Answer

The script only retrieves incidents created today.

Answer

The incident table is not joined with any other table.

Question 11

A developer is creating a business rule to automatically assign tasks to a specific group based on the category. The rule is set to run before insert and update on the Task table. The script uses current.assignment_group = 'IT Support'. However, the assignment group is not being set on update even though it works on insert. Which three potential causes should the developer investigate? (Choose three.)

Accepted Answer

The business rule's condition field requires the category to be set. Option A: If the business rule's condition depends on the category field, and the category isn't changed on update, the rule may not run, preventing assignment group update. Option C: If the script only runs on insert but not update, it won't execute on updates. Option E: Another business rule acting after this one could reset the assignment group. Option B: The assignment group being read-only on the form does not stop business rules from setting its value; this is not a cause. Option D: Running only in the global scope does not affect whether the rule runs on update; scope is not a cause.

Answer

The assignment group field is read-only on the form but can be set via business rule

Answer

The business rule is set to run only in the global scope

Question 12

A developer needs to create a new table to store custom survey responses. The table should have a field to store the survey name and a field to store the response text. The developer wants to ensure that the table is available in the 'Surveys' application module. Which property must be set on the table?

Accepted Answer

Application module. The Application module property determines which application module a table belongs to, making it visible and accessible within that module's scope. Setting this to 'Surveys' ensures the table appears in the Surveys application module, as required by the developer.

Answer

Application scope

Answer

Table name

Answer

Table label

Question 13

A ServiceNow instance is configured with a custom table 'u_asset_history' that stores historical records for asset changes. This table has a reference field 'u_asset' pointing to the 'alm_asset' table, and a date field 'u_change_date'. The application uses a business rule that runs on 'alm_asset' after update, querying the 'u_asset_history' table to find the most recent change for that asset. The business rule is declared as 'async' to improve performance. However, recently the async business rule has been failing frequently with an 'async queue limit reached' error. The instance has default configuration for transaction quotas. The team suspects that the async queue is getting overloaded because many asset updates are happening simultaneously. Which action should the administrator take to resolve this issue while minimizing impact on other processes?

Accepted Answer

Increase the system property 'glide.scope.async.quota' to allow more async transactions.. The error 'async queue limit reached' indicates that the instance's asynchronous transaction queue is full, which is a quota issue. Increasing the system property 'glide.scope.async.quota' raises the maximum number of concurrent asynchronous transactions allowed, directly addressing the overload without changing the business logic or impacting other processes. This is the correct approach because the business rule is already optimized to run asynchronously for performance, and the root cause is a capacity limit, not a query or design flaw.

Answer

Add an index on the 'u_asset' and 'u_change_date' fields in the 'u_asset_history' table to optimize the query.

Answer

Rewrite the business rule to run synchronously with a background script to avoid async queue limits.

Answer

Disable the business rule and implement a scheduled job to perform the same logic during off-peak hours.

Question 14

A developer is testing a REST API call to retrieve active users with the ITIL role created since last month. The response returns an error. What is the most likely cause?

Accepted Answer

The query parameter sysparm_query uses a script which is not allowed in REST API calls.. The error occurs because the sysparm_query parameter in a REST API call to the /api/now/table/sys_user endpoint does not support scripts; it only accepts encoded query strings using operators like '=', '^', 'STARTSWITH', etc. Using a script in sysparm_query violates the REST API specification, which expects a simple query string, not executable code, leading to a bad request error.

Answer

The Accept header should be application/xml.

Answer

The endpoint should be /api/now/table/sys_user_list.

Answer

The query should use sysparm_fields instead of sysparm_query.

Question 15

A flow designer wants to send an email notification with a custom logo. They need to ensure the email template references the correct image. What is the best practice?

Accepted Answer

Attach the image to the sys_attachment table and use the sys_id in the template.. Attaching the image to a sys_attachment and using the sys_id reference ensures it persists across upgrades and is the recommended approach.

Answer

Reference the image from an external CDN using a URL.

Answer

Upload the image directly into the email template using base64 encoding.

Answer

Store the image in the 'images' table and use the image name.

Question 16

A ServiceNow administrator is configuring Single Sign-On (SSO) using SAML 2.0 with a corporate identity provider. Users report that after authenticating, they are redirected back to ServiceNow but see an error: 'Unable to process SAML response. Invalid user.' The administrator checks the SSO log and sees the message: 'No user found with username: [user@company.com]'. The username format in the SAML assertion is userPrincipalName (e.g., user@company.com). ServiceNow user records use the 'User ID' field (e.g., 'user'). What configuration change should the administrator make to resolve this issue?

Accepted Answer

Set the 'User Field' property to 'User ID' in the SAML2 configuration to match users based on their User ID. The SAML assertion contains the userPrincipalName (user@company.com), but ServiceNow's default user matching field is the 'User ID' field, which stores only the username (e.g., 'user'). By setting the 'User Field' property to 'User ID' in the SAML2 configuration, ServiceNow will extract the username portion from the NameID (or a custom attribute) and match it against the 'User ID' field, resolving the mismatch. This avoids the need to change user records or the NameID format.

Answer

Change the 'NameID format' from 'Unspecified' to 'EmailAddress' in the SAML2 configuration

Answer

Create an LDAP integration to automatically create ServiceNow users from the identity provider

Answer

Update all ServiceNow user records to have the 'User ID' field populated as full email addresses

Question 17

A developer is debugging an issue where a Script Action in a Flow Designer flow is not triggering. The flow is configured to run when a record is created or updated in the incident table. The Script Action is supposed to set a field based on a condition, but it never executes. What should the developer check first?

Accepted Answer

Check the flow's trigger conditions to ensure they match the record update.. The most common reason a Script Action fails to trigger is that the flow's trigger conditions do not match the record update event. Flow Designer evaluates trigger conditions before any actions execute; if the conditions are misconfigured (e.g., expecting a specific field change that isn't occurring), the entire flow, including the Script Action, will not run. The developer should first verify that the trigger conditions align with the actual record creation or update scenario.

Answer

Check if the flow is published.

Answer

Check if the script include used in the Script Action is accessible.

Answer

Check if the Script Action script has syntax errors.

Question 18

A developer needs to count the number of records in the 'task' table that have been updated since the last import. Which GlideAggregate method is correct?

Accepted Answer

gr.addAggregate('COUNT', 'sys_id'). `addAggregate('COUNT', 'sys_id')` counts all records in the table, as `sys_id` is always present and unique. Option B is wrong because using `'number'` as the field would only count records where the `number` field is not null, potentially undercounting if any records have a null number. Option C is wrong because `addAggregate('COUNT')` omits the required field name, causing an error. Option D is wrong because `'count'` (lowercase) is not a valid aggregate function; the function name must be uppercase, e.g., `'COUNT'`.

Answer

gr.addAggregate('COUNT', 'number')

Answer

gr.addAggregate('COUNT')

Answer

gr.addAggregate('count')

Question 19

What is the most likely cause of this error?

Accepted Answer

The access token has expired or is invalid. A 401 Unauthorized error with Bearer authentication typically means the access token is invalid or expired. Therefore, option B is correct. Option A (timeout) would produce a different error (e.g., 504 Gateway Timeout). Option C (incorrect endpoint URL) would likely result in a 404 Not Found. Option D (missing Content-Type header) might cause a 400 Bad Request, not a 401.

Answer

The request timed out

Answer

The endpoint URL is incorrect

Answer

The Content-Type header is missing

Question 20

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.