Courseiva

ServiceNow Certified System Administrator CSA (SNOW-CSA) — Questions 1–75

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

Take a mock examExam hub

Page 1 of 7

Page 2
1
MCQhard

An SLA is defined with a condition of 'Priority is 1' and 'State is not Closed'. A task has Priority=1 and State=New. The SLA starts. Later the task is assigned and Priority is changed to 2, then back to 1. What happens to the SLA?

A.The SLA pauses and resumes
B.The SLA stops and a new SLA instance starts when priority returns to 1
C.The SLA stops and resumes with the same elapsed time
D.The SLA continues running because it started when conditions were met
AnswerB

SLA restarts when conditions are re-met.

Why this answer

When the priority changes from 1 to 2, the SLA condition 'Priority is 1' is no longer met, so the SLA stops. When priority returns to 1, a new SLA instance starts because the condition is re-evaluated from scratch; the SLA does not resume the previous timer. This is standard behavior for SLA definitions with conditions that are not based on a single continuous state.

Exam trap

The trap here is that candidates often assume SLAs pause and resume when conditions change, but ServiceNow stops and restarts a new SLA instance when the condition is re-met, which resets the timer.

How to eliminate wrong answers

Option A is wrong because the SLA does not pause and resume; it stops when the condition is no longer met, and a new instance starts when the condition is met again. Option C is wrong because the SLA does not resume with the same elapsed time; it stops completely and a new SLA instance begins with a fresh timer. Option D is wrong because the SLA does not continue running; it is condition-based, and once the priority changes away from 1, the condition fails and the SLA stops.

Full explanation →
2
MCQhard

A catalog item uses Flow Designer to send an email notification when the state changes to 'fulfilled'. The flow uses a trigger 'State changed' on the requested item table. However, the email is not sent. The flow logs show the trigger fired. What is the most likely issue?

A.The flow action 'Send Email' is not configured with a valid recipient
B.The trigger is set to 'State changed' but the state field is not properly referenced
C.The flow is set to 'Deactivated'
D.The email notification is blocked by an email property
AnswerA

The action may lack a recipient, causing it to fail silently.

Why this answer

Option A is correct because the most common reason a flow trigger fires but the email is not sent is that the 'Send Email' action lacks a valid recipient. In Flow Designer, the 'Send Email' action requires a recipient (e.g., user, group, or email address) to be explicitly defined; if the recipient field is empty or references a non-existent variable, the action will execute without sending the email, and no error will be logged in the flow logs.

Exam trap

The trap here is that candidates assume a fired trigger guarantees the email was attempted, but they overlook that the 'Send Email' action can complete without sending if the recipient is missing, and the flow logs will not show a failure for that action.

How to eliminate wrong answers

Option B is wrong because the flow logs show the trigger fired, which means the state field was properly referenced and the condition was met; if the state field were not properly referenced, the trigger would not have fired. Option C is wrong because if the flow were deactivated, the trigger would not fire at all, and the flow logs would not show the trigger firing. Option D is wrong because email properties (e.g., glide.email.smtp.enable) block all outbound email globally, not just for a specific flow; if an email property were blocking, the flow logs would typically show an error or the email would fail for all flows, not just this one.

Full explanation →
3
MCQhard

Refer to the exhibit. An administrator created the above Flow Designer action script to retrieve user details. When tested, the action returns 'User not found' for a valid user sys_id. What is the most likely cause?

A.The script is missing a condition check.
B.The variable 'inputs.user_sys_id' is not being passed correctly.
C.The 'get' method should use the first parameter as table name.
D.The get method should be called with one argument: the sys_id.
AnswerD

Correct: The correct syntax is gr.get(inputs.user_sys_id).

Why this answer

Option D is correct because in GlideRecord, the `get()` method with a single argument (the sys_id) retrieves a record by its unique system identifier. The script incorrectly passes two arguments (`inputs.user_sys_id` and a table name), which causes the method to fail and return false, leading to the 'User not found' message. The proper syntax is `gr.get(inputs.user_sys_id)`.

Exam trap

The trap here is that candidates often confuse the `get()` method's signature, mistakenly thinking it requires a table name as the first argument (like `getTable()` or `addQuery()`), when in fact the table is already defined by the GlideRecord constructor.

How to eliminate wrong answers

Option A is wrong because the script already has a condition check (the if-else block after the get call), so missing a condition check is not the issue. Option B is wrong because the variable 'inputs.user_sys_id' is correctly referenced and would be passed if the get method syntax were correct; the problem is not with the variable itself but with how it is used in the get method. Option C is wrong because the 'get' method does not accept a table name as the first parameter; the table is already set when the GlideRecord is instantiated with 'sys_user'.

Full explanation →
4
MCQmedium

An administrator is creating a new report to show the average time to resolve incidents for the last quarter. They want the report to automatically update as new incidents are resolved. Which report type should they use?

A.Bar chart report with a condition for resolved incidents.
B.Pivot table report with a 'Average' aggregation.
C.Scorecard report with a metric for average resolution time.
D.List report with a 'Average' aggregation on the 'Resolved' field.
AnswerD

List reports can compute averages and update dynamically.

Why this answer

A List report with an 'Average' aggregation on the 'Resolved' field is the correct choice because it automatically recalculates the average as new records are added or updated, ensuring the report reflects the most current data without manual intervention. List reports in ServiceNow support real-time aggregation on specific fields, making them ideal for dynamic metrics like average resolution time.

Exam trap

The trap here is that candidates confuse report types (List, Pivot, Scorecard) with visualization types (Bar chart) or assume that any report with an aggregation will auto-update, but only List reports with field-level aggregations dynamically reflect new records without manual refresh.

How to eliminate wrong answers

Option A is wrong because a Bar chart report is a visualization type, not a report type that supports automatic updating of aggregated data; it requires a data source that must be manually refreshed or scheduled. Option B is wrong because a Pivot table report is designed for cross-tabulation and grouping, not for automatically updating a single average metric over time; it would need manual re-run to reflect new incidents. Option C is wrong because a Scorecard report is used for performance indicators with targets and thresholds, not for simple average calculations; it relies on pre-defined metrics that do not automatically update with new incident resolutions.

Full explanation →
5
Multi-Selectmedium

Which TWO of the following are valid ways to modify the layout of a form in ServiceNow?

Select 2 answers
A.Using the Form Designer
B.Creating an Access Control Rule (ACL)
C.Creating a UI Policy that hides or shows fields
D.Modifying the Dictionary Override
E.Creating a report on the table
AnswersA, C

Form Designer is the primary tool for layout changes.

Why this answer

Options A and D are correct. Form Designer allows dragging fields and sections. UI Policies can change field visibility, which affects layout.

Option B is wrong because ACLs control data access, not layout. Option C is wrong because dictionary overrides set field properties like label, but not layout. Option E is wrong because reports are separate from form layout.

Full explanation →
6
MCQeasy

A catalog item has a variable with a mandatory condition: if the variable 'category' is 'software', then 'software name' is mandatory. This is best implemented using:

A.UI Policy
B.Catalog Client Script
C.ACL
D.Variable Condition
AnswerA

UI policies are designed for conditional mandatory, visibility, etc.

Why this answer

A UI Policy is the correct choice because it allows you to define a mandatory condition on a catalog item variable without writing any code. In this case, you would create a UI Policy that runs when the 'category' variable is 'software', and within that policy set the 'software name' variable's mandatory attribute to true. This is the standard, no-code approach for enforcing variable-level mandatory conditions in Service Catalog.

Exam trap

The trap here is that candidates often confuse 'Variable Condition' (which controls visibility) with 'UI Policy' (which controls mandatory, read-only, and visibility), leading them to pick D instead of A.

How to eliminate wrong answers

Option B (Catalog Client Script) is wrong because client scripts are used for client-side validation or dynamic behavior, but they require JavaScript and are not the recommended method for simply making a variable mandatory based on another variable's value; UI Policy is the declarative, no-code alternative. Option C (ACL) is wrong because Access Control Lists govern data access permissions (read/write/delete) on records, not form-level variable behavior like mandatory conditions. Option D (Variable Condition) is wrong because variable conditions are used to show or hide variables, not to enforce mandatory status; they control visibility, not requiredness.

Full explanation →
7
MCQeasy

An administrator imports a CSV file into the incident table using an import set. After the import, several records are duplicated. What is the most likely cause?

A.The CSV contained duplicate rows.
B.The target table has an index on the number field.
C.The transform map does not have a coalesce field set.
D.The import set row limit was exceeded.
AnswerC

Without coalesce, every row creates a new record.

Why this answer

Option C is correct because the transform map lacks a coalesce field, which is required to match incoming records to existing records in the target table. Without a coalesce field, the import set treats every row as a new record, causing duplicates even if the CSV contains unique data. Coalesce fields define the unique key (e.g., sys_id or number) used to prevent duplicate inserts.

Exam trap

ServiceNow often tests the misconception that duplicate CSV rows are the root cause, but the real issue is the absence of a coalesce field in the transform map, which controls deduplication logic regardless of source data uniqueness.

How to eliminate wrong answers

Option A is wrong because duplicate rows in the CSV would cause duplicates only if the transform map does not use coalesce to deduplicate; the question states 'several records are duplicated' implying the issue is systematic, not just repeated rows. Option B is wrong because an index on the number field would help enforce uniqueness and prevent duplicates, not cause them—indexes improve lookup performance but do not control import deduplication logic. Option D is wrong because exceeding the import set row limit would cause the import to fail or truncate, not create duplicate records; the limit caps the number of rows processed per import set run.

Full explanation →
8
MCQeasy

A company wants to allow users to submit requests for new software without any manual intervention. Which self-service feature should be used to automate the request process?

A.Record Producer
B.Approval Engine
C.SLA Definition
D.Flow Designer
AnswerA

Record Producers allow users to submit requests that automatically create records.

Why this answer

A Record Producer is the correct self-service feature because it allows users to submit requests for new software through a catalog item without any manual intervention. It automatically creates a record (e.g., a catalog task or request) in the platform based on the user's submission, enabling a fully automated request process.

Exam trap

The trap here is that candidates often confuse Flow Designer (a process automation tool) with a self-service submission feature, but Flow Designer does not provide a user-facing catalog interface for submitting requests.

How to eliminate wrong answers

Option B (Approval Engine) is wrong because it is a process component that manages approval workflows, not a self-service feature for submitting requests; it requires a record to already exist. Option C (SLA Definition) is wrong because it defines service level agreements and time-based targets, not a mechanism for users to submit requests. Option D (Flow Designer) is wrong because it is a tool for designing automated workflows and processes, but it does not provide a direct user-facing self-service submission interface like a Record Producer does.

Full explanation →
9
MCQmedium

A company wants to allow managers to view all incidents, but only their own direct reports' incidents to be editable. Which ACL approach is most efficient?

A.Create a read ACL for managers and a write ACL with a script condition checking manager relationship.
B.Use a business rule to set a field indicating editable and use ACL on that field.
C.Use role-based ACLs and assign a separate role for each manager.
D.Create separate write ACLs for each manager's direct reports.
AnswerA

A script condition dynamically checks the relationship, making it scalable.

Why this answer

Option A is correct because it uses a read ACL to grant all managers view access to all incidents, and a separate write ACL with a script condition that dynamically checks whether the incident's assigned user is a direct report of the current manager. This approach is efficient as it avoids duplicating ACLs per manager or per group, leveraging a single script condition to enforce the manager–direct report relationship at runtime.

Exam trap

The trap here is that candidates often overcomplicate the solution by thinking they need separate ACLs or roles per manager, when a single scripted ACL condition can dynamically evaluate the manager–direct report relationship at runtime, which is both efficient and scalable.

How to eliminate wrong answers

Option B is wrong because using a business rule to set a field indicating editability and then an ACL on that field adds unnecessary complexity and latency; the ACL script condition can directly evaluate the relationship without needing an extra field or business rule. Option C is wrong because creating a separate role for each manager is not scalable and violates role-based access control best practices; roles should represent job functions, not individual users. Option D is wrong because creating separate write ACLs for each manager's direct reports is administratively unsustainable and does not scale as the number of managers or direct reports changes; a single scripted ACL is far more efficient.

Full explanation →
10
MCQmedium

A company has a custom table 'u_employee_data' with a before query business rule that sets 'u_department' to 'Engineering' when the current user is in the 'ITIL' role. After the business rule is activated, users in the 'ITIL' role report that when they query the table, they see only records with department 'Engineering'. However, the business rule is intended to set the default department for new records only. What is the most likely cause?

A.The business rule should be set to 'async' to avoid affecting queries.
B.The business rule is set to run on the client side instead of server side.
C.The business rule is running on 'before query' instead of 'before insert'.
D.The condition script uses 'gs.getUser().hasRole("ITIL")' incorrectly.
AnswerC

Before query modifies the query for all retrievals, not just new records.

Why this answer

The business rule is configured to run on the 'before query' operation, which means it executes every time a query is made against the 'u_employee_data' table. This causes the condition to set the 'u_department' field to 'Engineering' for all records returned by the query, effectively filtering the result set to only those with that department. The intended behavior is to set the default department only when a new record is created, which requires the business rule to run on the 'before insert' operation instead.

Exam trap

The trap here is that candidates may confuse 'before query' with 'before insert' because both involve setting field values, but 'before query' affects all retrieved records while 'before insert' only affects new record creation.

How to eliminate wrong answers

Option A is wrong because setting the business rule to 'async' would not change the operation it runs on; asynchronous execution still runs on the same event (before query) and would still affect queries, not solve the issue. Option B is wrong because client-side business rules do not exist in ServiceNow; business rules are always server-side, and the problem is about the event trigger, not the execution location. Option D is wrong because the condition script using 'gs.getUser().hasRole("ITIL")' is correct for checking role membership; the issue is not with the condition but with the business rule running on the wrong event.

Full explanation →
11
MCQeasy

Which feature should be used to allow users to track the status of their service catalog requests via the self-service portal?

A.My Requests module
B.My Items module
C.Service Catalog module
D.Requested Items related list
AnswerA

This module shows the user's submitted requests and their status.

Why this answer

The My Requests module in ServiceNow provides users with a dedicated view to track the status, stage, and approval progress of their service catalog requests. It displays all requests submitted by the user, including those from both the service catalog and other request sources, and allows them to see real-time updates without needing ITIL roles or elevated permissions.

Exam trap

The trap here is that candidates confuse the My Requests module (which tracks the overall request lifecycle) with the My Items module (which tracks provisioned items), or they mistakenly think the Service Catalog module itself provides tracking capabilities.

How to eliminate wrong answers

Option B is wrong because the My Items module shows the individual catalog items (e.g., software, hardware) that have been provisioned to the user, not the status of the original service catalog request. Option C is wrong because the Service Catalog module is the interface for browsing and submitting new requests, not for tracking existing ones. Option D is wrong because the Requested Items related list is a back-end view typically found on the request record itself and is not exposed via the self-service portal for end users; it is used by fulfillers or administrators.

Full explanation →
12
MCQmedium

A company has implemented a service catalog for IT requests. The catalog item 'New Laptop' includes variables for hardware specifications. After submission, the request is assigned to the hardware team. However, the hardware team reports that they cannot see the user's preferred operating system choice. What is the most likely cause?

A.The catalog item variable is not mapped to the corresponding task variable.
B.The user did not fill in the variable.
C.The variable is not added to the 'Request' form.
D.The variable is not set to 'Mandatory'.
AnswerA

To appear on tasks, catalog variables must be mapped to task variables using variable mapping.

Why this answer

In ServiceNow, when a catalog item is submitted, the requested item (RITM) is created. If the catalog item is configured to generate a task (e.g., for the hardware team), the variables from the catalog item must be explicitly mapped to the task via the 'Variable Mappings' related list on the task's variable model or the catalog item's task configuration. Without this mapping, the operating system variable's value is stored only on the RITM and is not passed to the task, making it invisible to the hardware team.

Option A correctly identifies this missing mapping as the root cause.

Exam trap

ServiceNow often tests the distinction between variable visibility on the RITM versus the task, and the trap here is that candidates assume all variables from the catalog item automatically appear on the task, when in fact they must be explicitly mapped.

How to eliminate wrong answers

Option B is wrong because if the user did not fill in the variable, the value would be empty on the RITM as well, but the question states the hardware team cannot see the choice, implying the value exists somewhere but is not visible on their task. Option C is wrong because the variable is already on the 'Request' form (the catalog item's variable form), which is where the user submitted it; the issue is not about the request form but about the task form not displaying it. Option D is wrong because making a variable mandatory only enforces that the user must provide a value before submission; it does not affect whether that value is propagated to downstream tasks.

Full explanation →
13
MCQmedium

A company wants to allow users to request software licenses through the service catalog. The request form should automatically populate the user's manager's email address. Which configuration option should the administrator use?

A.Use a Data Lookup definition on the catalog item.
B.Use a Flow Designer action to set the variable.
C.Use a Catalog Client Script with onChange catalog variable.
D.Use a default value on the variable with a script that retrieves the manager's email.
AnswerD

Correct: A default value script can query the manager's email from the user record.

Why this answer

Option D is correct because a default value on a catalog variable can use a script (e.g., gs.getUser().getManagerEmail()) to dynamically populate the manager's email address when the form loads. This approach directly meets the requirement without requiring additional triggers or lookups.

Exam trap

The trap here is that candidates often choose a client-side script (Option C) thinking it can run on load, but Catalog Client Scripts require an explicit trigger (onLoad or onChange), and onLoad scripts cannot set variable values directly without additional logic.

How to eliminate wrong answers

Option A is wrong because a Data Lookup definition is used to populate a variable from a database table based on a lookup field, not to dynamically compute a value like the current user's manager email. Option B is wrong because a Flow Designer action runs after the form is submitted, not on form load, so it cannot pre-populate the variable before the user sees the form. Option C is wrong because an onChange Catalog Client Script triggers only when a specific variable changes, not on form load, and cannot automatically populate a field without a triggering event.

Full explanation →
14
MCQmedium

A large organization with 15,000 active users recently migrated from UI15 to UI16. Users are now reporting that form load times have increased significantly, especially on the Incident form, which has many sections and fields. The system administrator notices that the form is taking over 8 seconds to load. The administrator has checked the server logs and found that the majority of time is spent on 'getFormMeta' calls. The Incident form uses several UI policies, client scripts, and catalog client scripts. There are no business rules with heavy scripts on the table. Which course of action should the administrator take to improve form load performance?

A.Request an upgrade to the latest ServiceNow release which includes performance improvements
B.Set the system property 'glide.ui.form.load.max_sections' to 5 to limit sections
C.Convert client scripts to UI policies to leverage server-side execution
D.Review and disable unnecessary UI policies that are set to run on form load
AnswerD

UI policies execute on load and can be heavy; disabling unneeded ones improves performance.

Why this answer

Option C is correct because disabling UI policies that run on form load can significantly reduce client-side processing. Option A is wrong because reducing system properties may affect other tables. Option B is wrong because client scripts can be optimized, but UI policies are often heavier.

Option D is wrong because upgrading is not a quick fix and may not address the root cause.

Full explanation →
15
MCQhard

An administrator creates this after business rule on the 'catalog_item' table but notices that no work notes are being added. What is the most likely reason?

A.The script is missing a 'current.update()' call.
B.The business rule order is too low.
C.The business rule is not set to run 'after'.
D.The 'work_notes' field is not on the form.
AnswerA

In after business rules, modifications are not automatically saved; current.update() is required.

Why this answer

The 'after' business rule runs after the database insert or update operation has already completed. At that point, any changes made to field values in the script, such as setting work_notes, are not automatically saved back to the database. The script must explicitly call current.update() to persist those changes, otherwise the work_notes value is lost.

Exam trap

The trap here is that candidates assume any field assignment in a business rule is automatically saved, but ServiceNow only auto-saves changes in 'before' business rules, not in 'after' business rules.

How to eliminate wrong answers

Option B is wrong because business rule order only affects the sequence of execution among multiple rules on the same table and same phase; it does not prevent a single rule from executing or saving field changes. Option C is wrong because the administrator explicitly created the rule as an 'after' business rule, and the issue is not about the phase but about missing persistence of field updates. Option D is wrong because the work_notes field does not need to be on the form for a business rule to set it; business rules operate at the database layer and can modify any field regardless of form configuration.

Full explanation →
16
MCQeasy

Refer to the exhibit. A catalog client script with the above code runs on load of a catalog item. Which statement is true?

A.The category variable will be set to 'software' only if the user does not change it.
B.The script will run on every page load and set the category to 'software'.
C.The script will cause an error because onLoad should use g_form.setDisplay.
D.The script will only run if the variable 'category' is visible.
AnswerB

onLoad runs each time the form loads, unconditionally setting the value.

Why this answer

Option B is correct because the `onLoad` catalog client script runs every time the catalog item form is loaded, and the code `g_form.setValue('category', 'software')` unconditionally sets the category field to 'software' on each load. This overrides any previous value or user input from a prior session, ensuring the field is always set to 'software' when the form renders.

Exam trap

ServiceNow often tests the distinction between `onLoad` (runs every time the form loads) and `onChange` (runs only when a specific field changes), leading candidates to mistakenly think `onLoad` scripts run only under certain conditions like user interaction or field visibility.

How to eliminate wrong answers

Option A is wrong because the script runs on every load and sets the category to 'software' regardless of whether the user changes it; the user's change would be overwritten on the next load, not preserved. Option C is wrong because `g_form.setValue` is the correct method for setting a field's value in an `onLoad` client script; `g_form.setDisplay` controls visibility, not value assignment, and no error occurs. Option D is wrong because the script executes on every page load irrespective of the field's visibility; visibility does not affect the execution of `onLoad` scripts.

Full explanation →
17
MCQhard

A custom table 'u_custom_server' extends 'cmdb_ci_server' and has additional fields. The admin notices that while regular attribute updates on the parent table propagate correctly to the child, some custom fields are not being updated during discovery. What is the most likely cause?

A.The custom fields are not defined as 'Active' in the dictionary.
B.The discovery probe does not have access to the custom fields.
C.The identification rule does not include custom fields.
D.The custom table has a stale glide record.
AnswerC

If custom fields are not part of the identification rule, discovery will not update them.

Why this answer

Option C is correct because ServiceNow's CMDB identification and reconciliation framework uses identification rules to determine which fields are used to match CI records during discovery. Custom fields on a child table like 'u_custom_server' are not automatically included in the parent table's identification rule; they must be explicitly added to the identification rule for the CI class. Without this, the discovery probe may create duplicate CIs or fail to update those custom fields, as the system does not consider them part of the unique identifier or update set.

Exam trap

The trap here is that candidates often assume discovery updates all fields on a table automatically, but ServiceNow's CMDB requires explicit configuration of identification rules to control which fields are used for matching and updating, especially for custom fields on extended tables.

How to eliminate wrong answers

Option A is wrong because if a custom field is not marked as 'Active' in the dictionary, it would not appear in the form or be available for data entry, but discovery updates are driven by the identification and reconciliation engine, not the field's active state. Option B is wrong because discovery probes operate at the system level and do not have field-level access controls; they use MID servers and credentials to collect data, and any field that exists in the table can be populated if the probe is configured to collect it. Option D is wrong because a 'stale glide record' is not a standard ServiceNow concept; records can be stale due to reconciliation rules or update failures, but this is a symptom, not a root cause, and the issue is specifically about identification rules not including custom fields.

Full explanation →
18
MCQhard

A notification on the 'incident' table is configured to send an email when the 'state' field changes to 'Resolved'. The condition uses the condition builder with 'State changes to Resolved'. However, the notification also sends when an incident is updated without a state change. What is the most likely cause?

A.The condition builder is incorrectly configured and should use 'State equals Resolved'.
B.The notification has multiple subscribers causing duplicate evaluations.
C.The 'Send when' field is set to 'Record is updated' instead of 'Record is inserted or updated'.
D.A business rule in the background updates the state to 'Resolved' on every update, so the notification fires each time.
AnswerD

Correct: If a BR always sets state to Resolved, the condition evaluates true on every update.

Why this answer

Option C is correct. The condition builder 'State changes to Resolved' fires on any update that meets the condition, but if there is no state change, it might still fire if the condition script is not properly checking the previous value. The most common cause is that the notification is also triggered by a business rule that updates the incident and sets state to Resolved even when state didn't change.

Option A is wrong because the condition builder is fine. Option B is wrong because the 'Send when' setting does not cause that. Option D is wrong because subscribers don't affect condition.

Full explanation →
19
Multi-Selecthard

Which TWO of the following are true about catalog client scripts in ServiceNow?

Select 2 answers
A.They use GlideRecord to query data.
B.They can run on both client and server.
C.They are defined per catalog item only.
D.They can be triggered on load, onChange, or onSubmit.
E.They can access the g_form API.
AnswersD, E

These are the standard trigger points for catalog client scripts.

Why this answer

Option D is correct because catalog client scripts can be triggered on three specific events: onLoad (when the form loads), onChange (when a field value changes), and onSubmit (when the form is submitted). These triggers allow dynamic client-side behavior such as field validation, auto-population, or conditional visibility without requiring a server round-trip.

Exam trap

The trap here is confusing catalog client scripts with catalog UI policies: candidates often think client scripts can use GlideRecord (server-side) or run on the server, but ServiceNow enforces a strict client-server separation where client scripts cannot access server-side APIs directly.

Full explanation →
20
MCQhard

Your organization has implemented a notification on the 'incident' table to send an email when an incident's priority is changed. The notification is configured with a condition: 'Priority changes to 1 - Critical' and uses the 'Send email' action. Recently, administrators noticed that for a single incident that was updated multiple times, duplicate emails were sent. The incident record's audit history shows that the priority was only changed once. What is the most likely cause?

A.The email notification is configured with 'Send when record is updated' and the update triggers multiple business rules that each fire the notification.
B.The 'Send email' action is set to 'Send to all users in the role' and multiple users have the same role.
C.The notification is also triggered by the 'cmdb_ci' field update.
D.The notification condition has a script that incorrectly evaluates to true multiple times.
AnswerD

Correct: A buggy script could cause multiple triggers.

Why this answer

Option D is correct because the notification condition uses a script that evaluates to true multiple times during a single update, causing the 'Send email' action to fire repeatedly. Even though the audit history shows the priority changed only once, a flawed script can return true for other field changes or on subsequent database operations, leading to duplicate emails. This is a common issue when conditions are not properly scoped to detect only the specific field change.

Exam trap

The trap here is that candidates assume duplicate emails are caused by multiple users or multiple triggers, but the real issue is a poorly written condition script that evaluates to true on every update, not just when the priority field actually changes.

How to eliminate wrong answers

Option A is wrong because 'Send when record is updated' triggers the notification once per update transaction, not multiple times; multiple business rules firing would still result in a single notification per update unless they explicitly call the notification action. Option B is wrong because 'Send to all users in the role' sends one email per user, but the issue is duplicate emails for the same user, not multiple recipients. Option C is wrong because the 'cmdb_ci' field update would not cause the notification to fire unless the condition explicitly checks that field; the condition is set to 'Priority changes to 1 - Critical', so unrelated field updates do not trigger it.

Full explanation →
21
MCQhard

A large enterprise uses ServiceNow for IT Service Management. They have a complex SLA structure with multiple SLA definitions on the Incident table. Each SLA definition has conditions based on category, priority, and assignment group. The company recently merged with another organization, and the new combined company has doubled the number of incidents. The SLA performance has degraded significantly: SLA breaches have increased by 40%, and the SLA engine is taking longer to process. The system administrator has checked the instance health and found that the SLA job is running but taking an average of 5 minutes per execution, and there are often multiple instances of the SLA job queued. The administrator needs to improve SLA performance without changing the business requirements. Which course of action is most effective?

A.Consolidate similar SLA definitions by using conditions with OR operators and simplify the SLA structure to reduce the number of active SLA definitions.
B.Schedule the SLA job to run only during business hours to reduce off-hours processing.
C.Disable SLA evaluation for incidents with low priority (4 and 5) to reduce volume.
D.Increase the SLA job interval from 1 minute to 5 minutes to reduce the frequency of execution.
AnswerA

Fewer SLA definitions mean fewer SLA instances to create and evaluate, improving performance.

Why this answer

Option A is correct because consolidating SLA definitions reduces the number of active SLA records that the SLA job must evaluate per incident. The SLA job iterates through all active SLA definitions for each incident; fewer definitions mean fewer evaluations per incident, directly reducing processing time and the likelihood of queued job instances. This approach preserves all business requirements by using OR conditions to combine similar rules rather than removing them.

Exam trap

The trap here is that candidates often choose to increase the job interval (Option D) thinking it reduces load, but this only delays processing and does not fix the underlying inefficiency of too many SLA definitions being evaluated per incident.

How to eliminate wrong answers

Option B is wrong because scheduling the SLA job only during business hours would delay SLA processing for incidents created outside those hours, potentially causing breaches due to late evaluation and violating business requirements. Option C is wrong because disabling SLA evaluation for low-priority incidents changes the business requirements by removing SLA coverage for those incidents, which is not allowed per the question. Option D is wrong because increasing the SLA job interval from 1 minute to 5 minutes reduces execution frequency but does not address the root cause of excessive processing per execution; it would simply delay breach detection and could worsen the backlog of queued jobs.

Full explanation →
22
MCQhard

A catalog item has multiple variables, and the administrator wants to show a variable only if a previous variable is set to a specific value. Which feature should be used?

A.UI Policy
B.Client Script
C.Catalog Client Script
D.Access Control List (ACL)
AnswerA

UI policies control visibility and mandatory conditions.

Why this answer

A UI Policy is the correct feature because it allows an administrator to dynamically show or hide catalog item variables based on the value of a previous variable, without requiring any client-side scripting. UI Policies run on the client side and evaluate conditions in real-time, making them ideal for this declarative, condition-based visibility requirement.

Exam trap

The trap here is that candidates often confuse Catalog Client Scripts with UI Policies because both can react to variable changes, but UI Policies are the correct no-code solution for simple show/hide logic, while Catalog Client Scripts require scripting and are intended for more complex client-side behaviors.

How to eliminate wrong answers

Option B is wrong because Client Scripts are used for client-side logic like field validation or value manipulation, not for controlling variable visibility based on variable values. Option C is wrong because Catalog Client Scripts are designed for scripting on catalog forms (e.g., onChange or onSubmit), but they require JavaScript code and are not the declarative, no-code feature intended for simple show/hide conditions. Option D is wrong because Access Control Lists (ACLs) control data access and security permissions, not the visibility of form fields or variables.

Full explanation →
23
Multi-Selectmedium

An administrator is creating a service catalog item for a VPN access request. The item should only be available to employees in the IT department. Which two configurations can enforce this? (Choose two.)

Select 2 answers
A.Use a Flow to check department and redirect to error page.
B.Set the 'Available for' field on the catalog item to a User Criteria record.
C.Add a catalog client script to check department and hide the item.
D.Variable condition to show item only if department is IT.
E.User Criteria with condition 'Department is IT'.
AnswersB, E

Correct: The 'Available for' field directly controls who can order the item.

Why this answer

Option B is correct because the 'Available for' field on a catalog item allows you to restrict visibility based on User Criteria records, which can define conditions like department membership. This configuration ensures that only users matching the criteria (e.g., IT department) can see and request the item in the service catalog.

Exam trap

The trap here is that candidates often confuse client-side scripting (catalog client scripts) with server-side access control, or they think variable conditions can control item visibility, when in fact only User Criteria or the 'Available for' field properly restrict catalog item availability.

Full explanation →
24
MCQeasy

A user can see a catalog item in the Service Portal but when they click on it, they get an error 'Item not available'. What is the most likely reason?

A.The user does not have the appropriate role to view the item.
B.The Service Portal catalog page is misconfigured.
C.The item's 'Available for' condition is not met.
D.The catalog item is set to 'Inactive'.
AnswerC

Correct: User criteria can make an item visible but not available for order.

Why this answer

The error 'Item not available' when clicking a catalog item in Service Portal typically occurs because the item's 'Available for' condition evaluates to false for the current user. This condition can be based on user criteria, such as location, department, or other variables, and when unmet, the item appears in the catalog but cannot be requested. Option C is correct because this is the most common cause of the described behavior.

Exam trap

The trap here is that candidates often confuse visibility (controlled by ACLs or roles) with availability (controlled by 'Available for' conditions), assuming that if an item is visible, it must be requestable.

How to eliminate wrong answers

Option A is wrong because if the user lacked the appropriate role to view the item, the item would not appear in the catalog at all, not just fail when clicked. Option B is wrong because a misconfigured Service Portal catalog page would typically cause display or navigation issues, not a specific 'Item not available' error tied to a single item's availability logic. Option D is wrong because if the catalog item were set to 'Inactive', it would not be visible to any user in the Service Portal, contradicting the scenario where the user can see it.

Full explanation →
25
MCQmedium

An administrator wants to add a new application 'HR Service' to the application navigator with a custom icon. Which table stores the application menu and module definitions?

A.sys_app
B.sys_app_application
C.sys_ui_module
D.sys_app_module
AnswerB

sys_app_application stores application menu definitions.

Why this answer

The table `sys_app_application` stores the definitions for application menus and modules, which are used to build the application navigator in ServiceNow. When an administrator adds a new application like 'HR Service' with a custom icon, the menu and module records are created in this table, linking to the application record in `sys_app`.

Exam trap

The trap here is that candidates often confuse `sys_app` (the application definition) with `sys_app_application` (the menu/module definitions), or mistakenly recall the non-existent `sys_app_module` table from similar-sounding concepts in other platforms.

How to eliminate wrong answers

Option A is wrong because `sys_app` stores the application record itself (e.g., name, vendor, version), not the menu or module definitions. Option C is wrong because `sys_ui_module` is a legacy table for UI modules in the old UI16 navigator, not the current standard for application menu/module definitions. Option D is wrong because `sys_app_module` does not exist as a standard table in ServiceNow; the correct table for modules within an application is `sys_app_application`.

Full explanation →
26
MCQhard

A company wants to block all update operations on the 'problem' table for users with only the 'itil' role, except for the user who created the record. Which ACL configuration should be used?

A.Create an ACL with type 'record', operation 'write', role 'itil', condition script 'current.assignment_group == gs.getUser().getMyGroups()', and set 'Requires role' true.
B.Create an ACL with type 'record', operation 'write', role 'itil', condition script empty, and uncheck 'Requires role'.
C.Create an ACL with type 'record', operation 'write', role 'itil', condition script 'current.created_by != gs.getUserID()', and set 'Requires role' true.
D.Create an ACL with type 'record', operation 'write', role 'itil', condition script 'current.created_by == gs.getUserID()', and set 'Requires role' true.
AnswerC

Denies write to itil users if they are not the creator.

Why this answer

Option C is correct because it uses a condition script that denies write access to users with the 'itil' role when the current record's creator is not the logged-in user. The ACL type 'record' with operation 'write' and 'Requires role' checked ensures that only users with the 'itil' role are evaluated, and the condition script 'current.created_by != gs.getUserID()' returns true for users who did not create the record, thus blocking their update operations. This matches the requirement to block all updates except for the record creator.

Exam trap

The trap here is that candidates often confuse the condition logic, selecting Option D because they think 'current.created_by == gs.getUserID()' will allow only the creator, but in a deny ACL, a true condition blocks access, so Option D would block the creator instead of allowing them.

How to eliminate wrong answers

Option A is wrong because it uses a condition script checking 'current.assignment_group == gs.getUser().getMyGroups()', which is irrelevant to the requirement of blocking updates based on record creator; it would incorrectly allow or deny updates based on group membership, not creator identity. Option B is wrong because it leaves the condition script empty and unchecks 'Requires role', which would apply the ACL to all users regardless of role, failing to restrict only users with the 'itil' role and potentially blocking all users from updating the table. Option D is wrong because it uses the condition script 'current.created_by == gs.getUserID()', which returns true for the record creator, thus allowing updates for the creator but also inadvertently allowing updates for any user who matches the creator condition; however, the requirement is to block all updates except for the creator, so the condition should deny when the user is not the creator, not allow when they are.

Full explanation →
27
MCQhard

An organization uses ServiceNow Discovery to populate the CMDB. They notice that some CIs are missing required relationships after discovery. What is the most likely reason?

A.The discovered CIs are in different classes that do not have relationship rules.
B.The discovery probes and sensors are not configured to create relationships.
C.The IRE is set to 'reconcile only' and not 'create'.
D.The relationship type is not defined in the CMDB.
AnswerB

Probes and sensors must be designed to identify and create relationships during discovery.

Why this answer

Discovery probes and sensors are responsible for collecting data from devices, but they do not automatically create relationships unless specifically configured to do so. If the probes and sensors lack the necessary configuration to identify and record relationships, the discovered CIs will remain isolated in the CMDB. This is the most common cause of missing relationships after a Discovery run.

Exam trap

The trap here is that candidates often confuse the IRE's role (which handles CI creation and reconciliation) with the role of Discovery probes/sensors (which handle relationship creation), leading them to incorrectly select Option C.

How to eliminate wrong answers

Option A is wrong because relationship rules are defined between CI classes, and if the discovered CIs belong to classes that do not have relationship rules, the IRE would still create the CIs but simply not populate relationships; the question states that relationships are missing, not that the CIs themselves are missing. Option C is wrong because the IRE's 'reconcile only' mode prevents creation of new CIs but does not affect relationship creation; relationships are created by Discovery probes/sensors, not by the IRE. Option D is wrong because if the relationship type were not defined in the CMDB, Discovery would still create the CIs and the relationship would simply be stored with a generic or default type, not be entirely absent.

Full explanation →
28
Drag & Dropmedium

Drag and drop the steps to create a new UI Policy 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

Why this order

UI Policies control form behavior client-side.

Full explanation →
29
Matchingmedium

Match each ServiceNow flow designer action to its purpose.

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

Concepts
Matches

Insert a new record into a table

Modify an existing record

Retrieve data from a record

Send an email notification

Execute custom server-side script

Why these pairings

Flow Designer uses these actions to automate processes.

Full explanation →
30
MCQhard

During a CMDB health review, an administrator finds that many CI records have the same serial number but different names and IP addresses. What is the most likely root cause?

A.The CMDB has a scheduled job that deletes old CIs.
B.The CI class has a unique constraint on the name field.
C.The identification rule for the CI class does not include the serial number.
D.The reconciliation rule is set to 'Create' instead of 'Update'.
AnswerC

Without serial number as an identifier, the system creates new records instead of updating existing ones.

Why this answer

The correct answer is C because the identification rule determines which fields are used to uniquely identify a CI. If the serial number is not included in the identification rule, the CMDB cannot detect duplicates based on serial number, allowing multiple CIs with the same serial number but different names and IP addresses to be created. This is a common misconfiguration that leads to CI proliferation and data inconsistency.

Exam trap

The trap here is that candidates often confuse identification rules with reconciliation rules, assuming that reconciliation settings control duplicate detection, when in fact identification rules define the uniqueness criteria that trigger reconciliation.

How to eliminate wrong answers

Option A is wrong because a scheduled job that deletes old CIs would remove CIs based on age or last updated time, not cause duplicate serial numbers with different names and IP addresses. Option B is wrong because a unique constraint on the name field would prevent duplicate names, but the issue here is duplicate serial numbers with different names, so a name constraint would not cause or prevent this problem. Option D is wrong because setting the reconciliation rule to 'Create' instead of 'Update' would cause new CIs to be created on every import, but it would not specifically result in the same serial number appearing on multiple CIs with different names and IPs; the identification rule is what controls how duplicates are detected.

Full explanation →
31
MCQmedium

Given the IRE identification rule shown, what will happen when a Discovery probe sends a CI with a name that already exists in the CMDB but with a different business_service?

A.The discovery will fail and not create or update any CI.
B.The existing CI will be updated with the new business_service.
C.A new CI will be created because the business_service is different.
D.The identification rule will match based on name only, ignoring business_service.
AnswerC

Since the combination of name and business_service does not match, IRE creates a new CI.

Why this answer

The IRE (Identification and Reconciliation Engine) rule in ServiceNow uses the 'name' field as the primary identifier for CIs. When a Discovery probe sends a CI with a name that already exists but a different business_service, the IRE treats the business_service as a separate attribute, not part of the identification key. Therefore, it creates a new CI because the combination of identification attributes (name alone) does not match any existing CI when the business_service differs, as the rule does not include business_service in the match criteria.

Exam trap

The trap here is that candidates assume the 'name' field is a unique identifier across all attributes, but ServiceNow's IRE treats each identification rule independently, and a different non-key attribute like business_service forces a new CI creation, not an update or failure.

How to eliminate wrong answers

Option A is wrong because Discovery does not fail; the IRE processes the CI and either creates or updates based on the identification rule, not failing due to a name match with a different attribute. Option B is wrong because the existing CI will not be updated with the new business_service; the IRE only updates CIs when all identification attributes match, and since business_service is not part of the identification rule, a name match alone does not trigger an update. Option D is wrong because the identification rule does not match based on name only; it matches based on the defined identification attributes (name), but the rule's behavior is to create a new CI when the business_service differs, not to ignore it.

Full explanation →
32
MCQmedium

During an import, the source data contains duplicate records that should be ignored (not imported). The target table has a unique key field u_employee_id. Which configuration in the transform map will prevent these duplicates from creating new records?

A.Use a script in the 'On Before' transform to check for existing records.
B.Set the 'Reject duplicates' checkbox on the transform map.
C.Set the 'Coalesce' field to true on the field mapping for u_employee_id.
D.Configure a business rule on the target table to reject duplicates.
AnswerC

Coalescing on a unique identifier prevents duplicate key imports by matching existing records.

Why this answer

Coalesce on a unique field ensures that if a record with the same value already exists, the transform will update or skip (based on action). Option B is not a real setting. Option C could work but is not the best practice.

Option D is not appropriate.

Full explanation →
33
MCQeasy

A company has a business rule that runs on the Incident table during update. The rule checks if the state is 'In Progress' and sets a field. However, after saving, the field is not being set. Which of the following is the most likely cause?

A.The business rule is using 'setValue' instead of 'setDisplayValue'.
B.The business rule is set to run after the record updates but another business rule with a higher order reverts the field.
C.The business rule has the condition 'Current state changes' unchecked.
D.The business rule is set to run on 'display' instead of 'update'.
AnswerB

A higher-order rule can modify the field after this rule sets it.

Why this answer

Option B is correct because if a business rule runs after the record updates (i.e., 'When to run' is set to 'After'), and another business rule with a higher order number runs later and reverts the field, the first rule's change will be overwritten. The order of execution is determined by the 'Order' field; lower numbers run first. Since the field is not being set after save, a higher-order 'After' rule is the most likely culprit, as it can undo the change made by the original rule.

Exam trap

The trap here is that candidates often assume a business rule not working is due to a configuration error like using the wrong method or missing a condition, but the real issue is often the execution order of multiple 'After' business rules where a higher-order rule reverts the change.

How to eliminate wrong answers

Option A is wrong because 'setValue' sets the field's internal value, while 'setDisplayValue' sets the display value for choice fields; using 'setValue' is correct for setting a field value and would not prevent the field from being set. Option C is wrong because the condition 'Current state changes' being unchecked means the rule runs on every update regardless of state change, which would not prevent the field from being set; in fact, it would make the rule run more often. Option D is wrong because a business rule set to run on 'display' would not execute during an update operation at all; it would only run when the record is viewed, so it would never set the field during save, but the question states the rule 'runs on the Incident table during update', implying it is configured to run on update, not display.

Full explanation →
34
MCQhard

Refer to the exhibit. An incident is created with state 'New' (1). The user creating the incident has the role 'itil', not 'admin'. After the business rule runs, what is the value of the priority field?

A.The priority remains null because the ACL denies write for non-admin users.
B.The priority is set to 1 because the business rule runs before the ACL check.
C.The priority is set to 1 but the update fails due to ACL.
D.The priority is set to 1 because business rules run with system user privileges.
AnswerD

Business rules execute with system user, so ACLs are not enforced.

Why this answer

The business rule runs before insert and sets priority to 1. However, the ACL for writing to priority requires admin role. The business rule runs with system user privileges, so it bypasses ACLs.

Therefore, the priority is set to 1.

Full explanation →
35
MCQmedium

A company wants to ensure that when a server CI is retired, all its associated running services are automatically updated to reflect the retirement. What is the best practice?

A.Configure a business rule on the CI class to update related CIs on state change.
B.Use the CI Lifecycle Manager to define a retirement business rule.
C.Use the Relationship Viewer to manually edit each relationship.
D.Create a scheduled job to check for retired CIs and update dependencies.
AnswerB

CI Lifecycle Manager offers built-in capabilities to trigger updates on related CIs when a CI is retired.

Why this answer

The CI Lifecycle Manager provides a dedicated framework for defining lifecycle states and automating actions when a CI transitions between states, such as retirement. By configuring a retirement business rule within the CI Lifecycle Manager, you can automatically update or retire all associated running services when a server CI is retired, ensuring consistency without manual intervention.

Exam trap

The trap here is that candidates often assume a simple business rule on the CI class is sufficient, but the SNOW-CSA exam emphasizes the CI Lifecycle Manager as the best practice for managing CI state transitions and their cascading effects on related records.

How to eliminate wrong answers

Option A is wrong because a business rule on the CI class can trigger on state change, but it lacks the lifecycle-aware context and built-in relationship handling that the CI Lifecycle Manager provides; it would require custom scripting to manage all related services. Option C is wrong because manually editing each relationship via the Relationship Viewer is not scalable and contradicts the goal of automation. Option D is wrong because a scheduled job introduces latency and complexity, and it does not provide real-time, event-driven updates when a CI is retired, unlike the lifecycle framework.

Full explanation →
36
Multi-Selectmedium

An ACL on the Task table has a role condition requiring the 'itil' role. A user with the 'itil' role is trying to update a task but is denied. Which TWO factors could be causing this? (Select two.)

Select 2 answers
A.The user also has a role that denies access.
B.The update operation requires a specific condition script that returns false.
C.The record is locked by another user.
D.Another ACL on the same table denies write access.
E.The ACL is set to 'Create' instead of 'Write'.
AnswersB, D

A script condition returning false denies access.

Why this answer

Options A and D are correct. A condition script that returns false would deny access. Another more specific ACL that denies access would take precedence.

Option B is wrong because roles do not deny; they allow. Option C is wrong because the user has the required role. Option E is wrong because record locking is not ACL-related.

Full explanation →
37
MCQhard

An SLA is paused due to a pause condition. The administrator wants to permanently stop tracking SLA for a specific incident. What should be done?

A.Set the SLA state to 'Cancelled' on the indicator.
B.Remove the incident from the SLA definition condition.
C.Set the SLA definition to inactive.
D.Delete the SLA record from the SLA table.
AnswerA

Cancelling stops tracking for that specific incident.

Why this answer

Option A is correct because setting the SLA state to 'Cancelled' on the indicator permanently stops tracking for that specific incident without affecting other incidents or the SLA definition. This action marks the SLA as no longer applicable, and the system will not continue to calculate or update the SLA for that record.

Exam trap

The trap here is that candidates may confuse 'pausing' an SLA with 'cancelling' it, or think that modifying the SLA definition or deleting the record is the correct way to stop tracking for a single incident.

How to eliminate wrong answers

Option B is wrong because removing the incident from the SLA definition condition would modify the definition itself, potentially affecting future incidents that match the condition, and it does not stop tracking for the specific incident already attached. Option C is wrong because setting the SLA definition to inactive would stop all SLA tracking for any incident using that definition, not just the specific incident. Option D is wrong because deleting the SLA record from the SLA table would remove the historical data and could cause errors or data integrity issues; the correct approach is to cancel the SLA on the indicator, not delete the record.

Full explanation →
38
Multi-Selectmedium

Which THREE elements are required when creating a new report in the Reporting module? (Choose three.)

Select 3 answers
A.Condition
B.Group by field
C.Report name
D.Table
E.Chart type
AnswersC, D, E

Every report must have a name.

Why this answer

Option C is correct because every report in ServiceNow must have a unique Report name to identify and save it in the Reporting module. Without a name, the system cannot store or retrieve the report, and the Save button remains disabled until a name is provided.

Exam trap

ServiceNow often tests that candidates confuse optional configuration elements (like conditions and grouping) with mandatory fields, leading them to select Condition or Group by field instead of the required Report name, Table, and Chart type.

Full explanation →
39
MCQhard

A large enterprise with over 10,000 users and 50,000 active incidents has been using ServiceNow for two years. Recently, the IT managers have noticed that the incident form loads very slowly for end users, especially when opening existing records. The form contains over 40 fields including several reference fields like 'Configuration Item', 'Assignment group', and 'Assigned to'. The system administrator suspects that the form is slow due to the number of fields and the way they are loaded. Additionally, the admin wants to improve the user experience by reducing clutter. The admin is considering several approaches: (A) removing fields from the default view to reduce the number of fields loaded, (B) enabling 'Form Layout Personalization' so users can hide fields they don't need, (C) creating a new view with fewer fields and assigning it to all users via a UI policy based on role, (D) using 'Form Sections' to collapse fields into tabs. Which approach is the most effective for improving form load performance while maintaining usability?

A.Create a new view with only essential fields and assign it to users via a UI policy based on role.
B.Enable Form Layout Personalization so users can hide fields they don't need.
C.Remove fields from the default view to reduce the number of fields loaded.
D.Use Form Sections to collapse fields into tabs.
AnswerA

A lean view reduces the number of fields loaded, improving performance. UI policy can assign the view to appropriate roles.

Why this answer

Creating a new view with only essential fields and assigning it via a UI policy based on role directly reduces the number of fields loaded on the form, which minimizes database queries and client-side rendering overhead. This approach improves performance because ServiceNow loads all fields in a view, including reference fields that trigger additional lookups, so fewer fields mean faster load times. It also maintains usability by tailoring the form to specific roles, ensuring users see only relevant data without manual customization.

Exam trap

The trap here is that candidates confuse visual hiding (via personalization or sections) with actual removal of fields from the server-side load, but only reducing the fields in the view definition eliminates the performance overhead.

How to eliminate wrong answers

Option B is wrong because enabling Form Layout Personalization allows users to hide fields client-side, but the fields are still loaded in the DOM and their reference data is still fetched, so it does not improve form load performance. Option C is wrong because removing fields from the default view affects all users and can break workflows or hide required fields, reducing usability without a targeted approach. Option D is wrong because using Form Sections to collapse fields into tabs only hides them visually; all fields and their reference lookups are still loaded when the form opens, so performance remains unchanged.

Full explanation →
40
Multi-Selecthard

A notification is set to send an email when an incident is updated with 'Urgency' = 'High'. The notification is not sending. Which THREE of the following could be the cause? (Select three.)

Select 3 answers
A.The notification has a condition that also checks 'State' which is not met.
B.The user's email address is missing from the user record.
C.The email notification system is configured with SMTP but the mail server is unreachable.
D.The notification is set to 'Active' = false.
E.The incident record is being updated by a web service that does not trigger business rules.
AnswersA, B, D

If the condition includes additional criteria, they must all be met.

Why this answer

Option A is correct because a notification's condition can include multiple fields, such as 'State' in addition to 'Urgency'. If the condition requires 'State' to be a specific value that is not met when the incident is updated, the notification will not trigger. This is a common misconfiguration where the condition logic is more restrictive than intended.

Exam trap

ServiceNow often tests the distinction between a notification not being triggered (condition not met or inactive) versus a notification being triggered but failing to deliver (SMTP issue), and candidates mistakenly select SMTP issues when the question explicitly says 'not sending' meaning not triggered.

Full explanation →
41
MCQmedium

An administrator notices that a scheduled job that creates Catalog Tasks from a report runs successfully but produces duplicate tasks for the same request. What is the most likely cause?

A.The report does not filter out tasks that have already been created
B.The scheduled job uses the 'Run once' option
C.The report condition uses '=' instead of 'starts with'
D.The scheduled job runs too frequently
AnswerA

Without a filter, the job will create tasks for all records each time.

Why this answer

Option A is correct because the most likely cause of duplicate Catalog Tasks is that the report driving the scheduled job does not include a filter to exclude records for which a task has already been created. Without this filter, each time the job runs, it re-evaluates the same source records and creates a new task for each, leading to duplicates.

Exam trap

The trap here is that candidates often focus on scheduling frequency or operator syntax, missing the fundamental requirement that the report must be designed to exclude records that have already been processed.

How to eliminate wrong answers

Option B is wrong because the 'Run once' option would cause the job to execute only a single time, which would not produce duplicates across multiple runs. Option C is wrong because the operator used in the report condition ('=' vs 'starts with') affects string matching logic, not the creation of duplicate tasks from the same source data. Option D is wrong because while running too frequently could create multiple tasks if the report is not filtered, the frequency itself is not the root cause; the core issue is the lack of a filter to prevent re-processing already-handled records.

Full explanation →
42
MCQhard

A notification is configured to send an email when an incident is assigned to a user. However, users are receiving duplicate emails. Which of the following is the most likely cause?

A.The notification is triggered by a business rule that runs on after update.
B.The notification has 'Who will receive' set to both 'Assigned user' and 'User in group'.
C.The notification has two separate conditions that both evaluate to true.
D.The notification is set to 'Send for each record' and the record is being updated multiple times.
AnswerB

If both recipients are the same user (e.g., user is in the group and is the assigned user), they receive two emails.

Why this answer

Option B is correct because when 'Who will receive' is set to both 'Assigned user' and 'User in group', the notification can be sent to the same user twice if that user is both the assigned user and a member of the group. This is a common cause of duplicate emails in ServiceNow notifications, as the system evaluates each recipient list independently and sends separate emails.

Exam trap

ServiceNow often tests the misconception that duplicate emails are caused by multiple conditions or business rules, but the real trap is that selecting multiple recipient types in 'Who will receive' can cause the same user to receive the notification multiple times.

How to eliminate wrong answers

Option A is wrong because a business rule running on 'after update' does not inherently cause duplicate emails; it is the trigger for the notification, and duplicates would only occur if the notification itself has multiple recipients or multiple triggers. Option C is wrong because having two separate conditions that both evaluate to true would cause the notification to fire twice only if the notification is configured to send for each condition separately, but by default, a single notification with multiple conditions still sends one email per record update. Option D is wrong because 'Send for each record' is used for batch updates or multiple records, not for a single record being updated multiple times; duplicate emails from multiple updates would require the notification to be triggered on each update, not the 'Send for each record' setting.

Full explanation →
43
MCQhard

An SLA definition is configured to start when an incident's state changes to 'In Progress'. However, the SLA is not starting for incidents that are moved to 'In Progress'. The incident's assignment group is 'IT Support' and the SLA condition includes an additional filter: 'category = network'. What is the most likely cause?

A.The SLA schedule is set to 24x7 but the incident was created outside business hours.
B.The SLA definition has a pause condition that triggers on state change.
C.The incident's category is not 'network'.
D.The SLA definition is on the 'task' table instead of 'incident'.
AnswerC

The SLA condition includes 'category = network', so if the incident's category is different, the SLA will not start.

Why this answer

The SLA condition includes an additional filter requiring 'category = network'. If the incident's category is not set to 'network', the SLA will not start regardless of the state change to 'In Progress'. This is because SLA conditions in ServiceNow are evaluated as a whole; all conditions must be met for the SLA to begin.

Exam trap

The trap here is that candidates often overlook the additional filter condition and assume the state change alone should start the SLA, ignoring that all conditions in the SLA definition must be satisfied simultaneously.

How to eliminate wrong answers

Option A is wrong because the SLA schedule (24x7) would not prevent the SLA from starting; it only defines when time counts toward the SLA, not whether the SLA starts. Option B is wrong because a pause condition would stop an already-running SLA, not prevent it from starting; the issue is that the SLA never starts. Option D is wrong because the SLA definition is explicitly configured on the 'incident' table (as stated in the question), so being on the 'task' table would not apply here and would not cause this behavior.

Full explanation →
44
MCQhard

A catalog item uses a 'Catalog Client Script' to hide a variable when another variable is set to 'No'. However, the script is not working. The script is of type 'onChange' and the variable to hide is a 'Single Line Text'. What is the most likely cause?

A.The variable type 'Single Line Text' does not support hiding.
B.The script is missing a 'g_form.setDisplay()' call.
C.The script should be of type 'onSubmit' instead of 'onChange'.
D.The variable's 'Display' property is set to 'Static' or 'Read only'.
AnswerD

If Display is static, client scripts cannot hide it.

Why this answer

Option D is correct because when a variable's 'Display' property is set to 'Static' or 'Read only', the client-side script cannot override that setting via `g_form.setDisplay()`. The catalog client script runs on the client, but the variable's display behavior is enforced by the platform's UI policy layer, which takes precedence over client script calls. This is a common misconfiguration where the variable's display property is locked, preventing the onChange script from hiding it.

Exam trap

ServiceNow often tests the misconception that a missing `g_form.setDisplay()` call is the root cause, when in reality the variable's display property is locked by a UI policy or the variable's own configuration, which silently overrides the client script.

How to eliminate wrong answers

Option A is wrong because 'Single Line Text' variables fully support hiding via client scripts; there is no restriction on variable type for hiding. Option B is wrong because while `g_form.setDisplay()` is the correct method to hide a variable, the issue is not its absence but rather the variable's display property overriding the script's attempt. Option C is wrong because an 'onSubmit' script runs at form submission, not on variable change, so it would not dynamically hide the variable when the triggering field changes; 'onChange' is the correct type for this behavior.

Full explanation →
45
Multi-Selecteasy

Which TWO are valid options when configuring a module in the application navigator? (Choose two.)

Select 2 answers
A.Table name (optional)
B.Link type
C.Role (optional)
D.Condition filter
E.Module name (optional)
AnswersB, D

Link type defines what the module opens (list, form, etc.).

Why this answer

Option B is correct because the 'Link type' is a required configuration when adding a module to the application navigator. It determines how the module behaves when clicked, such as opening a new window, displaying in the same window, or using a specific UI action. Without setting the link type, the module cannot properly navigate the user to the intended target.

Exam trap

ServiceNow often tests the misconception that 'Table name' and 'Role' are optional fields, when in fact they are required for module configuration, while 'Condition filter' is an optional but valid advanced setting.

Full explanation →
46
MCQeasy

A company wants to allow end users to submit requests for new software installations through the Service Portal. The fulfillment process should automatically route requests to the software team based on the requested software category. Which configuration ensures this automation without additional custom scripting?

A.Use Flow Designer to create a flow that triggers on request submission and assigns the record.
B.Create an Assignment Rule that matches on the requested software category and assigns to the software group.
C.Set the Default Assignment on the Record Producer to the software group.
D.Create an Access Control Rule (ACL) to restrict the category field to the software team.
AnswerB

Assignment Rules automatically route records based on conditions.

Why this answer

Option B is correct because Assignment Rules in ServiceNow can automatically assign records to a group based on condition matching, such as the requested software category. This configuration requires no custom scripting and is the standard, out-of-box mechanism for routing catalog items or requests based on field values.

Exam trap

The trap here is that candidates often confuse Assignment Rules with Record Producer defaults or Flow Designer, thinking that any automation requires a flow, when in fact the out-of-box Assignment Rule is the correct and simplest tool for condition-based routing without custom scripting.

How to eliminate wrong answers

Option A is wrong because Flow Designer, while capable of automation, is a more complex, low-code tool that is not the simplest out-of-box solution for this specific routing need; it would be overkill and could require additional configuration beyond the basic assignment rule. Option C is wrong because setting a Default Assignment on the Record Producer would assign all requests from that producer to the software group, regardless of the category selected, which does not meet the requirement of routing based on the requested software category. Option D is wrong because an Access Control Rule (ACL) controls data visibility and edit permissions, not routing or assignment logic; it would not automate the assignment of requests.

Full explanation →
47
MCQeasy

An administrator wants to add a new section to the incident form to group related fields. Which tool should they use?

A.Dictionary Override
B.Application Navigator
C.UI Policy
D.Form Designer
AnswerD

Form Designer allows adding sections, fields, and configuring the form layout.

Why this answer

Option B is correct because the Form Designer is the modern tool for adding sections and rearranging fields on a form. Option A is wrong because Application Navigator is for navigating modules. Option C is wrong because UI Policies control field behavior, not layout.

Option D is wrong because Dictionary Overrides set field properties, not add sections.

Full explanation →
48
MCQhard

An import set transform map includes field maps with script actions. The import fails with 'Script execution error'. Where should the administrator look first?

A.Import set row errors
B.Data source configuration
C.Transform map's field map log
D.System log
AnswerD

The system log is a good source but may be less specific than row errors.

Why this answer

When a script action in a transform map field map throws an error, the system log (syslog) is the primary source for detailed JavaScript error messages, stack traces, and line numbers. Import set row errors only capture row-level failures like missing mandatory fields, not script execution details. The data source configuration and field map log do not store runtime script errors.

Exam trap

The trap here is that candidates often confuse 'import set row errors' (which show row-level validation failures) with 'script execution errors' (which are JavaScript runtime errors logged only in the system log), leading them to incorrectly select option A.

How to eliminate wrong answers

Option A is wrong because import set row errors capture row-level import failures (e.g., missing required fields, invalid reference qualifiers), but they do not contain JavaScript execution errors from script actions. Option B is wrong because the data source configuration defines how to connect to the source and parse records, but it does not log runtime script errors. Option C is wrong because the transform map's field map log shows field mapping details and transformation results, but it does not capture script execution errors; those are logged in the system log.

Full explanation →
49
MCQeasy

Refer to the exhibit. This JSON represents a table schema. What is the data type of the 'short_description' field?

A.Integer
B.String
C.Reference
D.Date
AnswerB

The type attribute is set to 'string'.

Why this answer

Option A is correct because the JSON shows 'type': 'string' for short_description. Options B, C, and D are incorrect.

Full explanation →
50
MCQhard

During peak usage, the Employee Center portal becomes slow. The administrator wants to improve performance without changing the user interface. What is the best practice approach?

A.Increase the instance size
B.Remove all widgets from the homepage
C.Disable the search feature
D.Enable caching for widgets
AnswerD

Caching reduces server calls and improves load times.

Why this answer

Enabling caching for widgets reduces server load and improves page load times by storing rendered widget output in memory, allowing subsequent requests to serve cached content without re-executing the underlying scripts or queries. This directly addresses performance degradation during peak usage without altering the user interface, making it the best practice approach.

Exam trap

ServiceNow often tests the misconception that performance issues must be solved by scaling infrastructure or removing features, rather than optimizing existing components through caching or other non-intrusive techniques.

How to eliminate wrong answers

Option A is wrong because increasing the instance size (vertical scaling) is a costly infrastructure change that does not address the root cause of inefficient widget rendering and may not be feasible or necessary; it also violates the constraint of not changing the user interface only indirectly. Option B is wrong because removing all widgets from the homepage would drastically alter the user interface and degrade the portal's functionality, contradicting the requirement to not change the UI. Option C is wrong because disabling the search feature would remove a core self-service capability, negatively impacting user experience and violating the requirement to maintain the existing interface.

Full explanation →
51
MCQmedium

A manager wants to share a dashboard with the entire team without granting individual roles. What is the easiest way to achieve this?

A.Create a report link and share via email
B.Set the dashboard to 'Public'
C.Publish the dashboard to a homepage
D.Add the dashboard to a role
AnswerD

Adding to a role would require assigning that role to users, which the manager wants to avoid.

Why this answer

Option D is correct because in ServiceNow, dashboards are shared by adding them to a role, which grants access to all users with that role without needing to assign individual users. This is the standard method for team-wide sharing, as roles are the primary access control mechanism for dashboards in the platform.

Exam trap

ServiceNow often tests the misconception that 'Public' or 'share via email' are valid sharing methods in ServiceNow, when in fact role-based access is the only supported and secure way to share dashboards with groups.

How to eliminate wrong answers

Option A is wrong because sharing a report link via email does not grant dashboard access; it only shares a static snapshot or link that may fail due to ACL restrictions, and it requires individual recipients to have appropriate permissions. Option B is wrong because ServiceNow dashboards do not have a 'Public' setting; visibility is controlled via roles, not a public toggle, and making a dashboard public would violate security best practices. Option C is wrong because publishing a dashboard to a homepage only makes it visible on that specific homepage, not to the entire team, and homepage visibility is still governed by role-based access controls.

Full explanation →
52
MCQeasy

A company wants to allow users to request IT equipment through the service portal. They need a catalog item that includes a variable for selecting a laptop model, and the request should be automatically assigned to the hardware team. What is the best way to accomplish the automatic assignment?

A.Create a business rule on the request table that assigns upon submission.
B.Create an assignment rule with the condition matching the catalog item.
C.Set the 'Assigned to' field in the catalog item definition.
D.Use Flow Designer to assign based on the catalog item.
AnswerB

Assignment rules automatically assign requests based on conditions, such as the catalog item.

Why this answer

Option B is correct because assignment rules in ServiceNow are specifically designed to automatically populate the 'Assigned to' field based on conditions such as the catalog item. By creating an assignment rule with a condition matching the catalog item (e.g., 'cat_item = IT Laptop Request'), the system will automatically assign the resulting request to the hardware team upon submission, without requiring additional scripting or manual intervention.

Exam trap

The trap here is that candidates often confuse the catalog item definition's 'Assigned to' field (which does not exist) with the assignment rule mechanism, or they overcomplicate the solution by choosing Flow Designer when a native, simpler feature (assignment rules) is the best practice.

How to eliminate wrong answers

Option A is wrong because business rules on the request table would require custom scripting and are not the recommended or best practice method for automatic assignment; they are more suited for data validation or complex logic. Option C is wrong because the 'Assigned to' field in the catalog item definition is not a standard field; catalog items define variables and workflow, not direct assignment fields, and setting it there would not trigger automatic assignment to a group. Option D is wrong because while Flow Designer can be used for assignment, it is an over-engineered solution for this simple requirement; assignment rules are the native, lightweight, and best-practice mechanism for automatic assignment based on catalog item conditions.

Full explanation →
53
MCQeasy

A form has a reference field that should display the ticket number. Which dictionary attribute controls the displayed value?

A.Reference qualifier
B.Choice field
C.Default value
D.Display value
AnswerD

The Display value attribute specifies the column to show when referencing a record.

Why this answer

Option A is correct because the 'Display value' attribute determines which field from the referenced table is shown. Options B, C, and D serve different purposes.

Full explanation →
54
MCQeasy

An administrator wants to create a new module under the 'User Administration' application menu. Which module type should be used to display a list of users?

A.List
B.Form
C.URL
D.Report
AnswerA

A list module shows a list of records from a table.

Why this answer

Option A is correct because a List module type is specifically designed to display a table of records from a specified table, such as the sys_user table for users. When creating a module under the 'User Administration' application menu, selecting List allows the administrator to configure the module to show a list view of user records, including columns, filters, and sorting options.

Exam trap

The trap here is that candidates may confuse a List module with a Report module, thinking a Report can display a list of users, but Reports are for aggregated or charted data, not a native record list view.

How to eliminate wrong answers

Option B is wrong because a Form module type is used to display a single record form for creating or editing a record, not a list of multiple users. Option C is wrong because a URL module type is used to link to an external or internal URL, such as a webpage or a report, not to display a native list of records from a table. Option D is wrong because a Report module type is used to display a report (e.g., chart, pivot table) based on a data source, not a standard list view of records.

Full explanation →
55
MCQmedium

An administrator notices that a custom module added to the application navigator is not visible to users with the 'itil' role. The module's 'Application' field is set to 'Global' and 'Roles' is empty. What is the most likely cause?

A.The module's 'Application' field is set to 'Global', which restricts visibility to admin users only.
B.The module's 'Active' flag is set to false.
C.The module was added using the 'Personalize Module' option, which is user-specific.
D.The 'Roles' field is empty, so the module is not visible to any user.
AnswerA

Global scope modules are admin-only unless roles are specified.

Why this answer

Option A is correct because when a module's 'Application' field is set to 'Global', it restricts visibility to users with the 'admin' role only, regardless of the 'Roles' field being empty. The 'Global' application scope is reserved for system-level modules that should only be accessible to administrators, not standard users like those with the 'itil' role. This is a common configuration trap where setting an application to 'Global' overrides the empty 'Roles' field, making the module invisible to non-admin users.

Exam trap

ServiceNow often tests the misconception that an empty 'Roles' field makes a module invisible to all users, when in fact it makes it visible to everyone, and the trap here is that candidates overlook how the 'Application' field set to 'Global' imposes admin-only visibility, overriding the default behavior of an empty 'Roles' field.

How to eliminate wrong answers

Option B is wrong because if the 'Active' flag were set to false, the module would not be visible to any user, including administrators, but the question states the module is not visible only to users with the 'itil' role, implying it might still be visible to admins. Option C is wrong because the 'Personalize Module' option creates user-specific modules that are only visible to the user who created them, but the scenario describes a custom module added to the application navigator, which is a system-wide change, not a personalization. Option D is wrong because an empty 'Roles' field means the module is visible to all users by default, not that it is hidden; the issue here is the 'Application' field set to 'Global' that overrides this behavior.

Full explanation →
56
MCQhard

A company has an SLA definition that starts when the state is 'New' and pauses when the state is 'On Hold'. A task is created with state 'New' at 10:00 AM. At 10:30 AM, the state is changed to 'In Progress'. At 11:00 AM, the state is changed to 'On Hold' for 30 minutes, then back to 'In Progress' at 11:30 AM. The task is resolved at 12:00 PM. The SLA has a 2-hour duration. What is the elapsed time used for SLA compliance?

A.2 hours
B.1 hour 30 minutes from state change to resolve
C.1 hour 30 minutes
D.1 hour
AnswerC

Correct calculation: 2 hours total minus 30 minutes pause.

Why this answer

The SLA definition starts when the state is 'New' and pauses when the state is 'On Hold'. The task was in 'New' from 10:00 to 10:30 (30 minutes), then 'In Progress' from 10:30 to 11:00 (30 minutes), then 'On Hold' from 11:00 to 11:30 (30 minutes, paused), then 'In Progress' from 11:30 to 12:00 (30 minutes). The total elapsed time for SLA compliance is the sum of non-paused time: 30 + 30 + 30 = 1 hour 30 minutes, which is within the 2-hour SLA duration.

Exam trap

The trap here is that candidates often forget to include the time before the first state change (the initial 'New' state) and incorrectly calculate elapsed time from the first state change or only after the hold, leading to wrong answers like B or D.

How to eliminate wrong answers

Option A is wrong because it assumes the entire 2-hour SLA duration was consumed, but the SLA was paused for 30 minutes while on hold, so the actual elapsed time is less. Option B is wrong because it incorrectly calculates from the first state change at 10:30 to resolve at 12:00, which is 1 hour 30 minutes, but this ignores the initial 30 minutes in 'New' state that also counts toward the SLA. Option D is wrong because it only counts the time after the hold period (11:30 to 12:00), omitting the 30 minutes in 'New' and the 30 minutes in 'In Progress' before the hold.

Full explanation →
57
MCQhard

An SLA is breached, but the breach time appears incorrect. The SLA definition uses a business schedule that excludes weekends. The incident was created on Friday at 5 PM and breached on Monday at 8 AM. Why did the breach time not exclude the weekend?

A.The schedule's 'Use schedule for progress' is unchecked
B.The business schedule is not attached to the SLA definition
C.The SLA condition is not met
D.The schedule's time zone is incorrect
AnswerC

An unmet condition would prevent SLA tracking, but the breach message indicates tracking occurred. This is incorrect.

Why this answer

If the business schedule is not attached to the SLA definition, the system uses the default schedule (which includes weekends). The proper attachment is necessary for schedule-based SLA calculations.

Full explanation →
58
MCQmedium

A system administrator wants to create a catalog item that allows users to request a new software license. The item needs to have a variable that lets the user choose the software from a list, and then automatically calculate the cost based on the license type and quantity. Which variable type should be used for the software selection?

A.Reference
B.Lookup Select
C.Select Box
D.Record Producer
AnswerB

Lookup Select dynamically loads options from a table and can display additional fields.

Why this answer

A Lookup Select variable type is correct because it allows the user to choose a software from a list defined in a lookup table, and it can store a reference to the lookup record while also enabling dynamic calculations (e.g., cost based on license type and quantity) via catalog client scripts or variable conditions. Unlike a Select Box, a Lookup Select maintains a separate table of options that can be easily updated without modifying the catalog item, and it supports advanced features like dependent lookups and default values from the lookup table.

Exam trap

The trap here is that candidates often confuse a Lookup Select with a Select Box, assuming both are interchangeable, but the Lookup Select is specifically designed for dynamic, table-driven lists that support advanced automation like cost calculations, whereas a Select Box is static and limited to hardcoded choices.

How to eliminate wrong answers

Option A is wrong because a Reference variable is used to link to a specific record in a table (e.g., a user record or a hardware asset), not to provide a static list of software choices for a catalog item. Option C is wrong because a Select Box provides a static list of choices defined directly on the variable, which cannot be easily maintained or updated without editing the catalog item, and it does not support dynamic calculations or dependent lookups as seamlessly as a Lookup Select. Option D is wrong because a Record Producer is a type of catalog item that creates a record in a specified table, not a variable type for user input selection.

Full explanation →
59
MCQhard

Refer to the exhibit. A ServiceNow administrator created a catalog item that allows users to select a CI via a reference variable named 'ci'. The business rule shown is supposed to update the CI's operational status to 'In Production' when the requested item is closed complete. However, the CI status is not being updated. What is the most likely cause?

A.The condition 'current.state.changesTo(3)' is incorrect; it should check if the state is already 3.
B.The script does not properly retrieve the CI record because current.variables.ci returns the sys_id but may not be accessible directly in an after business rule without using the sc_item_option table.
C.The reference variable 'ci' is not storing the sys_id of the CI; it stores the display value.
D.The business rule runs 'Before' instead of 'After', so the state hasn't changed yet.
AnswerB

Correct: Variable values are stored in the sc_item_option table and may not be directly accessible via current.variables in an after business rule. The script should use a GlideRecord query on sc_item_option.

Why this answer

Option B is correct because in an 'after' business rule on the Requested Item (sc_req_item) table, the variable values from the catalog item are not directly accessible via current.variables.ci. Instead, they are stored in the sc_item_option table and must be retrieved using a GlideRecord query on sc_item_option joined to the requested item's sys_id. The script attempts to use current.variables.ci, which does not resolve to the CI's sys_id in this context, causing the update to fail.

Exam trap

The trap here is that candidates assume current.variables.ci works in all server-side scripts, but ServiceNow restricts direct variable access to catalog client scripts and workflows, not business rules on the requested item table.

How to eliminate wrong answers

Option A is wrong because current.state.changesTo(3) is a valid condition that triggers when the state changes to 3 (Closed Complete); checking if the state is already 3 would not capture the transition. Option C is wrong because a reference variable stores the sys_id of the referenced record, not the display value, so the variable itself is not the issue. Option D is wrong because the business rule runs 'After' (as indicated by the 'after' keyword in the exhibit), so the state has already changed; running 'Before' would prevent the state change from being committed.

Full explanation →
60
MCQhard

Based on the exhibit, why did the transform create or update zero records?

A.The assigned_to field mapping is missing a coalesce
B.The staging table does not match the target table
C.The script on the category field has an error
D.The coalesce field is set incorrectly
AnswerC

The log shows script error, causing the row to skip.

Why this answer

The script on the category field throws an error, causing the transform to abort for that row. Since there is a script error, the entire row may fail. Option B is wrong because coalesce is true for number, meaning it should match, but error still happens.

Option C is wrong because the staging table exists (shown in XML). Option D is wrong because the direct mapping for assigned_to might work, but error on category causes whole row to fail.

Full explanation →
61
MCQhard

A catalog item uses a variable substitution in the short description like: 'Request for ${variable_name}'. The variable is a reference field to the 'Configuration Item' table. When a user submits the request, the short description displays 'Request for sys_id' instead of the display value. What could be the cause?

A.The reference qualifier on the variable is restricting allowed values
B.The display field of the Configuration Item table is not set correctly
C.The variable type is not a reference field
D.The variable substitution uses the field name instead of the variable name
AnswerB

If the display field is not the intended field (e.g., name), it may show the sys_id.

Why this answer

Option B is correct because the variable substitution in the short description uses the display value of the reference field. If the display field of the Configuration Item table is not set correctly (e.g., it is set to 'sys_id' instead of a meaningful field like 'name'), the substitution will output the sys_id instead of the intended display value. This is a common configuration issue in ServiceNow where the display field determines which column value is shown in reference fields and variable substitutions.

Exam trap

The trap here is that candidates often confuse the display field setting with reference qualifiers or variable types, thinking that restricting allowed values or changing the variable type would affect the output, when in fact the display field property is the direct cause of the sys_id being shown.

How to eliminate wrong answers

Option A is wrong because the reference qualifier restricts which records are available for selection, but it does not affect how the selected record's value is displayed in variable substitution. Option C is wrong because if the variable type were not a reference field, the variable substitution would likely fail or show an empty value, not the sys_id. Option D is wrong because variable substitution uses the variable name (e.g., '${variable_name}'), not the field name; using the field name would cause the substitution to not resolve at all.

Full explanation →
62
MCQhard

A ServiceNow administrator at a large enterprise is troubleshooting an issue with the incident form. A custom form section titled 'Sensitive Data' should only be visible to users with the 'security_admin' role. The administrator created a UI Policy with the condition g_user.hasRole('security_admin') and an action that sets the 'Sensitive Data' section's visible attribute to true. The UI Policy is active and set to run on load. However, users with the 'security_admin' role report that they do not see the section. The administrator verified that the section is configured with a 'Visible' condition that is blank, and the section's 'Roles' field is empty. What is the most likely reason the section is not showing?

A.The UI Policy condition should use 'g_user.hasRoleExactly' instead of 'g_user.hasRole'.
B.The section has a 'Visible' condition script that returns false, overriding the UI Policy.
C.A table-level ACL is blocking visibility of the section for all users.
D.The section's 'Roles' field is empty and must be set to 'security_admin'.
AnswerB

A section's own 'Visible' condition, if it returns false, will hide the section regardless of UI Policy.

Why this answer

The UI Policy is correctly configured to set the section's visible attribute to true when the condition is met. However, the section itself has a 'Visible' condition script that returns false, which overrides the UI Policy because the section's visibility condition is evaluated after the UI Policy runs. The UI Policy sets the visible attribute on the form, but the section's own condition script can independently control visibility, and if it returns false, the section remains hidden regardless of the UI Policy.

Exam trap

The trap here is that candidates often assume UI Policies always control form element visibility, but they forget that a section's own 'Visible' condition script can override UI Policy actions, leading them to incorrectly blame the UI Policy condition syntax or the Roles field.

How to eliminate wrong answers

Option A is wrong because 'g_user.hasRole' is the correct method to check for role membership; 'g_user.hasRoleExactly' is not a valid method in ServiceNow and would cause a script error. Option C is wrong because table-level ACLs control record-level access (read, write, etc.), not form section visibility; they do not affect whether a section is shown or hidden on a form. Option D is wrong because the 'Roles' field on a section controls visibility based on role membership, but it is empty, meaning no role restriction is applied; setting it to 'security_admin' would actually be an alternative way to restrict visibility, but the issue is that the section is not showing despite the UI Policy, so the empty Roles field is not the cause.

Full explanation →
63
MCQeasy

A user needs to access the 'Update Sets' module directly from the application navigator. Which filter path should they use?

A.update_set.list
B.sys_update_set.list
C.sys_update.set.list
D.update_sets
AnswerB

Correct table path for Update Sets.

Why this answer

Option D is correct because 'sys_update_set.list' is the table name for Update Sets. Options A, B, and C are incorrect because they do not match the correct table name or are not valid navigator paths.

Full explanation →
64
MCQmedium

An SLA is defined for incident resolution with a 4-hour breach timer. The SLA should not count time when the incident is in 'Awaiting Customer' status. The administrator has configured a pause condition on the SLA definition. However, when the state changes to 'Awaiting Customer', the SLA timer continues to run. The administrator wants to troubleshoot the issue. What should the administrator check first?

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

The pause condition specifies when the timer should stop; an incorrect or missing condition is the most likely cause.

Why this answer

Option C is correct because the pause condition on the SLA definition is the primary mechanism that stops the breach timer when the incident enters a specific state, such as 'Awaiting Customer'. If the timer continues to run despite the state change, the most likely cause is that the pause condition script or condition is incorrectly configured, not evaluating to true, or missing entirely. The administrator should first verify this condition before investigating other potential issues.

Exam trap

The trap here is that candidates confuse the SLA schedule's 'Pause' field (which handles calendar-based pauses) with the SLA definition's pause condition (which handles state-based pauses), leading them to incorrectly select option D.

How to eliminate wrong answers

Option A is wrong because the business rule that triggers SLA recalculation is responsible for updating the SLA after changes, but it does not directly control the pause behavior; a misconfigured pause condition would still cause the timer to run even if the recalculation rule is active. Option B is wrong because checking the SLA metric timeline shows historical data on timer states but does not identify why the pause condition failed to trigger; it is a diagnostic tool, not the first step in troubleshooting a configuration issue. Option D is wrong because the SLA schedule's 'Pause' field is used to define non-working hours or holidays that pause the timer, not to pause the timer based on a specific incident state like 'Awaiting Customer'; that state-based pause is controlled by the pause condition on the SLA definition itself.

Full explanation →
65
Multi-Selectmedium

Which TWO attributes are essential for identifying configuration items in the CMDB to ensure uniqueness? (Choose exactly 2.)

Select 2 answers
A.MAC address
B.Asset tag
C.Name
D.Serial number
E.IP address
AnswersA, D

Network interface MAC addresses are globally unique.

Why this answer

Option A (MAC address) is correct because a MAC address is a globally unique hardware identifier assigned to network interfaces by the manufacturer, making it a reliable and immutable attribute for uniquely identifying configuration items (CIs) such as servers, switches, and workstations in the CMDB. In ServiceNow, the MAC address is often used as a deduplication key to prevent duplicate CIs, especially when discovered via network probes or agents. Its uniqueness is guaranteed at the hardware level, unlike attributes that can be changed or reassigned.

Exam trap

The trap here is that candidates often confuse 'uniqueness' with 'common usage' and select IP address or name because they are frequently used in daily operations, but the exam specifically tests the understanding that MAC addresses and serial numbers are hardware-level, immutable identifiers that guarantee uniqueness across the entire CMDB.

Full explanation →
66
MCQmedium

A large enterprise uses ServiceNow for IT service management. They have a catalog item 'New Employee Setup' that is used by HR to request IT resources for new hires. The catalog item includes variables for employee name, start date, department, and manager. The workflow associated with this item creates a catalog task for the desktop team to prepare a laptop, and another catalog task for the network team to create accounts. Recently, the desktop team has been receiving tasks with incomplete information; the employee name variable is sometimes empty even though it is marked as mandatory. The administrator checked the variable definition and confirmed 'Mandatory' is set to 'true'. The variable is a 'Single Line Text' with no default value. The issue happens intermittently. What course of action should the administrator take to resolve this issue?

A.Add a workflow script activity that checks if the variable is empty and rejects the request if so.
B.Reorder the workflow activities so that the validation occurs earlier.
C.Change the variable type to 'Email' to enforce stronger validation.
D.Set the variable to 'Read only' and populate it from a reference field.
AnswerA

Server-side validation ensures data integrity even if client-side checks fail.

Why this answer

Option A is correct because the issue is that the mandatory field validation is being bypassed intermittently, likely due to the catalog item being submitted via a web service, REST API, or an integration where client-side mandatory checks are not enforced. Adding a workflow script activity that checks the variable value server-side ensures that even if the client-side validation fails, the request is rejected before proceeding, providing a reliable server-side guard.

Exam trap

The trap here is that candidates assume mandatory fields are always enforced server-side, but ServiceNow's mandatory attribute is primarily client-side, and the exam tests the understanding that server-side validation in a workflow is needed for scenarios like API submissions or intermittent bypasses.

How to eliminate wrong answers

Option B is wrong because reordering workflow activities does not address the root cause; the mandatory field validation is a client-side check that occurs before the workflow starts, so moving activities within the workflow will not enforce server-side validation. Option C is wrong because changing the variable type to 'Email' only changes the input format validation (e.g., requiring an '@' symbol), but it does not enforce that the field is non-empty; the mandatory attribute is still client-side and can be bypassed. Option D is wrong because setting the variable to 'Read only' and populating it from a reference field would prevent manual entry but does not solve the intermittent empty value issue; it also changes the data source and may not align with the requirement for free-text entry.

Full explanation →
67
MCQmedium

The flow above is not creating the task record. The variables are not being populated. What is the most likely cause?

A.The flow is not yet published.
B.The catalog item does not have the specified short_description variable.
C.The 'Create Record' action requires a 'number' field.
D.The trigger conditions are incorrectly referencing the catalog item.
AnswerB

The flow references a variable that doesn't exist, causing the action to fail.

Why this answer

Option B is correct because the flow references a variable named 'short_description' that does not exist on the catalog item. When a flow tries to read a variable that is not defined on the record, the variable resolves to null, causing the 'Create Record' action to fail silently or produce an empty field. This is a common misconfiguration where the variable name in the flow does not match the variable name defined on the catalog item.

Exam trap

The trap here is that candidates often assume the flow is not published or that the trigger conditions are wrong, when in fact the flow is running but failing due to a missing variable definition on the catalog item.

How to eliminate wrong answers

Option A is wrong because an unpublished flow will not trigger at all, but the question states the flow is running (it is not creating the task record), so the flow must be published. Option C is wrong because the 'Create Record' action does not require a 'number' field; the 'number' field is auto-generated by the system when the record is saved. Option D is wrong because if the trigger conditions were incorrectly referencing the catalog item, the flow would not trigger at all, but the flow is triggering (it is just not populating the variables).

Full explanation →
68
MCQhard

An SLA is defined with a condition that triggers only when a field 'priority' is 1 or 2. However, some tickets with priority 1 are not getting SLA attached. What should the administrator check first?

A.Check the SLA definition condition.
AnswerA

The condition on the SLA definition determines when the SLA starts; if it's not evaluating to true for tickets with priority 1, the SLA won't attach.

Why this answer

The SLA definition condition is the first place to troubleshoot why an SLA is not attaching. Option B is about business hours, not condition. Option C is general.

Option D is not a standard check.

Full explanation →
69
MCQmedium

Refer to the exhibit. This ACL is applied to the Incident table for 'write' operation. A user is editing their own incident but is still denied. What is the issue?

A.The script returns false because current.caller_id is not the user's sys_id.
B.The ACL is set to 'read' instead of 'write'.
C.The user does not have the necessary role.
D.The script returns true but another ACL denies.
AnswerD

A more specific ACL can override this one.

Why this answer

Option D is correct because when an ACL is applied to a table for 'write' operations, multiple ACLs can evaluate the same operation. Even if one ACL (the one shown) returns true, another ACL on the same table for the same operation may return false, causing the overall write to be denied. The exhibit shows a script that checks `current.caller_id == gs.getUserID()`, which should allow the user to edit their own incident, but another ACL with a higher order or a different condition is blocking the write.

Exam trap

The trap here is that candidates assume a single ACL's result determines access, but ServiceNow evaluates all matching ACLs in order, and a 'false' from any ACL (unless overridden) will deny the operation, even if another ACL returns 'true'.

How to eliminate wrong answers

Option A is wrong because the script explicitly compares `current.caller_id` to `gs.getUserID()`, which returns the current user's sys_id; if the user is editing their own incident, this condition returns true, not false. Option B is wrong because the ACL is explicitly applied to the Incident table for 'write' operation, as stated in the question, and the exhibit shows the ACL type is 'record' with operation 'write', so it is not set to 'read'. Option C is wrong because the ACL does not require a role; it uses a script condition, and the question does not indicate that a role is missing or that the user lacks any required role.

Full explanation →
70
MCQmedium

A user has personalized their form by rearranging fields. The administrator wants to reset the form layout to the default for that user. What should the administrator do?

A.Delete the user's personalization from sys_user_preference
B.Set the form's 'Reset' attribute to true
C.Run a scheduled job to clear all user preferences
D.Use the 'Restore Default' button on the form
AnswerA

This directly removes the personalization, reverting to the default layout.

Why this answer

Option B is correct: form personalizations are stored in the sys_user_preference table; deleting the specific record resets the layout for that user. Option A (return false button) works only for the user themselves. Option C is not an attribute.

Option D is too broad.

Full explanation →
71
MCQeasy

A ServiceNow administrator is designing a catalog workflow that requires approval from the user's manager only if the total cost of the request exceeds $500. Which workflow configuration should be used?

A.Add an Approval - Group activity and set the 'Approval Group' to 'Manager's Group'.
B.Set the variable 'total_cost' as 'Required If' a condition.
C.Add an Approval - User activity with a Condition that checks if the variable 'total_cost' is greater than 500.
D.Use an Approval Group activity and add the manager as a member.
AnswerC

This allows the approval to be conditional based on cost.

Why this answer

Option C is correct because the Approval - User activity allows you to specify a single user (the manager) and attach a condition that evaluates the 'total_cost' variable. When the condition is true (total_cost > 500), the approval activity runs; otherwise, it is skipped. This directly implements the requirement for manager approval only when the cost exceeds $500.

Exam trap

The trap here is that candidates often confuse 'Required If' variable conditions with workflow approval conditions, or assume that an Approval Group activity can be used for a single user by adding them as a member, but neither approach provides the conditional logic needed to trigger approval only when cost exceeds $500.

How to eliminate wrong answers

Option A is wrong because an Approval - Group activity sends the request to an entire group (e.g., 'Manager's Group'), not to the specific manager of the user, and it lacks a condition to trigger only when cost exceeds $500. Option B is wrong because setting a variable as 'Required If' only controls whether the variable must be filled in, not whether an approval step runs; it does not add any approval logic. Option D is wrong because an Approval Group activity (like Option A) requires a group, not a single user, and adding the manager as a member does not create a conditional approval based on cost.

Full explanation →
72
MCQhard

Refer to the exhibit. An import set has a row with short_description='Test', category='network', and number='INC001'. The target table has an existing record with number='INC001' and description='Old Desc'. What will happen when the transform runs?

A.The transform fails due to coalesce conflict.
B.A new record is created.
C.No action because coalesce field is invalid.
D.The existing record is updated with description='Test'.
AnswerD

Coalesce matches on number, so the existing record is updated.

Why this answer

The transform uses the coalesce field 'number' to match the incoming record (number='INC001') with the existing target record (number='INC001'). Since a match is found, the transform performs an update operation. The short_description field from the import set row ('Test') is mapped to the description field on the target table, so the existing record's description is updated to 'Test'.

Exam trap

ServiceNow often tests the misconception that a coalesce match always causes a conflict or error, when in fact it triggers an update if the match is unique and the coalesce field is correctly configured.

How to eliminate wrong answers

Option A is wrong because there is no coalesce conflict; the coalesce field 'number' matches exactly one existing record, so the transform proceeds with an update. Option B is wrong because a new record is created only when no matching record is found via the coalesce field; here a match exists. Option C is wrong because the coalesce field 'number' is valid and correctly configured to identify duplicates; it is not invalid.

Full explanation →
73
Multi-Selecthard

An administrator is configuring a Virtual Agent topic to handle common IT questions. Which three components are required to build a basic topic? (Choose three.)

Select 3 answers
A.A trigger phrase that users type to invoke the topic.
B.A catalog item that the topic will order.
C.An output message that sends the response to the user.
D.A knowledge base article to provide the answer.
E.A topic script that defines the conversation flow.
AnswersA, C, E

Correct: Trigger phrases are necessary for the Virtual Agent to recognize the user's intent.

Why this answer

A trigger phrase is required because it defines the user input that initiates the Virtual Agent topic. Without a trigger phrase, the system has no way to match user utterances to the correct topic, making it impossible to start the conversation flow.

Exam trap

The trap here is that candidates often mistake optional enhancements (like catalog items or knowledge base articles) for mandatory components, but ServiceNow explicitly requires only a trigger phrase, an output message, and a topic script to define a functional basic topic.

Full explanation →
74
MCQhard

An administrator notices that a scheduled flow designed to send approval reminders is not triggering. The flow is set to run on the sysapproval_approver table with a condition of 'state = requested'. What is the most likely cause?

A.The flow is deactivated
B.The flow's trigger type is 'Data Trigger' and not scheduled
C.The flow is scoped incorrectly
D.The condition is incorrect
AnswerB

A scheduled flow must use a 'Schedule' trigger; data triggers fire on record changes, not on a schedule.

Why this answer

Option B is correct because a scheduled flow that is not triggering on the sysapproval_approver table despite a valid condition most likely has its trigger type set to 'Data Trigger' instead of 'Scheduled'. A scheduled flow requires the trigger type to be explicitly set to 'Scheduled' to run at defined intervals; if it is set to 'Data Trigger', it will only execute on record creation or update, not on a time-based schedule.

Exam trap

ServiceNow often tests the distinction between trigger types in Flow Designer, where candidates assume a scheduled flow automatically runs on a schedule without verifying that the trigger type is explicitly set to 'Scheduled' rather than 'Data Trigger'.

How to eliminate wrong answers

Option A is wrong because if the flow were deactivated, it would not run at all, but the question states the flow is 'scheduled' and not triggering, implying it is active but not executing as expected. Option C is wrong because scoping issues typically cause flows to fail on execution or not be visible, but they do not prevent a scheduled flow from triggering based on its schedule; the trigger type is the primary factor. Option D is wrong because the condition 'state = requested' is correct for filtering approval records that need reminders; an incorrect condition would cause the flow to run but not process records, not fail to trigger entirely.

Full explanation →
75
MCQeasy

A user is able to view records in the Incident table but cannot edit them. Which ACL type is preventing the edit?

A.write
B.read
C.create
D.delete
AnswerA

Write ACL controls the ability to update records.

Why this answer

The correct answer is A (write). In ServiceNow, the write ACL controls the ability to update or edit existing records. Since the user can view records (read ACL allows this) but cannot edit them, the write ACL is the one blocking the operation.

The write ACL is evaluated when a user attempts to modify a record after it has been created.

Exam trap

The trap here is that candidates often confuse the write ACL with the read ACL, thinking that if they can see the record, they should be able to edit it, but ServiceNow separates these permissions distinctly.

How to eliminate wrong answers

Option B (read) is wrong because the read ACL controls the ability to view records, and the user can already view them, so the read ACL is not preventing the edit. Option C (create) is wrong because the create ACL controls the ability to insert new records, not edit existing ones. Option D (delete) is wrong because the delete ACL controls the ability to remove records, not modify them.

Full explanation →

Page 1 of 7

Page 2

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 →