Courseiva

ServiceNow Certified Application Developer CAD (SNOW-CAD) — Questions 451–481

481 questions total · 7pages · All types, answers revealed

Take a mock examExam hub
Page 6

Page 7 of 7

451
Matchingmedium

Match each ServiceNow feature to its primary service.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Automation

Self-service portal

Conversational AI chatbot

Reporting and dashboards

CMDB population and maintenance

Why these pairings

The correct matches are: Virtual Agent to AI Search, Performance Analytics to Performance Analytics, Service Catalog to Service Portal, and Knowledge Base to Knowledge Management. Common confusions include mixing Virtual Agent with Service Portal or associating Performance Analytics with Knowledge Management.

Full explanation →
452
MCQhard

A scheduled import brings in 50,000 records daily. Which approach is the MOST efficient for transforming these records?

A.Load all rows first, then run the transform as a batch process
B.Run the transform after each row is inserted into the staging table
C.Use a database view to transform data on the fly
D.Write directly to the target table using insert statements
AnswerA

Batch transform is the recommended pattern for large volumes.

Why this answer

Loading all rows into the staging table first and then running the transform as a batch process is the most efficient for 50,000 records because it minimizes overhead and leverages bulk processing. Option B is incorrect because transforming each row individually introduces significant per-record overhead. Option C is incorrect because database views are not designed for import transforms and may not support required mappings.

Option D is incorrect because direct insert statements bypass import set logic and transform rules.

Full explanation →
453
Multi-Selecteasy

Which TWO statements are true about ServiceNow Business Rules? (Select TWO)

Select 2 answers
A.Business Rules run on the client side.
B.Business Rules can be set to run on 'before' or 'after' the database operation.
C.Business Rules can only be triggered by updates to a record.
D.Business Rules are executed asynchronously by default.
E.Business Rules can be used to send email notifications.
AnswersB, E

Correct, they have a 'When to run' property.

Why this answer

Business Rules are server-side scripts that execute when a record is inserted, updated, deleted, or queried. They can be configured to run 'before' the database operation (to modify data before it is saved) or 'after' the operation (to perform additional actions like logging or notifications). This flexibility is a core feature of the ServiceNow platform.

Exam trap

The trap here is that candidates often confuse server-side Business Rules with client-side scripts, or assume they only run on updates, but the exam tests the precise trigger conditions and execution context.

Full explanation →
454
MCQmedium

An organization has a ServiceNow instance that integrates with an external HR system using a scheduled job that runs every hour. The job uses a REST message to fetch new hire records and creates user accounts in ServiceNow via a transform map. Recently, the number of new hires has increased significantly, and the job now takes over an hour to complete, causing the next job to start before the previous one finishes. The administrator notices that the transform map is using 'Coalesce' set to 'false' because the external system does not provide a unique identifier. The job also creates a large number of intermediate records that are later updated. The administrator wants to optimize the process to prevent overlapping job runs. Which course of action should the administrator take?

A.Increase the scheduled job's interval to run every 2 hours to avoid overlap
B.Set the 'Maximum rows to load' property on the transform map to a value that ensures the job finishes within 60 minutes
C.Change the transform map to run asynchronously using a flow triggered by the import set row
D.Configure the import set table loader to run in multiple parallel threads to process records faster
AnswerB

Limiting the rows per run controls the job duration, preventing overlap.

Why this answer

Setting the 'Maximum rows to load' property on the transform map limits the number of rows processed per run, ensuring the job completes within the 60-minute window. This prevents overlapping runs by capping the workload, allowing the scheduled job to finish before the next trigger, without requiring changes to the integration logic or external system.

Exam trap

The trap here is that candidates often assume increasing the interval or adding parallelism (Options A or D) will solve the overlap, but they overlook that without a unique identifier, parallel processing can cause duplicates, and simply delaying the job does not fix the underlying processing speed issue.

How to eliminate wrong answers

Option A is wrong because simply increasing the interval to 2 hours does not address the root cause of slow processing; the job would still take over an hour and could still overlap if the workload remains unconstrained, and it reduces data freshness. Option C is wrong because running the transform map asynchronously via a flow triggered by the import set row does not prevent overlapping job runs; it only decouples processing from the scheduled job, but the underlying bottleneck of processing large volumes without a unique identifier remains, and flows can still queue up and cause delays. Option D is wrong because configuring the import set table loader to run in multiple parallel threads can cause data integrity issues when 'Coalesce' is set to 'false' (no unique identifier), leading to duplicate records or race conditions, and it does not guarantee the job finishes within the hour.

Full explanation →
455
Multi-Selectmedium

Which TWO actions can be performed directly from ServiceNow Studio?

Select 2 answers
A.Configure email notifications.
B.Run a scheduled job.
C.Configure form layout.
D.Create a new table.
E.Define a workflow.
AnswersC, D

Correct. Form layout can be edited directly in Studio.

Why this answer

Options C and D are correct because ServiceNow Studio provides functionality to create new tables and configure form layouts. Option A is incorrect because configuring email notifications is done in the System Notifications module, not in Studio. Option B is incorrect because running scheduled jobs is managed in the Scheduled Jobs module.

Option E is incorrect because defining workflows is done in the Workflow Editor, not in Studio.

Full explanation →
456
MCQmedium

Refer to the exhibit. Which scenario most likely caused this error?

A.The Business Rule runs on delete and 'current' is null.
B.The Business Rule tries to access a field that doesn't exist.
C.The Business Rule uses 'previous.sys_id' but the record is new.
D.The Business Rule is not active.
AnswerC

On insert, previous is null.

Why this answer

When a Business Rule runs on 'insert' or 'update' and references 'previous.sys_id', the 'previous' object is null for new records (since there is no prior version). This causes a 'Cannot read property 'sys_id' of null' error. The error occurs specifically because the script attempts to access a property on an undefined object.

Exam trap

ServiceNow often tests the distinction between 'current' and 'previous' objects in Business Rules, and the trap here is that candidates may not realize 'previous' is null for new records, leading them to incorrectly assume the error is about a missing field or inactive rule.

How to eliminate wrong answers

Option A is wrong because if a Business Rule runs on delete and 'current' is null, the error would be about 'current' being null, not 'previous'. Option B is wrong because accessing a non-existent field typically throws a 'Field does not exist' error, not a null reference error on 'previous'. Option D is wrong because an inactive Business Rule simply does not execute, so it would not produce any error at all.

Full explanation →
457
Multi-Selectmedium

Which THREE best practices should a developer follow when designing a service portal widget? (Choose three.)

Select 3 answers
A.Define widget options for configuration
B.Avoid using the widget's server-side script for any logic
C.Use server-side scripts to fetch data
D.Use client-side scripts exclusively for data retrieval
E.Use the widget's 'Client Script' field sparingly and only for UI interactions
AnswersA, C, E

Options make widgets reusable and configurable without code changes.

Why this answer

Using server-side scripts for data, defining clear options, and following widget scope best practices ensure maintainable and performant widgets.

Full explanation →
458
MCQhard

A large enterprise uses ServiceNow for IT Service Management. They have a custom Service Portal for end-users to submit catalog requests. Recently, mobile users reported that the portal is extremely slow on their devices, while desktop users experience no issues. The portal theme uses many custom CSS animations and high-resolution images. Additionally, the widget client scripts are complex and make multiple GlideAjax calls on page load. The development team wants to optimize mobile performance without redesigning the entire portal. Evaluate the options and select the best course of action.

A.Increase server-side caching for widgets and use a CDN for static assets
B.Consolidate multiple GlideAjax calls into a single server-side script and use mobile-optimized images
C.Remove all custom CSS animations and replace high-res images with scalable vector graphics
D.Implement lazy loading for images and defer all GlideAjax calls until after page load
AnswerB

Reducing the number of server round trips and using lighter images directly improves mobile performance by decreasing network latency and rendering effort.

Why this answer

The best course of action because consolidating multiple GlideAjax calls into a single server-side script reduces the number of network round trips, which is critical for mobile performance where latency and bandwidth are limited. Using mobile-optimized images (smaller dimensions, compressed) directly reduces data transfer and rendering load. Option A (caching and CDN) helps but does not address the initial load issue or the multiple calls.

Option C (removing animations and using SVG) reduces client-side rendering overhead but does not tackle the primary bottleneck of excessive GlideAjax calls. Option D (lazy loading and deferred calls) can improve perceived performance but still initiates the same number of calls eventually, and deferring essential calls may delay functionality.

Full explanation →
459
MCQhard

A global business rule that runs on after query on the Task table is causing performance degradation. The rule modifies the query condition for all task records. The developer needs to optimize the rule without changing its functionality. Which approach is best?

A.Move the script to a condition builder script include
B.Convert the business rule to a script action in a flow designer
C.Make the business rule asynchronous
D.Use glideRecord.addEncodedQuery() instead of addQuery()
AnswerD

addEncodedQuery allows passing a single encoded query string, reducing multiple database calls.

Why this answer

Using `glideRecord.addEncodedQuery()` allows the business rule to directly apply a pre-encoded query string to the GlideRecord object, which is more efficient than using multiple `addQuery()` calls. This reduces the overhead of parsing individual conditions and improves performance when modifying query conditions on the Task table, without altering the rule's functionality.

Exam trap

The trap here is that candidates often assume asynchronous execution (Option C) always improves performance, but they overlook that changing the business rule to asynchronous would prevent it from modifying the query condition before execution, thus breaking the required functionality.

How to eliminate wrong answers

Option A is wrong because moving the script to a condition builder script include does not address the performance degradation; it merely relocates the logic without optimizing the query construction. Option B is wrong because converting the business rule to a script action in Flow Designer introduces additional orchestration overhead and is not designed for optimizing query conditions in a before query business rule. Option C is wrong because making the business rule asynchronous would change its functionality—it would no longer run synchronously during the query phase, which is required to modify the query condition before execution.

Full explanation →
460
MCQhard

Refer to the exhibit. What does this ACL condition allow?

A.Any user can update incidents when state is '3'.
B.Only users without 'itil' role can update incidents in state '3'.
C.Users with 'itil' role can update incidents in state 'Resolved'.
D.Users with 'itil' role can update incidents in state 'On Hold'.
AnswerD

State 3 corresponds to 'On Hold' and role condition is itil.

Why this answer

The ACL condition grants update access when the user has the 'itil' role and the incident state is '3', which is 'On Hold'. Option A is incorrect because it ignores the role requirement. Option B is wrong because it says users without 'itil' role can update, but the ACL requires the 'itil' role.

Option C is wrong because state '3' is 'On Hold', not 'Resolved'.

Full explanation →
461
MCQeasy

A developer needs to create a record in the 'task' table when a specific condition is met in a Business Rule. The new record should be linked back to the current record via a reference field. What is the best practice to ensure the new record is created in the same transaction?

A.Use GlideRecord with newRecord() and set values, then call insert().
B.Use Flow Designer to create the record asynchronously.
C.Use the GlideRecord updateMultiple() method.
D.Call a Scripted REST API to insert the record.
AnswerA

This is the standard way to create records in the same transaction within a Business Rule.

Why this answer

Using GlideRecord with newRecord() and insert() within the same Business Rule ensures the new 'task' record is created in the same database transaction as the current record. This guarantees atomicity: if the insert fails, the entire transaction rolls back, preventing orphaned records. The reference field linking back to the current record is set synchronously before the insert, maintaining data integrity.

Exam trap

The trap here is that candidates often think asynchronous methods like Flow Designer are 'best practice' for decoupling, but the question explicitly requires same-transaction creation, which only synchronous GlideRecord insert provides.

How to eliminate wrong answers

Option B is wrong because Flow Designer asynchronously creates the record in a separate transaction, breaking atomicity and potentially causing race conditions or orphaned records if the current transaction fails. Option C is wrong because updateMultiple() is used to update existing records in bulk, not to insert a new record; it cannot create a new record linked to the current one. Option D is wrong because calling a Scripted REST API introduces a separate HTTP request and transaction, defeating the purpose of same-transaction creation and adding unnecessary latency and failure points.

Full explanation →
462
MCQeasy

A developer is creating a catalog item that requires a user to upload a file. Which variable type should be used?

A.Attachment
B.Multi Line Text
C.Single Line Text
D.Checkbox
AnswerA

Attachment variable type allows file uploads.

Why this answer

The Attachment variable type is specifically designed for file uploads in ServiceNow catalog items. It provides a built-in file picker and stores the uploaded file as an attachment on the requested record, enabling users to submit documents directly through the catalog form.

Exam trap

ServiceNow often tests the distinction between variable types that handle data differently; the trap here is that candidates might confuse 'Attachment' with 'Single Line Text' thinking a file path can be entered as text, but ServiceNow requires the dedicated Attachment variable for actual file uploads.

How to eliminate wrong answers

Option B (Multi Line Text) is wrong because it is intended for free-form text input spanning multiple lines, not for file uploads. Option C (Single Line Text) is wrong because it accepts only a single line of text and cannot handle binary file data. Option D (Checkbox) is wrong because it represents a boolean true/false value and has no capability for file attachment.

Full explanation →
463
MCQmedium

A developer created a UI Script and a Client Script as shown. Both scripts set urgency and impact to '1' when priority is '1'. However, when the priority is changed to '1' on an existing record, the urgency and impact fields do not update. What is the most likely cause?

A.The UI Script is not being called because it is not associated with any form or event
B.The priority field is not a choice field, so onChange does not fire
C.The Client Script function name is incorrect; it should be 'onChangePriority'
D.The g_form API is deprecated and no longer works
AnswerA

UI Scripts are not automatically executed; they must be called from a Client Script or UI Policy.

Why this answer

A UI Script is a reusable client-side script that must be explicitly called from a Client Script, UI Policy, or form event to execute. In this scenario, the UI Script is not associated with any form or event, so it never runs when the priority field changes. The Client Script alone cannot invoke the UI Script without a direct call, leaving the urgency and impact fields unupdated.

Exam trap

ServiceNow often tests the distinction between defining a script and executing it, trapping candidates who assume that simply creating a UI Script will automatically run it on field changes without an explicit trigger.

How to eliminate wrong answers

Option B is wrong because the onChange event fires on any field change, including choice fields like priority; the issue is not about field type but about the UI Script not being triggered. Option C is wrong because the Client Script function name can be any valid JavaScript function name; the onChange event is bound to the field, not the function name, so 'onChangePriority' is not required. Option D is wrong because the g_form API is not deprecated and continues to work in current ServiceNow versions; the problem is unrelated to API deprecation.

Full explanation →
464
MCQmedium

A developer writes a script to display the department name of the caller on a custom form. The script uses: gs.getUser().getDepartment().getName(). However, the script throws a null pointer exception for some users. Which is the most likely cause and solution?

A.The Department table is empty
B.The script uses incorrect dot-walking syntax; use getValue('department') instead
C.The user table does not have a department reference field
D.Some users do not have a department assigned, and the script does not check for null
AnswerD

When getDepartment() returns null, calling getName() on null causes a NullPointerException. The solution is to add a null check before calling getName().

Why this answer

The NullPointerException suggests that getDepartment() returned null for users without a department. Option A is wrong because the script is syntactically correct. Option B is wrong because reference exists.

Option C is wrong because department records exist.

Full explanation →
465
MCQeasy

A company needs to allow employees to request a new laptop through a catalog item. The form should only show a 'Configuration' section if the user selects 'Yes' for 'Custom Configuration?'. Which design approach best accomplishes this?

A.Use a UI Policy to show/hide the section based on the field value.
B.Use a client script to hide the section when the field changes.
C.Use an ACL to restrict access to the section.
D.Use a catalog client script to set the visibility.
AnswerA

UI Policies are the standard way to control visibility of fields/sections declaratively.

Why this answer

UI Policies are declarative and maintainable for showing/hiding variables based on conditions, unlike client scripts which can be brittle.

Full explanation →
466
Multi-Selecteasy

Which THREE of the following are features available in ServiceNow for integrating data with external systems? (Choose three.)

Select 3 answers
A.SOAP Web Service
B.LDAP
C.Email
D.REST API
E.Print
AnswersA, B, D

SOAP is another web service integration.

Why this answer

REST API, SOAP Web Service, and LDAP are standard integration features in ServiceNow. Email and Print are not used for data integration.

Full explanation →
467
MCQhard

A developer writes a business rule that queries the 'incident' table using GlideRecord. The script loops through all incidents and updates a field. After running, the developer notices that only a subset of records were updated. What is the most likely cause?

A.The user running the script lacks write ACL on the table
B.The GlideRecord query did not include a condition, so it used a default filter that limited results
C.The field name used in the update was misspelled
D.The script did not call getRowCount() before the loop
AnswerB

Without an explicit query, GlideRecord may apply a default filter (e.g., active=true) or system limit.

Why this answer

GlideRecord queries in ServiceNow automatically apply a default filter when no explicit condition is set, typically limiting results to records where the `active` field is `true`. This default behavior, known as the 'active filter,' causes the script to only process a subset of incidents (those that are active) rather than all records in the table, explaining why only some were updated.

Exam trap

The trap here is that candidates assume GlideRecord returns all records by default, but ServiceNow's platform applies an implicit active filter, causing partial results unless explicitly overridden.

How to eliminate wrong answers

Option A is wrong because a lack of write ACL would cause an error or permission denial, not a silent partial update of a subset of records. Option C is wrong because a misspelled field name would result in a script error or the update not being applied to any record, not a partial update of some records. Option D is wrong because `getRowCount()` is not required for looping through GlideRecord results; the loop iterates over the record set regardless of whether `getRowCount()` is called, so its absence does not cause a subset of records to be updated.

Full explanation →
468
MCQmedium

A developer writes a widget client controller that uses spUtil.get to fetch data from the server. The data is correctly returned, but the widget does not update the UI. What is the most likely cause?

A.The widget's HTML template does not reference the correct variable name
B.The callback does not assign the result to a $scope variable
C.The server script did not set data correctly
D.The spUtil.get method is deprecated
AnswerB

Correct: Without updating $scope, AngularJS does not know to re-render.

Why this answer

spUtil.get returns a promise, and the success callback should assign to $scope to trigger digest cycle. If the callback does not update a $scope property, the view will not update.

Full explanation →
469
MCQhard

A developer is optimizing a Business Rule that runs on every update to the 'incident' table. The rule uses GlideAggregate to count related records. The developer notices performance degradation. Which change will most improve performance while maintaining functionality?

A.Replace GlideAggregate with GlideRecord and count results manually.
B.Add a database index on the foreign key field used in the aggregate.
C.Add a condition to the Business Rule such as 'current.changesField('state')' to only run the aggregate when relevant.
D.Use the gs.addInfoMessage() to log the count and disable the script in production.
AnswerC

Limiting execution to only when the 'state' field changes reduces unnecessary processing.

Why this answer

It prevents the GlideAggregate from executing on every update, instead running only when the 'state' field changes. This reduces unnecessary database operations, directly addressing the performance degradation while preserving the rule's functionality when needed.

Exam trap

ServiceNow often tests the misconception that adding an index (Option B) is the universal performance fix, but the trap here is that reducing unnecessary execution (Option C) is a more impactful optimization than improving query speed for a query that runs too often.

How to eliminate wrong answers

Option A is wrong because replacing GlideAggregate with GlideRecord and manually counting results would be even less efficient, as it retrieves all related records into memory rather than performing a server-side count. Option B is wrong because while adding a database index can improve query performance, it does not address the root cause of running the aggregate on every update; the performance gain is marginal compared to reducing execution frequency. Option D is wrong because using gs.addInfoMessage() to log the count and disabling the script in production would eliminate the functionality entirely, not maintain it.

Full explanation →
470
MCQeasy

Refer to the exhibit. The Business Rule is set to run on before update. When a record's category is changed to 'hardware', the assignment group is updated correctly. However, when a record is inserted with category 'hardware', the assignment group is not set. Why?

A.The condition 'current.category.changes()' returns false on insert.
B.The Business Rule does not run on insert.
C.The Business Rule runs after the database operation.
D.The setValue method does not work on insert.
AnswerA

On insert, changes() is false because no previous value.

Why this answer

The condition 'current.category.changes()' checks if the category field has changed from its previous value. On insert, there is no previous value, so this condition returns false, causing the business rule to not execute the assignment group update. Option B is incorrect because the business rule does run on insert (it is configured to run on insert as well, despite the stem mentioning only 'before update'), but the condition fails.

Option C is incorrect because the rule runs before the database operation. Option D is incorrect because setValue works on insert.

Full explanation →
471
MCQeasy

When creating a new table using the 'Create Table' module, which setting determines whether the table will inherit fields from an existing table?

A.Application
B.Extends
C.Table name
D.Table label
AnswerB

The 'Extends' field lets you choose a parent table to inherit fields.

Why this answer

'Extends,' is correct because it allows the new table to inherit fields from an existing parent table. Option A, 'Application,' defines the application scope, not inheritance. Option C, 'Table name,' is the system name.

Option D, 'Table label,' is the display name.

Full explanation →
472
MCQeasy

In ServiceNow Studio, which file type is automatically generated when creating a new application?

A.update.xml
B.readme.md
C.manifest.xml
D.app.xml
AnswerC

Correct. Manifest.xml defines application metadata.

Why this answer

ServiceNow Studio automatically generates a manifest.xml file for each new application. This file contains metadata about the application. Option A is incorrect because update.xml files are used for update sets, not automatically generated for applications.

Option B is incorrect; readme.md is an optional file that can be added manually. Option D is incorrect; app.xml is not a standard file generated by Studio.

Full explanation →
473
MCQhard

A developer needs to debug an issue where a client script is not triggering when a field changes. What is the most efficient first step in troubleshooting within Studio?

A.Review the syslog for error messages.
B.Open the client script in Studio and use the 'Debug' button.
C.Check the ACLs on the table.
D.Add a gs.log() statement to the server-side code.
AnswerB

This allows running the script in debug mode to see if it fires and track variables.

Why this answer

Studio includes a debug feature for client scripts that allows step-by-step execution and inspection. Option A is indirect, C is not relevant to client script execution, and D is server-side.

Full explanation →
474
Multi-Selecthard

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

Select 3 answers
A.The business rule's condition field requires the category to be set
B.The assignment group field is read-only on the form but can be set via business rule
C.The script does not include a condition to run on update
D.The business rule is set to run only in the global scope
E.Another business rule is resetting the assignment group after this rule runs
AnswersA, C, E

If the business rule has a condition that checks for category, the rule may not fire on update if the category field is not updated or empty.

Why this answer

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.

Full explanation →
475
Multi-Selecthard

Which THREE considerations are important when designing a ServiceNow REST API for external consumption? (Choose three.)

Select 3 answers
A.Implement rate limiting to protect the instance from overload.
B.Use versioning in the API path (e.g., /api/now/v1/table).
C.Use GlideAggregate for performance in the API script.
D.Always use OAuth 2.0 for authentication.
E.Provide meaningful error messages in the response body.
AnswersA, B, E

Rate limiting prevents abuse and maintains performance.

Why this answer

Implementing rate limiting is crucial for protecting a ServiceNow instance from being overwhelmed by excessive API requests from external consumers. Without rate limiting, a single client could degrade performance for all users or even cause an outage. ServiceNow provides built-in mechanisms like the REST API rate limit property (glide.rest.rate_limit) to control request frequency per client.

Exam trap

The trap here is that candidates may confuse internal implementation techniques (like GlideAggregate) with high-level design considerations for external REST APIs, or assume that OAuth 2.0 is strictly required when ServiceNow actually supports multiple authentication methods.

Full explanation →
476
Drag & Dropmedium

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

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

The correct sequence starts with accessing the Application Creator, then initiating the wizard, providing application details, choosing a template, and finally creating the application.

Full explanation →
477
MCQeasy

A developer wants to send an email notification when a new incident is created. Which component should be configured to trigger the notification?

A.Use Flow Designer to create a flow that sends an email.
B.Write a Business Rule that calls the email utility.
C.Create a Notification record with the condition 'New' and 'Action: record inserted'.
D.Create an ACL with email action.
AnswerC

Notifications are the standard way to send emails on record events.

Why this answer

In ServiceNow, the native Notification mechanism is specifically designed to send emails based on conditions like 'New' and 'Action: record inserted'. When a new incident is created, the system evaluates the notification's condition; if it matches, the notification triggers automatically without requiring custom scripting or flow design. This is the standard, out-of-box approach for email alerts on record creation.

Exam trap

The trap here is that candidates often confuse the purpose of Business Rules (which can also send emails via script) with the dedicated Notification engine, leading them to choose Option B, but ServiceNow's best practice and the exam emphasize using the native Notification record for simple email triggers on record creation.

How to eliminate wrong answers

Option A is wrong because Flow Designer is typically used for more complex, multi-step automations; while it can send emails, it is not the simplest or most direct component for a basic trigger-on-insert notification, and using it would introduce unnecessary overhead. Option B is wrong because writing a Business Rule that calls the email utility is a custom scripting approach that bypasses the built-in Notification engine, leading to maintenance challenges and potential performance issues; ServiceNow recommends using Notifications for such standard email triggers. Option D is wrong because ACLs (Access Control Lists) control data access and security, not email notifications; they have no capability to send emails or trigger actions on record insertion.

Full explanation →
478
MCQeasy

A company is importing user records from a CSV file using an import set. The transform map is configured to update existing records and insert new ones based on the email field. After running the import, they notice that some existing records were not updated even though the email matched. The email field in the target user table is correctly populated and has a unique index. The source CSV file has no obvious formatting issues. The import set runs without errors. What is the most likely cause?

A.The transform map's 'Coalesce' checkbox is not selected on the email field mapping.
B.The source CSV has trailing spaces in the email field.
C.The email field in the target table is not indexed.
D.The import set table does not have a unique index on the email field.
AnswerA

Correct: Coalesce must be enabled for the system to match incoming records to existing target records based on that field.

Why this answer

The most likely cause is that the 'Coalesce' checkbox is not selected on the email field mapping in the transform map. Coalesce must be enabled for the system to use that field to match existing records in the target table. Without coalesce, the system treats all incoming records as new, so updates will not occur even if the email matches.

Option B is incorrect because trailing spaces would affect all matching, not just some records, and the scenario states no formatting issues. Option C is incorrect because indexing affects performance, not matching. Option D is incorrect because the import set table does not need a unique index for target matching; the matching is based on the target table's email field, which has a unique index.

Full explanation →
479
Multi-Selecthard

Which THREE of the following are correct statements about Service Portal client controllers?

Select 3 answers
A.They can use AngularJS services like $http and $timeout.
B.They run on the server and are called via server-side includes.
C.They must define a $scope variable explicitly to bind data to the template.
D.They can call the server using $scope.server.get() or $scope.server.post().
E.They are AngularJS controllers that handle client-side logic.
AnswersA, D, E

AngularJS services are available in client controllers.

Why this answer

Service Portal client controllers are AngularJS controllers that run in the browser. They can use standard AngularJS services such as $http for making AJAX calls to external APIs or the instance, and $timeout for delaying execution, which are both injected as dependencies.

Exam trap

ServiceNow often tests the misconception that client controllers run on the server or require explicit $scope declaration, confusing them with server-side scripts or older AngularJS patterns.

Full explanation →
480
Multi-Selectmedium

Which TWO approaches are valid for importing data from an external database into ServiceNow on a recurring basis? (Choose two.)

Select 2 answers
A.Set up a MID Server to run a scheduled transform map from an external SQL query.
B.Use a REST API with a periodic flow that calls an external endpoint.
C.Write a business rule that triggers on an external event via web service.
D.Use an email inbound action to parse CSV attachments from the external system.
E.Configure a JDBC data source and scheduled import set.
AnswersA, E

MID Server can execute SQL queries and transform data into ServiceNow.

Why this answer

A MID Server can execute a scheduled SQL query against an external database and then run a transform map to map the retrieved data into ServiceNow tables. This approach is a standard pattern for recurring data imports using the MID Server's JDBC capabilities combined with scheduled import sets.

Exam trap

The trap here is that candidates often confuse 'importing from an external database' with any external data integration, but the question specifically requires direct database import, which mandates JDBC and a MID Server, not REST APIs or email-based methods.

Full explanation →
481
MCQhard

A developer creates a scheduled job that updates a custom table's records. The job runs successfully but the table's 'Updated' field does not reflect the correct time. What could be the reason?

A.The scheduled job's schedule interval is longer than the update frequency.
B.The script used 'setWorkflow(false)' which bypasses the auto-update of the 'Updated' field.
C.The table does not have the appropriate record-level ACLs.
D.The scheduled job runs too fast for the system to record the update.
AnswerB

setWorkflow(false) disables business rules and field updates like 'Updated'.

Why this answer

The 'Updated' field is set automatically when a record is updated through the UI, but if the update is done via direct database update (e.g., using GlideRecord without setWorkflow(true)), the system might not update the field. Also, conditional or dirty flag may not set. However, the most likely is that the update script used setWorkflow(false) or bypassed the auto-update mechanism.

Option A is wrong because performance of the job is not related. Option C is wrong because Access controls do not affect system fields like 'Updated'. Option D is wrong because the job's schedule time is irrelevant.

Full explanation →
Page 6

Page 7 of 7

All pages

1234567

Practice SNOW-CAD by domain

Target a specific domain to shore up weak areas.

Working with DataPlatform Features and IntegrationIntegrating and managing application dataAutomating application logic with business rules and scriptsApplication development using ServiceNow StudioCreating and customizing tables and dataDesigning interfaces and user experiencesCore Application DevelopmentUser Interface Development
See all domains with question counts →