Courseiva

ServiceNow Certified System Administrator CSA (SNOW-CSA) — Questions 451–510

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

Take a mock examExam hub
Page 6

Page 7 of 7

451
MCQmedium

Refer to the exhibit. An administrator runs this script in a background script. What is the effect?

A.It approves all approvals in the system.
B.It will cause an infinite loop.
C.It will fail because 'approval_for' is not a valid field.
D.It approves all pending approvals for the current user.
AnswerD

The script targets only records where approval_for matches the current user and state is requested.

Why this answer

The script uses `GlideRecord` to query the `sysapproval_approver` table for records where `approver` equals the current user's sys_id and `state` is 'pending'. It then sets each record's `state` to 'approved' and updates it. This approves only the pending approvals assigned to the current user, not all approvals in the system.

Exam trap

ServiceNow often tests the distinction between 'all approvals' and 'approvals for the current user' to see if candidates notice the filter condition in the GlideRecord query.

How to eliminate wrong answers

Option A is wrong because the script filters by the current user's sys_id and pending state, so it does not approve all approvals in the system—only those for the current user. Option B is wrong because the script iterates over a GlideRecord result set and updates each record once; there is no recursive call or loop that would cause an infinite loop. Option C is wrong because 'approval_for' is not referenced in the script; the script uses 'approver' and 'state', which are valid fields on the sysapproval_approver table.

Full explanation →
452
MCQeasy

An administrator wants to create a new view called 'Mobile View' for the incident form to optimize it for mobile devices. Where should this view be created?

A.On the 'sys_ui_section' table
B.On the 'incident' table record under 'Views'
C.In the 'sys_ui_view' table directly
D.In the 'Application Navigator' module
AnswerB

Views are created from the table record's related list 'Views'.

Why this answer

Option B is correct because views for specific tables, such as the 'incident' table, are created directly on the table record under the 'Views' related list. This allows the administrator to define a custom layout optimized for mobile devices, which is then stored as a 'sys_ui_view' record associated with the table. The platform uses this view when the 'Mobile View' is selected or when the form is accessed from a mobile device.

Exam trap

The trap here is that candidates often think views are created directly in the 'sys_ui_view' table (Option C) because that is where the records are stored, but the correct procedure is to create them from the table record's 'Views' related list to ensure proper table association and platform configuration.

How to eliminate wrong answers

Option A is wrong because the 'sys_ui_section' table stores individual sections of a form, not the entire view; creating a view there would only define a section, not a complete mobile-optimized layout. Option C is wrong because while views are ultimately stored in the 'sys_ui_view' table, directly creating a record there bypasses the necessary table-level association and view configuration that the platform requires for proper behavior. Option D is wrong because the 'Application Navigator' module is used to configure the left-hand navigation menu and modules, not to create form views.

Full explanation →
453
Multi-Selectmedium

Which TWO of the following are valid ways to customize the appearance and functionality of a service portal page for self-service users?

Select 2 answers
A.Edit the HTML of the page directly
B.Add and configure widgets on the page
C.Edit the portal's CSS file directly
D.Modify the portal's style sheet in the system properties
E.Apply a theme from the theme library
AnswersB, E

Widgets provide modular functionality and can be added to pages.

Why this answer

The correct options are B and D. Widgets can be added to portal pages, and themes customize the look and feel. Option A is wrong because CSS variables can be used but editing the entire CSS file directly is not the recommended method.

Option C is wrong because themes are the correct way. Option E is wrong because the style sheet can be edited but it's not the primary customization method.

Full explanation →
454
MCQeasy

A new ServiceNow administrator is tasked with setting up a dashboard for the IT help desk. The team wants to see a list of their assigned open incidents and a pie chart showing incident priority. The administrator creates two separate reports: a list report for open incidents and a pie chart for priority. Then, the administrator creates a new dashboard and adds both reports to it. However, the dashboard displays the reports in a single column, stacked vertically. The team wants the reports to appear side by side for a better overview. The administrator is unsure how to achieve this layout without rebuilding everything. What should the administrator do?

A.Use a UI Macro to arrange report positions within the dashboard.
B.Modify the report output format to display inline.
C.Create a new dashboard using a two-column template and add the reports again.
D.Edit the dashboard's layout property and change the column count to 2.
AnswerD

This directly changes the layout to display reports side by side without recreating the dashboard.

Why this answer

Dashboards have a layout configuration that allows changing the number of columns. Editing the dashboard's properties to set a two-column layout is the simplest and most efficient way to achieve a side-by-side arrangement. Creating a new dashboard would require re-adding reports, and UI Macros or report format changes do not affect dashboard layout.

Full explanation →
455
MCQmedium

A manager wants to see a real-time gauge on their homepage showing the number of open incidents assigned to their team. Which widget should they add to their dashboard?

A.Mashup widget
B.Report gauge widget
C.HTML widget
D.Filter widget
AnswerB

Report gauge widget displays a report as a gauge, perfect for showing counts.

Why this answer

Option C is correct because a 'Report gauge' widget displays a visual representation of a report’s data, such as a count of open incidents. Option A is wrong because 'HTML' widget is for custom HTML, not for reports. Option B is wrong because 'Filter' widget is for filtering data, not displaying gauges.

Option D is wrong because 'Mashup' widget is for external content, not ServiceNow reports.

Full explanation →
456
MCQhard

An incident has state set to 'In Progress' (value 2). When the user loads the form or updates the state, what is the resulting form behavior?

A.The 'assigned_to' field is mandatory and the 'assignment_group' field is hidden
B.The 'assigned_to' field is mandatory but the 'assignment_group' field remains visible
C.The 'assigned_to' field is not mandatory because the Client Script overrides the UI Policy
D.The 'assigned_to' field is mandatory and the 'assignment_group' field is hidden, but the Client Script causes an error
AnswerA

UI Policy sets both actions; Client Script reinforces mandatory.

Why this answer

Option A is correct. The UI Policy runs on load and update: it sets assigned_to mandatory (true) and assignment_group hidden. The Client Script also runs on change: it sets assigned_to mandatory (true).

So both effects occur. Option B is wrong because the UI Policy also makes assignment_group invisible. Option C is wrong because the Client Script does not set assigned_to mandatory to false; it sets it to true.

Option D is wrong because the UI Policy does not conflict; both set mandatory to true.

Full explanation →
457
MCQhard

An administrator is troubleshooting an issue where a form section on the incident form is not visible to users with the 'itil' role, but is visible to admins. The section has no UI Policy or ACL restricting it. What is the most likely cause?

A.The section has a role requirement that the users lack
B.An ACL is blocking the fields in the section
C.The fields in the section are marked as mandatory
D.The section has 'Visible' set to false in the form layout
AnswerA

Sections can be role-restricted; if users lack the role, the section is hidden.

Why this answer

Option C is correct because form sections can be assigned roles via the 'Roles' field on the section definition. If the section is restricted to a role that users lack, it won't display. Option A is wrong because the 'Visible' attribute on the form is a general flag, not role-specific.

Option B is wrong because if there is no ACL, ACLs are not the cause. Option D is wrong because the 'Mandatory' attribute makes a field mandatory, not invisible.

Full explanation →
458
MCQeasy

What is the purpose of the 'cmdb_rel_ci' table?

A.It stores the actual relationships between CIs.
B.It stores the CI classification rules.
C.It stores the CI hierarchy tree.
D.It stores the list of all relationship types.
AnswerA

Each record in cmdb_rel_ci represents a relationship between two CIs.

Why this answer

The 'cmdb_rel_ci' table in ServiceNow stores the actual relationships between Configuration Items (CIs). Each row in this table represents a specific instance of a relationship, linking a parent CI to a child CI via a defined relationship type, enabling the CMDB to model dependencies and connectivity in the infrastructure.

Exam trap

The trap here is that candidates confuse the 'cmdb_rel_ci' table (which stores actual relationship instances) with the 'cmdb_rel_type' table (which stores relationship definitions), leading them to select option D.

How to eliminate wrong answers

Option B is wrong because CI classification rules are stored in the 'cmdb_class' table, not 'cmdb_rel_ci'. Option C is wrong because the CI hierarchy tree is derived from the 'cmdb_rel_ci' table but is not stored as a separate tree structure; the hierarchy is built dynamically from the relationship records. Option D is wrong because the list of all relationship types is stored in the 'cmdb_rel_type' table, not 'cmdb_rel_ci'.

Full explanation →
459
MCQeasy

A business rule is configured to run 'before' a record is updated. If the business rule sets a field value and then a subsequent 'after' business rule also updates the same field, what will be the final value stored in the database?

A.Both values are stored in a history field
B.The database rejects the second change
C.The value set by the 'after' business rule
D.The value set by the 'before' business rule
AnswerC

The 'after' rule runs after the initial save and can modify the record again.

Why this answer

In ServiceNow, business rules execute in a defined order: 'before' business rules run first, followed by 'after' business rules. When both a 'before' and an 'after' business rule update the same field, the 'after' business rule executes later in the transaction and its value overwrites the 'before' business rule's value. The final value stored in the database is therefore the one set by the 'after' business rule, because the database write occurs after all business rules have completed.

Exam trap

The trap here is that candidates often assume 'before' rules have final authority because they run earlier, but ServiceNow's execution order ensures 'after' rules override 'before' rules for the same field.

How to eliminate wrong answers

Option A is wrong because ServiceNow does not automatically store both values in a history field; field history is only recorded if the 'Audit' feature is enabled on the field, and even then it tracks changes over time, not both values from a single update. Option B is wrong because the database does not reject the second change; ServiceNoW's database engine (MySQL/MariaDB) processes the final value after all business rules run, and no conflict detection is triggered for sequential updates within the same transaction. Option D is wrong because the 'before' business rule runs first, but its value is overwritten by the later-executing 'after' business rule, so the 'before' value is not the final stored value.

Full explanation →
460
Multi-Selecteasy

An administrator is setting up an import set to load data from a CSV file into the Incident table. Which TWO of the following are required steps in the import process?

Select 2 answers
A.Create an import set table to store the imported data.
B.Schedule the import to run automatically.
C.Use the Import Set Row API to create a transform map.
D.Create a data lookup table to standardize values.
E.Create a transform map to define field mappings.
AnswersA, E

An import set table is automatically created when you define an import set.

Why this answer

Option A is correct because an import set table must be created to temporarily store the raw data from the CSV file before any transformation occurs. This table acts as a staging area, allowing the system to hold the imported records and then apply a transform map to map and move the data into the target Incident table. Without an import set table, there is no structure to receive the incoming CSV data.

Exam trap

ServiceNow often tests the distinction between required steps and optional enhancements, so candidates mistakenly select optional steps like scheduling or data lookups as mandatory, when only the import set table and transform map are essential.

Full explanation →
461
MCQeasy

A ServiceNow administrator wants to archive old CMDB history records that are older than 12 months to improve performance. Which approach should be used?

A.Increase the 'CMDB History Pruning Frequency' property
B.Manually delete rows from the 'cmdb_ci_history' table using SQL
C.Use the 'Archive Old Records' functionality in CMDB Workspace
D.Run a scheduled report to export and then delete records
AnswerC

This is the designed feature to safely archive old history records.

Why this answer

Option C is correct because the CMDB Workspace provides a built-in 'Archive Old Records' functionality specifically designed to move old CMDB history records (e.g., from the `cmdb_ci_history` table) to an archive table, improving performance without data loss. This approach is supported by ServiceNow's recommended best practices for managing CMDB history data, as it preserves records for compliance while reducing the active table size.

Exam trap

The trap here is that candidates often confuse 'pruning' (which deletes records) with 'archiving' (which moves records to a separate table), leading them to choose Option A, or they incorrectly assume that manual SQL operations are acceptable in ServiceNow, which is a common anti-pattern tested on the CSA exam.

How to eliminate wrong answers

Option A is wrong because increasing the 'CMDB History Pruning Frequency' property only controls how often the system checks for records to prune (delete), not the archival of old records; it does not archive data and may lead to permanent deletion if combined with pruning rules. Option B is wrong because manually deleting rows from the `cmdb_ci_history` table using SQL violates ServiceNow's supported practices, bypasses the platform's audit and security controls, and can cause data integrity issues or break application logic. Option D is wrong because running a scheduled report to export and then delete records is a manual, error-prone process that does not leverage ServiceNow's native archival capabilities, risks incomplete or inconsistent data removal, and lacks the automated tracking and rollback features of the Archive Old Records functionality.

Full explanation →
462
MCQhard

During a CMDB audit, an administrator discovers that some CIs have a 'sys_class_name' of 'cmdb_ci' instead of a specific subclass like 'cmdb_ci_server'. What is the most likely cause?

A.The administrator manually changed the class field to 'cmdb_ci'.
B.The CI was created by Discovery and the sensor failed to classify it.
C.The identification rule is incorrectly configured to map to the base table.
D.The CI has been retired and the class was reset.
AnswerC

If identification rules or scripts directly create records in cmdb_ci without subclass, the CI will have sys_class_name 'cmdb_ci'.

Why this answer

The most likely cause is an incorrectly configured identification rule that maps the CI to the base table 'cmdb_ci' instead of a specific subclass. Identification rules determine how CIs are matched and created; if the rule's 'Table' field is set to 'cmdb_ci' rather than a subclass like 'cmdb_ci_server', all new CIs matching that rule will be created at the base class level, losing subclass-specific attributes and relationships.

Exam trap

The trap here is that candidates often assume Discovery sensors are solely responsible for classification, but the identification rule's table setting is the primary driver for the CI's class assignment, and a misconfigured rule can override sensor classification.

How to eliminate wrong answers

Option A is wrong because manually changing the class field to 'cmdb_ci' would require explicit user action and is not a typical cause for multiple CIs having the base class; the administrator is discovering the issue, not causing it. Option B is wrong because Discovery sensors classify CIs based on identification and classification rules; if a sensor fails to classify, the CI would typically remain unclassified or get a default class, not specifically 'cmdb_ci' — the base class assignment is driven by the identification rule's table mapping. Option D is wrong because retiring a CI does not reset its class; retirement only changes the 'Install Status' field to 'Retired' and does not alter the 'sys_class_name'.

Full explanation →
463
Multi-Selecthard

A user reports that a field is not visible on the form. Which three factors could cause a field to be hidden? (Choose three.)

Select 3 answers
A.The field's visibility condition in a UI Policy
B.The field is not in the current form view
C.The user does not have the required role to view the field
D.The field's 'Active' checkbox is unchecked
E.The field is configured as read-only
AnswersA, B, C

UI Policies can set the visible attribute to false based on conditions.

Why this answer

Options A, C, and D are correct: UI Policy can set visible false; field not in form view; role restriction in dictionary. Option B (active checkbox) does not hide on form; it hides from table. Option E (read-only) does not hide, just makes non-editable.

Full explanation →
464
MCQhard

A catalog client script is used to populate a variable's value from an external table. The script works in the development instance but fails in production. Which troubleshooting step should be taken first?

A.Ensure the external table exists in the production instance
B.Review the system logs for script errors
C.Verify that the script's 'Run as' and 'Global' flags are set correctly in production
D.Check if the workflow attached to the catalog item is active
AnswerC

Client scripts may depend on user context; production might have different security or scope settings.

Why this answer

Option A is correct because catalog client scripts can be context-sensitive; checking the script's 'Run as' or 'Global' setting reveals scope differences. Option B (workflow) is irrelevant. Option C (log) is possible but not first step.

Option D (table) does not address client script execution context.

Full explanation →
465
MCQeasy

A company wants to allow employees to request software through the service catalog. Each software item requires the employee to select a license type (Standard, Professional, or Enterprise). Which variable type should be used for the license type selection?

A.Multi-select checkbox
B.Text field
C.Checkbox
D.Single-select dropdown
AnswerD

A single-select dropdown is the correct variable type for selecting one license type from a list.

Why this answer

A single-select dropdown is the correct choice because the license type (Standard, Professional, Enterprise) represents a set of mutually exclusive options where the employee must choose exactly one. This variable type enforces data integrity by preventing multiple selections, which would be invalid for a license type field.

Exam trap

ServiceNow often tests the distinction between single-select and multi-select controls, and the trap here is that candidates may choose 'Multi-select checkbox' because they think employees might need multiple license types, but the question explicitly states each software item requires selecting a license type, implying exactly one.

How to eliminate wrong answers

Option A is wrong because a multi-select checkbox allows the user to select multiple values simultaneously, which is inappropriate for a mutually exclusive license type selection. Option B is wrong because a text field would require manual entry, introducing the risk of typos, inconsistent formatting, and invalid values that would break downstream automation or reporting. Option C is wrong because a checkbox is a binary (true/false) control and cannot represent three distinct license types.

Full explanation →
466
Multi-Selecteasy

An administrator notices that a UI Policy does not seem to run on the incident form. Which two of the following are likely reasons for this issue? (Choose two.)

Select 2 answers
A.The UI Policy is defined on a different table.
B.The UI Policy is ordered after all other UI Policies.
C.The UI Policy is inactive.
D.The UI Policy condition is set to 'true' without any additional condition.
E.The UI Policy has a syntax error in its condition script.
AnswersA, C

UI Policies only run on the form for the table they are associated with.

Why this answer

A UI Policy must be active to execute, and it only runs on forms for the table it is defined on. Inactive policies are ignored, and policies on a different table will never trigger. Script errors may cause runtime failures but the policy still attempts to run; ordering or condition being always true do not prevent execution.

Full explanation →
467
MCQmedium

A user reports that a catalog item's 'Requested for' field is not being set correctly after submission. The catalog item uses a workflow that includes a 'Set Requested For' activity. What is the most likely cause?

A.The workflow context variable for requested for is missing
B.The workflow is not published
C.The 'Set Requested For' activity is configured with a static user value
D.The catalog item variable mapping is incorrectly configured
AnswerC

This activity can explicitly set the requested for user; if static, it replaces the submitted value.

Why this answer

The 'Set Requested For' activity in a ServiceNow workflow explicitly overrides the 'Requested for' field on the catalog item. If it is configured with a static user value, it will always set that user regardless of who submitted the request, causing the reported issue. This is the most direct cause because the activity's configuration takes precedence over the default behavior of populating the field with the requester.

Exam trap

The trap here is that candidates often assume the issue is with variable mapping or workflow publishing, when in fact the 'Set Requested For' activity's static configuration directly overrides the expected dynamic behavior.

How to eliminate wrong answers

Option A is wrong because the workflow context variable for 'requested for' is not a standard variable; the 'Set Requested For' activity uses its own configuration, not a context variable. Option B is wrong because an unpublished workflow would prevent the catalog item from functioning entirely, not just cause a specific field to be set incorrectly. Option D is wrong because catalog item variable mappings control how variables are passed to the workflow, not the 'Requested for' field, which is a system field handled separately by the 'Set Requested For' activity.

Full explanation →
468
MCQeasy

A junior administrator wants to see which CIs have been updated in the last 24 hours. Which table contains the change log for CMDB CIs?

A.sys_journal_field
B.sys_audit
C.cmdb_ci
D.cmdb_ci_history
AnswerD

This table tracks all CMDB CI updates.

Why this answer

The `cmdb_ci_history` table is specifically designed to track changes to CMDB CIs, including updates made in the last 24 hours. It stores historical snapshots of CI attribute changes, making it the correct table for a junior administrator to query for recent CI updates.

Exam trap

The trap here is that candidates often confuse the `sys_audit` table (which logs changes to any record) with the dedicated `cmdb_ci_history` table, not realizing that CMDB has its own specialized history table for CIs.

How to eliminate wrong answers

Option A is wrong because `sys_journal_field` stores journal entries (like work notes or comments) attached to records, not the change log for CMDB CIs. Option B is wrong because `sys_audit` tracks changes to any table's records via audit rules, but it is a generic auditing table, not the dedicated CMDB CI history table. Option C is wrong because `cmdb_ci` is the main table that stores the current state of CIs, not the historical change log.

Full explanation →
469
MCQhard

An administrator needs to ensure that when a user changes the 'State' field to 'Resolved' on an incident form, the 'Resolution Notes' field becomes mandatory. What should be configured?

A.Business rule
B.Client script with onChange event
C.UI policy
D.Data policy
AnswerC

UI policies can make fields mandatory based on conditions without scripting.

Why this answer

A UI policy is the correct choice because it allows you to make a field mandatory based on a condition on the same form without requiring a server round-trip. When the 'State' field changes to 'Resolved', the UI policy can set the 'Resolution Notes' field to mandatory, and it runs client-side in real-time as the user interacts with the form.

Exam trap

The trap here is that candidates often confuse UI policies with client scripts or business rules, but UI policies are the only out-of-box mechanism that can make a field mandatory based on a condition without requiring a server round-trip or custom scripting.

How to eliminate wrong answers

Option A is wrong because a business rule runs server-side and cannot dynamically change field properties like mandatory on the client form in real-time without a page refresh. Option B is wrong because a client script with onChange event can detect the field change but cannot directly make another field mandatory; it would require additional scripting to manipulate the UI, which is not the standard or recommended approach. Option D is wrong because a data policy enforces mandatory fields at the database level during record submission, not interactively on the form as the user changes fields.

Full explanation →
470
MCQhard

A catalog item is configured but does not appear in the Service Portal for end users. The item is categorized under 'Software' and the catalog is 'IT Services'. The Service Portal widget 'sc_category_item' is used. Which of the following is the most likely reason?

A.The catalog item's 'Order' field is set to 0.
B.The catalog item's 'Portal' field is empty or set to the wrong portal.
C.The catalog item has a 'Roles' restriction that does not include the user's role.
D.The catalog item's 'Module' is not set to 'Service Catalog'.
AnswerB

The Portal field must be set to the correct portal for the item to appear there.

Why this answer

The most likely reason is that the catalog item's 'Portal' field is empty or set to the wrong portal. In ServiceNow, the 'Portal' field on a catalog item determines which Service Portal(s) the item appears in. If this field does not include the target portal (e.g., 'IT Services'), the item will not be visible in that portal's catalog, even if the 'sc_category_item' widget is used.

This is a common configuration oversight.

Exam trap

The trap here is that candidates often confuse the 'Portal' field with the 'Category' or 'Roles' fields, assuming that if the item is in the correct category and no roles are set, it should appear everywhere, but the Portal field explicitly scopes visibility to specific portals.

How to eliminate wrong answers

Option A is wrong because setting the 'Order' field to 0 does not hide the item; it simply places it at the top of the list (lowest order value) or may cause it to appear first, not disappear. Option C is wrong because a 'Roles' restriction would prevent the item from being visible to users without that role, but the question states the item is not visible to end users at all, not that it is visible to some but not others; the 'Portal' field is a more direct cause for complete invisibility. Option D is wrong because the 'Module' field is not a standard field on a catalog item; it is used on record producers or other configurations, and the Service Catalog module is automatically associated with catalog items via the 'sc_cat_item' table, so this is not a relevant setting.

Full explanation →
471
MCQmedium

A high-priority incident is created on Monday at 16:30 (within schedule). The incident is assigned to an agent at 17:00. The state changes to 'In Progress' at 17:30. What is the SLA breach time?

A.17:00
B.16:30
C.17:30
D.18:00
AnswerC

Breach time is creation time + 1 hour, 16:30 + 1 = 17:30.

Why this answer

The SLA breach time is calculated from when the incident is created (16:30) plus the defined resolution time, but the clock stops when the state changes to 'In Progress' (17:30) because the SLA is paused during the 'In Progress' state. Since the incident was created at 16:30 and moved to 'In Progress' at 17:30, the elapsed time is 1 hour. If the SLA resolution time is, for example, 4 hours, the breach time would be 16:30 + 4 hours = 20:30, but the question implies the breach time is the moment the SLA is breached, which is when the state changes to 'In Progress' if the SLA timer has already exceeded the allowed time.

However, in ServiceNow, the breach time is the date/time when the SLA is expected to breach based on the schedule and pauses; here, the breach time is 17:30 because the SLA timer stops at that point and the incident has already consumed 1 hour of the resolution time, making the breach time equal to the 'In Progress' timestamp if the resolution time is 1 hour or less.

Exam trap

The trap here is that candidates mistakenly think the SLA breach time is the creation time or assignment time, rather than understanding that the breach time is dynamically calculated based on the start time, resolution duration, and any pauses in the SLA timer.

How to eliminate wrong answers

Option A is wrong because 17:00 is the assignment time, not the SLA breach time; the SLA breach time is based on the creation time plus the resolution time, not the assignment time. Option B is wrong because 16:30 is the creation time, which is the start of the SLA timer, not the breach time; the breach time is calculated by adding the resolution duration to the creation time. Option D is wrong because 18:00 is an arbitrary time not derived from the given data; the breach time is specifically 17:30 when the state changes to 'In Progress' and the SLA timer pauses, assuming the resolution time is exactly 1 hour.

Full explanation →
472
Multi-Selectmedium

Which TWO of the following are best practices when working with ACLs?

Select 2 answers
A.Always create a single, broad ACL that covers all needs
B.Ensure ACLs are scoped to the application that needs them
C.Use the condition builder instead of scripts for simple conditions
D.Grant 'read' access to all users on all tables to simplify administration
E.Write complex scripts in ACLs to handle all edge cases
AnswersB, C

Scoping prevents ACLs from affecting other applications.

Why this answer

Option B is correct because ACLs should be scoped to the specific application that requires them. This ensures that only the necessary records and fields are accessible, following the principle of least privilege. Overly broad ACLs can expose sensitive data and violate data security requirements.

Exam trap

The trap here is that candidates often think a single broad ACL simplifies administration, but ServiceNow's ACL evaluation engine processes ACLs in order, and a broad ACL can inadvertently grant access to records that should be restricted.

Full explanation →
473
MCQeasy

A company wants to allow users to reset their own passwords via the Service Portal. Which feature should be configured?

A.User Criteria
B.Password Reset Plugin
C.Self-Service Password Reset
D.ACLs
AnswerC

This feature allows users to reset their own passwords from the Service Portal.

Why this answer

The Self-Service Password Reset (SSPR) feature allows end users to reset their own passwords through the Service Portal without requiring administrator intervention. It integrates with the Service Portal's native UI and leverages email or SMS verification to authenticate the user before allowing a password change. This directly meets the requirement for user-initiated password resets via the Service Portal.

Exam trap

The trap here is that candidates confuse the 'Password Reset Plugin' (which handles password reset via email links) with the 'Self-Service Password Reset' feature (which is specifically designed for the Service Portal), leading them to select Option B instead of C.

How to eliminate wrong answers

Option A is wrong because User Criteria is used to control which users can see or access specific catalog items, knowledge articles, or records, not to enable password reset functionality. Option B is wrong because the Password Reset Plugin is a legacy feature that enables password reset via email links or the instance login page, but it does not integrate with the Service Portal's native self-service interface. Option D is wrong because ACLs (Access Control Lists) control read/write permissions on records and fields, not the ability to reset passwords through a self-service portal workflow.

Full explanation →
474
MCQmedium

A company recently upgraded their ServiceNow instance from Paris to Quebec. After the upgrade, several users report that the 'Assignment Group' field on the Incident form is missing for users with the 'itil' role. The field is still visible for administrators. The administrator checks the dictionary entry for the 'assignment_group' field and finds that it has no roles set. The form layout for the 'Default view' includes the field. The UI Policy that previously controlled visibility of this field has been deactivated. An audit of the upgrade logs shows no errors related to this field. The administrator suspects that a new feature introduced in Quebec might have affected the field visibility. Which action should the administrator take to restore the field visibility for 'itil' users?

A.Check the 'Visibility' field on the dictionary entry for 'assignment_group' and set it to 'All' if it is set to 'Admin'.
B.Create a UI Policy that sets the 'assignment_group' field visible when the form loads.
C.Add the 'itil' role to the 'Roles' field on the dictionary entry for 'assignment_group'.
D.Create a new Access Control Rule (ACL) to grant read access to the 'itil' role for the 'assignment_group' field.
AnswerA

The 'Visibility' field on the dictionary can hide fields from non-admin users.

Why this answer

In Quebec, a new 'Visibility' field was added to dictionary entries. When set to 'Admin', the field is hidden from non-admin users regardless of form layout or UI Policies. Since the dictionary entry for 'assignment_group' has no roles set but the field is missing for 'itil' users, the administrator should check and set the 'Visibility' field to 'All' to restore visibility.

Exam trap

The trap here is that candidates may focus on UI Policies or ACLs, overlooking the new Quebec-specific 'Visibility' dictionary field that directly controls field visibility at the metadata level.

How to eliminate wrong answers

Option B is wrong because creating a new UI Policy would be redundant and ineffective if the dictionary-level 'Visibility' field is set to 'Admin', as dictionary settings override UI Policies. Option C is wrong because adding the 'itil' role to the 'Roles' field on the dictionary entry would restrict the field to only users with that role, but the field is already missing for 'itil' users, and the current 'Roles' field is empty, so this would not solve the issue. Option D is wrong because ACLs control data access and security, not form field visibility; the field is already visible to admins, indicating no ACL issue, and the problem is a UI-level visibility setting.

Full explanation →
475
MCQeasy

An import set row fails with the error 'Coalesce field not found on target table'. What is the most common cause?

A.The coalesce field is not mapped in the transform map.
B.The import set row is missing data in the coalesce field.
C.The staging table is incorrectly configured.
D.The target table does not have the specified coalesce field.
AnswerA

The coalesce field must be mapped in the transform map to a field on the target table.

Why this answer

The 'Coalesce field not found on target table' error occurs when the transform map specifies a coalesce field that is not mapped to any target column in the transform map. The coalesce field is used to determine whether an import set row should update an existing record or create a new one; if the field is not mapped, the system cannot locate it on the target table during the coalesce operation, triggering this error. Option A correctly identifies that the coalesce field is missing from the transform map's field mappings, which is the most common root cause.

Exam trap

The trap here is that candidates often assume the error means the target table lacks the column, when in fact the column exists but is simply not mapped in the transform map's field mappings.

How to eliminate wrong answers

Option B is wrong because missing data in the coalesce field would cause a different error (e.g., 'Coalesce field is empty' or a null coalesce failure), not a 'not found on target table' error. Option C is wrong because the staging table configuration (e.g., table name, columns) does not affect the coalesce field lookup; the error is specific to the transform map's mapping of the coalesce field to the target table. Option D is wrong because if the target table did not have the specified coalesce field, the error would occur at transform map creation or validation time, not during import set row processing; the error message explicitly states 'not found on target table' but the actual issue is the lack of mapping in the transform map, not the absence of the field on the table.

Full explanation →
476
MCQhard

A before business rule on the Change Request table is supposed to set the 'risk' field based on the 'impact' and 'urgency' fields. The rule uses the current.update() method. However, when the rule runs, it causes a recursive loop. What is the best solution?

A.Use current.setValue() instead of current.update().
B.Use current.update() with a query to avoid recursion.
C.Add a condition to check if the risk field is already set.
D.Set the business rule to run after instead of before.
AnswerA

setValue() modifies the field without triggering another business rule.

Why this answer

Option A is correct because current.update() triggers the business rule again on the same record, causing a recursive loop. Using current.setValue() only modifies the field in memory without writing to the database, so it does not re-trigger the business rule. This is the standard pattern for avoiding recursion in before business rules when setting field values.

Exam trap

The trap here is that candidates may think checking a condition or changing the timing (before vs. after) will stop recursion, but the root cause is the use of current.update() which always triggers a new database write and re-evaluation of business rules.

How to eliminate wrong answers

Option B is wrong because current.update() with a query still performs a database write, which will re-trigger the business rule and cause recursion; there is no built-in mechanism to suppress recursion via query parameters. Option C is wrong because checking if the risk field is already set does not prevent recursion—the business rule still calls current.update(), which will fire the rule again regardless of the field's current value. Option D is wrong because changing the business rule to run after instead of before does not solve the recursion; current.update() in an after business rule also writes to the database and re-triggers the rule, and after rules are typically used for non-field-setting actions like notifications.

Full explanation →
477
MCQmedium

A company wants to allow users to reset their own passwords through the portal. Which feature should be enabled?

A.SSO Configuration
B.Password Reset
C.LDAP Integration
D.Virtual Agent
AnswerB

This is the dedicated self-service password reset feature.

Why this answer

The Password Reset feature in ServiceNow allows users to reset their own passwords through the portal without requiring administrator intervention. This is achieved by configuring password reset policies, security questions, and email verification, enabling self-service password management directly within the platform.

Exam trap

ServiceNow often tests the distinction between authentication mechanisms (SSO, LDAP) and self-service features (Password Reset), leading candidates to confuse integration methods with the actual user-facing capability to reset passwords.

How to eliminate wrong answers

Option A is wrong because SSO Configuration is used for single sign-on authentication via external identity providers (e.g., SAML, OAuth), not for enabling users to reset their own passwords within ServiceNow. Option C is wrong because LDAP Integration synchronizes user accounts and attributes from an external directory (e.g., Active Directory) but does not provide a built-in mechanism for users to reset passwords through the ServiceNow portal; password reset would still require external directory tools or additional configuration. Option D is wrong because Virtual Agent is a chatbot for conversational self-service, but it does not natively handle password reset functionality unless specifically configured with flows or integrations; the core feature for password reset is the dedicated Password Reset module.

Full explanation →
478
Multi-Selecteasy

Which TWO of the following are true about business rules in ServiceNow? (Choose two.)

Select 2 answers
A.They are only available in the global scope.
B.They can be configured to run 'before' or 'after' a database operation.
C.They can be scheduled to run at specific times.
D.They can be set to run on display, insert, update, delete, or query.
E.They run on the client side to provide immediate feedback.
AnswersB, D

Correct: 'When to run' field specifies before or after.

Why this answer

Option B is correct because business rules in ServiceNow can be configured to run 'before' or 'after' a database operation (insert, update, delete, or query). This allows administrators to perform actions such as data validation or modification at specific points in the database transaction lifecycle, ensuring data integrity and automating business logic.

Exam trap

The trap here is that candidates often confuse business rules with scheduled jobs or client scripts, mistakenly thinking business rules can be scheduled or run client-side, when in fact they are strictly server-side and event-driven by database operations.

Full explanation →
479
MCQmedium

An administrator is troubleshooting an ACL that grants 'write' access to the 'incident' table for the 'itil' role. Despite the ACL being active, users with the 'itil' role cannot update incidents. The administrator confirms that no other write ACLs exist. What is the most likely reason?

A.The 'Required roles' field on the 'incident' table form layout requires a different role to update.
B.The ACL is defined on a different table that extends 'incident'.
C.There is a read ACL that denies read access, which prevents any write operations.
D.The table is set to 'High Security' in the application properties.
AnswerA

Correct: Form-level required roles can override ACLs for UI actions.

Why this answer

The most likely reason is that the 'Required roles' field on the 'incident' table form layout restricts update operations to a specific role that the 'itil' users do not have. Even though the ACL grants 'write' access to the 'itil' role, the form layout's 'Required roles' setting overrides ACL permissions by preventing the form from being submitted or updated by users without the specified role. This is a common misconfiguration where form-level restrictions are overlooked during ACL troubleshooting.

Exam trap

The trap here is that candidates often focus solely on ACLs and overlook the form layout's 'Required roles' setting, assuming that ACL permissions alone control all write operations, when in fact form-level restrictions can override ACL grants.

How to eliminate wrong answers

Option B is wrong because an ACL defined on a different table that extends 'incident' would still apply to the 'incident' table via inheritance, and if it grants write access, it would not prevent updates. Option C is wrong because a read ACL that denies read access would prevent users from viewing records, but it does not directly block write operations; write operations are controlled by separate write ACLs, and the administrator confirmed no other write ACLs exist. Option D is wrong because the 'High Security' setting in application properties affects table-level security by requiring the 'admin' role for all operations, but it does not selectively block updates for the 'itil' role; it would block all access unless the user has the 'admin' role.

Full explanation →
480
MCQeasy

A CMDB administrator notices that duplicate CIs are being created for the same server from different discovery sources. What is the most likely cause?

A.The identification rules for the CI class are not correctly defined.
B.The 'Prevent duplicates' flag is not enabled.
C.The reconciliation rules are misconfigured.
D.The CMDB is set to read-only mode.
AnswerA

Identification rules determine how CIs are uniquely identified; misconfiguration leads to duplicates.

Why this answer

Duplicate CIs occur when multiple discovery sources (e.g., Service Mapping, Discovery, or cloud APIs) identify the same server but the identification rules fail to reconcile them into a single CI. Identification rules define which attributes (such as serial number, MAC address, or FQDN) uniquely identify a CI class. If these rules are missing, incomplete, or incorrectly prioritized, the system treats each discovery event as a new CI, leading to duplicates.

Exam trap

The trap here is that candidates confuse 'identification rules' (which prevent duplicates by uniquely matching CIs) with 'reconciliation rules' (which resolve attribute conflicts after matching), leading them to incorrectly select option C.

How to eliminate wrong answers

Option B is wrong because the 'Prevent duplicates' flag is a UI-level setting that prevents manual creation of duplicate CIs in the CMDB interface, but it does not control duplicate creation from automated discovery sources. Option C is wrong because reconciliation rules handle conflict resolution (e.g., which source's attribute values to trust) after identification has already matched CIs; they do not prevent the initial creation of duplicate CIs. Option D is wrong because read-only mode prevents all CI creation and modification, so no duplicates would be created at all; the administrator would see errors or no changes, not duplicates.

Full explanation →
481
MCQmedium

A form has a UI Policy that sets a field mandatory. The mandatory is not applied. Which is a likely cause?

A.The field is already mandatory by dictionary
B.UI Policy order is too low
C.UI Policy condition returns false
D.UI Policy is set to 'Run on load' only
AnswerC

If the condition evaluates to false, the UI Policy does not apply its actions, such as setting mandatory.

Why this answer

Option B is correct because if the condition script returns false, the UI Policy actions will not execute. Options A, C, and D are less likely to cause this specific issue.

Full explanation →
482
MCQmedium

A project manager wants all incident forms to display a static informational message at the top for all users without any conditions. Which method is most efficient and requires the least ongoing maintenance?

A.Create a CMS banner that targets the incident module.
B.Add a form annotation to the incident form view.
C.Create a UI Script that runs on load and adds a message.
D.Create a UI Policy with an 'always true' condition to show a message.
AnswerB

Form annotations are static, easy to add, and do not require conditions or code.

Why this answer

Form annotations are static text that can be added directly to the form view and appear for all users without any conditions or scripting. UI Policies and UI Scripts add unnecessary overhead, and CMS banners are designed for global headers not specific to a table.

Full explanation →
483
MCQhard

A company has implemented a complex service catalog workflow that includes multiple approval stages and manual tasks. Recently, some requests have been stuck in the 'Pending' state without progressing. The administrator has verified that the approval conditions are met and the approval records are created. What is the most likely cause?

A.The workflow's 'Run As' property is not set to a user with sufficient permissions.
B.The workflow is not published.
C.The approval rules are running in the wrong order.
D.The 'Transition condition' on the workflow states is not met.
AnswerD

Transition conditions control state-to-state movement; if unmet, the workflow stays pending.

Why this answer

Option D is correct because in a Service Catalog workflow, states have transition conditions that must evaluate to true for the workflow to move from one state to the next. Even if approval conditions are met and approval records exist, if the transition condition on the 'Pending' state is not satisfied (e.g., a variable value, a condition script returning false, or a missing prerequisite), the request remains stuck. This is a common cause of stalled workflows when all other configuration appears correct.

Exam trap

The trap here is that candidates confuse approval rules (which control who approves) with workflow state transition conditions (which control when the workflow moves to the next state), leading them to incorrectly select option C about approval rules running in the wrong order.

How to eliminate wrong answers

Option A is wrong because the 'Run As' property affects the security context under which the workflow runs, but if approval records are already created and conditions are met, the issue is not about permissions to execute actions—it's about the workflow logic not advancing. Option B is wrong because if the workflow were not published, it would not run at all, and no approval records would be created; the administrator has verified that approval records exist, so the workflow must be published and active. Option C is wrong because approval rules define who approves and under what conditions, not the order of workflow state transitions; the order of approval rules does not cause a request to remain in 'Pending' if the approval records are already created.

Full explanation →
484
MCQhard

An import set fails with error 'Import set row processing error'. The transform map uses a script that references a table that does not exist. What is the first step to resolve this?

A.Re-create the import set definition
B.Change the data source type
C.Run the import set in a different scope
D.Update the transform script to reference a valid table
AnswerC

Running in a different scope may bypass the error if the table exists there, but the root cause is the table reference. However, the script referencing a non-existent table is the core issue; changing scope is a temporary fix. The best practice is to update the script.

Why this answer

Option C is correct because changing the scope allows the transform script to access a table that exists in a different application scope. Import set row processing errors often occur when a transform map script references a table that is not visible in the current scope, and running the import set in a different scope (e.g., the global scope) can resolve the issue by making the missing table accessible. This is a common troubleshooting step before modifying scripts or definitions.

Exam trap

The trap here is that candidates often jump to modifying the transform script (Option D) as the first step, but ServiceNow expects you to first verify scope-related table visibility, which is a common cause of such errors.

How to eliminate wrong answers

Option A is wrong because re-creating the import set definition does not address the root cause of a missing table reference; it would only recreate the same configuration. Option B is wrong because changing the data source type would alter the import mechanism entirely, not fix a script referencing a non-existent table. Option D is wrong because updating the transform script to reference a valid table is a valid fix, but it is not the first step; the first step should be to check if the table exists in a different scope, which can be done by running the import set in that scope without modifying the script.

Full explanation →
485
MCQmedium

An SLA is defined with a condition 'Active = true' but some incidents that are active are not triggering the SLA. What is the most likely cause?

A.The incidents have a state of 'Closed' and are no longer active
B.The SLA definition is not set to active
C.The SLA condition needs to also check that the incident state is not 'Closed'
D.The incidents are assigned to a group that does not have the SLA
AnswerA

If incidents are closed, they are not active, so the condition fails. The condition should exclude closed states.

Why this answer

The SLA definition includes a condition 'Active = true', but if an incident's state is 'Closed', it is no longer considered active in the system. SLAs in ServiceNow are triggered only when all conditions in the SLA definition are met, and the 'Active = true' condition requires the incident to be in an active state (typically states like New, In Progress, On Hold). A closed incident has its 'Active' field set to false, so it will not trigger the SLA, even if it was previously active.

Exam trap

The trap here is that candidates may think the SLA definition itself needs to be active (Option B) or that an explicit state check is required (Option C), when in fact the 'Active = true' condition already handles the exclusion of closed incidents, and the issue is that the incidents are no longer active due to their state.

How to eliminate wrong answers

Option B is wrong because the question states the SLA definition is defined with a condition 'Active = true', implying the SLA definition itself is active; the issue is with the incident's state, not the SLA definition's active flag. Option C is wrong because the condition 'Active = true' already implicitly excludes closed incidents, as the 'Active' field on an incident is set to false when the state is 'Closed'; adding an explicit check for state not being 'Closed' is redundant and not the root cause. Option D is wrong because SLA assignments are based on conditions defined in the SLA definition, not on group membership; if the condition 'Active = true' is not met, the SLA will not trigger regardless of the group assignment.

Full explanation →
486
MCQeasy

What is the purpose of the 'Flow Designer'?

A.To design custom forms
B.To configure reports and dashboards
C.To create and manage automated workflows without scripting
D.To manage user roles
AnswerC

Flow Designer enables no-code automation of business processes.

Why this answer

Flow Designer is a low-code/no-code automation tool in ServiceNow that enables administrators and developers to create, configure, and manage automated workflows—such as approvals, notifications, and record updates—without writing any JavaScript or scripting. It uses a visual drag-and-drop interface to build flows, actions, and triggers, directly supporting the platform's automation capabilities.

Exam trap

ServiceNow often tests the distinction between Flow Designer (automation) and Form Designer (UI customization), so candidates mistakenly choose 'design custom forms' because both tools have a visual designer interface.

How to eliminate wrong answers

Option A is wrong because designing custom forms is the purpose of the Form Designer (or UI Builder), not Flow Designer; Flow Designer focuses on workflow logic, not form layout. Option B is wrong because configuring reports and dashboards is handled by the Reports module and Performance Analytics, not by Flow Designer, which is strictly for automation flows. Option D is wrong because managing user roles is done through the User Administration or Role Management modules, whereas Flow Designer has no role in role-based access control.

Full explanation →
487
MCQmedium

A ServiceNow administrator creates a new report showing incident counts by category. After sharing the report with the IT team, some users report they cannot see the report in their navigation menu. What is the most likely cause?

A.The report is scheduled to run at night.
B.The users do not have the required roles to view the report.
C.The report is not marked as public.
D.The report uses an unsupported chart type.
AnswerC

Reports are private by default; marking as public makes them visible to all users with access to the module.

Why this answer

Option C is correct because reports in ServiceNow are private by default, meaning only the creator can see them. To make a report visible to other users in the navigation menu, the report must be marked as 'Public' in its properties. Without this setting, users without direct access to the report's URL will not see it in their module list.

Exam trap

The trap here is that candidates often confuse the 'Public' flag with role-based access or scheduling, assuming that sharing a report automatically makes it visible in the navigation menu, when in fact the 'Public' setting is required for that specific visibility.

How to eliminate wrong answers

Option A is wrong because scheduling a report to run at night affects when the data is refreshed, not the visibility of the report in the navigation menu. Option B is wrong because the question states the report was shared with the IT team, implying they have the necessary roles; the issue is specifically about the report not appearing in the navigation menu, which is controlled by the 'Public' flag, not roles. Option D is wrong because an unsupported chart type would cause an error when viewing the report, not prevent it from appearing in the navigation menu.

Full explanation →
488
MCQhard

A catalog client script is supposed to show a variable when another variable equals 'Yes'. The script runs on 'onChange' of the first variable. However, the second variable does not appear. What is a possible cause?

A.The g_form.setDisplay() method is used incorrectly.
B.The client script is not set to 'All' catalog items.
C.The condition is written with 'g_form.getValue' for the wrong variable.
D.The script is set to 'onLoad' instead of 'onChange'.
AnswerB

If the script is restricted to specific items, it won't run on others.

Why this answer

Option B is correct because a client script that is not set to run on 'All' catalog items will only execute on the specific catalog item it was created for. If the script is scoped to a different item, the onChange event for the first variable on the current item will not trigger the script, so the second variable will never be shown. In ServiceNow, catalog client scripts must be explicitly associated with the correct catalog item or set to 'All' to apply globally.

Exam trap

ServiceNow often tests the misconception that a client script will automatically apply to all catalog items unless explicitly scoped, when in fact the default behavior requires explicit association or setting the catalog item field to 'All'.

How to eliminate wrong answers

Option A is wrong because g_form.setDisplay() is a valid method for showing or hiding a variable, and if used correctly with the right parameters (e.g., g_form.setDisplay('variable_name', true)), it would work; the issue here is that the script does not run at all, not that the method is misused. Option C is wrong because if the condition were written with g_form.getValue for the wrong variable, the script would still execute but evaluate incorrectly; the symptom of the variable not appearing at all indicates the script is not firing, not a logic error in the condition. Option D is wrong because the question states the script runs on 'onChange' of the first variable, so it is not set to 'onLoad'; if it were onLoad, it would run when the form loads, not on a field change, but the problem description confirms the intended event is onChange.

Full explanation →
489
MCQeasy

A UI Policy is configured to run on load and on change for the department and category variables. When a user selects department 'IT' and category does not contain 'hardware', what is the behavior regarding the 'cost_center' variable?

A.The cost_center variable is hidden
B.The cost_center variable becomes mandatory
C.The cost_center variable becomes optional
D.The cost_center variable becomes read-only
AnswerC

Since the condition is false, the else branch sets mandatory to false, making it optional.

Why this answer

Option C is correct because the UI Policy script sets the cost_center variable to optional only when the department is 'IT' and the category does not contain 'hardware'. The condition 'category does not contain hardware' is evaluated as true for any category value that does not include the substring 'hardware', triggering the 'mandatory=false' action on the cost_center variable. This makes the field optional (i.e., not required) when the condition is met.

Exam trap

The trap here is that candidates often confuse 'does not contain' with 'is not' or 'does not equal', and may incorrectly assume the condition only applies when category is empty, or that the policy hides the field instead of just making it optional.

How to eliminate wrong answers

Option A is wrong because the UI Policy does not include any action to hide the cost_center variable; it only sets mandatory to false. Option B is wrong because the policy sets mandatory to false, not true, so the variable does not become mandatory. Option D is wrong because the policy does not change the read-only property of the cost_center variable; it only affects its mandatory state.

Full explanation →
490
MCQmedium

The JSON above shows part of a transform map configuration. What will happen when an import set row containing a value in the 'short_desc' field is processed?

A.A task record is created instead
B.The import fails because the target field name is incorrect
C.An existing incident record is updated with the short_description
D.A new incident record is created with the short_description populated
AnswerC

The transform action is 'insert', not 'update'.

Why this answer

The transform map configuration shown in the JSON includes a field mapping where 'short_desc' from the import set row is mapped to 'short_description' on the Incident table. When an import set row contains a value in 'short_desc', the transform engine will use the coalesce setting (if enabled) to match an existing incident record based on a unique identifier (e.g., number or sys_id). If a match is found, the existing incident is updated with the new short_description value; otherwise, a new incident would be created.

Since the question implies the coalesce is set to true (common in such configurations), the correct behavior is an update to an existing incident record.

Exam trap

ServiceNow often tests the misconception that any import set row with a value will always create a new record, but the trap here is that the coalesce setting on a key field (like 'number') causes an update to an existing record instead, which candidates overlook.

How to eliminate wrong answers

Option A is wrong because a task record is not created unless the transform map explicitly targets the Task table or uses a condition to change the target table; the mapping shows 'incident' as the target table. Option B is wrong because 'short_desc' is a valid source field name, and the target field 'short_description' is correct for the Incident table; the import will not fail due to an incorrect field name. Option D is wrong because if coalesce is enabled and a matching incident record exists, the transform engine will update that record rather than create a new one; a new incident is only created if no match is found.

Full explanation →
491
MCQmedium

Refer to the exhibit. When a user submits a request for a laptop, the approval is granted by admin even though admin is not the manager. Which configuration allows this?

A.Admin has the 'approval_admin' role that overrides normal approval constraints.
B.The workflow has an approval activity with 'Delegate to group' and admin is the group manager.
C.The catalog item's approval rule is set to 'Use approval group' and admin is a member of that group.
D.The approval group 'IT Hardware' has admin as a member and approval delegation is enabled.
AnswerC
Full explanation →
492
MCQeasy

A company needs to create a report that shows the average time taken to resolve incidents. Which report type would best fulfill this requirement?

A.Pivot table with average of resolved time
B.Line chart with trend over time
C.Bar chart with count of incidents
D.Scorecard with gauge
AnswerA

Pivot tables can calculate and display averages, making them ideal.

Why this answer

A pivot table with an average of resolved time is the correct choice because it directly computes the mean of the duration field (e.g., 'resolved_time' or 'time_to_resolve') for each grouping, such as by assignment group or category. This satisfies the requirement to show the average time taken to resolve incidents without visual clutter. In ServiceNow, pivot tables aggregate numeric data using functions like AVG, SUM, or COUNT, making them ideal for summary statistics.

Exam trap

ServiceNow often tests the distinction between aggregate functions (AVG, SUM) and visualizations that show trends or counts; the trap here is that candidates may confuse 'average time' with a trend line or a count-based chart, leading them to pick a line chart or bar chart instead of the pivot table.

How to eliminate wrong answers

Option B is wrong because a line chart with trend over time shows how a metric changes across a time series, not a single average value; it would display fluctuations in resolution time per period rather than the overall average. Option C is wrong because a bar chart with count of incidents shows the number of incidents, not the average resolution time; it answers 'how many' not 'how long'. Option D is wrong because a scorecard with gauge typically displays a single metric against a target (e.g., current SLA compliance percentage), not the average of a calculated field like resolved time.

Full explanation →
493
Matchingmedium

Match each ServiceNow acronym to its full form.

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

Concepts
Matches

Configuration Management Database

Service Level Agreement

Configuration Item

Common Service Data Model

IT Service Management

Why these pairings

These are common acronyms used in ServiceNow administration.

Full explanation →
494
Multi-Selectmedium

Which TWO statements about the ServiceNow application navigator are true? (Choose two.)

Select 2 answers
A.The navigator displays all tables in the instance.
B.Users can add links to the navigator as favorites.
C.The navigator can be filtered by typing in the filter field.
D.End users can add new modules to the navigator.
E.Administrators can customize the navigator by creating new modules.
AnswersC, E

The filter field allows searching modules.

Why this answer

Option C is correct because the ServiceNow application navigator includes a built-in filter field that allows users to quickly locate modules, reports, or other navigator entries by typing keywords. This filter dynamically narrows the displayed items based on the input, improving navigation efficiency without requiring administrative changes.

Exam trap

The trap here is that candidates may confuse the navigator's filter functionality with the global search or think that end users can customize the navigator structure, when in fact only administrators can create modules and the filter is a simple client-side text match.

Full explanation →
495
MCQmedium

An organization uses an approval process for all catalog requests. They want a delegated approver to be able to approve on behalf of the manager. Which configuration is required?

A.Enable 'Approval Delegation' on the system property only.
B.Use the 'Delegate' related list on the approval rule.
C.Configure the delegate in the user record of the approver.
D.Set the 'Approval Delegation' property to true and configure delegates on the user record.
AnswerD

Correct: Both steps are required for delegation to work.

Why this answer

Option D is correct because ServiceNow requires both the 'Approval Delegation' system property to be set to true and the delegate to be configured on the user record of the approver. This two-part configuration enables a delegated approver to act on behalf of the manager during an approval process, ensuring the delegation is recognized by the approval engine.

Exam trap

The trap here is that candidates often think enabling the system property alone is sufficient, or that delegation is configured on the approval rule, but ServiceNow requires both the property and the delegate configuration on the user record to function correctly.

How to eliminate wrong answers

Option A is wrong because enabling only the system property does not specify who the delegate is; the delegate must also be configured on the user record. Option B is wrong because the 'Delegate' related list is not available on approval rules; delegation is configured on the user record, not on the rule itself. Option C is wrong because configuring the delegate on the user record alone, without setting the 'Approval Delegation' property to true, will not activate the delegation functionality.

Full explanation →
496
Drag & Dropmedium

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

Business Rules run on server-side when records are inserted, updated, or deleted.

Full explanation →
497
Multi-Selectmedium

Which THREE are correct about form views? (Choose three.)

Select 3 answers
A.Form views can be imported from other instances.
B.A form view can only contain one section.
C.A form view defines which fields are displayed and their layout.
D.A form view can be assigned to a specific role.
E.If no view is assigned to a user, the default view is used.
AnswersC, D, E

Views control field placement.

Why this answer

Option C is correct because form views in ServiceNow are the primary mechanism for controlling which fields appear on a form and how they are arranged (e.g., order, sections, and visibility). The view definition is stored in the 'sys_ui_view' table and can be customized per table to tailor the user experience without altering the underlying data model.

Exam trap

ServiceNow often tests the misconception that form views are limited to a single section, but ServiceNow explicitly supports multiple sections within one view to group related fields.

Full explanation →
498
MCQhard

A system administrator needs to hide the 'Delete' button on the incident form for users with the 'itil' role, but allow it for administrators. What is the best approach?

A.Modify the form view to remove the button
B.UI policy with role condition
C.Business rule checking role
D.ACL with condition on role
AnswerB

UI policies can hide form buttons based on conditions like user roles.

Why this answer

A UI Policy with a role condition is the best approach because it dynamically controls the visibility of the 'Delete' button on the incident form based on the user's role. UI Policies run client-side and can hide or show fields and buttons without requiring a page refresh, making them ideal for form-level UI changes. By setting the condition to 'role=itil' and the action to 'Hide', the button will be hidden for itil users but remain visible for administrators who do not have that condition applied.

Exam trap

The trap here is that candidates often confuse ACLs (which control backend access) with UI Policies (which control frontend visibility), leading them to choose ACLs for hiding buttons instead of using the correct client-side mechanism.

How to eliminate wrong answers

Option A is wrong because modifying the form view to remove the button would permanently hide it for all users, including administrators, which does not meet the requirement of allowing it for administrators. Option C is wrong because a Business Rule runs server-side and cannot directly hide a UI element on the form; it would require additional client-side scripting or a UI Policy to achieve the visibility change. Option D is wrong because an ACL controls data access and record-level operations (like delete), not the visibility of UI elements on the form; an ACL would prevent the delete action but would not hide the button itself.

Full explanation →
499
Multi-Selectmedium

Which TWO of the following are true regarding catalog item variables? (Choose two.)

Select 2 answers
A.Variables defined on a catalog item cannot be referenced in workflows.
B.Variables are always displayed in the order they were created.
C.Variables can be configured as 'Read only' after submission.
D.Variables in a variable set are independent and cannot share values across sets.
E.Variables can have a 'Default Value' that is populated by a script.
AnswersC, E

Read only setting controls editability on the request form after submit.

Why this answer

Options B and D are correct. Option A is wrong because variables can be referenced in workflows via 'current.variables.variable_name'. Option C is wrong because variable sets can be shared, but the variables themselves are independent if cloned.

Option E is wrong because variables can be ordered by 'Order' field.

Full explanation →
500
Drag & Dropmedium

Drag and drop the steps to set up an SLA definition 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

SLA definitions specify timeframes for task completion.

Full explanation →
501
MCQhard

Refer to the exhibit. What is the primary purpose of this Business Rule?

A.To update a timestamp field on the parent CI whenever a child CI is updated.
B.To prevent updates to child CIs if the parent CI has not been updated recently.
C.To log all changes made to a CI in a custom table.
D.To delete child CIs when the parent CI is deleted.
AnswerA

The script retrieves the parent and sets a timestamp field.

Why this answer

The Business Rule shown is an 'After' update rule that triggers on the 'cmdb_ci' table. It uses a 'setValue' call on the parent record (via 'current.parent') to update the 'sys_updated_on' field, which is the system timestamp. This ensures that whenever a child CI is updated, the parent CI's timestamp is refreshed, maintaining an accurate audit trail of changes in the CMDB hierarchy.

Exam trap

ServiceNow often tests the misconception that a Business Rule updating a related record's timestamp is for logging or deletion, when in fact it is purely for maintaining a freshness indicator in a parent-child CI relationship.

How to eliminate wrong answers

Option B is wrong because the rule does not check any timestamps or prevent updates; it only updates the parent's timestamp after a child update. Option C is wrong because the rule does not write to a custom table or use any logging mechanism like 'gs.log' or 'GlideRecord.insert' to a separate table. Option D is wrong because the rule does not perform any delete operations; it only updates a timestamp field on the parent, and there is no cascading delete logic.

Full explanation →
502
Multi-Selecthard

Which THREE elements are required for a successful 'Password Reset' flow in ServiceNow? (Choose three.)

Select 3 answers
A.The 'Password Reset' plugin activated.
B.A valid email address for the user.
C.A reset password URL configured in system properties.
D.The 'password_reset' role assigned to the user.
E.The user's security questions answered.
AnswersA, B, C

The plugin provides the necessary functionality.

Why this answer

Option A is correct because the 'Password Reset' plugin must be activated to enable the password reset functionality in ServiceNow. Without this plugin, the system lacks the core application logic and tables required to process password reset requests, making it a mandatory prerequisite.

Exam trap

The trap here is that candidates often assume security questions or a specific role are mandatory, but ServiceNow's password reset flow is designed to work with just the plugin, a valid email, and the configured URL, making the other options distractors that seem plausible but are not required.

Full explanation →
503
MCQeasy

What is the purpose of the CMDB Health Dashboard?

A.To manage user roles and permissions for CMDB
B.To monitor the completeness and compliance of CI data in the CMDB
C.To visualize relationships between CIs
D.To configure discovery schedules and probes
AnswerB

The Health Dashboard tracks data quality metrics.

Why this answer

The CMDB Health Dashboard is designed to monitor the completeness and compliance of Configuration Item (CI) data within the CMDB. It provides metrics and visualizations that help administrators identify data quality issues, such as missing mandatory fields, stale CIs, or violations of CMDB rules, ensuring the CMDB remains a reliable source of truth for IT operations.

Exam trap

The trap here is that candidates often confuse the CMDB Health Dashboard with the CI Relationship Map or Discovery configuration, but the dashboard is strictly a monitoring tool for data quality, not for managing relationships or discovery schedules.

How to eliminate wrong answers

Option A is wrong because managing user roles and permissions for the CMDB is handled through the Role Administration module and Access Controls (ACLs), not the CMDB Health Dashboard. Option C is wrong because visualizing relationships between CIs is the purpose of the Service Graph Connector or the CI Relationship Map, not the Health Dashboard. Option D is wrong because configuring discovery schedules and probes is done within the Discovery module, specifically in the Discovery Schedules and Probe configurations, not the CMDB Health Dashboard.

Full explanation →
504
Multi-Selectmedium

A ServiceNow administrator is configuring Data Segmentation for CMDB. Which TWO statements are true about Data Segmentation? (Select exactly 2)

Select 2 answers
A.It can be applied to individual CI fields.
B.It can be used to restrict access to CI records based on user criteria.
C.It is configured in the Data Segmentation module under System Security.
D.It requires the subscription of a separate CMDB product license.
E.It can be combined with standard ACLs for granular control.
AnswersB, E

Data Segmentation allows record-level access based on user attributes.

Why this answer

Data Segmentation in ServiceNow restricts access to CI records based on user criteria, such as business unit or location, by evaluating conditions against the user's session. This is a row-level security mechanism that filters which CI records a user can see, making Option B correct. It works alongside standard ACLs, which handle field- and record-level permissions, allowing administrators to layer both for granular control, confirming Option E.

Exam trap

The trap here is that candidates often confuse Data Segmentation with field-level ACLs or assume it requires an additional license, when in fact it is a row-level security feature that is part of the base CMDB and works in conjunction with, not instead of, standard ACLs.

Full explanation →
505
MCQmedium

Refer to the exhibit. A workflow for a catalog item has three stages. The 'Run Script' activity sets the assigned_to to the current user (the requester). The approval activity approves by the manager. The 'Create Task' activity creates a catalog task. When the workflow runs, the task is created but is assigned to the requester instead of the fulfillment group. What is the likely cause?

A.The task creation activity is configured to assign to the requester by default.
B.The 'Run Script' activity sets the assigned_to on the request, but the task creation activity does not copy that value; the task should have its own assignment.
C.The workflow should have a 'Set Values' activity after the approval to assign the task.
D.The approval activity reassigned the request to the manager.
AnswerB

The script modifies the request record, not the task.

Why this answer

Option B is correct because the 'Run Script' activity sets the `assigned_to` field on the request record itself, but the 'Create Task' activity creates a separate catalog task record. The task creation activity does not automatically inherit the `assigned_to` value from the request; it uses its own assignment configuration, which defaults to the requester if no fulfillment group or specific assignment is defined. This causes the task to be assigned to the requester instead of the intended fulfillment group.

Exam trap

ServiceNow often tests the misconception that setting a field on the request record (via a 'Run Script' activity) will automatically propagate to child records like tasks, when in reality each record type has its own independent assignment logic.

How to eliminate wrong answers

Option A is wrong because the task creation activity does not have a default to assign to the requester; the assignment behavior depends on the activity's configuration, such as the 'Assignment group' or 'Assigned to' fields, which are not set to the requester by default. Option C is wrong because a 'Set Values' activity after approval would not fix the issue; the assignment must be configured within the 'Create Task' activity itself or via a script that explicitly sets the task's assignment fields. Option D is wrong because the approval activity approves by the manager but does not reassign the request; it only changes the state of the approval record, not the `assigned_to` field of the request or task.

Full explanation →
506
MCQmedium

Refer to the exhibit. This script runs in a background script. Which set of records will be printed?

A.Incidents with state=3 AND assigned_to is not null
B.Incidents with state=3 AND priority<=3 AND assigned_to is not null
C.Incidents with priority<=3
D.All incidents
AnswerB

All three conditions are combined with AND.

Why this answer

Option B is correct because the script queries incidents where state=3, priority<=3, and assigned_to is not null (AND logic). Options A, C, and D describe different sets.

Full explanation →
507
MCQhard

A ServiceNow administrator is responsible for importing data from an external HR system into the Employee table. The import set uses a transform map that creates new records and updates existing ones based on the employee number. Recently, the administrator noticed that some existing records are being incorrectly duplicated. The transform map is configured with a coalesce on the 'Employee Number' field. After reviewing the import log, the administrator finds that the import set rows are being processed, but the coalesce is not matching correctly. The HR system sends data with employee numbers that have leading zeros, but the ServiceNow employee number field is stored without leading zeros. For example, employee number '0123' in the source is '123' in ServiceNow. The administrator needs to fix this issue without modifying the HR system data. Which course of action should the administrator take?

A.Modify the import set table to store employee numbers as strings with leading zeros.
B.Add a script in the transform map to remove leading zeros from the employee number before the coalesce runs.
C.Change the coalesce field to a different unique field such as email address.
D.Use a before business rule on the Employee table to trim leading zeros on the employee number field.
AnswerB

This normalizes the source value to match the target during the coalesce operation.

Why this answer

Option B is correct because the coalesce operation in a transform map runs before field mapping scripts, so a script placed in the transform map's 'Script' field (or a 'Before' script) can normalize the source value by removing leading zeros before the coalesce attempts to match. This ensures the incoming '0123' is converted to '123' and correctly matches the existing record in the Employee table.

Exam trap

The trap here is that candidates mistakenly think a business rule or field-level script can fix the coalesce matching, but the coalesce runs before those scripts, so only a transform map script executed before the coalesce can normalize the source value for correct matching.

How to eliminate wrong answers

Option A is wrong because modifying the import set table to store employee numbers as strings with leading zeros does not fix the coalesce matching issue; the coalesce compares against the target table field, which still lacks leading zeros, so duplicates would persist. Option C is wrong because changing the coalesce field to a different unique field like email address is a workaround that avoids the root cause and may introduce new matching problems if email is not consistently unique or present. Option D is wrong because a before business rule on the Employee table runs after the record is already created or updated, so it cannot prevent the duplicate creation caused by the coalesce failing to match during the import.

Full explanation →
508
Matchingmedium

Match each ServiceNow application scope to its description.

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

Concepts
Matches

Accessible across all applications in the instance

Isolated application with its own tables and access controls

System scope for core platform functionality

Custom applications developed by the instance owner

Pre-built applications available from ServiceNow Store

Why these pairings

Scopes define the boundaries and accessibility of applications.

Full explanation →
509
MCQhard

A large enterprise uses ServiceNow for IT Service Management and has implemented a self-service portal with over 50 catalog items. Recently, the IT team receives complaints that certain catalog items are not visible to users who should have access based on their roles. The administrator has verified that the catalog items are set to 'User Criteria' and 'Roles' correctly. Additionally, the portal's 'Catalog Categories' and 'Homepage' configuration seem correct. However, users still report missing items. Upon investigation, the administrator notices that the 'Available for' criteria on some catalog items include conditions like 'User's Department is IT', but the users in IT claim they still cannot see the item. The administrator checks the user records and confirms that the department field is correctly populated. What is the most likely cause of this issue?

A.The 'Can read' role on the 'Request' table is missing for the users.
B.The system's cache for user criteria evaluation has not been flushed after the latest updates to the criteria.
C.The portal uses a custom URL that triggers incorrect encoding for some catalog item categories.
D.The catalog items are assigned to a fulfillment group that the users are not members of.
AnswerB

ServiceNow caches criteria evaluation; flushing the cache or waiting for periodic refresh resolves visibility issues.

Why this answer

The most likely cause is that the system's cache for user criteria evaluation has not been flushed after the latest updates to the criteria. ServiceNow caches user criteria evaluations to improve performance, and when criteria are modified, the cache must be cleared (via the 'Flush Cache' related link on the User Criteria record or by running the 'User Criteria Cache Flush' scheduled job) before the changes take effect. Without this flush, the system continues to use stale cached results, causing users to be incorrectly denied access to catalog items even though their department field is correctly populated.

Exam trap

The trap here is that candidates often focus on role-based access or configuration errors (like fulfillment groups or table permissions) and overlook the fact that ServiceNow caches user criteria evaluations, so changes to criteria conditions require a cache flush to take effect immediately.

How to eliminate wrong answers

Option A is wrong because the 'Can read' role on the 'Request' table controls whether a user can view existing request records, not whether they can see catalog items in the service catalog; catalog item visibility is governed by user criteria and roles on the item itself, not table-level read permissions. Option C is wrong because custom URLs or encoding issues would affect the entire portal or category display, not selectively hide specific items from users who meet the criteria, and the administrator already verified the portal's 'Catalog Categories' and 'Homepage' configuration are correct. Option D is wrong because fulfillment groups determine who can fulfill a request, not who can see or submit the catalog item; visibility is controlled by user criteria and roles, not fulfillment group membership.

Full explanation →
510
MCQeasy

A user reports that the 'My Work' module is missing from the application navigator. The administrator has assigned the user the 'sn_hr_core.hr_case_agent' role. Which step should the administrator take to troubleshoot this issue?

A.Check the sys_module list for role requirements on the 'My Work' module.
B.Ask the user to clear their browser cache and reload the instance.
C.Deactivate and reactivate the 'My Work' module in the application navigator.
D.Assign the user the 'admin' role to ensure full access.
AnswerA

Role requirements determine module visibility.

Why this answer

The 'My Work' module is a standard application module that may have role-based visibility restrictions defined in the sys_module record. By checking the sys_module list, the administrator can verify if the 'sn_hr_core.hr_case_agent' role is included in the required roles for the module. If the role is missing, the module will not appear in the application navigator for that user.

Exam trap

The trap here is that candidates often jump to client-side fixes like clearing cache or assume a module is broken, rather than understanding that module visibility is role-driven and must be verified in the sys_module record.

How to eliminate wrong answers

Option B is wrong because clearing the browser cache would not resolve a role-based visibility issue; it only addresses client-side caching problems. Option C is wrong because deactivating and reactivating the module does not change role assignments; it would only affect the module's active state, not its role requirements. Option D is wrong because assigning the 'admin' role is an overprivileged workaround that bypasses proper role-based access control and is not a recommended troubleshooting step.

Full explanation →
Page 6

Page 7 of 7

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 →