ServiceNow Certified System Administrator CSA SNOW-CSA Questions 226–300 | Page 4/7

226

MCQmedium

An administrator creates an Application Menu with a condition and adds a module to it. Users with the correct role cannot see the module. The module has no roles restriction. What could be the issue?

A.The menu's condition fails for those users

B.The module is inactive

C.The application menu is not active

D.The module's roles are empty

AnswerA

A condition on the menu can restrict visibility based on user attributes; if it fails, modules in that menu are hidden.

Why this answer

The menu's condition may fail for those users, hiding the module. Option B would hide the module for all users if it were inactive. Option C would hide the entire menu for all users if it were inactive.

Option D means no role restriction, so it should be visible, but the menu condition overrides.

Full explanation →

227

MCQeasy

A CMDB administrator wants to identify which user last updated a CI record. Which table contains this information?

A.sys_user

B.sys_audit

C.sys_ci

D.sys_metadata

AnswerB

sys_audit records all changes to records including the user.

Why this answer

The sys_audit table stores the audit history of all field-level changes made to CI records, including the user who made the update, the timestamp, and the old and new values. When a CMDB administrator needs to identify the last user to update a CI, querying sys_audit with the appropriate filter on the record's sys_id and ordering by the 'sys_created_on' field descending will reveal the most recent change and its author.

Exam trap

The trap here is that candidates often confuse the table storing the CI record (sys_ci) with the table storing the change history (sys_audit), mistakenly thinking the record itself contains the last updated user field, whereas ServiceNow stores that metadata in the audit trail.

How to eliminate wrong answers

Option A is wrong because sys_user is the table that stores user account records (e.g., login credentials, roles), not the history of CI updates. Option C is wrong because sys_ci is the table that stores the CI records themselves, not the audit trail of who modified them. Option D is wrong because sys_metadata is the table that stores system metadata definitions (e.g., table schemas, field definitions), not user-driven change history.

Full explanation →

228

MCQhard

An administrator wrote a business rule to automatically close all child tasks when an incident is resolved. However, some child tasks are not getting closed. Which of the following is the most likely reason for this issue?

A.The 'parent' field does not exist on the task table

B.The business rule is async and may not run correctly if the state change is not committed

C.The business rule should be synchronous to affect child records

D.The GlideRecord query syntax is incorrect

AnswerB

Async business rules run after the record update, but the condition might be evaluated before the commit in some cases, causing issues.

Why this answer

When a business rule is asynchronous, it runs after the database transaction that triggered it has been committed. This means there can be a delay between when the incident is resolved and when the rule executes. During that interval, it's possible for the incident state to be changed again or for new child tasks to be created.

If the incident state is no longer "Resolved" when the async rule runs, the condition in the script may prevent child tasks from being closed. Additionally, any child tasks created after the rule runs will remain open. A synchronous business rule would execute within the same transaction, ensuring that all existing child tasks are closed immediately and eliminating such timing issues.

Exam trap

The trap here is that candidates often assume asynchronous business rules are always better for performance, but they forget that asynchronous rules cannot see uncommitted data, leading to missed child record updates when the rule depends on the parent's new state.

How to eliminate wrong answers

Option A is wrong because the 'parent' field does exist on the task table by default in ServiceNow; it is a core field used for task-to-task relationships, and its absence would cause a different error. Option C is wrong because synchronous business rules are actually the default and can affect child records; the issue here is not about sync vs async but about the timing of the state change visibility. Option D is wrong because the GlideRecord query syntax is not inherently incorrect; the problem is that the query runs before the parent state change is committed, not that the syntax is faulty.

Full explanation →

229

MCQeasy

An organization wants to allow users to submit requests via a self-service portal without needing to log in. Which configuration is required to enable this?

A.Configure ACLs to allow public read access on the portal page

B.Make the portal page a public page in the portal properties

C.Disable the 'Require login' option in the portal configuration

D.Select the 'Allow public access' checkbox on the portal page record

AnswerB

Setting the page as public allows anonymous access.

Why this answer

Making a portal page a public page in the portal properties allows unauthenticated users to access it without logging in. This configuration is specific to ServiceNow portals, where the 'Public' setting on the portal record overrides the default authentication requirement for all pages within that portal.

Exam trap

The trap here is that candidates confuse the portal-level 'Public' setting with page-level or ACL-based controls, often selecting 'Allow public access' on a page record (which does not exist) or thinking ACLs alone can grant anonymous page access.

How to eliminate wrong answers

Option A is wrong because ACLs control data-level access (e.g., records in tables), not page-level visibility; public read ACLs would expose data but still require a session for the portal page to render. Option C is wrong because there is no 'Require login' option in portal configuration; the correct setting is the 'Public' checkbox on the portal record, not a global toggle. Option D is wrong because the 'Allow public access' checkbox does not exist on the portal page record; public access is configured at the portal level, not per page.

Full explanation →

230

MCQhard

An administrator imports data from a CSV file into the 'cmdb_ci' table using a transform map. The import set row contains fields 'name', 'serial_number', and 'manufacturer'. The transform map has a field mapping for 'name' with a co-paste of 'name' and 'serial_number'. Another mapping for 'serial_number' uses a script to concatenate 'SN-' prefix. The 'manufacturer' field is not mapped. After the import, the resulting 'name' field contains 'Laptop123, SN-12345' and 'serial_number' contains 'SN-12345'. Which statement best describes the outcome?

A.The import fails because the 'manufacturer' field is not mapped

B.The 'name' field contains 'Laptop123, SN-12345' and 'serial_number' contains 'SN-12345'

C.The 'name' field contains 'Laptop123, 12345' because the script for 'serial_number' overrides the co-paste for 'name'

D.The 'serial_number' field remains '12345' because the co-paste mapping for 'name' consumed the source field

AnswerB

Co-paste for 'name' concatenates source 'name' and source 'serial_number' (original), and the script for 'serial_number' transforms its own value.

Why this answer

The transform map's field mapping for 'name' uses a co-paste of 'name' and 'serial_number', which concatenates the source values with a comma and space, resulting in 'Laptop123, SN-12345'. The mapping for 'serial_number' uses a script that adds the 'SN-' prefix to the source 'serial_number' value, producing 'SN-12345'. The unmapped 'manufacturer' field is simply ignored during import, causing no failure.

Therefore, the outcome matches option B exactly.

Exam trap

The trap here is that candidates mistakenly believe unmapped fields cause import failures or that field mappings consume source values, preventing other mappings from using them, when in fact each mapping reads independently from the source row.

How to eliminate wrong answers

Option A is wrong because unmapped fields in an import set row do not cause the import to fail; they are simply not populated in the target table. Option C is wrong because the script for 'serial_number' does not override the co-paste for 'name'; both mappings operate independently on their respective target fields. Option D is wrong because the co-paste mapping for 'name' does not consume the source 'serial_number' field; it reads it as a source value but does not remove it from the row, so the 'serial_number' mapping still receives the original source value.

Full explanation →

231

MCQhard

An administrator is managing a CMDB that contains both physical and virtual servers. The company uses a custom field 'u_os_version' to track the operating system version. When new servers are discovered, the field is populated correctly. However, when the operating system is updated manually by the IT team, the field is not updated. The administrator wants the CMDB to automatically reflect manual changes made to server operating systems. Which approach should be taken?

A.Configure the Discovery probe to re-discover the server after an OS update.

B.Create a business rule on the server table to update the CI when the OS is changed.

C.Use the CI Class Manager to set the field as 'Reconcilable'.

D.Use a scheduled job to query the server's actual OS version periodically.

AnswerB

A business rule can trigger on update events and populate the custom CMDB field accordingly.

Why this answer

A business rule on the server table can detect when the 'u_os_version' field is manually updated and automatically update the corresponding CI record. This ensures that changes made outside of Discovery are reflected in the CMDB without requiring re-discovery or scheduled jobs, leveraging ServiceNow's event-driven architecture.

Exam trap

The trap here is that candidates often confuse 'Reconcilable' fields with automatic update propagation, but reconciliation only resolves conflicts during data source merges, not for manual changes.

How to eliminate wrong answers

Option A is wrong because re-discovering the server after an OS update would only work if Discovery runs again, but it does not automatically trigger on manual changes; it requires manual intervention or a scheduled job, making it inefficient and not real-time. Option C is wrong because setting a field as 'Reconcilable' in CI Class Manager affects how conflicts are resolved during reconciliation processes, not how manual updates are captured or propagated. Option D is wrong because a scheduled job to query the server's actual OS version periodically introduces latency and overhead, and it does not provide immediate synchronization when the OS is manually updated.

Full explanation →

232

MCQeasy

Which module is used to create and manage record producers?

A.Process Automation > Record Producers

B.Service Portal > Record Producers

C.Service Catalog > Record Producers

D.System Definition > Record Producers

AnswerC

This is the correct navigation path for record producers.

Why this answer

Record producers are a type of catalog item that allows users to submit records directly from the Service Catalog. They are created and managed under Service Catalog > Record Producers, where you define the target table, form fields, and mapping logic to generate a new record in the platform upon submission.

Exam trap

The trap here is that candidates confuse record producers with catalog items or think they are managed under Process Automation or System Definition, but the SNOW-CSA exam specifically tests that record producers are a subtype of catalog items located under Service Catalog > Record Producers.

How to eliminate wrong answers

Option A is wrong because Process Automation > Record Producers does not exist; record producers are not managed under Process Automation, which handles flows, actions, and approvals. Option B is wrong because Service Portal > Record Producers is not a valid navigation path; while record producers can be used on the Service Portal, they are created and managed in the Service Catalog module, not within the Service Portal configuration itself. Option D is wrong because System Definition > Record Producers is not a standard navigation; System Definition deals with tables, fields, and dictionaries, not the creation of record producers, which are catalog items.

Full explanation →

233

MCQmedium

A company needs to add a reference field on the Incident form that points to the Service Catalog item requested. However, the reference field must only allow selection of Catalog Items that are in the 'Software' category. Which configuration should be used?

A.Create a UI policy to show/hide the field

B.Set a default value on the reference field

C.Add a reference qualifier to the field with condition 'Category = Software'

D.Use an Access Control Rule to limit visibility

AnswerC

Reference qualifier filters the list to matching records.

Why this answer

A reference qualifier is the standard mechanism in ServiceNow to filter the records that appear in a reference field's lookup. By adding a condition such as 'Category = Software' to the reference qualifier on the field pointing to the Service Catalog item table (sc_cat_item), only catalog items in the 'Software' category will be selectable, meeting the requirement precisely.

Exam trap

The trap here is that candidates often confuse UI policies (which control field behavior) with reference qualifiers (which control lookup data), leading them to choose option A instead of the correct filtering mechanism.

How to eliminate wrong answers

Option A is wrong because UI policies control the visibility, mandatory status, or read-only state of fields based on conditions, but they cannot filter the selectable records in a reference field's lookup list. Option B is wrong because setting a default value only pre-populates the field with a specific record; it does not restrict the user from selecting other records that do not meet the category condition. Option D is wrong because Access Control Rules (ACLs) govern record-level security (who can read, write, etc.) and do not filter the options presented in a reference field's lookup; they would either block access entirely or allow it, not provide a filtered list.

Full explanation →

234

MCQmedium

A user reports that a catalog item is not visible to them, but other users in the same department can see it. What is the most likely cause?

A.User criteria restricts visibility

B.The item is in a different category

C.The item is out of stock

D.The item is not active

AnswerA

User criteria can limit which users see the item.

Why this answer

User criteria is a visibility rule applied to catalog items that restricts which users or groups can see the item in the service catalog. If one user cannot see the item while others in the same department can, the most likely cause is that the user criteria on the catalog item excludes that specific user, either by user, role, group, or location criteria.

Exam trap

The trap here is that candidates often confuse visibility restrictions (user criteria) with availability or lifecycle states (active, out of stock), assuming an item is hidden because it is unavailable rather than because of a user-specific rule.

How to eliminate wrong answers

Option B is wrong because a catalog item being in a different category would affect all users, not just one user, and categories are used for organizing items, not for per-user visibility. Option C is wrong because out-of-stock status affects availability or fulfillment, not visibility in the catalog; users can still see out-of-stock items. Option D is wrong because if the item were not active, it would be hidden from all users, not just a single user.

Full explanation →

235

MCQhard

During a CMDB audit, an administrator discovers duplicate CI records for the same network switch. The switch is identified by its serial number. The identification rule currently uses IP address and MAC address as identifiers. What is the most likely cause of the duplicate records?

A.There is a conflict in the class hierarchy.

B.The discovery source is set to ServiceNow Discovery only, but multiple sources exist.

C.The reconciliation rule is set to manual mode.

D.The serial number is not included in the identification rule.

AnswerD

Without a unique identifier like serial number, duplicates can occur.

Why this answer

The duplicate CI records exist because the identification rule does not include the serial number, which is the unique hardware identifier for the switch. Without it, the system cannot reliably match the discovered switch to an existing CI, so a new record is created each time the switch is discovered with a different IP or MAC address. Including the serial number in the identification rule ensures that the same physical device is always reconciled to the same CI record.

Exam trap

The trap here is that candidates often assume reconciliation rules (Option C) prevent duplicates, but duplicates are actually created during the identification phase, before reconciliation is ever applied.

How to eliminate wrong answers

Option A is wrong because a class hierarchy conflict would cause issues with CI classification or inheritance, not duplicate records for the same device. Option B is wrong because the discovery source setting does not cause duplicates; multiple sources are handled by identification and reconciliation rules. Option C is wrong because manual reconciliation mode affects how conflicts are resolved, not the creation of duplicate records; duplicates are created during identification, before reconciliation is applied.

Full explanation →

236

MCQmedium

A company's CMDB has been populated with configuration items (CIs) from various discovery sources. However, when querying the CMDB for all Windows servers, the result set is missing some servers that are known to exist. The administrator has verified that the servers are discovered and appear in the discovery logs. What is the most likely cause of this issue?

A.The missing servers are duplicates and have been merged into other CIs.

B.The missing servers have a status of 'Retired' in the CMDB.

C.The user running the query does not have the cmdb_read role.

D.The missing servers are classified under a different CMDB class than the one being queried.

AnswerD

Class hierarchy and classification determine query results.

Why this answer

The CMDB organizes CIs into a hierarchical class structure (e.g., cmdb_ci_server, cmdb_ci_win_server). If a Windows server is classified under a different parent class (e.g., cmdb_ci_linux_server due to misclassification or a custom class), a query filtering specifically on the Windows server class will exclude it. Discovery populates the CI with the correct class based on the identification and classification rules, but manual reclassification or an incorrect identification rule can place the CI in a different class, making it invisible to class-specific queries.

Exam trap

The trap here is that candidates assume discovery success guarantees the CI is in the expected class, but ServiceNow's CMDB class hierarchy and classification rules can place discovered CIs into a different class, making them invisible to class-specific queries even though they exist in the CMDB.

How to eliminate wrong answers

Option A is wrong because duplicate CIs are handled by identification and reconciliation rules, which may merge or update CIs, but the merged CI retains the original CI's class and is still queryable; it would not be missing from the result set. Option B is wrong because a 'Retired' status does not remove the CI from the CMDB; it remains in the table and is still returned by queries unless the query explicitly filters on status. Option C is wrong because the cmdb_read role grants read access to the CMDB tables; if the user lacked this role, they would receive a security error or see no results at all, not a partial set of missing servers.

Full explanation →

237

MCQeasy

A company needs to import user records from a CSV file into the User [sys_user] table. The file contains a 'department' column that should map to the 'department' field in ServiceNow. However, the department values in the CSV are full names (e.g., 'Human Resources'), but the department field in ServiceNow uses a reference to the Department [cmn_department] table. What is the best practice for handling this import?

A.Use a before business rule on the User table to convert the department name after the record is inserted.

B.Create a transform map that maps the source field to the target field, and use a field mapping script to convert the department name to the correct sys_id.

C.Use the Import Set Row API to programmatically map the values during import.

D.Manually edit the CSV file to replace department names with the corresponding sys_id values.

AnswerB

This is the standard method to handle reference field mapping during import.

Why this answer

Import Set Rows are processed through transform maps, which allow field mapping scripts to convert source values (like 'Human Resources') into the corresponding sys_id in the Department [cmn_department] table. This is the standard, supported approach for handling reference field lookups during imports, ensuring data integrity without manual intervention or post-insert processing.

Exam trap

The trap here is that candidates often confuse a before business rule (which runs after insert) with a transform script (which runs during import), leading them to choose option A instead of recognizing that transform maps are the correct declarative tool for reference field lookups.

How to eliminate wrong answers

Option A is wrong because a before business rule runs after the record is inserted, meaning the reference field would already have failed validation or stored an incorrect value; it's too late to convert the department name to a sys_id. Option C is wrong because the Import Set Row API is used for programmatic row-level operations, not for defining reusable field-level mappings or lookups; it bypasses the transform map's declarative capabilities. Option D is wrong because manually editing the CSV to include sys_id values is error-prone, not scalable, and violates the principle of automated, repeatable imports; ServiceNow provides transform maps precisely to avoid this.

Full explanation →

238

MCQmedium

A manager wants a report that shows the number of incidents opened each day for the past 30 days, broken down by category. They want to see the data as a line chart with multiple lines (one per category). What report type and options should the admin select?

A.Pie chart with a filter for the last 30 days and a breakdown by category.

B.List report with a 'Count' aggregation grouped by 'Opened' and 'Category'.

C.Line chart with 'Group by' set to 'Category' and 'Stacked' set to 'No'.

D.Bar chart with 'Group by' set to 'Category' and 'Stacked' set to 'Yes'.

AnswerC

Line chart with multiple lines per category is the correct choice.

Why this answer

A line chart with 'Group by' set to 'Category' and 'Stacked' set to 'No' produces a multi-line chart where each line represents a distinct category, showing the number of incidents opened each day over the past 30 days. This directly meets the manager's requirement for a line chart with multiple lines, one per category, without stacking the values.

Exam trap

The trap here is that candidates often confuse 'Group by' with 'Stacked' options, mistakenly thinking that 'Stacked' set to 'Yes' is needed for multiple lines, when in fact 'Stacked' controls whether values are cumulative (stacked) or independent (separate lines), and 'Group by' is what creates the multiple series.

How to eliminate wrong answers

Option A is wrong because a pie chart cannot display trends over time as a line chart; it shows proportions at a single point in time, not daily counts over 30 days. Option B is wrong because a list report with 'Count' aggregation grouped by 'Opened' and 'Category' produces a tabular list, not a line chart, and cannot visualize the data as a line chart with multiple lines. Option D is wrong because a bar chart with 'Group by' set to 'Category' and 'Stacked' set to 'Yes' creates stacked bars, not separate lines; stacking would combine categories into a single bar per day, obscuring individual category trends.

Full explanation →

239

MCQmedium

An administrator wants to create a homepage that displays a filtered list of high-priority incidents assigned to the current user. Which widget should be used?

A.Dashboard widget with a list report

B.Content Selector widget

C.HTML widget with embedded Jelly script

D.Metric tag widget

AnswerA

List report widget can filter incidents and display them.

Why this answer

The Dashboard widget with a list report is correct because it allows an administrator to embed a filtered list report directly on a homepage. By configuring the report to filter for 'high-priority incidents' and setting the condition 'Assigned to is current user', the widget dynamically displays only the relevant records for the logged-in user, meeting the requirement without custom scripting.

Exam trap

The trap here is that candidates may confuse the Content Selector widget (which also displays lists) with the Dashboard widget, not realizing that the Content Selector is specifically for knowledge articles and CMS content, not for ad-hoc filtered table reports.

How to eliminate wrong answers

Option B is wrong because the Content Selector widget is used to display content from a knowledge base or CMS, not to show filtered list reports from tables like Incident. Option C is wrong because while an HTML widget with embedded Jelly script could technically achieve this, it is not the standard or recommended approach; ServiceNow provides the Dashboard widget with list reports as a no-code solution, and using Jelly would be unnecessarily complex and harder to maintain. Option D is wrong because the Metric tag widget is designed to display metric scores or indicators (e.g., SLAs) on a form or dashboard, not to show a filtered list of records from a table.

Full explanation →

240

MCQeasy

A system administrator receives a request to add a new field called 'Business Impact' to the 'cmdb_ci' table. Which method should be used to ensure the field is available to all CI classes?

A.Add the field to the 'cmdb_ci' table directly

B.Add the field to a child class like 'cmdb_ci_computer'

C.Use the 'Include Table' configuration to add the field

D.Create a new extension table for the field

AnswerA

This adds the field to the base table and all its descendants.

Why this answer

The 'cmdb_ci' table is the base table for all Configuration Items (CIs) in the CMDB. Adding a field directly to this table ensures it is inherited by all child CI classes (e.g., cmdb_ci_computer, cmdb_ci_server) through the table hierarchy. This is the standard method for making a field universally available across all CI types without creating redundant or inconsistent data structures.

Exam trap

The trap here is that candidates often assume adding a field to a specific child class is sufficient for all CIs, overlooking the inheritance hierarchy and the base table's role in universal field availability.

How to eliminate wrong answers

Option B is wrong because adding the field to a child class like 'cmdb_ci_computer' would only make it available to that specific class and its descendants, not to all CI classes. Option C is wrong because the 'Include Table' configuration is used to extend a table's schema by including fields from another table, not to add a new field directly to the base table. Option D is wrong because creating a new extension table would isolate the field to that table and require additional configuration to associate it with the base CI classes, defeating the purpose of universal availability.

Full explanation →

241

MCQmedium

A consultant is designing a CMDB for a large enterprise. The data from multiple discovery tools is being imported into the CMDB. Some CIs are being duplicated due to minor differences in serial numbers. Which approach best prevents duplicates without losing data integrity?

A.Set a 'unique' constraint on the Serial Number field

B.Configure a reconciliation rule to merge duplicates automatically

C.Use a data certification rule to validate serial numbers

D.Instruct the discovery teams to manually de-duplicate

AnswerA

Prevents insertion of duplicate serial numbers, enforcing uniqueness at the database level.

Why this answer

Setting a 'unique' constraint on the Serial Number field prevents duplicate CIs by enforcing that no two records can have the same serial number at the database level. This approach preserves data integrity because it blocks insertion of duplicates rather than merging or overwriting existing data, which could cause loss of attribute history or relationships.

Exam trap

The trap here is that candidates often confuse reconciliation rules (which handle existing duplicates) with prevention mechanisms, leading them to choose Option B instead of understanding that a unique constraint blocks duplicates at the database level before they can occur.

How to eliminate wrong answers

Option B is wrong because reconciliation rules merge duplicates after they are created, which can lead to data loss if attributes conflict or if relationships are incorrectly consolidated; they do not prevent duplicates at the point of import. Option C is wrong because data certification rules validate data quality (e.g., format or completeness) but do not enforce uniqueness or prevent duplicate serial numbers from being inserted. Option D is wrong because manual de-duplication is error-prone, unscalable, and does not provide a systematic, automated prevention mechanism; it also risks human error and inconsistent application across large datasets.

Full explanation →

242

Multi-Selectmedium

Which TWO conditions must be met for a catalog item to appear in the service catalog on the portal? (Choose two.)

Select 2 answers

A.The item has a workflow attached.

B.The item is in 'Published' state.

C.The item is in an active category.

D.The item has a price of 0.

E.The 'Available for' field includes the current user's roles.

AnswersB, E

Only published items appear in the service catalog.

Why this answer

A catalog item must be in the 'Published' state to be visible in the service catalog on the portal. The 'Published' state indicates that the item has been approved and is ready for end users to request. Items in 'Draft' or 'Retired' states are hidden from the portal, regardless of other configurations.

Exam trap

The trap here is that candidates often confuse the 'Active' flag on the category with the item's own state, or assume that a workflow or price is required for visibility, when in fact only the Published state and role-based availability control portal appearance.

Full explanation →

243

MCQhard

Refer to the exhibit. A catalog item has a variable 'department' (choice list with values 'IT', 'HR', 'Finance') and a variable 'cost_center' (choice list initially empty). The client script is supposed to add an option to 'cost_center' when 'department' is set to 'IT'. However, when a user selects 'IT', no new option appears. What is the most likely reason?

A.The variable 'cost_center' is not a 'Choice' variable type.

B.The script is a server-side script and cannot use 'g_form'.

C.The script needs to call 'g_form.clearOptions()' before adding options.

D.The method should be 'g_form.addOption()' with different syntax.

AnswerA

addOption only works on choice-type variables.

Why this answer

The `g_form.addOption()` method only works on variables of type 'Choice' (or similar select-type variables like 'Select Box'). If 'cost_center' is not a Choice variable, the client script cannot dynamically add options to it, and the method call silently fails or has no effect. In ServiceNow, only choice-based variable types support runtime option manipulation via client-side APIs.

Exam trap

The trap here is that candidates assume any variable with a choice list is a 'Choice' variable, but ServiceNow distinguishes between the variable type (which must be 'Choice') and the presence of choice records; the `g_form.addOption()` method only works on variables with the correct underlying type.

How to eliminate wrong answers

Option B is wrong because the script is described as a client script, and `g_form` is a client-side API available in client scripts, catalog client scripts, and UI policies; it cannot be used in server-side scripts, but here the context implies client-side execution. Option C is wrong because `g_form.clearOptions()` is not required before adding options; `g_form.addOption()` can add options to an existing list without clearing it first, and clearing is only needed if you want to replace all options. Option D is wrong because `g_form.addOption()` is the correct method name and syntax for adding an option to a choice variable in a client script; the issue is not with the method name or syntax but with the variable type not supporting dynamic options.

Full explanation →

244

Multi-Selecteasy

A ServiceNow administrator is configuring a Catalog Item to handle employee laptop requests. Which TWO of the following are valid methods to automatically populate a variable's value based on the requester's information? (Choose two.)

Select 2 answers

A.Use a Catalog Data Lookup Rule to reference the user's department.

B.Use a Catalog Client Script (onLoad) with g_form.setValue() to set the variable from the user's record.

C.Use a Flow Designer flow triggered on 'Request created' to update the variable after submission.

D.Use a Business Rule on the Catalog Item table to set the variable.

E.Use a Variable Default Value with a GlideRecord script to query the sys_user table.

AnswersB, E

Catalog Client Scripts can use g_form to set values on load based on requester info.

Why this answer

A Catalog Client Script with an onLoad event can use the g_form.setValue() method to populate a variable from the requester's user record. This script runs before the form is rendered, allowing dynamic population of fields based on the current user's sys_user data. Option E is correct because a Variable Default Value can include a GlideRecord script that queries the sys_user table to set the variable's initial value based on the requester's information, such as their department or location.

Exam trap

The trap here is that candidates often confuse Catalog Data Lookup Rules with Variable Default Values, thinking they can directly reference the requester's user record, but Data Lookup Rules require a reference field to trigger, while Variable Default Values can use GlideRecord to query sys_user directly.

Full explanation →

245

Multi-Selectmedium

Which TWO are true about Service Level Agreements (SLAs) in ServiceNow?

Select 2 answers

A.A Business Rule can be used to pause or cancel an SLA.

B.SLA definitions can specify a start condition based on a record field value.

C.SLAs are defined per user to track individual performance.

D.SLAs can only be created for the Incident table.

E.Once an SLA is breached, it is automatically deleted from the system.

AnswersA, B

Business Rules can update SLA records using the SLA API.

Why this answer

Business Rules in ServiceNow can be configured to pause or cancel an SLA based on specific conditions, such as changes in state or assignment. This is achieved by writing a Business Rule that triggers on the appropriate table (e.g., task) and uses the `stopSLA()` or `pauseSLA()` methods on the SLA record. This allows administrators to automate SLA lifecycle management without manual intervention.

Exam trap

The trap here is that candidates often assume SLAs are only for the Incident table (Option D) or that breached SLAs are deleted (Option E), but ServiceNow allows SLAs on multiple task tables and retains breached SLAs for historical analysis.

Full explanation →

246

MCQeasy

A multinational company has implemented a Service Catalog to streamline IT requests. The catalog item 'New Laptop Request' includes a workflow that routes approvals based on the cost center of the requester. Recently, several requests submitted by employees in the Finance department are stuck in 'Submitted' state without any approval activity. The workflow has a condition that checks the variable 'cost_center' and if it equals 'Finance', the approval is sent to the Finance manager. Other requests from departments like HR and Marketing proceed normally. The administrator has verified that the 'Finance' cost center value is correctly entered on the requests, the users have appropriate roles, and the approval assignments are active. What is the most likely cause of the issue?

A.The approval rule should be changed to auto-approve for Finance.

B.The workflow approval timeout is set too short and needs to be increased.

C.The catalog item should be reconfigured to not use a workflow.

D.The workflow condition that triggers the Finance approval stage is not evaluating correctly.

AnswerD

If the condition fails, the workflow may not proceed to the approval stage, leaving requests in 'Submitted'.

Why this answer

The issue is that the workflow condition checking the 'cost_center' variable for 'Finance' is not evaluating correctly, causing the approval stage to be skipped or not triggered. Since other departments work fine, the workflow logic itself is likely flawed—perhaps due to a data type mismatch (e.g., comparing a string to a different type) or a typo in the condition script. The administrator has verified data entry, roles, and approval assignments, so the root cause is the condition logic in the workflow.

Exam trap

ServiceNow often tests the misconception that approval assignment or user roles are the cause, when the real issue is a logic error in the workflow condition that prevents the approval stage from being reached.

How to eliminate wrong answers

Option A is wrong because auto-approving Finance requests would bypass the required manager approval, which is not a fix for a broken condition; it changes business process. Option B is wrong because a timeout would cause requests to move to a 'Timed Out' or 'Cancelled' state, not remain stuck in 'Submitted' without any approval activity. Option C is wrong because removing the workflow would eliminate all routing logic, including the working approvals for HR and Marketing, and does not address the specific condition failure.

Full explanation →

247

Multi-Selecthard

Which THREE of the following are valid workflow activities in a Service Catalog workflow? (Choose three.)

Select 3 answers

A.Approval - Dynamic

B.Scrum Task

C.Run Script

D.Wait for Condition

E.Approval - User

AnswersC, D, E

Run Script executes server-side code.

Why this answer

Run Script is a valid workflow activity in ServiceNow Service Catalog workflows. It allows you to execute a script (JavaScript) during the workflow, enabling custom logic such as updating records, calling APIs, or performing calculations. This activity is part of the standard workflow activities available in the Workflow Editor.

Exam trap

The trap here is that candidates confuse 'Approval - Dynamic' with a real activity name, but ServiceNow only has 'Approval - User' and 'Approval - Group' as standard approval activities, and 'Dynamic' refers to how the approver is determined, not the activity name.

Full explanation →

248

Multi-Selecthard

Which THREE actions can be performed using UI policies? (Choose three.)

Select 3 answers

A.Set a field's default value

B.Make a field read-only

C.Make a field mandatory

D.Create a new field on the form

E.Hide a field

AnswersB, C, E

UI policies can set read-only.

Why this answer

UI policies can set the 'read-only' attribute on a field, preventing users from modifying its value based on conditions. This is a core function of UI policies, which control field behavior on a form without requiring server-side scripting.

Exam trap

The trap here is that candidates often confuse UI policies with Data Policies or client scripts, assuming UI policies can set default values or create fields, but UI policies only modify existing field attributes on the client side.

Full explanation →

249

Multi-Selectmedium

A business rule is configured to run on 'after' update. Which TWO of the following conditions would cause the rule to execute? (Select two.)

Select 2 answers

A.The condition script returns false.

B.The condition checkbox is unchecked (no condition).

C.The condition checkbox is checked but script returns false.

D.The condition script returns true.

E.The table is not the specified table.

AnswersB, D

Unchecked condition means rule runs unconditionally.

Why this answer

When the condition checkbox is unchecked, the business rule has no condition script, so it always executes on the specified event (after update). Option D is correct because a condition script that returns true explicitly tells the rule to run. The 'after' update timing means the rule runs after the database write, but the condition still controls whether execution occurs.

Exam trap

The trap here is that candidates often think an unchecked condition checkbox means the rule never runs, but it actually means the rule always runs because there is no condition to evaluate.

Full explanation →

250

MCQmedium

At the current time (09:45), what is the total pause duration for this SLA instance?

A.15 minutes

B.0 minutes

C.45 minutes

D.30 minutes

AnswerA

The first pause lasted 15 minutes; second pause just started.

Why this answer

The SLA instance was paused at 09:30 and resumed at 09:45, resulting in a total pause duration of 15 minutes. In ServiceNow, SLA pause duration is calculated as the cumulative time between pause and resume actions, excluding the paused time from the SLA clock.

Exam trap

The trap here is that candidates often misinterpret the pause duration as the time remaining on the SLA or confuse the pause start time with the SLA start time, leading them to select 30 or 45 minutes instead of calculating the exact interval between pause and resume.

How to eliminate wrong answers

Option B is wrong because the SLA was paused at 09:30, so the pause duration cannot be 0 minutes; a pause event occurred. Option C is wrong because 45 minutes would imply the pause started at 09:00 and ended at 09:45, but the pause began at 09:30, not 09:00. Option D is wrong because 30 minutes would require the pause to last from 09:15 to 09:45 or 09:30 to 10:00, but the resume time is 09:45, making 15 minutes the correct duration.

Full explanation →

251

MCQmedium

During a workflow, a catalog item's quantity variable 'qty' must be validated to be between 1 and 10. If the value is outside this range, the request should be rejected with a message. Which approach should the administrator take?

A.Add a 'Before Order' script in the catalog item that validates and aborts if invalid.

B.Create a Catalog Client Script with 'onChange' event to validate and show error.

C.Create a UI Policy to set the variable as mandatory and add a condition.

D.Set the variable's 'Type' to 'Integer' and add a 'Min' and 'Max' attribute.

AnswerA

Before Order scripts run on submit and can abort the request with an error message.

Why this answer

The 'Before Order' script runs server-side when the user clicks the 'Order Now' button, allowing the administrator to validate the 'qty' variable and use `gs.addErrorMessage()` followed by `current.abortAction()` to reject the request with a message. This approach ensures the validation occurs at the point of submission, before the request is processed, and provides immediate feedback to the user.

Exam trap

The trap here is that candidates often confuse client-side validation (like UI Policies or Client Scripts) with server-side enforcement, assuming that showing an error message on the client side is sufficient to reject the request, but only a server-side script like 'Before Order' can truly abort the transaction.

How to eliminate wrong answers

Option B is wrong because a Catalog Client Script with 'onChange' event runs client-side and can show an error message but cannot abort the order submission; it only reacts to field changes, not the final submission. Option C is wrong because a UI Policy can set a variable as mandatory or show/hide fields based on conditions, but it cannot perform custom validation logic like checking a numeric range or aborting the request. Option D is wrong because setting the variable's 'Type' to 'Integer' with 'Min' and 'Max' attributes only enforces the range on the client side for basic input validation, but it does not provide a mechanism to reject the request with a custom message; it simply prevents the user from entering out-of-range values.

Full explanation →

252

MCQhard

A catalog item uses a workflow with a 'Run Script' activity that contains a script to update a custom table. The script works correctly when executed manually in the Scripts Background, but fails when invoked by the workflow. What is the most likely reason?

A.The workflow runs with a different security context, causing permission issues

B.The workflow script references a variable that is undefined in that context

C.The script uses incorrect GlideRecord API methods

D.The workflow is in draft mode

AnswerA

Background scripts run as the user executing them, while workflow scripts may run as system or a designated user with different rights.

Why this answer

The most likely reason is that the workflow runs under the security context of the workflow engine (typically the 'workflow' user or the system user), not the current user's context. When the script is executed manually in Scripts Background, it runs with the full privileges of the admin user, which may include write access to the custom table. In contrast, the workflow's Run Script activity may lack the necessary ACL permissions (e.g., write or create) on the custom table, causing the GlideRecord update to fail silently or throw an error.

Exam trap

ServiceNow often tests the misconception that a script's behavior is identical in all execution contexts, but the trap here is that candidates overlook the security context difference between Scripts Background (admin privileges) and workflow execution (workflow user privileges), leading them to choose a generic scripting error like undefined variables or API misuse.

How to eliminate wrong answers

Option B is wrong because if the script referenced an undefined variable, it would fail in both Scripts Background and the workflow, not just the workflow; the question states the script works manually. Option C is wrong because incorrect GlideRecord API methods would cause failures in both contexts, not selectively; the script works manually, so the API usage is valid. Option D is wrong because a workflow in draft mode cannot be executed at all; the question implies the workflow is running (it fails during execution), so draft mode is irrelevant.

Full explanation →

253

MCQmedium

After applying a new theme, some modules are missing from the application navigator. What is the most likely cause?

A.Modules are inactive

B.Theme overrides the navigation

C.User roles changed

D.Cache needs refresh

AnswerA

Inactive modules are hidden from navigation. The theme change may have triggered a review, but inactivation is the direct cause.

Why this answer

When a new theme is applied in ServiceNow, the theme controls the visual styling but does not control which modules appear in the application navigator. Modules are missing because they are set to inactive, which hides them from the navigator regardless of the active theme. The most likely cause is that the modules themselves have been deactivated, often due to a system property or upgrade that changed their active state.

Exam trap

The trap here is that candidates confuse the visual impact of a theme (which changes colors and layout) with the functional visibility of modules, assuming a theme can hide or show modules, when in fact only module activation status or role-based ACLs control that.

How to eliminate wrong answers

Option B is wrong because themes in ServiceOnly affect the look and feel (colors, fonts, logos) and do not override the navigation structure or module visibility. Option C is wrong because user roles control access to modules via ACLs, but if a module is inactive, it is hidden from all users regardless of their roles. Option D is wrong because a cache refresh (e.g., clearing the browser cache or running a system cache flush) would not restore inactive modules; cache issues typically cause display glitches or outdated styling, not missing modules.

Full explanation →

254

Drag & Dropmedium

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

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

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

Creating a new user in ServiceNow requires navigating to the Users module, clicking New to open a blank record, entering mandatory fields like User ID and Email, and finally submitting the form. Skipping or reordering steps leads to errors or missing fields.

Full explanation →

255

MCQeasy

A service desk manager wants to provide a self-service option for employees to reset their own passwords. The company is using ServiceNow's Virtual Agent. The administrator needs to configure the Virtual Agent to handle password reset requests. Which component should be used to design the conversation flow for password reset?

A.Scripted REST API

B.Conversation Flow Application

C.Topic Block

D.Flow Designer

AnswerC

Topic blocks define the conversation flow in Virtual Agent.

Why this answer

Topic Blocks are the correct component for designing conversation flows in ServiceNow Virtual Agent. They allow administrators to define the dialog, prompts, and logic for handling specific user intents like password reset, without requiring custom scripting. This is the native, low-code approach for building Virtual Agent conversations.

Exam trap

The trap here is that candidates confuse Flow Designer (used for backend automation) with Topic Blocks (used for conversational design), leading them to select Flow Designer instead of the correct component for Virtual Agent conversations.

How to eliminate wrong answers

Option A is wrong because Scripted REST APIs are used for external integrations and custom endpoints, not for designing conversation flows within Virtual Agent. Option B is wrong because 'Conversation Flow Application' is not a real ServiceNow component; the correct term is Topic Block or Flow Designer for flows. Option D is wrong because Flow Designer is used for creating workflows and automation outside of Virtual Agent, not for designing the conversational dialog and branching logic specific to Virtual Agent topics.

Full explanation →

256

Multi-Selectmedium

Which TWO are benefits of using Service Catalog with Record Producers?

Select 2 answers

A.No need to design a flow

B.Support for order guides

C.Ability to create records in any table

D.Ability to attach workflows

E.Automatic variable creation

AnswersC, D

Record Producers can be configured to populate any table.

Why this answer

Record Producers can be configured to create records in any table, not just the task or incident tables. This allows organizations to automate record creation across custom tables, extending the flexibility of Service Catalog beyond standard ITSM processes.

Exam trap

The trap here is that candidates confuse Record Producers with simple form submissions, assuming they automatically handle all table fields without manual mapping, or they mistakenly think Record Producers inherently support order guides, which is a separate catalog feature.

Full explanation →

257

MCQmedium

A user reports that when they submit a catalog item from the Service Portal, they do not receive an email notification confirming the request. The notification is configured on the Request table. What is the likely issue?

A.The notification is set to 'Send me a copy' only

B.The user does not have the 'Receive email' role

C.The notification lacks a condition

D.The notification is not active for the specific catalog item

AnswerD

Each catalog item has a 'Send email receipt' checkbox that must be checked for the notification to be sent.

Why this answer

Notifications in ServiceNow are evaluated against the table they are configured on, but they also require the 'Active' checkbox to be enabled for the specific catalog item. If the notification is not active for that catalog item, it will not trigger when the request is submitted, even if the notification is configured on the Request table. The user's report indicates the notification exists but is not firing, pointing to a per-item activation issue.

Exam trap

The trap here is that candidates often assume a notification configured on the Request table will always fire for all requests, overlooking the per-catalog-item activation setting that can disable it for specific items.

How to eliminate wrong answers

Option A is wrong because 'Send me a copy' only sends a copy to the user who triggered the notification, but it does not prevent the notification from being sent; it merely adds an additional recipient. Option B is wrong because the 'Receive email' role is not required for a user to receive notifications; notifications are sent based on the notification configuration and the user's email address in their user record, not a specific role. Option C is wrong because a notification without a condition will fire for every record on the table, so the lack of a condition would actually cause the notification to be sent, not prevent it.

Full explanation →

258

MCQhard

A performance issue is reported on the Change Request list view: it takes several seconds to load. The list has 5000 records and uses several calculated fields. Which optimization should be applied first?

A.Add a group by condition on the list view

B.Set the list control to 'Auto' to reduce data threshold

C.Increase the 'glide.ui.list.threshold' system property to 10000

D.Create a new list view that includes only essential columns

AnswerD

Fewer columns reduces data load and improves performance.

Why this answer

Reducing the number of columns in a list view minimizes the data retrieved per row, directly addressing the performance bottleneck caused by calculated fields. Calculated fields are evaluated for every row on every load, so removing unnecessary columns reduces server-side computation and database query overhead. This is the most effective first optimization as it targets the root cause without increasing data volume or altering system thresholds.

Exam trap

The trap here is that candidates often assume increasing the list threshold or using aggregation will solve performance issues, but they fail to recognize that calculated fields are the primary performance drain and that reducing columns is the simplest and most effective first step.

How to eliminate wrong answers

Option A is wrong because adding a group by condition does not reduce the number of records or columns; it only aggregates data, which can actually increase processing overhead on a list view with calculated fields. Option B is wrong because setting the list control to 'Auto' adjusts the pagination behavior but does not reduce the number of records loaded or the evaluation of calculated fields; it merely changes how the list is displayed. Option C is wrong because increasing 'glide.ui.list.threshold' to 10000 would allow more records to load at once, worsening performance by forcing the system to evaluate calculated fields for even more rows.

Full explanation →

259

MCQhard

You are a ServiceNow administrator for a large enterprise. The company has a custom application that uses a table 'u_asset_tracking' to track IT assets. The table has a before insert business rule that sets the 'u_assigned_to' field to the current user if the field is empty. Recently, the security team reported that some users are able to view asset records that they should not see. After investigation, you find that the 'u_asset_tracking' table has no ACLs defined, and the default table ACL allows read access to all authenticated users. The business rule is working correctly. You need to restrict read access so that users can only see records where 'u_assigned_to' is themselves or where they are in the same 'u_department' as the record's 'u_department'. You must ensure that the solution does not affect other tables. Which approach should you take?

A.Modify the default table ACL for the 'u_asset_tracking' table to require the 'asset_user' role.

B.Create a new ACL for the 'u_asset_tracking' table with type 'record', operation 'read', condition script 'current.u_assigned_to == gs.getUserID() || current.u_department == gs.getUser().getDepartment()', and set order to 0. Ensure 'Requires role' is unchecked.

C.Add a business rule to restrict read access by deleting records from the glide record set.

D.Create a new ACL for the 'u_asset_tracking' table with type 'record', operation 'read', condition script 'current.u_assigned_to == gs.getUserID()', and require the 'asset_user' role.

AnswerB

This ACL grants read access only to matching records and, with order 0, takes precedence over the default ACL.

Why this answer

It creates a record-level ACL with a condition script that enforces row-level security: users can only read records where they are the assigned user or share the same department. The order of 0 ensures this ACL is evaluated before the default table ACL, and leaving 'Requires role' unchecked allows the condition to grant access without requiring a specific role, thus restricting read access based solely on the condition.

Exam trap

The trap here is that candidates often think modifying the default table ACL or adding a role requirement is sufficient, but they miss that record-level ACLs with condition scripts are the correct way to implement row-level security without affecting other tables.

How to eliminate wrong answers

Option A is wrong because modifying the default table ACL to require a role would apply to all tables, not just 'u_asset_tracking', and would not enforce the row-level condition (assigned to or same department). Option C is wrong because a business rule cannot restrict read access; business rules run on server-side operations like insert, update, delete, or query, but they cannot prevent a user from viewing records in a list or form (ACLs control read access). Option D is wrong because it only checks if the user is the assigned user, ignoring the department condition, and requiring the 'asset_user' role would block users without that role even if they meet the condition, which is not the requirement.

Full explanation →

260

MCQeasy

Which UI element allows an administrator to add a new section to an existing form and populate it with fields?

A.Access Control Rule

B.Form Layout configuration

C.UI Policy

D.Dictionary Entry

AnswerB

Form Layout lets you add sections and arrange fields.

Why this answer

The Form Layout configuration is the correct UI element because it allows administrators to define the layout of fields on a form, including adding new sections and populating them with fields. This is done by dragging and dropping fields into the desired section within the Form Layout configuration page, which directly controls the form's structure.

Exam trap

The trap here is that candidates often confuse the Form Layout configuration with Dictionary Entries, thinking field properties control layout, or with UI Policies, assuming client-side rules can restructure forms, when in fact only the Form Layout directly manages sections and field placement.

How to eliminate wrong answers

Option A is wrong because Access Control Rules (ACLs) control user permissions to read, write, create, or delete records, not the layout or addition of sections to forms. Option C is wrong because UI Policies define client-side behavior (like making fields mandatory or visible) based on conditions, but they do not add sections or fields to a form's layout. Option D is wrong because Dictionary Entries define the properties of individual fields (such as type, length, and reference), but they do not manage the structural layout of sections on a form.

Full explanation →

261

Drag & Dropmedium

Drag and drop the steps to configure an inbound email action in ServiceNow into the correct order.

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

Steps

Order

1Step 1

2Step 2

3Step 3

4Step 4

Why this order

The correct sequence for configuring an inbound email action in ServiceNow is to first create the action record, then define the conditions (such as the table and condition script), then write the action script that processes incoming emails, and finally save and activate the action. This order ensures that all necessary fields are properly set and the action works as intended.

Full explanation →

262

Multi-Selecteasy

A ServiceNow administrator needs to create a service catalog item that requires the user to select a configuration item (CI) that will be affected by the requested service. The catalog item should also send an email notification to the CI's assigned support group when the request is submitted. Which TWO actions must the administrator take?

Select 2 answers

A.Use a variable of type 'CI Selector' to allow selection of a CI.

B.Create a business rule or flow that adds the CI’s assigned support group to the watch list of the CI record upon catalog item submission.

C.Add a variable of type 'Reference' pointing to the Configuration Item [cmdb_ci] table.

D.Set up an email notification on the catalog item itself to send when the request is submitted.

E.Configure the catalog item to automatically populate the 'Assigned group' field on the CI record.

AnswersB, C

Correct: Adding the support group to the watch list enables email notifications to them.

Why this answer

Adding the CI's assigned support group to the watch list of the CI record ensures that the group receives email notifications when the request is submitted. This leverages the platform's notification engine, which sends emails to users and groups in the watch list of the record. Option C is also correct because a Reference variable pointing to the cmdb_ci table allows the user to select a specific CI from the CMDB, which is required for the catalog item to know which CI is affected.

Exam trap

The trap here is that candidates often confuse the 'CI Selector' variable type (which does not exist) with the correct 'Reference' variable type, or they incorrectly think email notifications can be configured directly on a catalog item rather than on the resulting request record.

Full explanation →

263

MCQmedium

An administrator needs to create a workflow that sends an email to the approver when a request is approved, and sends a different email when the request is rejected. What is the appropriate workflow component to use for this branching logic?

A.Use a 'Timer' activity to delay and then check state.

B.Use a 'Begin Approval' activity and then a 'Decision' activity.

C.Use an 'Approval' activity with two 'Outcome' branches.

D.Use a 'Condition' activity to check the approval state.

AnswerC

Approval activity provides outcomes for approved and rejected.

Why this answer

The 'Approval' activity in ServiceNow workflows inherently supports branching via 'Outcome' branches. When an approval is processed (approved or rejected), the workflow engine evaluates the outcome and follows the corresponding branch, allowing you to attach different email notifications to each path without additional logic activities.

Exam trap

The trap here is that candidates often overcomplicate the solution by adding a separate 'Decision' or 'Condition' activity, not realizing that the 'Approval' activity itself provides native outcome-based branching for approved and rejected states.

How to eliminate wrong answers

Option A is wrong because a 'Timer' activity is used to introduce a delay or schedule a time-based event, not to evaluate approval outcomes or implement branching logic. Option B is wrong because 'Begin Approval' is not a valid workflow activity; the correct activity is 'Approval', and adding a separate 'Decision' activity is redundant since the 'Approval' activity already provides outcome-based branching. Option D is wrong because a 'Condition' activity checks a condition (e.g., field value) but does not directly capture the result of an approval process; using it would require manually setting a state variable, which is less efficient and error-prone compared to the built-in outcome branches of the 'Approval' activity.

Full explanation →

264

MCQmedium

An administrator wants to enforce that when the 'state' field of an incident is set to 'Resolved', the 'resolution_notes' field must be filled. Which approach should be used?

A.Create a UI Policy that sets the 'resolution_notes' field to mandatory when state is 'Resolved'

B.Create a data policy with a condition on the state field

C.Create a data lookup condition on the incident table

D.Create a business rule that checks the condition and shows an error message

AnswerA

UI Policies are client-side and can make fields mandatory based on conditions.

Why this answer

UI Policies run on the client side and can dynamically set field attributes like 'mandatory' based on conditions evaluated in real time as the user interacts with the form. When the 'state' field changes to 'Resolved', the UI Policy can immediately make the 'resolution_notes' field mandatory, ensuring the user cannot submit the form without filling it. This approach provides instant visual feedback and prevents submission without requiring a server round-trip.

Exam trap

The trap here is that candidates often confuse Data Policies with UI Policies, thinking Data Policies can enforce client-side mandatory behavior, but Data Policies only enforce rules on the server side during record inserts/updates and do not affect the user's ability to submit the form.

How to eliminate wrong answers

Option B is wrong because Data Policies enforce field-level constraints (like mandatory or read-only) on the server side during database operations, but they do not run on the client side and cannot provide real-time form behavior or prevent submission before the record is saved. Option C is wrong because a data lookup condition is used to validate or populate fields based on a lookup to another table, not to enforce mandatory field requirements based on a field value change. Option D is wrong because a Business Rule runs on the server side after the record is saved (or before, but still server-side), so it cannot prevent the user from submitting the form; it can only show an error message after submission, which is a poor user experience and does not enforce the requirement at the point of data entry.

Full explanation →

265

MCQeasy

A company wants to collect the same set of user details (name, email, department) in multiple catalog items. What is the best practice to achieve this?

A.Create a single catalog item with all variables and clone it for each item.

B.Create a variable set with the required variables and add it to each catalog item.

C.Use UI policies to display the same fields on multiple items.

D.Configure the variables on the 'sc_cat_item' table and reference them.

AnswerB

Variable sets promote reuse and central management.

Why this answer

Variable sets in ServiceNow allow you to define a reusable group of variables (e.g., name, email, department) that can be added to multiple catalog items. This ensures consistency, reduces duplication, and simplifies maintenance because any update to the variable set automatically propagates to all items that use it. Cloning items (Option A) would create separate copies of the variables, leading to maintenance overhead and potential drift.

Exam trap

The trap here is that candidates confuse UI policies (which control field behavior) with variable sets (which define the fields themselves), leading them to choose Option C because they think 'display the same fields' is a UI policy function, when in fact UI policies cannot create or replicate variable definitions across items.

How to eliminate wrong answers

Option A is wrong because cloning a catalog item creates independent copies of all variables; any future change would need to be applied manually to each clone, defeating the purpose of reuse and increasing administrative burden. Option C is wrong because UI policies control the visibility, readability, or mandatory status of fields on a form, but they do not define or store the variables themselves—they cannot create the same set of fields across multiple items. Option D is wrong because the 'sc_cat_item' table stores catalog item records, not variable definitions; variables are stored in the 'sc_item_option' and related tables, and referencing them directly on the table would not provide a reusable, structured way to add the same fields to multiple items.

Full explanation →

266

MCQeasy

A form has a field with a default value that is automatically populated when a new record is created. The administrator wants to change this default value. Where should the administrator set the new default?

A.Business Rule

B.Dictionary entry for the field

C.UI Policy

D.Client Script

AnswerB

The dictionary entry has a 'Default value' field that populates automatically on new records.

Why this answer

The default value for a field is stored in the dictionary entry for that field. Changing the default value in the dictionary entry ensures that all new records created after the change will use the new default. This is the correct and intended method for setting field defaults in ServiceNow.

Exam trap

The trap here is that candidates often confuse the purpose of UI Policies or Client Scripts with setting default values, but the dictionary entry is the only place where a true field-level default is stored and applied at record creation.

How to eliminate wrong answers

Option A is wrong because Business Rules run on the server side after a record is saved or queried, and they are not designed to set default values for new records before the form loads. Option C is wrong because UI Policies control field visibility, mandatory status, and read-only state based on conditions, but they do not set default values for fields. Option D is wrong because Client Scripts run in the browser and can set field values on the client side, but they are not the standard or recommended way to set a default value that should be applied automatically when a new record is created; the dictionary entry is the authoritative source for defaults.

Full explanation →

267

Matchingmedium

Match each ServiceNow update set state to its meaning.

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

Concepts

Matches

Update set is being worked on

All changes have been captured and are ready to commit

Update set has been applied to the target instance

Update set will not be processed

Changes are reviewed before committing

Why these pairings

Update set states track progress: Draft (building), Complete (ready), Testing (validating), Committed (applied). Common confusions involve mixing Committed with Draft or Testing with Complete.

Full explanation →

268

MCQhard

A workflow on a catalog item has a 'Set Values' activity that sets the variable 'state' to 'approved'. The workflow then proceeds to a 'Task' activity. However, the task is never created. The log shows the workflow completed successfully. What is a possible reason?

A.The condition on the 'Task' activity evaluated to false

B.The 'Set Values' activity failed silently

C.The catalog item's 'Run workflow' flag is unchecked

D.The workflow is set to run asynchronously and the task is delayed

AnswerA

The Task activity's condition determines whether the task is created. If false, no task is created.

Why this answer

The 'Task' activity in a ServiceNow workflow has a condition property that must evaluate to true for the task to be created. If the condition evaluates to false, the workflow engine skips the activity entirely and continues to the next step, logging the workflow as completed successfully without creating the task. This matches the symptom where the 'Set Values' activity runs (setting state to 'approved') but no task appears.

Exam trap

The trap here is that candidates assume a 'Set Values' activity always leads to the next activity executing, but they overlook that the 'Task' activity itself has a condition that can prevent its execution even when the workflow completes successfully.

How to eliminate wrong answers

Option B is wrong because if the 'Set Values' activity failed silently, the workflow would typically log an error or the state variable would not be set to 'approved', contradicting the given that the workflow completed successfully. Option C is wrong because the 'Run workflow' flag on a catalog item controls whether the workflow triggers at all when the item is requested; if it were unchecked, the workflow would never start, but the log shows it completed. Option D is wrong because asynchronous execution does not prevent task creation; it only means the workflow runs in the background, but the task would still be created once the workflow processes that activity.

Full explanation →

269

MCQmedium

A consultant is designing the CMDB for a large enterprise. The company wants to track relationships between business services, applications, and infrastructure components. Which relationship model should be used to represent that a business service depends on an application, which in turn depends on a server?

A.Dependency relationship (structural)

B.Membership relationship

C.Ownership relationship

D.Connectivity relationship

AnswerA

Structural dependency is the correct type for service-dependency modeling.

Why this answer

A dependency relationship (structural) is the correct model because it explicitly captures the directional 'depends on' nature of the chain: a business service relies on an application, which in turn relies on a server. In ServiceNow CMDB, structural dependency relationships (e.g., 'Depends on' or 'Used by') are designed to represent these hierarchical, transitive dependencies between CIs, enabling impact analysis and root cause mapping.

Exam trap

The trap is that candidates confuse 'dependency' with 'connectivity' in ServiceNow, because both involve links between CIs, but connectivity only describes physical or logical network links without the directional 'depends on' semantics required for service impact chains in ServiceNow.

How to eliminate wrong answers

Option B is wrong because a membership relationship (e.g., 'Member of' or 'Contains') groups CIs into a logical collection (like a cluster or a business service group) but does not express directional dependency or transitive chaining between individual CIs. Option C is wrong because an ownership relationship (e.g., 'Owned by') defines administrative or financial responsibility for a CI, not technical dependency or service impact flow. Option D is wrong because a connectivity relationship (e.g., 'Connects to' or 'Communicates with') models network or physical links between CIs (like a server connected to a switch) but lacks the directional 'depends on' semantics needed to represent service-to-application-to-infrastructure chains.

Full explanation →

270

MCQmedium

Refer to the exhibit. A user with the itil role can read incidents only if their department matches the property 'dept_hr_id'. What happens if the script is removed?

A.No users can read incidents.

B.All itil users can read incidents.

C.All users can read incidents.

D.Only itil users whose department matches can read incidents.

AnswerB

Correct; the condition alone grants read to itil role.

Why this answer

The script in the ACL condition enforces the department match requirement. Removing the script removes that condition, leaving only the 'itil' role requirement. Since the ACL still requires the 'itil' role, all users with that role can read all incidents, regardless of department.

Exam trap

The exam often tests the misconception that removing a condition from an ACL removes all restrictions, when in fact only that specific condition is removed and other conditions (like role requirement) still apply.

How to eliminate wrong answers

Option A is wrong because the ACL still grants read access to users with the 'itil' role; removing the script does not block all users. Option C is wrong because the ACL still requires the 'itil' role, so users without that role cannot read incidents. Option D is wrong because it describes the behavior when the script is present, not when it is removed.

Full explanation →

271

MCQeasy

Which role is required to create a report in the Reporting module?

A.admin

B.report_user

C.report_admin

D.report_creator

AnswerC

This role provides full control over reports.

Why this answer

The report_admin role is required to create reports in the Reporting module because it grants full administrative permissions over reports, including creation, editing, and deletion. The report_user role only allows viewing and running existing reports, not creating new ones.

Exam trap

ServiceNow often tests the distinction between report_user and report_admin, where candidates mistakenly assume that report_user can create reports because it allows running them, but creation requires the higher-privileged report_admin role.

How to eliminate wrong answers

Option A is wrong because the admin role is a global administrator role that provides full system access, but it is not specifically required for creating reports; the report_admin role is the designated role for report creation. Option B is wrong because the report_user role only permits viewing and executing existing reports, not creating new ones. Option D is wrong because report_creator is not a valid role in ServiceNow; the correct role for creating reports is report_admin.

Full explanation →

272

MCQeasy

A company wants to restrict access to CI records based on the business service they belong to. What feature should they use?

A.ACLs on cmdb_ci table

B.CMDB Application Access Control

C.CMDB Data Segmentation

D.Condition-based ACLs

AnswerC

Data Segmentation allows record-level access based on defined conditions.

Why this answer

CMDB Data Segmentation (option C) is the correct feature because it allows administrators to restrict access to CI records based on the business service they belong to, using a segmentation rule that filters CIs by their 'business_service' field. This is specifically designed for multi-tenant or service-based access control in the CMDB, ensuring users only see CIs associated with their assigned business services.

Exam trap

The trap here is that candidates confuse CMDB Data Segmentation with standard ACLs or condition-based ACLs, not realizing that Data Segmentation is a purpose-built feature for business service-based CI filtering, whereas ACLs require more manual and less maintainable configuration.

How to eliminate wrong answers

Option A is wrong because ACLs on the cmdb_ci table apply globally to all CI records without the ability to dynamically filter by business service; they would require complex condition scripts for each service, which is not scalable. Option B is wrong because CMDB Application Access Control is a legacy feature that controls access to the CMDB application module itself, not to individual CI records based on business service. Option D is wrong because condition-based ACLs, while powerful, are a general ACL type that can filter records, but they are not the dedicated, out-of-box feature designed specifically for business service-based CI segmentation; CMDB Data Segmentation provides a simpler, declarative approach without custom scripting.

Full explanation →

273

Multi-Selectmedium

A ServiceNow administrator notices that the CMDB contains duplicate CI records for the same server. The duplicates were created by different discovery sources. Which TWO actions should the administrator take to resolve this issue and prevent future duplicates? (Choose two.)

Select 2 answers

A.Use the 'Reconcile' operation in the CMDB Workspace to manually merge the duplicates.

B.Run the 'Remove Duplicate CIs' scheduled job with the 'Delete' flag enabled.

C.Set the 'Identification Engine' to automatically merge duplicate CIs based on serial number.

D.Update the discovery source rules to exclude the duplicate server from future discovery.

E.Configure the CI Class Manager to require a unique combination of serial number and model ID.

AnswersA, E

The Reconcile operation allows administrators to manually merge duplicate CI records, resolving the immediate issue.

Why this answer

The 'Reconcile' operation in the CMDB Workspace allows an administrator to manually review and merge duplicate CI records, which is necessary when duplicates are created by different discovery sources and automatic rules cannot resolve the conflict. This action directly resolves the existing duplicate records by consolidating them into a single authoritative CI.

Exam trap

The trap here is that candidates often confuse the 'Remove Duplicate CIs' scheduled job (which deletes duplicates automatically) with the 'Reconcile' operation (which merges them manually), leading to the misconception that automatic deletion is a safe and complete solution when it can cause data loss.

Full explanation →

274

MCQmedium

A system administrator has created a UI Policy to make several fields mandatory on the incident form when the 'Category' field equals 'Software'. The policy works correctly when creating a new incident: if the user selects 'Software', the fields become mandatory. However, when viewing an existing incident and changing the category to 'Software', the fields do not become mandatory. The administrator verifies that the condition is correctly set to 'Category equals Software' and the action sets mandatory true on the target fields. The UI Policy is active and the order is not relevant. What is the most likely reason for this behavior?

A.The UI Policy condition is checking the wrong field.

B.The UI Policy is set to 'Run on Load' only, not 'Run on Change'.

C.The UI Policy order is too low compared to other policies.

D.The UI Policy is inactive.

AnswerB

UI Policies must have 'Run on Change' checked to execute when a field value changes on an existing record.

Why this answer

UI Policies have two execution triggers: 'Run on Load' (fires when the form loads) and 'Run on Change' (fires when a specified field changes). When creating a new incident, the form loads with the condition already evaluated, so 'Run on Load' makes the fields mandatory. However, when editing an existing incident and changing the Category to 'Software', the change event does not re-trigger the policy unless 'Run on Change' is enabled.

Without this setting, the policy only applies on initial form load, not on subsequent field modifications.

Exam trap

The trap here is that candidates assume a UI Policy with a condition will automatically re-evaluate when the condition field changes, but they overlook the separate 'Run on Change' checkbox required for that behavior.

How to eliminate wrong answers

Option A is wrong because the administrator verified the condition is correctly set to 'Category equals Software', so the field reference is not the issue. Option C is wrong because the order of UI Policies only affects the sequence of execution when multiple policies apply to the same fields; the problem here is a missing trigger, not a conflict in order. Option D is wrong because the administrator explicitly states the UI Policy is active and works on new records, so inactivity is not the cause.

Full explanation →

275

Multi-Selectmedium

Which THREE of the following are required for ServiceNow Discovery to successfully populate the CMDB?

Select 3 answers

A.The CMDB CI tables with open ACLs

B.Valid credentials for the target devices

C.A discovery schedule configured for the IP range

D.A MID Server that can reach the target devices

E.The Identification and Reconciliation Engine (IRE) enabled

AnswersB, C, D

Credentials are necessary for authentication.

Why this answer

Valid credentials (Option B) are required because ServiceNow Discovery uses SNMP, SSH, WMI, or REST to probe target devices. Without correct credentials, the MID Server cannot authenticate to the device, so it cannot read configuration data or populate CI attributes in the CMDB.

Exam trap

ServiceNow often tests that candidates confuse the IRE as a hard requirement for Discovery, when in fact Discovery can function with the legacy identification engine, making Option E a tempting but incorrect choice.

Full explanation →

276

Multi-Selectmedium

Which TWO of the following are valid ways to define who receives a notification in ServiceNow? (Choose two.)

Select 2 answers

A.Email address

B.Users in a role

C.Dynamic recipient

D.Group

E.Email address from a field

AnswersB, E

Correct: Sends to all users with the specified role.

Why this answer

ServiceNow allows notifications to be sent to all users who have a specific role assigned. When 'Users in a role' is selected as the recipient type, the system evaluates the role membership at runtime and sends the notification to every active user with that role, making it a valid and commonly used recipient definition.

Exam trap

The trap here is that candidates often confuse the 'Email address from a field' option (which is valid) with a static 'Email address' field (which is not a recipient type), and they may also mistake 'Dynamic recipient' for a real option when ServiceNow uses 'Dynamic user' or 'Dynamic group' instead.

Full explanation →

277

Multi-Selecthard

Which THREE factors can cause a transform to skip a row (resulting in 'Skipped' status in the import log)?

Select 3 answers

A.A field mapping script returns false.

B.Coalesce matches an existing record and the transform action is 'Insert only'.

C.The source field is empty for an optional target field.

D.The target field is read-only.

E.The transform condition evaluates to false.

AnswersA, B, E

Returning false in a mapping script causes that row to be skipped.

Why this answer

A field mapping script that returns false explicitly tells the transform engine to skip the current row. When the script evaluates to false, the import engine does not process the row further, resulting in a 'Skipped' status in the import log. This is a deliberate mechanism to filter out rows based on custom logic.

Exam trap

The trap here is that candidates confuse 'Skipped' with 'Error' or 'Warning' statuses, thinking that any field-level issue (like an empty optional field or read-only target) causes the entire row to be skipped, when in fact only specific conditions or scripts that return false, or a coalesce match with 'Insert only', trigger a skip.

Full explanation →

278

MCQhard

An administrator notices that a custom table 'u_custom_infrastructure' was created as a child of 'cmdb_ci'. However, records in this table are not appearing in the CMDB dashboard reports that show all CIs. What is the likely reason?

A.The table has permissions that restrict report access

B.The records have not passed data certification

C.The table's 'Display in CMDB dashboard' property is disabled

D.The table is not included in the 'CMDB Base Class' report definition

AnswerD

Reports may need to be configured to include all child classes.

Why this answer

The CMDB dashboard reports are typically configured to display records from specific base classes or tables. If 'u_custom_infrastructure' is a child of 'cmdb_ci' but is not explicitly included in the 'CMDB Base Class' report definition, the report will not query that table, so its records will not appear. This is a common configuration oversight when extending the CMDB schema.

Exam trap

The trap here is that candidates often confuse table-level properties (like permissions or display flags) with report-level configuration, assuming a child table automatically inherits visibility in all parent-class reports.

How to eliminate wrong answers

Option A is wrong because table permissions control who can view or edit records, not whether records appear in a report definition; if the administrator can see the table, permissions are not the issue. Option B is wrong because data certification is a process for validating data quality, not a prerequisite for a record to be included in a CMDB dashboard report; uncertified records still appear in reports unless explicitly filtered. Option C is wrong because the 'Display in CMDB dashboard' property does not exist on a table; the visibility of a table in CMDB dashboards is controlled by the report definition, not a table-level flag.

Full explanation →

279

MCQhard

An administrator needs to implement a service catalog item that requires the user to select a location from a list, and based on that location, the available cost center options should be filtered. Which configuration should be used?

A.A variable set with a reference qualifier

B.A catalog client script

C.A business rule

D.A UI policy with a condition

AnswerA

Reference qualifiers allow dynamic filtering of reference fields based on conditions, including other variables.

Why this answer

A reference qualifier on the cost center variable can dynamically filter options based on another variable's value. A variable set groups variables but does not filter. A UI policy can show/hide but not filter reference options.

A business rule runs server-side and is not suitable for client-side filtering.

Full explanation →

280

MCQeasy

Which role is required to create and manage catalog items?

A.snc_platform_user

B.admin

C.itil

D.catalog_admin

AnswerB, D

Admin has full access to all ServiceNow modules, including the Service Catalog, and can create and manage catalog items.

Why this answer

Both the admin and catalog_admin roles have the necessary permissions to create and manage catalog items. The admin role provides unrestricted access to all ServiceNow modules, including the Service Catalog, making it fully capable of managing catalog items. The catalog_admin role is specifically designed for catalog management, granting granular permissions to create, modify, and manage catalog items, categories, and variables.

The other roles listed lack the required privileges for catalog item creation and management.

Exam trap

Candidates often overlook the admin role because they think the question asks for the 'required' role, implying a specific catalog role. However, admin also fulfills the requirement, making both B and D correct. The trap is that many choose only catalog_admin without considering admin's full access.

How to eliminate wrong answers

Option A is wrong because snc_platform_user is a basic platform user role that provides minimal access to the instance, typically for API or integration purposes, and does not include any catalog management permissions. Option B is wrong because while the admin role can perform all tasks including catalog management, it is overly broad and not the specific role required for catalog item management; the question asks for the role that is required, and admin is not the minimum required role. Option C is wrong because the itil role is designed for ITIL process compliance and provides access to service desk features like incidents and requests, but it does not grant permissions to create or manage catalog items.

Full explanation →

281

MCQhard

A developer writes the script include above to create an approval record. When the method is called from a business rule on the requested item table, the approval is created but assigned to the wrong user. What is the most likely cause?

A.The method should use 'new GlideRecord' instead of 'var gr'

B.The method uses gs.getUser() which returns the current user running the script, not the intended approver

C.The method is not using the correct GlideRecord table name

D.The method should call rec.update() after inserting the approval

AnswerB

In a business rule, the current user is often the system, not the actual requestor.

Why this answer

The script uses `gs.getUser()` to set the approver, which returns the user currently running the script (the system user or the user triggering the business rule), not the intended approver. In ServiceNow, `gs.getUser()` retrieves the session user, which in a business rule context is the user who triggered the rule, not necessarily the user who should approve the request. To assign the correct approver, the script should reference a field from the current record (e.g., `current.approver`) or use a specific user sys_id.

Exam trap

The trap here is that candidates assume `gs.getUser()` always returns the 'user' they think of as the approver, but in ServiceNow it returns the user running the script, which in a business rule is the user who triggered the rule, not the intended approval target.

How to eliminate wrong answers

Option A is wrong because using `var gr` vs `new GlideRecord` is a syntax preference, not a functional difference; both create a new GlideRecord instance, and the issue is not about variable declaration. Option C is wrong because the table name is not the problem; the approval record is created successfully, just assigned to the wrong user, indicating the table name is correct. Option D is wrong because `rec.insert()` already creates the record; calling `rec.update()` after insert is unnecessary and would not fix the user assignment issue.

Full explanation →

282

MCQmedium

Refer to the exhibit. A user with username 'john.doe' tries to view an incident record. What is the outcome?

A.The user can view the incident because no ACLs apply to incident table.

B.The user can view the incident because they have the itil role.

C.The user cannot view the incident because the ACL is missing a condition for itil role.

D.The user cannot view the incident because the ACL condition evaluates to false.

AnswerD

Both conditions are false, so read is denied.

Why this answer

The ACL condition on the incident table evaluates to false for user 'john.doe'. In ServiceNow, an ACL (Access Control List) with a condition that returns false prevents the user from viewing the record, even if they have a role like 'itil'. The exhibit likely shows an ACL with a condition such as 'true == false' or a script that returns false, which overrides any role-based access.

Exam trap

The trap here is that candidates assume having the 'itil' role guarantees read access to all incidents, but ServiceNow ACLs can deny access even to users with the correct role if a condition evaluates to false.

How to eliminate wrong answers

Option A is wrong because ACLs do apply to the incident table by default; ServiceNow uses ACLs to control read, write, create, and delete access on all tables. Option B is wrong because having the 'itil' role does not automatically grant view access if a more specific ACL condition evaluates to false; role-based access is subject to ACL conditions. Option C is wrong because the ACL is not missing a condition for the itil role; rather, the existing condition explicitly evaluates to false, which denies access regardless of role membership.

Full explanation →

283

MCQmedium

An administrator needs to delete a large number of records from the cmdb_ci table based on a condition. Which method is recommended for bulk deletion to ensure data integrity and performance?

A.Use a script that iterates and deletes each record using glideRecord.delete().

B.Use a direct SQL DELETE statement in a background script.

C.Use a GlideRecord script with deleteMultiple() to delete all matching records in one transaction.

D.Use the 'Delete all records in this table' option in the table configuration.

AnswerC

deleteMultiple() is efficient and safe for bulk deletions.

Why this answer

DeleteMultiple() processes all matching records in a single database transaction, ensuring data integrity by respecting business rules, ACLs, and database constraints while offering better performance than iterating individual deletes. This method is specifically designed for bulk deletion in ServiceNow, balancing efficiency with platform safety.

Exam trap

The trap here is that candidates often choose Option A (iterative delete) because it seems safer, but they overlook the severe performance penalty and risk of transaction log overflow when deleting large volumes of records individually.

How to eliminate wrong answers

Option A is wrong because iterating and deleting each record with glideRecord.delete() in a loop is inefficient for large datasets, causing excessive database round-trips and potential timeouts. Option B is wrong because direct SQL DELETE statements bypass ServiceNow's business logic, ACLs, and audit trails, risking data integrity and violating platform best practices. Option D is wrong because the 'Delete all records in this table' option removes every record unconditionally, ignoring the specified condition and potentially deleting unintended data.

Full explanation →

284

Multi-Selecthard

Which THREE of the following are best practices for CMDB data maintenance? (Choose exactly 3.)

Select 3 answers

A.Scheduled reconciliation to identify and merge duplicates

B.Disabling discovery for all CIs to prevent changes

C.Manually updating all CI attributes

D.Regular data certification to ensure data quality

E.Setting up data refresh schedules for imported data

AnswersA, D, E

Reconciliation keeps the CMDB clean.

Why this answer

Scheduled reconciliation is a core CMDB best practice that uses identification rules to automatically detect and merge duplicate CIs, ensuring a single source of truth. This process relies on the CMDB's reconciliation engine, which compares CI attributes against defined identification and reconciliation rules to resolve conflicts without manual intervention.

Exam trap

ServiceNow often tests the misconception that disabling discovery is a valid maintenance strategy, when in fact it is the opposite; the trap here is confusing 'maintenance' with 'preventing change' rather than 'ensuring data accuracy through automation'.

Full explanation →

285

MCQhard

An administrator is troubleshooting why a CMDB CI's last discovered date is not updating after a successful discovery run. The CI is in a valid state and the discovery schedule runs. What could be the cause?

A.The CMDB identification rule has a condition that excludes this CI from updates.

B.The discovery source is set to 'ServiceNow' but the CI was created manually.

C.The reconciliation rule is set to 'Manual' and the discovered data conflicts with existing data.

D.The CI is a parent class and child class discovery is updating child records.

AnswerC

Manual reconciliation prevents automatic updates when conflicts arise, so the date stays unchanged.

Why this answer

When a reconciliation rule is set to 'Manual', the CMDB will not automatically update CI attributes with discovered data if there is a conflict with existing data. The CI remains in its last discovered state until a manual reconciliation is performed, even if the discovery run succeeds and the CI is valid.

Exam trap

The trap here is that candidates often confuse reconciliation rules with identification rules or assume that a successful discovery run always updates the last discovered date, overlooking the impact of manual reconciliation settings on attribute updates.

How to eliminate wrong answers

Option A is wrong because identification rules determine how CIs are matched and identified, not whether updates are applied after identification; a condition that excludes a CI would prevent it from being identified or updated at all, not just the last discovered date. Option B is wrong because the discovery source being set to 'ServiceNow' is the correct source for ServiceNow discovery, and a manually created CI can still be updated by discovery if the identification rule matches it; the issue is not about the source value. Option D is wrong because parent-child class relationships do not prevent the parent CI's last discovered date from updating; discovery of child records typically updates the parent's last discovered date as part of the hierarchy update logic.

Full explanation →

286

MCQhard

A large enterprise has extensively customized the Incident table with many UI Policies and Client Scripts. After a recent upgrade, users report that the incident form takes significantly longer to load, especially on records with many fields. The administrator investigates and discovers that multiple UI Policies share the same condition but are defined separately, causing the condition to be evaluated multiple times. Additionally, there are several client scripts that also evaluate the same conditions. The administrator wants to reduce page load time without altering the functionality. The instance is running on a mid-sized deployment with no budget for hardware scaling in the near term. Which course of action will best address the performance issue?

A.Disable all client-side scripting and rely solely on server-side validation.

B.Increase the system's form load timeout setting to prevent errors.

C.Convert all UI Policies to Client Scripts to move processing to the client.

D.Combine UI Policies with identical conditions into a single UI Policy with multiple actions.

AnswerD

This reduces the number of condition evaluations, decreasing server load and improving load time.

Why this answer

Combining UI Policies with identical conditions into a single UI Policy reduces redundant condition evaluations, directly improving performance. Increasing timeouts only masks the problem, disabling client-side scripting removes functionality, and converting to client scripts may still evaluate conditions inefficiently.

Full explanation →

287

MCQmedium

An administrator is designing a service catalog for IT requests. They want to group related catalog items under categories such as 'Hardware' and 'Software'. Additionally, they want to allow users to search for items within a category. What is the best practice for structuring the catalog?

A.Use categories within a single service catalog to group items

B.Use the home page to list items and no categories

C.Create a separate catalog for each category

D.Create a catalog for each department and include all items

AnswerA

Categories are the standard way to group items and the search spans the entire catalog.

Why this answer

Using a single service catalog with categories is the best practice because it allows administrators to logically group related catalog items (e.g., Hardware, Software) while maintaining a unified search and request experience. Categories are metadata tags that filter items within the same catalog, enabling users to browse or search for items within a specific category without needing to navigate multiple catalogs. This approach aligns with ServiceNow's out-of-the-box design, where a single catalog can contain multiple categories, and each category can have its own set of items.

Exam trap

The trap here is that candidates confuse 'categories' with 'catalogs', thinking that each logical grouping requires its own catalog, when in fact ServiceNow's architecture uses categories as a lightweight grouping mechanism within a single catalog to maintain a unified user experience and simplify administration.

How to eliminate wrong answers

Option B is wrong because listing all items on the home page without categories eliminates the ability to group related items, making it difficult for users to find specific requests and violating the requirement to allow searching within a category. Option C is wrong because creating a separate catalog for each category would fragment the user experience, requiring users to switch between multiple catalogs to find items, and it would complicate administration by duplicating catalog-level configurations (e.g., variables, workflows) that should be shared. Option D is wrong because creating a catalog per department is an organizational choice that does not address the requirement to group items under categories like 'Hardware' and 'Software'; it would also force users to know which department owns a catalog before searching, which is not the intended design for a service catalog.

Full explanation →

288

MCQhard

A large import set of 10,000 user records from an HR system is failing intermittently during transformation to the sys_user table. Some rows are inserted successfully, but others show errors in the import log: 'Transform script error: null reference at line 15 of the transform map script.' The administrator reviews the transform map and finds a script that sets the department field by looking up a department table. The script assumes the department code always exists in the department table, but some records have codes that are not present. The administrator needs to ensure all rows are imported reliably, even if some data is missing. What is the best course of action?

A.Use a 'Run as GlideRecord' operation in the transform map to ensure each row is processed individually.

B.Create a separate import set for each user record to isolate failures.

C.Fix the transform script to check for the existence of the department code before using it, and set a default value or skip the field if not found. Then use an Import Set Row condition to only process rows that are valid.

D.Add a condition to skip rows that have null values in the department field.

AnswerC

This addresses the root cause by handling missing data in the script, and the row condition ensures only rows with sufficient data are transformed.

Why this answer

It directly addresses the root cause: the transform script fails when a department code is missing from the reference table. By adding a null check before using the lookup result and providing a default or skipping the field, the script becomes resilient to missing data. Using an Import Set Row condition then ensures that only rows with valid department codes are processed, preventing the intermittent null reference errors while still importing all other rows successfully.

Exam trap

The trap here is that candidates often choose to skip rows with null values (Option D) instead of handling the missing data gracefully, failing to recognize that the requirement is to import all rows reliably, not just those with complete data.

How to eliminate wrong answers

Option A is wrong because 'Run as GlideRecord' processes each row individually but does not fix the null reference error; the script would still fail on rows with missing department codes. Option B is wrong because creating a separate import set for each record would be impractical and does not solve the underlying script logic issue; it would also break the batch import process and increase administrative overhead. Option D is wrong because skipping rows with null values in the department field would discard valid records that simply lack a department code, whereas the requirement is to import all rows reliably, possibly with a default value for missing data.

Full explanation →

289

MCQeasy

A report is created but shows no data. The table and conditions appear correct. What is the most likely cause?

A.The report is scheduled to run daily

B.The report type is set to 'Bar chart' but the data is numeric

C.The report is set to 'Run as' a user without roles to view the data

D.The report has a modulo condition on sys_id

AnswerC

Report runs with authority of specified user; lack of roles returns no data.

Why this answer

In ServiceNow, reports execute under the security context of the user specified in the 'Run as' field. If that user lacks the necessary roles (e.g., snc_internal or specific table read roles) to view the underlying data, the report will run without errors but return zero rows, even if the table and conditions are correct. This is a common misconfiguration when reports are shared or scheduled.

Exam trap

The trap here is that candidates often assume a report with correct table and conditions will always show data, overlooking that ServiceNow enforces data visibility based on the executing user's roles and ACLs, not the report creator's.

How to eliminate wrong answers

Option A is wrong because scheduling a report to run daily does not affect whether data appears; scheduling only controls when the report is generated, not the visibility of data. Option B is wrong because a bar chart can display numeric data; the chart type is a visualization choice and does not cause an empty report. Option D is wrong because a modulo condition on sys_id would filter results but would not cause a report to show no data unless the condition is impossible; even then, it would be a logical filter issue, not a permissions or context issue.

Full explanation →

290

MCQmedium

An administrator runs a CMDB health report for the CI class cmdb_ci_server and sees the exhibit. Which attribute is the highest priority to populate first?

A.Operating system (os)

B.Serial number (serial_number)

C.Model ID (model_id)

D.Manufacturer

AnswerB

800 missing, the highest number, and critical for identification.

Why this answer

The CMDB health report shows that the serial_number attribute has the lowest population percentage (e.g., 45%) compared to other attributes. Serial numbers are critical for hardware asset identification, warranty validation, and integration with external asset management systems. Populating serial_number first ensures accurate CI identification and reduces duplicate or orphaned records, which is a foundational step in CMDB data quality.

Exam trap

The trap here is that candidates often prioritize attributes like operating system or manufacturer because they seem more relevant to server operations, but the CMDB health report specifically highlights population gaps, and serial_number is the most critical for unique CI identification and deduplication.

How to eliminate wrong answers

Option A is wrong because operating system (os) is a software attribute that, while important for server management, is often dynamically discovered and can be populated later without impacting CI uniqueness. Option C is wrong because model_id, though useful for hardware categorization, is not a unique identifier and can be derived from manufacturer and other attributes. Option D is wrong because manufacturer is a broad classification attribute that, like model_id, does not provide unique CI identification and is typically populated via discovery or manual entry without affecting record deduplication.

Full explanation →

291

Multi-Selecthard

Which three conditions are required for a catalog item to appear in the Service Portal? (Choose three.)

Select 3 answers

A.The catalog item must be in a category that is published to the portal.

B.The catalog item must be available for the user's role.

C.The catalog item must have a mandatory variable.

D.The catalog item must be active.

E.The user must have the 'catalog_admin' role.

AnswersA, B, D

Only categories with 'Portal' property checked are visible.

Why this answer

A catalog item must be in a category that is published to the Service Portal because the portal only displays items from categories that have been explicitly published. If the category is not published, the item will not appear regardless of other settings.

Exam trap

The trap here is that candidates often confuse mandatory variables or admin roles as prerequisites for visibility, when in fact they are unrelated to the core conditions of active, published category, and role availability.

Full explanation →

292

MCQeasy

A report using the 'server_by_os' database view is expected to show a record for each server. However, a server without an operating system entry is not appearing in the report. What is the most likely reason?

A.The view is missing a required field.

B.The view is not refreshed.

C.The server's OS field is null.

D.The join is defined as an INNER JOIN, excluding servers without a matching OS record.

AnswerD

INNER JOIN requires matching records in both tables.

Why this answer

The report is built on a database view that joins the server table with the operating system table. If the join is an INNER JOIN, only records with matching rows in both tables are returned. A server with a null OS field has no matching OS record, so it is excluded from the result set.

This is the most likely reason the server is missing from the report.

Exam trap

The trap here is that candidates assume a null field value is the direct cause of the missing record, when in fact the underlying join type (INNER JOIN) is the mechanism that excludes rows with null foreign keys.

How to eliminate wrong answers

Option A is wrong because a missing required field would typically cause an error or prevent the view from being created, not silently exclude a row. Option B is wrong because views in ServiceNow are dynamic and reflect the underlying data in real time; they do not require manual refresh. Option C is wrong because a null OS field alone does not cause a row to be excluded; it is the join type (INNER JOIN) that filters out rows with null foreign keys.

Full explanation →

293

MCQmedium

A company uses SLA definitions with a time zone of 'US/Eastern'. A task is created at 10:00 PM Eastern on a Sunday. The SLA definition has a start condition that triggers on creation, a 4-hour duration, and a schedule that includes only weekdays 9 AM to 5 PM. What is the expected SLA state at 2:00 PM Eastern on Monday?

A.In Progress (still running)

B.In Progress (not breached)

C.Breached (at 1 PM)

D.Breached (at 2 PM)

AnswerC

The SLA started at 9 AM Monday, and with a 4-hour duration, it breached at 1 PM.

Why this answer

The SLA starts at 10:00 PM Eastern on Sunday, but the schedule only counts weekdays 9 AM–5 PM. The first eligible time is Monday 9 AM, so the 4-hour duration runs from 9 AM to 1 PM Eastern on Monday. At 2:00 PM Eastern on Monday, the SLA has already exceeded its 4-hour window, meaning it breached at 1 PM.

Option C correctly identifies the breach time.

Exam trap

The trap here is that candidates mistakenly calculate the 4-hour duration from the creation time (10 PM Sunday) instead of from the first schedule start (9 AM Monday), leading them to think the SLA is still in progress or breaches later.

How to eliminate wrong answers

Option A is wrong because the SLA is not 'in progress (still running)' — the 4-hour duration has already elapsed by 2 PM Monday, so the SLA is breached, not still running. Option B is wrong because 'in progress (not breached)' implies the SLA is still within its allowed time, but the 4-hour window ended at 1 PM, so it is breached. Option D is wrong because the breach occurs at 1 PM, not 2 PM — the 4-hour duration from the schedule start (9 AM) ends at 1 PM, making 2 PM a post-breach state.

Full explanation →

294

MCQhard

Refer to the exhibit. A priority 1 incident is created and then immediately closed (state changed to 6) before the notification processes. Will the notification be sent?

A.Yes, because the incident was priority 1 at creation.

B.No, because the state is 6 when the condition is evaluated.

C.It depends on the order of business rules.

D.Yes, because the notification is triggered after insert.

AnswerB

Correct; condition fails because state is 6.

Why this answer

The notification condition is evaluated after the incident is saved, at which point the state is already 6 (Closed). The notification is not sent because the condition (e.g., priority = 1) is evaluated against the current record state, and a closed incident typically does not match the notification criteria. In ServiceNow, notifications are triggered by business rules that run after the database operation, so the final state of the record determines whether the condition is met.

Exam trap

ServiceNow often tests the misconception that a notification condition is evaluated at the moment of record creation rather than at the time the notification business rule executes, leading candidates to overlook the impact of subsequent state changes within the same transaction.

How to eliminate wrong answers

Option A is wrong because the notification condition is evaluated at the time of the business rule execution, not at the moment of creation; the priority 1 at creation is irrelevant if the state changes before the notification runs. Option C is wrong because the order of business rules does not affect the fact that the state is 6 when the notification condition is evaluated; the notification is tied to the after-insert business rule, which runs after all other business rules on the same event. Option D is wrong because while the notification is triggered after insert, the condition is evaluated on the current record state, which is 6 due to the immediate state change, so the notification will not be sent.

Full explanation →

295

Multi-Selecteasy

Which TWO of the following are valid CMDB base classes? (Choose exactly 2.)

Select 2 answers

A.cmdb_ci_win_system

B.cmdb_ci

C.cmdb_ci_linux_system

D.cmdb_ci_service

E.cmdb_ci_computer

AnswersB, D

This is the root CMDB CI table.

Why this answer

In ServiceNow, the CMDB base classes are the top-level classes from which all other configuration items (CIs) inherit. `cmdb_ci` is the root base class for all CIs, and `cmdb_ci_service` is a base class specifically for business and technical services. Both are defined in the CMDB data model as foundation classes that cannot be deleted and serve as parents for more specific CI types.

Exam trap

The trap here is that candidates often mistake common CI types like `cmdb_ci_win_system` or `cmdb_ci_computer` for base classes because they appear frequently in CMDB tables, but ServiceNow defines only a few true base classes (e.g., `cmdb_ci`, `cmdb_ci_service`, `cmdb_ci_infrastructure`) from which all others inherit.

Full explanation →

296

MCQhard

Refer to the exhibit. After submitting the catalog item, a catalog task is created. Which of the following is true about the catalog task?

A.The catalog task's state is 'Work In Progress'

B.The catalog task is assigned to John Doe

C.The catalog task's short_description will be 'Install Adobe Photoshop on WS-102'

D.The catalog task is assigned to the 'IT' department

AnswerC

Correct. The expression concatenates the variable values.

Why this answer

The catalog item's variable mapping or task template is configured to set the short_description field to 'Install Adobe Photoshop on WS-102'. In ServiceNow, when a catalog item creates a catalog task, the task's short_description is typically populated from a variable or a fixed value defined in the task template or workflow. The exhibit (not shown) would indicate that the short_description is explicitly set to this value, making it the accurate statement.

Exam trap

The trap here is that candidates assume the catalog task's state or assignment is based on default behavior (e.g., 'Work In Progress' or 'IT' department) rather than recognizing that these values are explicitly configured in the task template or workflow, and the exhibit provides the specific short_description value.

How to eliminate wrong answers

Option A is wrong because a newly created catalog task's default state is 'Open', not 'Work In Progress'; the state transitions to 'Work In Progress' only when a user clicks 'Work In Progress' on the task. Option B is wrong because the catalog task is not assigned to John Doe; assignment is determined by the assignment group or user specified in the task template or workflow, and the exhibit does not indicate John Doe as the assignee. Option D is wrong because the catalog task is not assigned to the 'IT' department; assignment groups are specific to the task template or workflow configuration, and the exhibit does not show the 'IT' department as the assigned group.

Full explanation →

297

MCQhard

A catalog item uses a 'Variable set' that includes several variables. After updating the variable set, the changes do not appear on the catalog item form. What is the most likely cause?

A.The variable set cache has not been cleared

B.The variable set is not published

C.The catalog item's category has been changed

D.The catalog item is shared with a restricted role

AnswerA

ServiceNow caches variable set definitions; clearing the cache or re-saving the catalog item forces an update.

Why this answer

ServiceNow caches variable set definitions to improve performance. When a variable set is updated, the cache must be cleared (via 'Cache Flush' or by deactivating/reactivating the variable set) before the changes are reflected on the catalog item form. Without clearing the cache, the system continues to serve the stale, cached version of the variable set.

Exam trap

The trap here is that candidates assume changes to variable sets are immediately visible, similar to changes to catalog item variables, but ServiceNow's caching mechanism for variable sets requires a manual cache flush to apply updates.

How to eliminate wrong answers

Option B is wrong because variable sets are not 'published' like catalog items or record producers; they are simply active or inactive, and activation alone does not require a publish step. Option C is wrong because changing the catalog item's category does not affect the display of variables from a variable set; categories control item grouping, not variable rendering. Option D is wrong because sharing a catalog item with a restricted role controls visibility and access, not the rendering of variable set changes on the form.

Full explanation →

298

MCQmedium

Refer to the exhibit. An SLA definition has the condition shown. An incident is created with state=2, category='network', assignment_group=null, and caller_id=user1. Will the SLA start?

A.No, because the assignment_group is empty.

B.No, because the caller_id condition is not met.

C.No, because the category does not match.

D.Yes, because the condition is partially met.

AnswerA

The condition requires a non-empty assignment group.

Why this answer

The SLA definition includes a condition that requires assignment_group to be populated. Since the incident has assignment_group=null, the condition is not fully met, and the SLA will not start. SLAs in ServiceNow only start when all conditions in the definition are satisfied; a null value for a required field causes the condition to fail.

Exam trap

ServiceNow often tests the misconception that an SLA can start if most conditions are met, but the platform requires all conditions to be satisfied exactly as defined, including non-null values for required fields.

How to eliminate wrong answers

Option B is wrong because the caller_id condition is met (caller_id=user1 matches the definition), so it does not prevent the SLA from starting. Option C is wrong because the category condition is met (category='network' matches the definition), so it does not prevent the SLA from starting. Option D is wrong because SLA conditions must be fully met; partial satisfaction does not trigger the SLA start.

Full explanation →

299

MCQhard

Refer to the exhibit. A contractor submits a laptop request via the catalog item. The request is for a Standard laptop in the IT department. Which approval(s) will be triggered?

A.Auto-approve

B.Approval by IT Managers group only

C.Approval by Department Manager only

D.Both IT Managers and Department Manager approval

AnswerB

Correct. The first condition matches, triggering approval by IT Managers.

Why this answer

The catalog item is configured with an approval rule that requires approval by the IT Managers group for Standard laptop requests in the IT department. Since the contractor's request matches these criteria, only the IT Managers group approval is triggered. The Department Manager approval is not required because the rule does not specify it for this item.

Exam trap

The trap here is that candidates often assume a Department Manager approval is always required for requests within their department, but ServiceNow approval rules are explicitly defined per catalog item and can override or omit that default behavior.

How to eliminate wrong answers

Option A is wrong because auto-approve would only apply if no approval rule is defined or if the item is explicitly set to auto-approve, which is not the case here. Option C is wrong because the Department Manager approval is not triggered; the rule specifically targets the IT Managers group, not the department manager. Option D is wrong because both approvals are not required; only the IT Managers group approval is triggered based on the item's configuration.

Full explanation →

300

MCQmedium

When importing data, the import set table rows are not appearing after running the import. What is the most likely cause?

A.The transform map has the 'Cleanup after transform' checkbox selected.

B.The import source file was empty.

C.The transform map condition rejected all rows.

D.The transform map action is set to 'Create' and coalesce matches no records.

AnswerA

When this option is enabled, import set rows are automatically deleted after a successful transform, so they do not persist.

Why this answer

When the 'Cleanup after transform' checkbox is selected on the transform map, ServiceNow automatically deletes all rows from the import set table after the transform completes. This is designed to keep the import set table clean, but it means the rows are removed immediately after processing, so they will not appear when you query the import set table post-import.

Exam trap

ServiceNow often tests the misconception that import set rows are always retained after a transform, but the 'Cleanup after transform' checkbox is a deliberate setting that removes them, and candidates may overlook this option when troubleshooting missing import set rows.

How to eliminate wrong answers

Option B is wrong because if the import source file was empty, no rows would be created in the import set table during the import, but the question states rows are not appearing after running the import, implying the import ran successfully but rows are missing. Option C is wrong because if the transform map condition rejected all rows, the rows would still exist in the import set table (they would just not be transformed into target records), so they would appear in the import set table. Option D is wrong because if the transform map action is set to 'Create' and coalesce matches no records, the transform would create new target records, but the import set rows would still remain in the import set table unless explicitly deleted.

Full explanation →

ServiceNow Certified System Administrator CSA (SNOW-CSA) — Questions 226–300