Courseiva

ServiceNow Certified System Administrator CSA (SNOW-CSA) — Questions 301–375

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

Take a mock examExam hub
Page 4

Page 5 of 7

Page 6
301
MCQhard

A company uses a custom application with a table named 'project_task' that contains several reference fields pointing to large tables (e.g., 'User', 'Department'). Users report that the 'project_task' form takes over 10 seconds to load, primarily due to the time required to fetch options for these reference fields. The administrator wants to improve the form loading performance without removing any fields or changing the user workflow. The instance is on a standard license and performance optimization is a priority. Which approach should the administrator take?

A.Convert all reference fields to choice fields with a predefined list.
B.Write a client script to load reference options asynchronously using GlideAjax.
C.Add a reference qualifier to each reference field to limit the number of options displayed.
D.Enable the 'Use Ajax on Reference' option on the dictionary records for the reference fields.
AnswerD

This loads reference options asynchronously, allowing the form to render quickly while options populate in the background.

Why this answer

Enabling 'Use Ajax on Reference' on the dictionary records causes the reference fields to load their options asynchronously via AJAX after the form renders, rather than during the initial page load. This significantly reduces the initial load time because the large reference tables (e.g., 'User', 'Department') are not queried synchronously when the form is first opened.

Exam trap

The trap here is that candidates often think a reference qualifier (Option C) will improve performance by reducing the dataset, but they overlook that the query still executes synchronously during page load, whereas 'Use Ajax on Reference' changes the loading mechanism itself to be asynchronous.

How to eliminate wrong answers

Option A is wrong because converting reference fields to choice fields with a predefined list would require manual maintenance of static lists, which is impractical for large, dynamic tables like 'User' and 'Department', and would break referential integrity. Option B is wrong because writing a client script with GlideAjax to load reference options asynchronously is a custom approach that duplicates built-in functionality, adds unnecessary complexity, and is not the standard or recommended optimization for this scenario. Option C is wrong because adding a reference qualifier limits which records are displayed but does not change the synchronous loading behavior; the query still runs during page load, so it would not address the 10-second delay caused by fetching all options.

Full explanation →
302
MCQeasy

A ServiceNow administrator needs to create a report that shows the number of incidents opened each month for the last 12 months. The report should display a bar chart with months on the x-axis and count on the y-axis. Which report type and grouping should the administrator use?

A.Bar chart, group by Month on the Opened field
B.List report, sort by Opened
C.Pie chart, group by Month on the Opened field
D.Line chart, group by Day on the Opened field
AnswerA

Bar chart with monthly grouping effectively shows counts over time.

Why this answer

A bar chart is ideal for comparing discrete categories (months) over time, and grouping by Month on the Opened field aggregates incident counts per month. This meets the requirement of showing the number of incidents opened each month for the last 12 months with months on the x-axis and count on the y-axis.

Exam trap

The trap here is that candidates may confuse the appropriate chart type for time-series data (bar vs. line) or incorrectly choose a daily grouping when the requirement explicitly asks for monthly aggregation.

How to eliminate wrong answers

Option B is wrong because a List report displays raw data in a table format, not a visual bar chart, and sorting by Opened does not group or aggregate counts by month. Option C is wrong because a Pie chart shows proportions of a whole, not trends over time, and grouping by Month on the Opened field would create a pie slice per month, which is inappropriate for a 12-month time series. Option D is wrong because a Line chart could show trends but grouping by Day on the Opened field would produce daily data points, not monthly aggregates, and the requirement specifies months on the x-axis.

Full explanation →
303
MCQeasy

Which CMDB relationship type should be used to represent that a server is physically installed in a rack?

A.Depends on
B.Contains
C.Runs on
D.Connected to
AnswerB

Contains is used for physical hierarchy like rack and server.

Why this answer

The 'Contains' relationship type is correct because it models a parent-child containment hierarchy in the CMDB, where the rack is the container and the server is the contained item. This aligns with the CMDB's ability to represent physical location and dependencies, ensuring accurate service mapping and impact analysis.

Exam trap

ServiceNow often tests the confusion between 'Contains' and 'Depends on' by presenting scenarios where physical location is implied but candidates mistakenly choose a dependency relationship due to misinterpreting 'installed in' as a functional reliance.

How to eliminate wrong answers

Option A is wrong because 'Depends on' indicates a functional dependency (e.g., a server depends on a power source), not a physical containment relationship. Option C is wrong because 'Runs on' is used for software or application relationships (e.g., an application runs on a server), not for physical placement. Option D is wrong because 'Connected to' describes a network or cable connection (e.g., a server connected to a switch), not physical installation within a rack.

Full explanation →
304
Multi-Selecteasy

Which TWO methods allow an administrator to make a field read-only on a form? (Choose two.)

Select 2 answers
A.Configure the form layout to hide the field
B.Create an ACL that denies write access
C.Create a UI policy that sets the field to read-only when a condition is true
D.Set the field attribute to 'Read only' in dictionary entry
E.Add the field to a related list
AnswersC, D

UI policy can change state dynamically.

Why this answer

A UI policy can dynamically set a field to read-only based on a specified condition, such as a particular state or value. This allows administrators to control field editability at runtime without permanently altering the field's definition. Option D is correct because setting the 'Read only' attribute in the dictionary entry makes the field read-only globally across all forms and views, providing a static, system-wide restriction.

Exam trap

The trap here is that candidates often confuse ACLs (which control write access at the data layer) with UI policies (which control field editability at the presentation layer), leading them to incorrectly select option B as a method to make a field read-only on a form.

Full explanation →
305
MCQhard

A catalog item uses a Variable Editor to capture complex data. The user submits the request but the variable data is not stored in the sys_variable_value table. What could be the reason?

A.The variable is not configured to 'Store value'.
B.The variable is set to 'Read only'.
C.The Variable Editor is not included in the catalog item's workflow.
D.The variable type is 'Lookup Select'.
AnswerA

If 'Store value' is unchecked, the variable's value is not saved to sys_variable_value.

Why this answer

The 'Store value' checkbox on a variable definition controls whether the submitted value is persisted in the sys_variable_value table. If this checkbox is unchecked, the variable's data is captured during the request but is not saved to the database, which matches the symptom described in the question.

Exam trap

The trap here is that candidates often assume any variable captured on a form is automatically stored, overlooking the explicit 'Store value' configuration that governs persistence in the sys_variable_value table.

How to eliminate wrong answers

Option B is wrong because setting a variable to 'Read only' prevents the user from modifying the value in the catalog item form, but it does not affect whether the value is stored in the sys_variable_value table; the value is still saved upon submission. Option C is wrong because the Variable Editor is a UI element that renders the variable on the form; it does not need to be included in a workflow for the variable data to be stored—storage is controlled by the variable's configuration, not by workflow inclusion. Option D is wrong because the 'Lookup Select' variable type stores its selected value in the sys_variable_value table by default, provided the 'Store value' checkbox is enabled; the type itself does not prevent storage.

Full explanation →
306
MCQeasy

An order guide contains multiple catalog items. When the order guide is submitted, what is created?

A.One request with one requested item that contains all items
B.Multiple requests, one for each item
C.One request with multiple requested items
D.A single cart item
AnswerC

The order guide bundles items into a single request, each item becomes a requested item.

Why this answer

When an order guide is submitted in ServiceNow, it creates a single request (sc_request) containing multiple requested items (sc_req_item), one for each catalog item in the guide. This is because the order guide acts as a container that groups multiple catalog items into one submission, and the system automatically generates a parent request with child requested items to track fulfillment individually.

Exam trap

The trap here is that candidates often confuse the behavior of an order guide with a record producer or a single catalog item, assuming all items merge into one requested item or that multiple requests are generated, but ServiceNow specifically creates one request with multiple requested items to balance grouping and independent fulfillment.

How to eliminate wrong answers

Option A is wrong because it suggests all items are combined into one requested item, but ServiceNow creates separate requested items for each catalog item to allow independent fulfillment and tracking. Option B is wrong because it implies multiple requests are created, but ServiceNow creates a single request to group the items, not separate requests per item. Option D is wrong because a cart item is a temporary object used during the ordering process, not the final record created upon submission; the submission creates a request and requested items.

Full explanation →
307
MCQeasy

A user is unable to access the Service Portal. They receive a '404' error. What is the most likely cause?

A.The Service Portal application is not installed.
B.The portal URL is misspelled.
C.The user does not have the 'service_portal_user' role.
D.The user's browser cache is corrupted.
AnswerB

Correct: A 404 error typically indicates the URL does not exist.

Why this answer

A 404 error indicates a page not found, often due to a mistyped URL. Option A would typically show a permissions error, not 404. Option C is about roles, which would show an access denied error.

Option D is unlikely to cause a 404.

Full explanation →
308
MCQmedium

A ServiceNow administrator needs to create a database view that combines data from the cmdb_ci_server table and the cmdb_ci_netgear table. What is the correct method to achieve this?

A.Use the CMDB Explorer to merge CI classes.
B.Write a custom script to join tables and store results in a new table.
C.Create a report and save it as a view.
D.Use the Database Views module to create a view with join conditions.
AnswerD

Database Views is the correct feature for creating views.

Why this answer

The Database Views module in ServiceNow allows administrators to create a view that combines data from multiple tables using SQL-like join conditions. This is the standard, no-code method to create a virtual table that merges fields from cmdb_ci_server and cmdb_ci_netgear without modifying the underlying schema or duplicating data.

Exam trap

The trap here is that candidates confuse the Database Views module with reporting features or CMDB tools, assuming a report or CMDB Explorer can produce a queryable table, when only Database Views creates a true SQL-level join view.

How to eliminate wrong answers

Option A is wrong because the CMDB Explorer is used to visualize and manage CI class hierarchies and relationships, not to create database views that join tables. Option B is wrong because writing a custom script to join tables and store results in a new table is inefficient, bypasses platform best practices, and creates data redundancy rather than a live view. Option C is wrong because reports in ServiceNow can be saved as report views or dashboards, but they do not create a database view that can be queried like a table in the platform.

Full explanation →
309
MCQeasy

An administrator needs to identify which CI(s) are affected by a recent network outage. Which table should be queried to find the relationship between CIs and incidents?

A.task_ci
B.cmdb_ci
C.sys_ci_relation
D.cmdb_rel_ci
AnswerA

task_ci links tasks (like incidents) to CIs.

Why this answer

The task_ci table stores the direct relationship between tasks (including incidents) and configuration items (CIs). When an administrator needs to identify which CIs are affected by a specific incident, querying task_ci with the incident's sys_id will return the associated CIs. This table is the standard ServiceNow junction table for linking any task record (such as an incident) to CIs.

Exam trap

The trap here is that candidates often confuse the table for CI-to-CI relationships (cmdb_rel_ci) with the table for task-to-CI relationships (task_ci), leading them to select cmdb_rel_ci when the question specifically asks about incidents and CIs.

How to eliminate wrong answers

Option B (cmdb_ci) is wrong because it is the base table for all configuration items, storing CI attributes and not the relationship between incidents and CIs. Option C (sys_ci_relation) is wrong because it is not a standard ServiceNow table; the correct table for CI-to-CI relationships is cmdb_rel_ci. Option D (cmdb_rel_ci) is wrong because it stores relationships between CIs (e.g., 'runs on', 'connects to'), not the association between incidents and CIs.

Full explanation →
310
MCQeasy

A company needs to import data from a CSV file into the User table. The CSV includes fields for first name, last name, email, and department. However, the import fails because some email addresses are invalid. Which feature in ServiceNow can be used to prevent invalid emails from being imported?

A.Data Source configuration
B.Import Set Row
C.Transform Map with condition scripts
D.Import Set Table API
AnswerC

Transform Maps can include condition scripts to skip or error on invalid data, such as invalid email addresses.

Why this answer

A Transform Map with condition scripts allows you to validate incoming data before it is written to the target table. In this scenario, you can add a script to the transform map that checks each email address against a regular expression pattern (e.g., RFC 5322) and skips or rejects rows with invalid emails, preventing them from being imported into the User table.

Exam trap

The trap here is that candidates often confuse Data Source configuration (which handles parsing) with Transform Map condition scripts (which handle row-level validation), leading them to select Option A because they think validation is part of the data source setup.

How to eliminate wrong answers

Option A is wrong because a Data Source configuration defines how to parse the CSV file (e.g., delimiter, encoding) but does not include row-level validation logic to filter out invalid emails. Option B is wrong because an Import Set Row is a staging record that holds the raw imported data; it does not provide a mechanism to conditionally prevent rows from being transformed or inserted. Option D is wrong because the Import Set Table API is used to programmatically load data into an import set table, but it does not enforce validation rules on individual field values like email format.

Full explanation →
311
MCQhard

An SLA is defined to pause when state is 'Awaiting Customer'. The SLA timer continues to run even when the state changes to that value. What should the administrator check first?

A.Ensure the business rule that triggers SLA recalculation is active.
B.Check the SLA schedule for the 'Pause' field.
C.Verify the SLA pause condition script or condition.
D.Check the SLA metric timeline.
AnswerC

The pause condition specifies when the timer should be paused; if it's incorrect or not evaluating to true, the timer will not pause.

Why this answer

The SLA timer continues to run despite the state being 'Awaiting Customer', which indicates that the pause condition is not being evaluated correctly. The administrator must first verify the SLA pause condition script or condition to ensure it properly triggers a pause when the state changes to 'Awaiting Customer'. If the condition is misconfigured or not returning true, the timer will not pause as expected.

Exam trap

The trap here is that candidates often confuse the SLA schedule's pause functionality (which pauses based on time) with the pause condition (which pauses based on record state or other criteria), leading them to select Option B instead of C.

How to eliminate wrong answers

Option A is wrong because SLA recalculation business rules are used to recalculate SLA metrics after changes, not to control pause behavior; the issue is that the timer is not pausing, not that it needs recalculation. Option B is wrong because the SLA schedule's 'Pause' field defines when the SLA should pause based on time (e.g., weekends or holidays), not based on state changes like 'Awaiting Customer'. Option D is wrong because checking the SLA metric timeline would show the timer's history but does not identify the root cause of why the pause condition failed to trigger.

Full explanation →
312
MCQhard

What is the effect of this script on the import transform?

A.It will set the department to the current user's department for all imported records.
B.It will cause an error because the target might be null.
C.It will skip records without employee ID and prevent updating department for new records.
D.It will skip records that have no employee ID and set department for existing records only.
AnswerD

The return false on empty employee ID causes the row to be skipped. The department assignment only happens when target is not null (existing record).

Why this answer

The script uses `source.u_employee_id.nil()` to check if the employee ID field is empty. If it is nil, the script returns `false`, which causes the import transform to skip that record entirely (no insert or update). For records with an employee ID, the script then checks `action == 'update'` and only sets the department to the current user's department for existing records being updated.

New records (action 'insert') are not affected, so the department field remains unchanged for them.

Exam trap

The trap here is that candidates often assume the script sets the department for all records (including new ones) or that skipping records without an employee ID applies to both inserts and updates, when in fact the script only applies the department change to existing records being updated.

How to eliminate wrong answers

Option A is wrong because the script does not set the department for all imported records; it only sets it for records that have an employee ID and are being updated. Option B is wrong because the script does not cause an error due to a null target; the `target` object is always available in transform scripts, and the script safely uses `source.u_employee_id.nil()` to avoid null issues. Option C is wrong because while it correctly notes that records without employee ID are skipped, it incorrectly states that the script prevents updating department for new records; the script actually only updates department for existing records (update action) and does nothing for new records, so it does not 'prevent' an update that wasn't going to happen.

Full explanation →
313
MCQeasy

An administrator wants to automate the fulfillment of a catalog item that requires approval from the user's manager. Which combination of features should be used?

A.Virtual Agent and Flow Designer
B.Record Producer and Virtual Agent
C.Flow Designer with Approval step
D.Approval Engine and Email Notification
AnswerC

Flow Designer can include approval and trigger fulfillment.

Why this answer

Flow Designer provides a native Approval step that can be configured to route the request to the user's manager via the Manager field on the sys_user record. This allows the entire fulfillment process—including approval and subsequent actions—to be automated within a single Flow, eliminating the need for separate approval engine configurations or manual intervention.

Exam trap

The trap here is that candidates often confuse the Approval Engine (a standalone feature) with Flow Designer's Approval step, not realizing that Flow Designer integrates approval logic directly into an automated workflow, making it the correct choice for automating both approval and fulfillment.

How to eliminate wrong answers

Option A is wrong because Virtual Agent is a chatbot interface for user interaction, not a fulfillment automation tool; it cannot handle approval routing or fulfillment steps on its own. Option B is wrong because Record Producer creates catalog items from inbound emails or forms but lacks the ability to manage approval workflows; Virtual Agent again does not provide approval logic. Option D is wrong because the Approval Engine handles approval requests but does not automate the fulfillment process; Email Notification only sends messages and cannot execute post-approval actions like updating records or triggering flows.

Full explanation →
314
MCQhard

Refer to the exhibit. A user without the admin role attempts to update an incident record where the caller's department is 'Finance'. The user's department is 'IT'. What will happen?

A.The update is denied because the condition evaluates to false.
B.The update is allowed because the user has the admin role.
C.The update is allowed because the user's department matches the caller's department.
D.The update is denied because the ACL is misconfigured.
AnswerA

Both parts of the OR condition are false, so ACL denies.

Why this answer

The condition checks if user has admin role (false) or user's department equals caller's department (IT != Finance). Both false, so ACL denies write.

Full explanation →
315
MCQhard

An administrator is asked to design a solution to prevent unauthorized changes to the CMDB. The requirement is that any update to a CI's critical attributes (e.g., serial number, model) must be logged and require an approval. Which approach should be taken?

A.Configure the CMDB to use 'Data Certification' and require approval for attribute changes.
B.Use a database trigger that captures changes and creates a change request.
C.Create a business rule that fires on update, checks the previous values, and sends an approval request.
D.Set field-level audit on the critical fields and use the 'Audit' module to report changes.
AnswerC

A business rule with approval workflow can prevent unauthorized updates in real time.

Why this answer

A business rule that fires 'on update' with a condition checking previous values of critical attributes (e.g., serial number, model) can trigger an approval request via an approval engine or flow. This approach directly enforces the requirement that updates to those specific fields require approval before the change is committed, without relying on external modules or triggers that may bypass ServiceNow's native approval framework.

Exam trap

The trap here is that candidates often confuse 'audit' (which only logs changes) with 'approval' (which prevents changes), leading them to select Option D, or they mistakenly think database triggers (Option B) are a valid ServiceNow mechanism when the platform explicitly prohibits direct database operations.

How to eliminate wrong answers

Option A is wrong because 'Data Certification' is designed for periodic verification of CI accuracy by designated certifiers, not for real-time approval of attribute changes. Option B is wrong because database triggers are not supported in ServiceNow's platform architecture; they would require direct database manipulation, which is prohibited and would bypass all business logic and security rules. Option D is wrong because field-level audit only logs changes for reporting purposes and does not enforce an approval workflow; it provides visibility after the fact but does not prevent unauthorized changes.

Full explanation →
316
MCQhard

A user reports that after clicking 'New' on the incident module, the form loads but the 'Category' field is missing. Other users see the field. What is the most likely cause?

A.The field is hidden by a UI policy
B.The field is not in the default form view
C.The user has a personal form layout that removed the field
D.The user's role does not have read access to the field
AnswerC

Personalization can cause a field to be missing for an individual user.

Why this answer

The user's personal form layout can override the default form view, removing fields like 'Category' for that specific user while others see the field. This is a common scenario where a user has customized their own form layout, either intentionally or accidentally, by dragging the field off the form or using the personalization options.

Exam trap

The trap here is that candidates often confuse personal form layouts with UI policies or role-based access, assuming that a missing field for one user must be due to a system-wide rule rather than a user-specific customization.

How to eliminate wrong answers

Option A is wrong because a UI policy that hides the 'Category' field would apply to all users with the same conditions, not just one user. Option B is wrong because if the field were not in the default form view, it would be missing for all users, not just one. Option D is wrong because if the user's role did not have read access to the field, the field would typically be hidden or grayed out for all users with that role, not just a single user.

Full explanation →
317
Multi-Selecteasy

Which THREE of the following are features available in the UI16 interface?

Select 3 answers
A.Favorites list pinned at the top of the navigator
B.Ability to switch between Classic UI and UI16 via a button
C.Application tree view in the navigator
D.High-contrast themes for accessibility
E.Configurable Workspace for agents
AnswersA, C, D

UI16 includes a favorites section at the top.

Why this answer

The UI16 interface includes a Favorites list that can be pinned at the top of the navigator, allowing users to quickly access frequently used modules. This feature is part of the enhanced navigator in UI16, which replaces the classic application tree with a more streamlined, role-based menu.

Exam trap

The trap here is that candidates may confuse the Configurable Workspace (a separate agent interface) with a UI16 navigator feature, or assume a direct UI toggle exists for switching between Classic UI and UI16, when in fact the switch is handled through user preferences or system properties.

Full explanation →
318
Multi-Selecthard

Which THREE of the following are valid ways to customize the form layout for a table in ServiceNow? (Choose three.)

Select 3 answers
A.Using the 'Form Layout' option from the table's context menu to add/remove fields.
B.Using the 'Personalize Form' option to reorder fields for all users.
C.Creating a UI Policy that reorders fields using the 'Reorder' action.
D.Writing a Client Script that sets the visibility of fields.
E.Modifying the 'Form Sections' related list on the table's dictionary entry.
AnswersA, C, E

This updates the sys_ui_form_section table.

Why this answer

The 'Form Layout' option, accessible from the table's context menu (or via the 'Configure' > 'Form Layout' menu), allows administrators to add, remove, and reorder fields on a form. This directly modifies the underlying form XML configuration for the table, making it a standard and valid method for customizing form layout.

Exam trap

The trap here is that candidates often confuse user-level personalization ('Personalize Form') with global configuration ('Form Layout'), or assume that Client Scripts can permanently alter form layout when they only affect runtime behavior.

Full explanation →
319
Matchingmedium

Match each ServiceNow report type to its visual representation.

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

Concepts
Matches

Displays data as vertical bars

Shows proportions of a whole

Trends over time with connected points

Tabular view of data

Compares performance against targets

Why these pairings

Bar charts compare categories using bars, pie charts show proportions as slices, and line charts display trends over time. Common confusions involve swapping bar and pie chart definitions.

Full explanation →
320
MCQhard

An SLA definition has a duration of 8 hours and a schedule of 9am-5pm weekdays. An incident is updated to a state that triggers the SLA at 3pm on Friday. What is the expected breach time?

A.11am Monday
B.7pm Friday
C.9am Monday
D.3pm Monday
AnswerD

2 hours Friday + 6 hours Monday = 8 business hours.

Why this answer

The SLA is defined with a duration of 8 hours and a schedule of 9am-5pm weekdays. The incident triggers the SLA at 3pm on Friday. Since the SLA clock only runs during the defined schedule (9am-5pm weekdays), only 2 hours of the 8-hour duration are consumed on Friday (3pm to 5pm).

The remaining 6 hours must be completed starting at 9am on Monday, resulting in a breach time of 3pm on Monday.

Exam trap

The trap here is that candidates often forget that the SLA clock pauses outside the defined schedule and incorrectly calculate the breach time by adding the full 8 hours to the trigger time, leading to a wrong answer like 11pm Friday or ignoring the weekend entirely.

How to eliminate wrong answers

Option A is wrong because 11am Monday would be only 2 hours into Monday's schedule, totaling 4 hours (2 on Friday + 2 on Monday), not the full 8 hours required. Option B is wrong because 7pm Friday is outside the SLA schedule (9am-5pm), and the SLA clock stops at 5pm, so the breach cannot occur outside the defined schedule. Option C is wrong because 9am Monday is the start of the next scheduled window, but the remaining 6 hours have not yet elapsed, so the breach time must be later.

Full explanation →
321
MCQhard

A large enterprise uses ServiceNow for IT Service Management. They have a custom application that generates incidents automatically from monitoring alerts. The incidents are assigned to the 'Monitoring Queue' group. Recently, the team noticed that some incidents are not being assigned to any group and remain unassigned. Upon investigation, the administrator finds that the assignment rule for the 'Monitoring Queue' group uses a condition 'Category = Network' AND 'Impact = 3'. However, many alerts have 'Category' set to 'Network' but 'Impact' left blank. The administrator needs to ensure that all incidents from monitoring alerts with 'Category = Network' are assigned to the 'Monitoring Queue' group, regardless of impact. What should the administrator do?

A.Modify the existing assignment rule condition to 'Category = Network' OR 'Impact = 3'
B.Modify the existing assignment rule condition to 'Category = Network' only
C.Create a second assignment rule with condition 'Category = Network' and 'Impact is empty'
D.Set a default assignment on the Incident table to assign all unassigned incidents to the Monitoring Queue group
AnswerB

This assigns all incidents with Category=Network to the Monitoring Queue group.

Why this answer

Modifying the assignment rule condition to only check 'Category = Network' ensures that all incidents with that category are assigned to the 'Monitoring Queue' group, regardless of whether 'Impact' is blank or has any other value. Assignment rules in ServiceNow evaluate conditions against the current record; removing the 'Impact = 3' clause eliminates the dependency on that field. This directly addresses the requirement that incidents from monitoring alerts with 'Category = Network' must always be assigned, even when 'Impact' is not populated.

Exam trap

The trap here is that candidates often overcomplicate the solution by adding extra rules or conditions (like checking for empty fields) instead of simplifying the existing condition to remove the unnecessary dependency on the 'Impact' field.

How to eliminate wrong answers

Option A is wrong because changing the condition to 'Category = Network' OR 'Impact = 3' would still leave incidents with 'Category = Network' and a blank 'Impact' unassigned, since a blank 'Impact' does not equal '3' and the OR condition requires at least one operand to be true—but the blank field fails both checks unless the system treats blank as a match, which it does not. Option C is wrong because creating a second assignment rule with 'Category = Network' and 'Impact is empty' would cause duplicate assignment attempts when both rules match (e.g., if an incident has 'Category = Network' and 'Impact = 3'), leading to unpredictable behavior or order-dependent assignment; a single, simpler condition is the correct approach. Option D is wrong because setting a default assignment on the Incident table would apply to all unassigned incidents, not just those from monitoring alerts with 'Category = Network', and would override the intended logic for other groups or scenarios, potentially causing incorrect assignments across the entire table.

Full explanation →
322
MCQeasy

You are a ServiceNow administrator at a mid-sized company. The CMDB currently has over 100,000 CIs, and end users report that the CI search results are slow, often taking more than 10 seconds. The database has been optimized, but the issue persists. You have noticed that many CIs have empty or outdated fields. What is the best course of action to improve search performance without impacting data integrity?

A.Create a scheduled job to delete CIs that have not been updated in 90 days.
B.Disable the full-text search index and rely on basic database indexes.
C.Increase the database connection pool size and restart the instance.
D.Run the CMDB Data Manager to clean up empty fields and reduce index size.
AnswerD

Data Manager can identify and remove empty fields, shrinking the table and improving performance.

Why this answer

The CMDB Data Manager can identify and remove empty or outdated fields from CI records, which reduces the size of the database indexes. Smaller indexes improve search query performance without deleting entire CIs, thus preserving data integrity. This directly addresses the root cause—bloated indexes due to unnecessary data—rather than masking the issue with connection pool changes or risking data loss.

Exam trap

The trap here is that candidates confuse 'data integrity' with 'keeping all data,' leading them to choose Option A (deleting old CIs) instead of recognizing that cleaning empty fields preserves CIs while improving performance.

How to eliminate wrong answers

Option A is wrong because deleting CIs that haven't been updated in 90 days would remove potentially critical configuration items, violating data integrity and breaking dependencies like relationships or CI-based workflows. Option B is wrong because disabling the full-text search index would force searches to rely solely on basic database indexes, which are less efficient for partial or fuzzy matches, likely making search performance worse, not better. Option C is wrong because increasing the database connection pool size and restarting the instance only addresses connection bottlenecks, not the underlying index bloat caused by empty fields; it would not improve search query execution time.

Full explanation →
323
MCQmedium

A company is implementing ServiceNow CMDB and wants to ensure that all CIs in the 'Production' environment are backed up daily. What is the best practice to achieve this?

A.Set the 'cmdb_ci' table's 'Backup' field to true
B.Use the 'Export to XML' feature every night for production CIs
C.Configure the instance's automatic daily backup
D.Create a scheduled data export for only production CMDB records
AnswerC

ServiceNow provides automatic daily backups of the entire instance.

Why this answer

ServiceNow instances have a built-in automatic daily backup feature that captures the entire instance, including all CMDB records and CIs, regardless of environment. This ensures that production CIs are backed up daily without requiring manual configuration or selective exports, aligning with best practices for data protection and disaster recovery.

Exam trap

The trap here is that candidates may confuse CMDB-specific data management (like exporting records) with instance-level backup, or assume that a field or table-level setting can control backup behavior, when ServiceNow's backup is an all-or-nothing instance feature.

How to eliminate wrong answers

Option A is wrong because the 'cmdb_ci' table does not have a 'Backup' field; backup is managed at the instance level, not per CI or table. Option B is wrong because 'Export to XML' is a manual, one-time export tool, not an automated daily backup solution, and it does not guarantee consistent, scheduled backups for production CIs. Option D is wrong because creating a scheduled data export for only production CMDB records is an inefficient, custom approach that bypasses the native, comprehensive instance backup mechanism, and it may miss related data or dependencies.

Full explanation →
324
Multi-Selecteasy

Which TWO of the following are valid properties that can be set on a catalog item to control its behavior in the self-service portal?

Select 2 answers
A.Order
B.Display
C.Show on
D.Read only
E.Mandatory
AnswersA, C

Determines the order of catalog items within a category.

Why this answer

The 'Order' property on a catalog item determines the sequence in which items appear in the self-service portal. This integer-based property allows administrators to control the display order, with lower numbers appearing first, directly influencing user navigation and item prioritization.

Exam trap

The trap here is that candidates often confuse field-level properties like 'Mandatory' or 'Read only' (which apply to variables or questions) with catalog item-level properties that control portal behavior, leading them to select those incorrect options.

Full explanation →
325
MCQeasy

Which table is the base table for all configuration items in the CMDB?

A.cmdb_ci
B.cmdb_ci_storage
C.cmdb_ci_server
D.cmdb_ci_network
AnswerA

cmdb_ci is the base table for all CIs.

Why this answer

The `cmdb_ci` table is the base (parent) table for all configuration items in the CMDB. It contains common attributes such as name, sys_class_name, and operational status, and all specialized CI tables (like `cmdb_ci_server`, `cmdb_ci_storage`, and `cmdb_ci_network`) extend from it via class inheritance. This hierarchical structure ensures that any CI record, regardless of its specific type, has a corresponding row in `cmdb_ci`.

Exam trap

The trap here is that candidates often confuse the base table with a commonly used child table like `cmdb_ci_server` or `cmdb_ci_network`, thinking that because those tables are frequently referenced, they are the root of the CMDB hierarchy.

How to eliminate wrong answers

Option B is wrong because `cmdb_ci_storage` is a child table that extends `cmdb_ci` and is used specifically for storage devices (e.g., SAN, NAS), not as the base table for all CIs. Option C is wrong because `cmdb_ci_server` is a child table that extends `cmdb_ci` and is used specifically for server hardware and virtual machines, not as the base table. Option D is wrong because `cmdb_ci_network` is a child table that extends `cmdb_ci` and is used specifically for network devices (e.g., routers, switches), not as the base table.

Full explanation →
326
MCQmedium

An organization has multiple catalog items that use the same variable set 'Contact Info'. Recently, a change was made to the variable set to add a new variable 'Phone'. However, the existing catalog items that use this variable set do not show the new 'Phone' variable on their forms. The variable set is marked as 'Strictly enforced'? Actually, the variable set is not strictly enforced. The administrator expects the new variable to appear automatically on the items. What should the administrator do?

A.Publish the variable set again from the application publisher.
B.Delete the variable set and recreate it as a new one and re-associate all items.
C.Set the variable set to 'Strictly enforced' to force the new variable to appear.
D.For each catalog item, use the 'Update Variable Set' option to synchronize the changes.
AnswerD

This action updates the item's local copy of the variable set to include the new variable.

Why this answer

When a variable set is not strictly enforced, changes made to the variable set (such as adding a new variable) are not automatically propagated to catalog items that already use it. The administrator must use the 'Update Variable Set' action on each catalog item to synchronize the item's form with the updated variable set. This action refreshes the item's copy of the variable set variables, making the new 'Phone' variable appear.

Exam trap

The trap here is that candidates assume variable set changes are automatically reflected in all catalog items, but they overlook the distinction between strictly enforced and non-strictly enforced variable sets, where only strictly enforced sets propagate changes automatically.

How to eliminate wrong answers

Option A is wrong because the application publisher is used to publish application scoped updates, not to propagate variable set changes to catalog items; variable sets are not published via the application publisher. Option B is wrong because deleting and recreating the variable set is unnecessarily destructive and time-consuming; the correct approach is to synchronize existing items using the 'Update Variable Set' option. Option C is wrong because setting the variable set to 'Strictly enforced' would force all items to always reflect the latest variable set definition, but the administrator expects the new variable to appear automatically without changing the enforcement mode; the issue is that the items have not been synchronized, not that the variable set is not strictly enforced.

Full explanation →
327
Drag & Dropmedium

Drag and drop the steps to configure an outbound email account in ServiceNow 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

Outbound email accounts require SMTP type and proper server details for sending emails.

Full explanation →
328
Multi-Selecteasy

Which TWO are best practices for creating dashboards in ServiceNow?

Select 2 answers
A.Share the dashboard with all users by default.
B.Use widgets instead of reports.
C.Use multiple data sources for a single dashboard.
D.Use filters to allow interactive data exploration.
E.Add only necessary reports to avoid clutter.
AnswersD, E

Filters enhance user experience by enabling dynamic data viewing.

Why this answer

Filters enable interactive data exploration by allowing users to dynamically refine dashboard data without modifying the underlying reports or widgets. This aligns with ServiceNow's best practice of empowering end-users to self-serve insights while maintaining a clean, focused dashboard layout.

Exam trap

The trap here is that candidates often confuse 'using multiple data sources' with 'using multiple reports from different tables'—ServiceNow supports the latter, but the question specifically tests the misconception that mixing data sources (e.g., different database connections) is a best practice, which it is not.

Full explanation →
329
MCQeasy

What is the default behavior of an ACL if no ACL record exists for a given operation?

A.Log the attempt and allow.
B.Prompt the user for confirmation.
C.Deny access.
D.Allow access.
AnswerC

ServiceNow denies access if no ACL record exists.

Why this answer

The default behavior of an ACL is to deny access if no ACL record exists. This is a security measure. Therefore option C is correct.

Options A, B, and D are incorrect because they do not reflect the default deny behavior.

Full explanation →
330
MCQeasy

A user reports that a custom UI Action button labeled 'Escalate' has disappeared from the incident form after a recent upgrade. The administrator checks the UI Action record and confirms that it is active, has no conditions defined, and is associated with the Incident table. The UI Action is set to appear in the context menu and form button. The administrator also confirms that no UI Policies or client scripts are hiding it. What should the administrator check next to resolve the issue?

A.Check the form layout for the incident form view to ensure the UI Action is included.
B.Check if there is a condition on the UI Action that evaluates to false.
C.Check the application scope to ensure the UI Action is in the correct scope.
D.Check the access controls (ACLs) for the UI Action.
AnswerA

UI Actions must be placed in the form layout to appear; after upgrades, layout assignments can sometimes be lost.

Why this answer

The UI Action is active, has no conditions, and is associated with the Incident table, so it should appear. However, after an upgrade, the form layout may have been reset or the UI Action may not be placed in the desired form view. The administrator must check the form layout for the specific incident form view (e.g., 'Default view') to ensure the UI Action is added as a form button or context menu item, as UI Actions must be explicitly included in the form layout to appear on the form.

Exam trap

The trap here is that candidates often assume a UI Action will automatically appear on the form if it is active and has no conditions, but they overlook the requirement that UI Actions must be explicitly added to the form layout for the specific form view.

How to eliminate wrong answers

Option B is wrong because the administrator already confirmed that no conditions are defined on the UI Action, so checking for a condition that evaluates to false is irrelevant. Option C is wrong because the UI Action is associated with the Incident table and is active, and scope issues would typically prevent the UI Action from being visible or functional, but the administrator has not indicated any scope-related symptoms; moreover, UI Actions are not scoped to applications in the same way as other records, and the upgrade would not change the scope of an existing UI Action. Option D is wrong because access controls (ACLs) control who can see or use a UI Action based on roles, but the administrator has not mentioned any role-based restrictions, and the UI Action is active and has no conditions; ACLs would not cause a UI Action to disappear from the form unless the user lacks the required role, but the question states the user reports it disappeared after an upgrade, implying a configuration change rather than a permission issue.

Full explanation →
331
Multi-Selectmedium

Which TWO are valid methods to add a new form section?

Select 2 answers
A.Creating a new UI page
B.Modifying the table's XML definition
C.Adding a section in the sys_ui_section table
D.Using an application file
E.Using form designer
AnswersC, E

Directly inserting a record in the sys_ui_section table creates a section.

Why this answer

The sys_ui_section table stores the definitions of form sections in ServiceNow. Adding a record directly to this table is a valid method to create a new section on a form. Option E is correct because the Form Designer provides a graphical interface to add, remove, and rearrange sections on a form without manual table manipulation.

Exam trap

The trap here is that candidates often confuse modifying a table's XML definition (Option B) with adding a form section, but XML changes affect the form's structure at a lower level and are not the standard method for section creation.

Full explanation →
332
MCQmedium

A notification is not sending emails to the intended recipients. The notification's 'Who will receive' tab is set to 'Event creator' and the event is triggered by a business rule. However, the email recipient list is empty. What is the most likely cause?

A.The notification is inactive
B.The email template is missing the recipient field
C.The system property 'glide.email.smtp.port' is set incorrectly
D.The event was created by a system account, not a real user
AnswerD

System accounts like 'guest' have no valid email, resulting in empty recipient list.

Why this answer

When a notification's 'Who will receive' tab is set to 'Event creator' and the event is triggered by a business rule, the system resolves the recipient by looking up the user who triggered the event. If the event was created by a system account (e.g., 'system' or 'guest'), that account has no valid email address, resulting in an empty recipient list. This is the most likely cause because the notification is otherwise correctly configured and active.

Exam trap

The trap here is that candidates often assume the notification is inactive or misconfigured, but the real issue is that system accounts lack email addresses, causing the recipient list to be empty despite the notification being active and correctly configured.

How to eliminate wrong answers

Option A is wrong because if the notification were inactive, it would not attempt to send at all, but the question states the email recipient list is empty, implying the notification is active but fails to find recipients. Option B is wrong because the email template is used for the email body and subject, not for determining recipients; the recipient list is controlled by the 'Who will receive' tab and the event creator. Option C is wrong because an incorrect SMTP port would cause a delivery failure or error, not an empty recipient list; the recipient list is built before the SMTP connection is attempted.

Full explanation →
333
Multi-Selecteasy

An organization is importing help desk tickets from a legacy system using ServiceNow Import Sets. The import runs successfully, but no records are created in the Incident table. Which two steps should the administrator verify to resolve this issue?

Select 2 answers
A.Confirm the Data Source is associated with the Import Set Row.
B.Verify the Transform Map is active and mapped to the correct target table.
C.Ensure the import source is an email integration.
D.Review the Import Set Row condition field to ensure it is not set to 'Skip'.
E.Check that the Import Set table has a 'Staging Table' defined.
AnswersA, B

The Data Source links the Import Set to the Transform Map; without it, transformation does not occur.

Why this answer

The Data Source must be associated with the Import Set Row to define how the incoming data is parsed and mapped. Without this association, the Import Set cannot process the data correctly, even if the import runs without errors. This is a fundamental requirement in ServiceNow's import architecture.

Exam trap

ServiceNow often tests the distinction between Import Set Row and Transform Map configuration; the trap here is that candidates may focus on the Import Set Row's processing status (Option D) instead of the Transform Map's condition field, or assume a missing staging table (Option E) when the Import Set table itself serves that role.

Full explanation →
334
Multi-Selecthard

A company has a large CMDB and wants to improve query performance on CI tables. Which two actions would help achieve this? (Choose two.)

Select 2 answers
A.Adding indexes to frequently queried columns.
B.Disabling all CMDB audit history.
C.Increasing the database heap size.
D.Using the CI Cache feature.
E.Archiving historical data from the CI table.
AnswersA, E

Indexes improve query performance by allowing faster data retrieval.

Why this answer

Adding indexes to frequently queried columns (Option A) improves query performance by allowing the database to locate rows more efficiently, reducing full table scans. This is a standard database optimization technique that directly addresses slow CI table queries in ServiceNow.

Exam trap

The trap here is that candidates often confuse application-layer caching (CI Cache) with database-level query optimization, leading them to select Option D instead of recognizing that indexes and archiving are the correct database-focused actions.

Full explanation →
335
MCQmedium

Your company uses ServiceNow for IT Service Management. The 'incident' table has a custom 'create' ACL that restricts creation of incidents to users with the 'snc_internal' role. However, external users with the 'snc_external' role should also be able to create incidents via a portal. The portal uses a REST message that authenticates as a specific integration user. The integration user has the 'snc_internal' role. Despite the REST API call being successful, external users report that they cannot submit incidents through the portal. The system logs show that the REST API call returns a success, but the incident record is not created. What is the most likely cause?

A.The integration user's session has expired during the request.
B.The portal widget is using a different table name in the API call.
C.The ACL is evaluated against the portal user, who lacks the 'snc_internal' role.
D.The REST API endpoint is mapped to the wrong table.
AnswerC

Correct: In portal, the user's session is used for ACL checks.

Why this answer

ServiceNow ACLs are evaluated against the user who initiated the request, not the integration user making the REST API call. In this scenario, the portal widget executes under the context of the portal user (who lacks 'snc_internal'), so the 'create' ACL on the 'incident' table checks that user's roles, not the integration user's roles. Even though the REST message authenticates as an integration user with 'snc_internal', the system logs a success for the API call itself, but the ACL evaluation fails silently when the record creation is attempted, resulting in no incident record being created.

Exam trap

The trap here is that candidates assume the ACL is evaluated against the authenticated integration user (the REST message's credentials) rather than the end-user who triggered the portal action, leading them to overlook the role mismatch between the portal user and the ACL requirement.

How to eliminate wrong answers

Option A is wrong because if the integration user's session had expired, the REST API call would return an authentication error (e.g., HTTP 401), not a success status. Option B is wrong because using a different table name in the API call would cause a different error (e.g., 'Table not found' or HTTP 404), not a silent failure with a success response. Option D is wrong because if the REST API endpoint were mapped to the wrong table, the API call would either fail with an error or create a record in the wrong table, but the logs show a success response and no record creation, which points to an ACL issue, not a mapping issue.

Full explanation →
336
Multi-Selectmedium

A system administrator wants to prevent users from changing the value of a field after the record is saved. Which two features can be used to enforce this? (Choose two.)

Select 2 answers
A.Business Rule (before query)
B.Data Policy (update)
C.Client Script (onSubmit)
D.UI Policy (on load)
E.Dictionary (read only)
AnswersB, E

A Data Policy can enforce read-only on update, preventing changes after initial save.

Why this answer

(Data Policy (update)) is correct because a Data Policy with an 'update' condition can enforce that a field's value cannot be changed once the record is saved. It runs server-side during the update operation and can prevent the update from completing if the field value differs from the stored value. Option E (Dictionary (read only)) is correct because setting the 'Read only' attribute on a dictionary entry makes the field non-editable on forms and also prevents updates via web services or other server-side operations, effectively locking the value after the record is saved.

Exam trap

The trap here is that candidates often confuse client-side controls (Client Scripts and UI Policies) with server-side enforcement in ServiceNow, mistakenly believing that a client-side onSubmit script or UI Policy can reliably prevent field changes, when in fact only server-side mechanisms like Data Policies and Dictionary read-only settings provide true enforcement.

Full explanation →
337
MCQeasy

Which import set transform operation should be used to prevent duplicate records from being created when the source data contains a unique identifier column?

A.Default value
B.Ignore
C.Coalesce
D.Run script
AnswerC

Coalesce uses a field to match existing records.

Why this answer

(Coalesce) is correct because the Coalesce transform operation in ServiceNow import sets is specifically designed to prevent duplicate records by matching on a unique identifier column. When configured, Coalesce checks if a record with the same value in the specified field already exists in the target table; if it does, the import updates the existing record instead of creating a duplicate.

Exam trap

ServiceNow often tests the misconception that 'Ignore' or 'Default value' can prevent duplicates, but the trap is that only Coalesce performs the actual deduplication by matching on a unique identifier, while the other options handle field-level transformations or exclusions without any record-matching logic.

How to eliminate wrong answers

Option A (Default value) is wrong because it only sets a default value for a field when the source data is empty, and does not perform any deduplication logic. Option B (Ignore) is wrong because it simply skips the field during import, meaning the field is not mapped or processed, which does not prevent duplicate records. Option D (Run script) is wrong because it allows custom scripting for field transformation but does not inherently provide deduplication; while a script could be written to check for duplicates, the Coalesce operation is the dedicated, built-in mechanism for this purpose.

Full explanation →
338
Multi-Selectmedium

Which THREE factors can cause a catalog item to not appear in the service catalog for a user?

Select 3 answers
A.Item has a price
B.User's department is not in the item's entitlement
C.Item's category is not visible to user
D.User does not have the catalog item role
E.Item is inactive
AnswersC, D, E

If the category is not visible (e.g., due to role restrictions), items in that category are hidden.

Why this answer

The visibility of a catalog item is directly tied to the visibility of its parent category. If a category is not visible to a user (e.g., due to the 'Visible' flag being unchecked or the category being restricted by user criteria), all items within that category will be hidden from the user's service catalog view, regardless of the item's own visibility settings.

Exam trap

ServiceNow often tests the misconception that a price or department field directly controls catalog visibility, when in fact visibility is determined by the category's visibility flag and user criteria, not by pricing or departmental attributes.

Full explanation →
339
Multi-Selectmedium

Which three conditions must be met for an SLA to start automatically when a new incident is created? (Choose three.)

Select 3 answers
A.The incident matches the SLA's conditions.
B.The SLA definition is active.
C.The SLA definition is on the 'incident' table or a parent table.
D.The SLA schedule includes the current time.
E.The incident has a 'watch_list' set.
AnswersA, B, C

The condition filter must evaluate to true for the incident.

Why this answer

An SLA timer will only start automatically for a new incident if the incident record matches the conditions defined in the SLA definition. These conditions are typically set as a filter condition on the SLA Definition record (e.g., 'Priority is 1' or 'Category is Network'). If the incident does not satisfy these conditions, the SLA will not be applied or started.

Exam trap

ServiceNow often tests the misconception that the SLA schedule must include the current time for the SLA to start, but the schedule only governs when the clock ticks, not whether the SLA is initiated.

Full explanation →
340
MCQhard

A manager requests a report showing the average time to resolve incidents, grouped by assignment group, for the last month. The administrator creates a report on the Incident table using a bar chart with a 'Group By' on Assignment group and a 'Aggregate' on Resolved time (duration). The report displays an average that seems too low. Upon investigation, the administrator notices that incidents with very long resolution times (e.g., over 30 days) are not included in the report. The report filter is set to 'Active = false' and 'Resolved time is not empty'. The administrator suspects the time filter is incorrect. What is the most likely cause of the missing long-duration incidents?

A.The average calculation is using median instead of mean.
B.The report is based on a saved search that excludes incidents with 'Closed' state.
C.The report filter excludes incidents with state 'Resolved'.
D.The report uses a relative time filter that filters on the 'Created' date instead of the 'Resolved' date, excluding older incidents that were resolved in the last month.
AnswerD

Relative time filters default to the current date; if set to 'Created' in last month, it misses incidents created earlier but resolved recently.

Why this answer

The report uses a relative time filter that defaults to filtering on the 'Created' date rather than the 'Resolved' date. This means only incidents created within the last month are considered, even if they were resolved later. Incidents with very long resolution times (e.g., over 30 days) that were created before the filter window but resolved in the last month are excluded, causing the average to appear too low.

Exam trap

The trap here is that candidates assume the time filter automatically applies to the resolution date when the report is about resolved incidents, but ServiceNow defaults to the 'Created' date unless explicitly changed, causing older resolved incidents to be missed.

How to eliminate wrong answers

Option A is wrong because the report explicitly uses an 'Aggregate' on Resolved time with a bar chart, which defaults to average (mean) unless median is selected; the issue is missing data, not the aggregation method. Option B is wrong because the report filter is set directly on the Incident table, not based on a saved search; a saved search would appear in the report source, and the filter 'Active = false' and 'Resolved time is not empty' already includes resolved and closed incidents. Option C is wrong because the filter 'Active = false' includes incidents with state 'Resolved' (since 'Active' is a boolean field that is false for both 'Resolved' and 'Closed' states); excluding 'Resolved' would require a specific state condition, not the 'Active' field.

Full explanation →
341
MCQhard

After upgrading to a new version, a CMDB administrator notices that many CI records have been flagged as 'unverified' and their operational status changed. What is the most likely cause?

A.A scheduled job from the Discovery application marked CIs as unverified.
B.The IRE was reconfigured during upgrade.
C.The CMDB Data Manager job ran with incorrect parameters.
D.The identification and reconciliation rules were updated.
AnswerA

Discovery can flag CIs as unverified if it fails to identify them.

Why this answer

After a version upgrade, the Discovery application's scheduled jobs (e.g., 'Discovery Status Update' or 'Operational Status Update') automatically flag CIs as 'unverified' and reset their operational status to 'In Use' or 'Unverified' to force re-validation. This is a built-in safety mechanism to ensure that CIs discovered under the old version's logic are re-assessed under the new version's rules, preventing stale or incorrectly reconciled data from persisting.

Exam trap

The trap here is that candidates assume the IRE or CMDB Data Manager is responsible for status changes, when in fact the Discovery application's post-upgrade scheduled job is the specific mechanism that resets verification and operational status to force re-validation.

How to eliminate wrong answers

Option B is wrong because the Identification and Reconciliation Engine (IRE) is not reconfigured during an upgrade; its configuration is preserved, and changes to IRE behavior require explicit manual updates to identification rules or reconciliation engine properties. Option C is wrong because the CMDB Data Manager job does not set CIs as 'unverified' or change operational status; it handles data normalization, duplicate detection, and CI relationship maintenance, not status flags. Option D is wrong because updating identification and reconciliation rules would affect how CIs are matched and merged, but would not directly cause a bulk flagging of existing CIs as 'unverified' or change their operational status; that behavior is specific to Discovery's post-upgrade validation jobs.

Full explanation →
342
MCQeasy

A Service Catalog item has a variable that asks for the user's manager's email. The variable type is 'Email'. When the user submits the item, the manager should receive a notification. How should the variable be configured to ensure the email is valid?

A.Set the variable as 'Read only' and rely on data from sys_user table.
B.Add a regular expression in the variable's 'Regex' field.
C.Use a 'String' variable and add a client script to check format.
D.Use the 'Email' variable type; it includes validation.
AnswerD

The Email type validates the format upon submission.

Why this answer

The 'Email' variable type in Service Catalog automatically validates that the entered value conforms to a standard email format (e.g., user@domain.com). This built-in validation ensures the manager's email is syntactically correct before the notification is triggered, without requiring additional scripting or regex. Option D is correct because it leverages this native validation, which is the simplest and most reliable method.

Exam trap

The trap here is that candidates may overthink the solution and choose a more complex option (like regex or client scripts) instead of recognizing that the platform's native 'Email' variable type already provides the required validation.

How to eliminate wrong answers

Option A is wrong because setting the variable as 'Read only' would prevent the user from entering the manager's email, and relying on data from sys_user table does not guarantee the manager's email is provided or valid for this specific request. Option B is wrong because while a regular expression can validate email format, it is redundant and less maintainable than using the built-in 'Email' type validation, and it does not handle all edge cases (e.g., internationalized email addresses) as robustly. Option C is wrong because using a 'String' variable with a client script to check format is unnecessarily complex, prone to client-side bypass, and duplicates the validation that the 'Email' type already provides natively.

Full explanation →
343
MCQeasy

A ServiceNow administrator wants to share a report with the Sales team. The Sales team members do not have direct read access to the underlying table, but they need to see the report results. Which action should the administrator take?

A.Schedule the report to be sent via email to the Sales team daily.
B.Add the report to a dashboard and share the dashboard with the Sales team, ensuring the dashboard's 'Use dashboard owner's security context' option is enabled.
C.Export the report to PDF and email it manually.
D.Set the report's 'Share with' field to the Sales team group.
AnswerB

Dashboards can be configured to use the owner's security context, allowing viewers to see data without having direct table access.

Why this answer

Enabling the 'Use dashboard owner's security context' option on a shared dashboard allows users without direct read access to the underlying table to view the report results. This works by executing the report queries under the security context of the dashboard owner, bypassing the viewers' lack of table permissions while still respecting the owner's access rights.

Exam trap

The trap here is that candidates often assume sharing a report or dashboard is sufficient, but they overlook the critical requirement of underlying table access, which is bypassed only by the 'Use dashboard owner's security context' option, not by simple sharing or export methods.

How to eliminate wrong answers

Option A is wrong because scheduling a report via email sends a static snapshot of the data at that moment, but the email itself does not grant read access to the underlying table; the recipients still cannot view the live report or interact with it in the platform. Option C is wrong because exporting to PDF and emailing it manually is a manual, non-scalable workaround that does not leverage ServiceNow's sharing capabilities and still does not provide direct access to the report or its underlying data within the platform. Option D is wrong because setting the report's 'Share with' field to the Sales team group only shares the report object, but if the group members lack read access to the underlying table, they will receive an error or see no data when trying to view the report.

Full explanation →
344
MCQmedium

Refer to the exhibit. A UI policy is defined with the above script condition. Which of the following is correct?

A.The UI policy will only apply if the 'type' field is changed.
B.The UI policy must run on server-side to use g_form.
C.The script is invalid because UI policies cannot use script conditions.
D.The UI policy runs on client-side and makes serial_number mandatory when type is hardware.
AnswerD

UI policies are client-side by default; the script condition is evaluated on the client.

Why this answer

UI policies run on the client side (in the browser) and can use script conditions to evaluate field values. In this case, the script condition checks if the 'type' field equals 'hardware', and if true, the UI policy makes the 'serial_number' field mandatory. This is a standard client-side behavior for UI policies.

Exam trap

The trap here is that candidates often confuse UI policies (client-side) with business rules (server-side) and incorrectly assume that 'g_form' requires server-side execution, when in fact UI policies are client-side and use 'g_form' natively.

How to eliminate wrong answers

Option A is wrong because UI policies do not require the 'type' field to be changed; they evaluate the condition whenever the form loads or any field changes, depending on the 'onChange' setting, and here the condition is evaluated on form load as well. Option B is wrong because UI policies run on the client side by default, and 'g_form' is a client-side API, not a server-side one; server-side scripts use 'g_scratchpad' or business rules. Option C is wrong because UI policies can indeed use script conditions; the script condition is a valid and common feature of UI policies, allowing complex logic beyond simple field comparisons.

Full explanation →
345
MCQmedium

Refer to the exhibit. A business rule has this script and is set to run on 'before insert' and 'before query'. When a user creates a new incident and sets the assignment_group to 'Network', after saving the assignment_group displays 'Help Desk'. What is the most likely cause?

A.The script runs on 'before query' and overwrites the value when the record is retrieved
B.The script should use setValue instead of setDisplayValue
C.The setDisplayValue method is incorrect for this field
D.The script runs on 'before insert' and overwrites the user's selection
AnswerA

The 'before query' action runs every time the record is loaded, setting the assignment_group to 'Help Desk' regardless of saved value.

Why this answer

The script runs on 'before query', which executes when the record is retrieved from the database. Since the business rule is set to run on both 'before insert' and 'before query', the 'before query' phase overwrites the assignment_group value to 'Help Desk' after the user saves the record and it is retrieved for display. This explains why the user sees 'Help Desk' instead of 'Network' after saving.

Exam trap

The trap here is that candidates assume the 'before insert' phase is the only one affecting the saved value, overlooking that 'before query' runs on retrieval and can change what the user sees after saving.

How to eliminate wrong answers

Option B is wrong because setDisplayValue is the correct method for setting a display value on a reference field like assignment_group; setValue would set the sys_id, not the display name. Option C is wrong because setDisplayValue is valid for reference fields and is not inherently incorrect; the issue is the script's execution phase, not the method itself. Option D is wrong because if the script ran only on 'before insert', it would overwrite the user's selection before the record is saved, but the user would see 'Help Desk' immediately upon saving, not after saving; the fact that the value changes after saving points to the 'before query' phase.

Full explanation →
346
Multi-Selecteasy

Which TWO options are valid ways to schedule a report in ServiceNow?

Select 2 answers
A.Schedule to run hourly
B.Schedule to run immediately
C.Schedule to run once at a specific time
D.Schedule to run only when conditions change
E.Schedule to run weekly
AnswersC, E

One-time scheduling is valid.

Why this answer

ServiceNow allows scheduling a report to run once at a specific date and time, which is useful for one-time deliveries or ad-hoc reporting needs. This is configured in the report's Schedule tab by setting the frequency to 'Once' and specifying the exact run time.

Exam trap

The trap here is that candidates often confuse 'scheduling' with 'running on demand' or 'triggering based on conditions', but ServiceNow only supports time-based scheduling (once, daily, weekly, monthly) for reports, not immediate execution or condition-based triggers.

Full explanation →
347
MCQmedium

A company uses Discovery to populate the CMDB. After a recent change, some CIs are incorrectly classified as 'Network Gear' instead of 'Server'. What is the most efficient way to correct the classification for these specific CIs?

A.Delete the CIs and let Discovery recreate them.
B.Manually change the 'Class' field on each CI.
C.Update the Discovery classification pattern and re-run Discovery on the affected IPs.
D.Run the 'Identify CI' probe again.
AnswerC

Correcting the pattern and re-running Discovery will reclassify the CIs correctly and prevent future issues.

Why this answer

Discovery classification patterns define how CIs are categorized based on probe results. Updating the pattern to correctly identify the affected CIs and re-running Discovery on their IPs ensures that the classification is corrected at the source, preventing future misclassification without manual intervention or data loss.

Exam trap

The trap here is that candidates may think re-running the 'Identify CI' probe (Option D) will fix classification, but that probe only identifies CIs based on existing patterns and does not correct misclassification caused by a flawed pattern.

How to eliminate wrong answers

Option A is wrong because deleting CIs removes their relationships and historical data, and Discovery may recreate them with the same incorrect classification if the pattern is not fixed. Option B is wrong because manually changing the 'Class' field on each CI is inefficient for multiple CIs and does not address the root cause, so the misclassification will recur on the next Discovery run. Option D is wrong because the 'Identify CI' probe only identifies CIs but does not correct classification patterns; it would re-apply the same incorrect logic.

Full explanation →
348
MCQmedium

A CMDB administrator wants to ensure that all changes to CI records are tracked with the user who made the change. What system property must be set to true?

A.glide.record.audit
B.glide.cmdb.track.ci.changes
C.glide.cmdb.audit.enable
D.glide.sys.audit.all
AnswerA

Setting glide.record.audit to true enables auditing for all tables, including CMDB.

Why this answer

The `glide.record.audit` system property, when set to true, enables auditing for all records in the system, including Configuration Items (CIs) in the CMDB. This ensures that any change to a CI record is tracked with the user who made the modification, as required by the CMDB administrator. The property is a global audit toggle that applies to all tables, making it the appropriate choice for tracking CI changes.

Exam trap

The trap here is that candidates often confuse the global audit property with non-existent CMDB-specific properties like `glide.cmdb.audit.enable` or `glide.cmdb.track.ci.changes`, assuming that CI auditing requires a separate setting rather than the global `glide.record.audit` property.

How to eliminate wrong answers

Option B is wrong because `glide.cmdb.track.ci.changes` is not a valid system property in ServiceNow; there is no such property for tracking CI changes specifically. Option C is wrong because `glide.cmdb.audit.enable` is also not a valid system property; ServiceNow does not have a CMDB-specific audit property, as auditing is controlled at the table or global level. Option D is wrong because `glide.sys.audit.all` is not a valid system property; the correct global audit property is `glide.record.audit`, and `glide.sys.audit.*` properties do not exist in the platform.

Full explanation →
349
MCQmedium

Refer to the exhibit. What is the purpose of the 'condition' field in this discovery probe?

A.It defines the condition under which the probe triggers.
B.It specifies the condition for identifying duplicates.
C.It filters which discovered CIs should be updated by this probe.
D.It limits the probe to only query the database for existing records matching the condition.
AnswerC

The condition restricts the probe's updates to CIs matching the criteria.

Why this answer

In ServiceNow discovery probes, the 'condition' field is used to filter which discovered CIs should be updated by the probe. It acts as a predicate that evaluates against the discovered CI's attributes; only CIs that match the condition will have their fields updated by the probe's actions. This prevents the probe from overwriting CIs that do not meet specific criteria, ensuring targeted and accurate CI updates.

Exam trap

The trap here is that candidates often confuse the 'condition' field with the probe's trigger condition or with the identification rule, leading them to select option A or B, when in fact it is a post-discovery filter for updates.

How to eliminate wrong answers

Option A is wrong because the condition field does not define when the probe triggers; that is controlled by the probe's trigger schedule or the discovery process itself. Option B is wrong because duplicate identification is handled by the identification and reconciliation engine (IRE) using CI identifiers, not by the probe's condition field. Option D is wrong because the condition field does not limit database queries; it filters which discovered CIs are updated after the probe has already retrieved data from the target source.

Full explanation →
350
MCQhard

Refer to the exhibit. A ServiceNow administrator configures a catalog item for software installations. The flow logic is as shown. When a user requests 'Adobe Photoshop', the approval goes to Software Approvers instead of IT Management. What is the most likely cause?

A.The variable u_software_name is not being passed to the flow correctly.
B.The condition uses '==' which is case-sensitive; the user typed 'adobe photoshop' in lowercase.
C.The approval group 'IT Management' is not a valid group.
D.The flow is running in an older version that does not support conditions.
AnswerB

Why this answer

The condition in the flow uses '==' which is case-sensitive in ServiceNow. If the user typed 'adobe photoshop' in lowercase, it will not match the condition expecting 'Adobe Photoshop' (with capital letters), so the approval defaults to the 'Software Approvers' group instead of 'IT Management'. ServiceNow string comparisons with '==' are case-sensitive, unlike the '=' operator which is case-insensitive.

Exam trap

The trap here is that candidates often assume all string comparisons in ServiceNow are case-insensitive, overlooking that '==' is case-sensitive, and they may choose option A (variable passing issue) without considering the case mismatch.

How to eliminate wrong answers

Option A is wrong because if the variable u_software_name were not being passed correctly, the flow would likely fail or produce a different error, not simply route to the wrong approval group. Option C is wrong because if the approval group 'IT Management' were invalid, the flow would generate an error or fail to assign the approval, not silently route to 'Software Approvers'. Option D is wrong because conditions are fully supported in all modern versions of ServiceNow; older versions do not lack condition support, and the behavior described is due to case sensitivity, not version limitations.

Full explanation →
351
MCQeasy

Based on the exhibit, who will receive the email notification?

A.No one receives the email.
B.The caller only.
C.The assigned user only.
D.Both assigned user and caller.
AnswerB

Caller is set and receives.

Why this answer

The exhibit shows that the 'Caller' checkbox is selected in the notification's 'Who will receive' configuration, while the 'Assigned user' checkbox is not selected. In ServiceNow, when only the 'Caller' option is checked, the notification is sent exclusively to the user listed as the caller on the record, regardless of who the record is assigned to.

Exam trap

The trap here is that candidates often assume that the assigned user always receives notifications by default, but ServiceNow requires explicit selection of the 'Assigned user' checkbox in the notification record for that to happen.

How to eliminate wrong answers

Option A is wrong because the notification is configured with the 'Caller' checkbox selected, which means at least one recipient (the caller) will receive the email. Option C is wrong because the 'Assigned user' checkbox is not selected in the exhibit, so the assigned user will not receive the notification. Option D is wrong because both checkboxes would need to be selected for both the caller and assigned user to receive the notification; only the 'Caller' checkbox is selected.

Full explanation →
352
MCQmedium

A large enterprise uses ServiceNow for IT service management. The Service Catalog includes a 'New Employee Setup' bundle that contains multiple catalog items such as 'Create AD Account', 'Assign Laptop', and 'Provision Email'. Each catalog item has its own workflow. Recently, the 'Assign Laptop' catalog item has been failing intermittently. The workflow that runs for this item includes an approval step and several tasks. When the workflow fails, the requested item shows a state of 'Work in Progress' and the workflow context shows an error: 'The workflow could not find the activity named: Approve Laptop'. The workflow has an approval activity named 'Approve Laptop' and it is active. The approval activity is set to 'Run as' the workflow user. The workflow is associated with the catalog item correctly. The failure occurs only when the request is submitted by users who are not in the 'IT' role. What is the most likely cause of the failure?

A.The 'Approve Laptop' approval activity is deactivated.
B.The catalog item is not correctly linked to the workflow.
C.The approval activity requires a specific approval group that is not defined.
D.The workflow user does not have sufficient rights to execute the approval activity when the requester lacks the 'IT' role.
AnswerD

Correct: The workflow runs under the context of the workflow user, and if that user cannot access the activity due to ACLs, the workflow fails.

Why this answer

The error 'The workflow could not find the activity named: Approve Laptop' indicates that the workflow engine cannot locate the approval activity at runtime. Since the approval activity is set to 'Run as' the workflow user, and the failure occurs only when the requester lacks the 'IT' role, the most likely cause is that the workflow user does not have sufficient rights (e.g., missing the 'approver' role or ACL permissions) to execute the approval activity when the requester's role triggers a security context restriction. This is a common permission issue in ServiceNow workflows where the execution context of the activity depends on the requester's roles.

Exam trap

The trap here is that candidates assume the error 'could not find the activity' always means the activity is deactivated or missing, but ServiceNow can also throw this error when the activity exists but the execution context (user permissions) prevents the engine from accessing it, especially with 'Run as' settings and role-based restrictions.

How to eliminate wrong answers

Option A is wrong because the question explicitly states the approval activity named 'Approve Laptop' is active, so deactivation is not the issue. Option B is wrong because the workflow is correctly associated with the catalog item (the error is about a missing activity, not a missing workflow link), and the workflow runs partially (shows 'Work in Progress'). Option C is wrong because the error message specifically says 'could not find the activity', not that an approval group is missing; a missing approval group would cause a different error (e.g., 'No approvers available') or the activity would still be found.

Full explanation →
353
MCQeasy

A company wants to allow users to request software licenses through the service catalog. The request requires approval from the manager and then automatically creates a task for the procurement team. Which configuration option should be used?

A.Record Producer
B.Order Guide
C.Variable Set
D.Catalog Item with Approval and Task
AnswerD

A catalog item can be configured with an approval process and a task template to create a task automatically.

Why this answer

A Catalog Item can be configured with an approval flow (manager approval) and a task creation step for the procurement team, directly fulfilling the requirement. Record Producers create records from catalog requests but lack built-in approval and task generation. Order Guides bundle items but don't handle approvals or tasks.

Variable Sets collect data but don't define workflow actions.

Exam trap

The trap here is that candidates confuse Record Producers with Catalog Items, assuming Record Producers can handle approvals and tasks, but Record Producers are strictly for record creation without workflow automation.

How to eliminate wrong answers

Option A is wrong because a Record Producer is designed to create records (e.g., incidents or change requests) from a catalog request, not to manage approvals or generate tasks for procurement. Option B is wrong because an Order Guide is used to group multiple catalog items into a single order, but it does not provide approval workflows or task creation. Option C is wrong because a Variable Set is a reusable collection of variables for gathering user input, but it has no inherent approval or task generation capabilities.

Full explanation →
354
MCQeasy

A system administrator is configuring ACLs for a custom table 'u_employee_info' that should be visible to all employees but editable only by HR managers. The administrator creates two ACLs: one read ACL for the 'employee' role with type 'read', and one write ACL for the 'hr_manager' role with type 'write'. However, employees with the 'employee' role report that they cannot see any records in the table. The administrator verifies that the ACLs are active. What is the most likely issue?

A.The read ACL is set to type 'record' instead of 'table'.
B.The table 'u_employee_info' has no 'read' ACL defined by default, so access is denied.
C.The write ACL is overriding the read ACL because it has a higher priority.
D.The read ACL is set to require a role 'snc_employee' instead of 'employee'.
AnswerD

Correct: Role names must exactly match.

Why this answer

ServiceNow ACLs are role-based, and the read ACL must specify the exact role name as it exists in the system. If the role is named 'snc_employee' but the ACL references 'employee', the ACL will not match, and the system will deny read access by default. The administrator likely misconfigured the role name in the ACL condition.

Exam trap

The trap here is that candidates assume ACLs are inherited or that a write ACL implicitly grants read access, but ServiceNow requires separate ACLs for each operation and exact role name matching.

How to eliminate wrong answers

Option A is wrong because ACLs in ServiceNow are always applied at the table level for table access; there is no 'record' type for ACLs—the type 'record' does not exist. Option B is wrong because ServiceNow does not require a default read ACL; if no ACL matches, access is denied by default, but the administrator created a read ACL that should grant access if correctly configured. Option C is wrong because ACLs in ServiceNow do not have priority ordering; each ACL is evaluated independently, and a write ACL does not override a read ACL—both must be satisfied for their respective operations.

Full explanation →
355
Multi-Selectmedium

Which THREE of the following are valid options when configuring an Identification and Reconciliation (IRE) rule? (Select exactly 3)

Select 3 answers
A.Reconcile only
B.Create only
C.Fuzzy match
D.Exact match
E.Update only
AnswersA, B, D

Reconcile only is a valid action that updates existing CIs without creating new ones.

Why this answer

The 'Reconcile only' option in an IRE rule instructs the IRE engine to only reconcile existing CI records against incoming data, without creating new CIs. This is used when you want to ensure existing CIs are updated or validated but no new records should be created from the data source.

Exam trap

The trap here is that candidates confuse 'Reconcile only' with 'Update only' or think 'Fuzzy match' is a valid IRE option, but ServiceNow IRE only supports exact matching and the three specific actions: Reconcile only, Create only, and Exact match.

Full explanation →
356
MCQhard

During a CMDB health assessment, an administrator finds that the 'cmdb_ci_computer' table has 5000 records, but only 3000 have an 'operational_status' of 'In Use'. The administrator wants to view only the records with 'In Use' status in the CMDB reports. What is the most efficient approach?

A.Change the 'Display condition' of the table
B.Create a domain separation for 'In Use' CIs
C.Create a report with a condition where operational_status = 'In Use'
D.Modify the table's 'Condition Builder' to only show 'In Use' records
AnswerC

The report builder supports conditions to filter records.

Why this answer

The most efficient approach to view only records with 'In Use' status in CMDB reports is to apply a condition directly within the report definition. This method filters the data at query time without altering the underlying table structure or affecting other users, ensuring that the report shows only the desired subset of records while preserving the full dataset for other purposes.

Exam trap

The trap here is that candidates may confuse table-level configuration (like display conditions or condition builders) with report-level filtering, leading them to choose options that would globally alter the table instead of applying a simple, non-destructive filter in the report itself.

How to eliminate wrong answers

Option A is wrong because changing the 'Display condition' of the table would alter the default view for all users and all interactions with the table, which is not appropriate for a report-specific filter and could hide records needed for other operations. Option B is wrong because domain separation is used to isolate data for different business units or tenants, not to filter records based on a specific field value like operational_status; it would introduce unnecessary complexity and overhead. Option D is wrong because the 'Condition Builder' is used to define conditions for table-level behaviors such as business rules or UI policies, not for filtering records in reports; modifying it would affect the entire table's behavior rather than just the report output.

Full explanation →
357
MCQeasy

A user complains that when they submit a catalog item, they receive an error: 'The variable is mandatory but has no value.' However, the variable is not marked as mandatory in the item's variable definition. What could be the cause?

A.A Catalog Client Script of type 'onSubmit' sets the variable mandatory.
B.A Business Rule on the request table sets the variable mandatory.
C.A UI Policy on the record producer makes the variable mandatory.
D.The variable is mandatory in the parent catalog category.
AnswerA

Client scripts can enforce mandatory before submission.

Why this answer

A Catalog Client Script of type 'onSubmit' can dynamically set a variable as mandatory using the `g_form.setMandatory('variable_name', true)` method. This overrides the variable's definition in the catalog item, causing the 'mandatory but has no value' error even when the variable is not marked mandatory in the item's variable definition.

Exam trap

The trap here is that candidates assume mandatory status is only set in the variable definition or via UI Policies, overlooking that Catalog Client Scripts of type 'onSubmit' can dynamically enforce mandatory validation at submission time.

How to eliminate wrong answers

Option B is wrong because a Business Rule on the request table operates on the request record after submission, not on the catalog item's variables during submission; it cannot make a variable mandatory at the time of submission to trigger this specific error. Option C is wrong because a UI Policy on the record producer runs on the client side but only changes visibility, read-only state, or mandatory status based on conditions; however, UI Policies do not execute during the onSubmit event of a catalog item—they apply to record producers, not standard catalog items. Option D is wrong because the parent catalog category does not enforce mandatory settings on child catalog items; variable mandatory settings are defined per item, not inherited from the category.

Full explanation →
358
MCQmedium

A form has a reference field to the 'User' table. The administrator wants to ensure that when a user is selected, the user's email is automatically populated in another field. Which mechanism should be used?

A.Dictionary entry with a default value calculated from the reference field
B.Access Control Rule on the email field
C.UI Policy with an 'onChange' condition
D.Data lookup field configuration
AnswerC

Correct. A UI Policy with an 'onChange' condition on the reference field can automatically populate the email field when a user is selected, using the reference field's dot-walked value.

Why this answer

A UI Policy with an 'onChange' condition is the correct mechanism because it triggers client-side when the reference field changes, allowing the system to populate the email field based on the selected user. In ServiceNow, UI Policies can set field values dynamically when a field changes, using dot-walking to retrieve related field values like email from the User table. This approach works reactively on user interaction, unlike dictionary defaults which only apply on record creation.

Exam trap

Candidates often think that a dictionary default value with dot-walking will populate the email when the reference field changes, but dictionary defaults only set values on record creation. The correct reactive mechanism is a UI Policy with an onChange condition.

How to eliminate wrong answers

Option B is wrong because Access Control Rules (ACLs) control read/write permissions on fields, not automatic data population; they cannot set a field's value based on another field. Option C is wrong because a UI Policy with an 'onChange' condition can populate fields client-side, but it is less reliable for this use case as it depends on client-side execution and may not trigger correctly in all scenarios (e.g., when the record is created via web services or import sets). Option D is wrong because a Data Lookup field configuration is used to display related data from another table in a read-only manner, not to automatically populate a separate field with a value from a reference field.

Full explanation →
359
MCQmedium

Refer to the exhibit. An incident is updated and state changes from 'New' to 'In Progress'. Active is true. The notification is not sent. Which is the most likely cause?

A.The condition 'state changes' is not satisfied because the state changed from 'New' to 'In Progress', which is a change.
B.The email template 'incident_update' is missing or invalid.
C.The assigned user field is empty, so there is no recipient for the notification.
D.The notification is configured to send only on insert, not on update.
AnswerC

If assigned_to is empty, no user receives the notification.

Why this answer

The notification requires a recipient to send, and if the assigned user field is empty, the system cannot determine who should receive the notification. In ServiceNow, notifications rely on the 'Who will receive' condition, which often includes the 'Assigned user' field. Without a value in that field, the notification is not sent, even if the state change and active flag are correctly configured.

Exam trap

ServiceNow often tests the misconception that a state change or active flag alone guarantees notification delivery, but the real trap is that the notification will silently fail if the recipient field (e.g., assigned user) is empty, even when all other conditions are met.

How to eliminate wrong answers

Option A is wrong because the condition 'state changes' is satisfied when the state changes from 'New' to 'In Progress'; the notification is triggered on the update event, and the state change is a valid change. Option B is wrong because if the email template 'incident_update' were missing or invalid, the notification would still attempt to send but might fail with an error or send with a blank body, not silently fail to send. Option D is wrong because the notification is configured to send on update (the state change triggers an update), not only on insert; the scenario describes an update event, so the 'on update' condition is met.

Full explanation →
360
MCQmedium

A company's CMDB has duplicate CIs for the same server due to conflicting identification rules. The admin notices that some CIs are being merged incorrectly. What is the best practice to resolve this issue?

A.Increase the reconciliation engine's timeout value.
B.Run the CI Class Manager to delete duplicate CIs.
C.Review and refine the identification rules to ensure uniqueness criteria are correctly defined.
D.Disable all identification rules and use manual reconciliation.
AnswerC

This addresses the root cause by correcting the rules that cause misidentification.

Why this answer

Duplicate CIs in the CMDB arise from conflicting or poorly defined identification rules. The best practice is to review and refine these rules to ensure each CI has a unique set of identifying attributes (e.g., serial number, MAC address, or FQDN). This prevents incorrect merges and maintains data integrity without relying on manual cleanup or timeout adjustments.

Exam trap

The trap here is that candidates often confuse symptom fixes (like increasing timeouts or deleting duplicates) with the root cause solution, which is correcting the identification rules that govern CI uniqueness.

How to eliminate wrong answers

Option A is wrong because increasing the reconciliation engine's timeout value only affects how long the system waits for data sources to respond; it does not address the root cause of duplicate CIs or incorrect merges. Option B is wrong because running the CI Class Manager to delete duplicates is a reactive, manual fix that does not prevent future duplicates and can lead to data loss if CIs are merged incorrectly. Option D is wrong because disabling all identification rules and using manual reconciliation removes automation entirely, which is inefficient, error-prone, and defeats the purpose of a CMDB.

Full explanation →
361
MCQeasy

A user wants to quickly find an incident by its number without navigating through menus. Which feature should they use?

A.Navigator filter
B.Favorites
C.History
D.Global search
AnswerA

Typing the incident number in the navigator filter directly opens the record.

Why this answer

The Navigator filter allows users to quickly locate any record, including incidents, by typing its number directly into the filter field at the top of the left-hand navigation pane. This bypasses the need to navigate through menus or modules, providing instant access to the specific record. It is the fastest method for finding a record by its unique identifier without leaving the current view.

Exam trap

ServiceNow often tests the distinction between the Navigator filter (for quick record lookup by number) and Global search (for broader text searches), leading candidates to mistakenly choose Global search because they think it is the default search tool for all purposes.

How to eliminate wrong answers

Option B is wrong because Favorites are user-defined shortcuts to frequently accessed modules or reports, not a feature for searching by record number. Option C is wrong because History shows recently viewed records and modules, but it does not allow direct searching by a specific incident number. Option D is wrong because Global search performs a broader text-based search across multiple tables and fields, which is less efficient for quickly locating a record by its exact number compared to the Navigator filter.

Full explanation →
362
Multi-Selecthard

Which TWO statements are true about Service Catalog variables? (Choose two.)

Select 2 answers
A.Variables cannot be reordered after creation
B.Variables can be conditionally visible based on the value of another variable
C.Variables of type 'Reference' can be set to auto-populate from the user's record
D.Variables can be used in catalog item availability conditions
E.Default values for variables can be set in the workflow
AnswersB, C

Variable visibility conditions allow this.

Why this answer

Service Catalog variables can be configured with a 'Visible if' condition that evaluates the value of another variable on the same catalog item. This allows dynamic form behavior where a variable is shown or hidden based on user input, such as showing a 'Reason' field only when a 'Request Type' variable is set to 'Other'.

Exam trap

ServiceNow often tests the misconception that variables can be reordered only before creation, when in fact they can be reordered at any time using the Variable Editor's reorder functionality.

Full explanation →
363
MCQmedium

An administrator notices that a scheduled job that queries the cmdb_ci table is taking longer than expected. The job uses a glide query with multiple encoded queries. What is the best approach to improve performance without altering the job's results?

A.Create a database view on the cmdb_ci table and query the view instead.
B.Add an index on the fields used in the encoded query conditions.
C.Convert the glide query to a direct database query using System SQL.
D.Add an index on the sys_created_on field.
AnswerB

Indexing the filter fields accelerates query execution.

Why this answer

Adding an index on the fields used in the encoded query conditions directly reduces the number of rows scanned by the database engine when executing the GlideRecord query. This improves query performance without changing the logic or results of the scheduled job, as indexes only affect data access speed, not the data returned.

Exam trap

The trap here is that candidates often assume creating a view or using direct SQL will magically speed up queries, but ServiceNow's architecture requires proper indexing on the filtered columns to achieve performance gains without breaking platform security or result integrity.

How to eliminate wrong answers

Option A is wrong because creating a database view does not improve performance; views are just saved queries and still require scanning the underlying table unless the view is materialized (which ServiceNow does not support natively). Option C is wrong because converting to a direct System SQL bypasses ServiceNow's ACL and business logic, potentially altering results and violating platform best practices. Option D is wrong because adding an index on sys_created_on is irrelevant unless the encoded queries filter on that field; indexing the wrong columns provides no performance benefit.

Full explanation →
364
MCQeasy

A developer wants to create a Scripted REST API endpoint that returns data from a custom table. The endpoint must only be accessible to users with the 'api_user' role. Which of the following is the best practice to enforce this restriction?

A.Add a condition in the script that checks gs.hasRole('api_user') for each request.
B.Set the system property 'glide.service.catalog.enforce_acl' to true.
C.Use a 'read' ACL on the table and set the endpoint to 'Requires authentication'.
D.Define a read ACL on the custom table that requires the 'api_user' role.
AnswerD

Correct: ACLs provide table-level security.

Why this answer

The best practice for restricting access to a Scripted REST API endpoint in ServiceNow is to use an ACL (Access Control List) on the underlying table. When the endpoint is set to 'Requires authentication', the platform automatically evaluates table-level ACLs for each record operation. By defining a read ACL that requires the 'api_user' role, you enforce role-based access at the data layer, which is more secure and maintainable than checking roles in script.

Exam trap

The trap here is that candidates often confuse 'Requires authentication' with role-based access control, assuming that authentication alone is sufficient to restrict access to specific roles, when in fact a separate ACL is required to enforce the role check.

How to eliminate wrong answers

Option A is wrong because checking gs.hasRole('api_user') in script is an anti-pattern; it bypasses the platform's declarative security model, is harder to audit, and can be inconsistent if the script logic is not applied uniformly. Option B is wrong because the system property 'glide.service.catalog.enforce_acl' is specific to Service Catalog items, not Scripted REST APIs or custom table access. Option C is wrong because setting the endpoint to 'Requires authentication' only ensures the user is authenticated, not that they have the 'api_user' role; a read ACL on the table is still needed to enforce role-based restrictions.

Full explanation →
365
MCQmedium

A catalog item is configured to use an order guide. When a user submits the order guide, only the first catalog item in the guide appears. What is the most likely cause?

A.The workflow attached to the order guide is incomplete
B.The order guide's 'Delivery method' is set to 'One at a time'
C.The catalog items have mandatory variables that are not filled
D.The order guide is in a restricted category
AnswerB

This setting causes items to be presented sequentially, so only the first item appears initially.

Why this answer

When an order guide's 'Delivery method' is set to 'One at a time', the system processes only the first catalog item and stops, rather than adding all items to the cart. This setting is designed for scenarios where each item must be ordered individually, so submitting the guide results in only the first item appearing.

Exam trap

The trap here is that candidates often confuse 'Delivery method' with fulfillment or delivery scheduling, assuming it controls how items are shipped rather than how they are added to the cart during order guide submission.

How to eliminate wrong answers

Option A is wrong because an incomplete workflow attached to the order guide would affect fulfillment or approval processes, not the initial display of catalog items in the cart after submission. Option C is wrong because mandatory variables that are not filled would typically prevent submission or show validation errors, not cause only the first item to appear. Option D is wrong because a restricted category would prevent the user from seeing or accessing the order guide entirely, not cause partial item display after submission.

Full explanation →
366
Drag & Dropmedium

Drag and drop the steps to create a new report in ServiceNow 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 for creating a new report in ServiceNow begins by opening the Reports module, then selecting a table as the data source, followed by defining report criteria such as filters or conditions, and finally saving the report. This order ensures that each step builds logically on the previous one, from accessing the tool to specifying data and saving the configuration.

Full explanation →
367
MCQeasy

A user reports that when they submit a catalog item request from the Service Portal, they do not receive an email notification. The notification is configured correctly and works for other users. What should the administrator check first?

A.The user's notification preference or subscription
B.The email notification properties
C.The workflow attached to the catalog item
D.The notification configuration on the catalog item
AnswerA

The user may have unsubscribed or disabled notifications.

Why this answer

The user's notification preference or subscription is the first place to check when a single user does not receive notifications while others do. ServiceNow allows users to configure their own notification preferences, including opting out of certain notifications, which overrides system-level notification configurations. The administrator should verify that the user has not disabled the specific notification or unsubscribed from it.

Exam trap

The trap here is that candidates often jump to checking the notification configuration or workflow first, assuming a system-level misconfiguration, when the issue is actually user-specific and requires checking the user's individual subscription settings.

How to eliminate wrong answers

Option B is wrong because checking the email notification properties would be relevant if no users were receiving notifications, but the issue is isolated to one user. Option C is wrong because the workflow attached to the catalog item handles fulfillment processes, not email notification delivery; notifications are triggered independently via the notification system. Option D is wrong because the notification configuration on the catalog item is a system-level setting that applies to all users; since other users receive the notification, the configuration is correct.

Full explanation →
368
MCQmedium

Refer to the exhibit. The UI Policy script above is meant to make the Short Description field mandatory when the incident state is 'In Progress'. However, it does not work. What is the most likely reason?

A.The method 'g_form.setMandatory' is deprecated
B.The script is blocked by the 'glide.script.secure' property
C.There is a syntax error in the function parameters: 'previous !=null' is invalid
D.The script uses 'current' object which is not available in client scripts
AnswerC

The correct is 'previous' without the comparison.

Why this answer

The condition `previous != null` is invalid syntax in a UI Policy script. UI Policy scripts run on the client side and do not have access to the `previous` object, which is only available in server-side business rules. The correct approach would be to check the current state of the `state` field using `g_form.getValue('state')` or similar client-side methods.

Exam trap

ServiceNow often tests the distinction between client-side and server-side objects, and the trap here is that candidates mistakenly think `previous` is available in UI Policy scripts because it is commonly used in business rules, leading them to overlook the syntax error.

How to eliminate wrong answers

Option A is wrong because `g_form.setMandatory` is not deprecated; it is a standard client-side API used to make fields mandatory. Option B is wrong because the `glide.script.secure` property affects server-side script execution, not client-side UI Policy scripts. Option D is wrong because `current` is indeed available in UI Policy scripts as a client-side object representing the current record, but the issue is with `previous`, not `current`.

Full explanation →
369
MCQmedium

A record producer is configured to use table 'incident' and has a mapping that sets the short description from a variable. When the record producer is submitted, no incident is created. Which is the most likely cause?

A.The user does not have rights to create incidents
B.The table does not have a mandatory field that is not mapped
C.The variable mapping uses a wrong syntax
D.The record producer is not active
AnswerB

Mandatory fields must be mapped or have default values, otherwise record creation fails.

Why this answer

The most likely cause is that the target table (incident) has a mandatory field that is not mapped in the record producer's mapping. When a record producer creates a record, it must satisfy all mandatory field requirements of the target table; if a mandatory field is missing or unmapped, the system will fail to create the record, often without an explicit error to the user.

Exam trap

ServiceNow often tests the concept that a record producer can fail silently due to unmapped mandatory fields, leading candidates to incorrectly suspect permissions or syntax errors instead.

How to eliminate wrong answers

Option A is wrong because if the user lacked rights to create incidents, the system would typically show an ACL error or permission denied message, not silently fail to create the record. Option C is wrong because incorrect variable mapping syntax would usually cause a mapping error or a blank field, but the record producer would still attempt to create the record and might succeed if no mandatory fields are missing. Option D is wrong because if the record producer were inactive, it would not appear to the user at all, or the user would receive a 'producer not found' message, not a silent failure after submission.

Full explanation →
370
MCQhard

An administrator notices that a reference field on the cmdb_ci table, 'vendor', points to the 'core_company' table. However, some users report that they cannot select certain companies in the reference field. What is the most likely cause?

A.The 'display field' property is incorrectly configured
B.The 'vendor' field is marked as mandatory
C.The 'vendor' field has a reference qualifier that filters companies
D.The database view permission is set to 'none' for some users
AnswerC

Reference qualifiers limit the selectable records in a reference field.

Why this answer

Reference qualifiers are used to filter the records displayed in a reference field. If the 'vendor' field has a reference qualifier condition (e.g., 'active=true' or 'vendor_type=hardware'), only companies meeting that condition will appear in the dropdown, preventing users from selecting certain companies. This is the most likely cause when users cannot see specific records in a reference field.

Exam trap

The trap here is that candidates often confuse reference qualifiers (which filter available records) with display fields (which control what is shown in the field) or mandatory settings (which enforce data entry), leading them to pick option A or B instead of C.

How to eliminate wrong answers

Option A is wrong because the 'display field' property controls which column from the referenced table is shown in the field (e.g., 'name' vs 'u_number'), not which records are available for selection. Option B is wrong because marking a field as mandatory only requires a value to be entered before the record can be saved; it does not restrict which values can be selected. Option D is wrong because database view permissions control whether a user can see the table at all (e.g., via ACLs), not which specific records are filtered within a reference field; if permission were 'none', the field would likely show no results or an error, not a partial list.

Full explanation →
371
MCQeasy

In an import set, where is the staged data stored before transformation?

A.Target table (e.g., incident)
B.Import set row table (sys_import_set_row)
C.Transform map table
D.Data source table
AnswerB

Import set row table (sys_import_set_row): Correct. This table is the staging area where raw imported data is stored before any transformation occurs.

Why this answer

In ServiceNow, during the import set process, raw data from a data source is first loaded into the import set row table (sys_import_set_row). This table acts as a staging area. Only after transformation maps are applied does the data move to the target table (e.g., incident).

Therefore, staged data before transformation resides in the import set row table, not the target table.

Exam trap

The trap is that candidates may mistakenly think 'staged data' refers to data already transformed and ready for use in the target table. Instead, 'staged data' in ServiceNow import sets means raw data stored in the sys_import_set_row table before transformation.

How to eliminate wrong answers

Option A is wrong because the target table (e.g., incident) contains only transformed records after the import set runs, not the raw staged data. Option B is correct, but since the question asks for the correct answer, this is not a wrong option. Option C is wrong because the transform map table (sys_transform_map) stores the mapping definitions and field transformations, not the staged data itself.

Option D is wrong because the data source table (sys_data_source) defines the source connection and import set configuration, but does not hold the staged data rows.

Full explanation →
372
MCQmedium

An administrator wants to ensure that CI relationship data is accurate. Which tool should be used to identify CIs that have missing or invalid relationships?

A.CMDB Data Manager
B.CMDB Health Verification
C.Discovery
D.CI Change Request
AnswerB

CMDB Health Verification runs checks on CI data including relationships.

Why this answer

CMDB Health Verification is the correct tool because it specifically evaluates the completeness and accuracy of CI relationships by running health checks that flag CIs with missing or invalid relationships. It provides a dashboard and reports that highlight relationship gaps, enabling administrators to remediate data quality issues directly.

Exam trap

The trap here is that candidates often confuse Discovery (which creates relationships) with CMDB Health Verification (which validates existing relationships), leading them to choose Discovery as the tool for identifying missing relationships.

How to eliminate wrong answers

Option A is wrong because CMDB Data Manager is used for importing and updating CI data from external sources (e.g., spreadsheets or APIs), not for validating the quality of existing relationships. Option C is wrong because Discovery identifies CIs and their relationships by probing the network, but it does not retrospectively analyze or flag missing/invalid relationships in the CMDB. Option D is wrong because CI Change Request is a process for requesting changes to CI records, not a tool for auditing relationship accuracy.

Full explanation →
373
MCQmedium

A company wants to allow users to submit requests for new software installations through the Service Portal. The catalog item should show different options based on the user's department. Which feature should be configured on the catalog item to achieve this?

A.Variable order
B.Catalog item templates
C.Variable visibility conditions
D.User criteria
AnswerC

Variable visibility conditions show or hide variables based on conditions like department.

Why this answer

Variable visibility conditions allow you to control which catalog item variables are displayed to users based on conditions such as the user's department field. When a user from a specific department submits a request, only the variables that match their department's visibility condition will appear, enabling dynamic form behavior without creating separate catalog items.

Exam trap

The trap here is that candidates often confuse 'user criteria' (which controls catalog item visibility) with 'variable visibility conditions' (which controls variable visibility within a catalog item), leading them to select Option D incorrectly.

How to eliminate wrong answers

Option A is wrong because variable order only controls the sequence in which variables appear on the form, not their visibility based on user attributes. Option B is wrong because catalog item templates are used to pre-populate field values or create a baseline for new catalog items, not to conditionally show or hide variables. Option D is wrong because user criteria control who can see or access the entire catalog item, not which variables are displayed within the item.

Full explanation →
374
Matchingmedium

Match each database table type to its description.

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

Concepts
Matches

Top-level table in a class hierarchy

Table that inherits fields from a parent table

Parent table for work-related records like incidents and changes

Stores system configuration data

Stores audit trail and activity log entries

Why these pairings

Understanding table types is key for data modeling in ServiceNow. Core tables provide common fields, extension tables inherit from parents, task tables track work, and journal tables store logs.

Full explanation →
375
MCQhard

A large financial institution uses ServiceNow CMDB to manage their IT infrastructure. They have a complex environment with multiple data sources: Discovery, SCCM, and a custom integration from their cloud provider. The CMDB contains over 100,000 CIs. Recently, the CMDB team noticed that for a specific set of Windows servers, the 'os_version' attribute is being updated to an incorrect value every night. The value comes from the SCCM integration, which is supposed to be the authoritative source for software-related attributes. However, the 'os_version' attribute should be authoritative from Discovery. The IRE is configured with reconciliation rules, but the issue persists. The team also finds that the Discovery job for these servers runs at 2:00 AM, and the SCCM integration runs at 3:00 AM. The incorrect value appears after the SCCM run. The reconciliation rules are set so that Discovery is authoritative for 'os_version', but the SCCM integration still overwrites it. What is the most likely cause and recommended action?

A.Enable the IRE 'Strict' mode to prevent any updates from non-authoritative sources.
B.Disable the SCCM integration for these servers and rely solely on Discovery.
C.Change the order of the integrations so that SCCM runs before Discovery.
D.Review and correct the reconciliation rule to ensure Discovery is the authoritative source for 'os_version' and that the rule is active.
AnswerD

If the rule is misconfigured or inactive, SCCM may overwrite the attribute.

Why this answer

The reconciliation rule is the mechanism that dictates which data source is authoritative for a specific attribute. If the rule is misconfigured, inactive, or not properly scoped, the IRE will allow the SCCM integration to overwrite the 'os_version' attribute even though Discovery is intended to be authoritative. Reviewing and correcting the rule ensures that the IRE enforces the correct source priority for that attribute.

Exam trap

The trap here is that candidates assume changing the order of integrations (Option C) will fix the issue, but the IRE's reconciliation rules, not the sequence of data ingestion, determine which source is authoritative for a given attribute.

How to eliminate wrong answers

Option A is wrong because enabling IRE 'Strict' mode would block all updates from non-authoritative sources, but the SCCM integration is still an authorized data source; the issue is a misconfigured reconciliation rule, not the IRE mode. Option B is wrong because disabling the SCCM integration removes a valuable authoritative source for software attributes and does not address the root cause of the reconciliation rule misconfiguration. Option C is wrong because changing the order of integrations does not affect which source is authoritative; the IRE uses reconciliation rules to determine source priority, not the order of data ingestion.

Full explanation →
Page 4

Page 5 of 7

Page 6

All pages

1234567

Practice SNOW-CSA by domain

Target a specific domain to shore up weak areas.

Reporting, SLA and ImportsSelf-Service and AutomationUI, Navigation and FormsDatabase Administration and CMDBService Catalog and WorkflowsApplication Rules, ACL and Notifications
See all domains with question counts →