ServiceNow Certified System Administrator CSA SNOW-CSA Questions 76–150 | Page 2/7

Multi-Selectmedium

An administrator is troubleshooting issues with the CMDB identification and reconciliation engine. Which three components are part of the identification and reconciliation process? (Choose three.)

Select 3 answers

A.Transform maps

B.Reconciliation rules

C.Data source

D.Identification rules

E.CI Class Manager

AnswersB, C, D

These rules specify how to handle CI merging and conflict resolution.

Why this answer

Reconciliation rules (B) are a core component of the CMDB identification and reconciliation process because they define how to handle duplicate or conflicting CIs during the reconciliation phase. These rules determine which data source takes precedence, whether to merge or overwrite attributes, and how to resolve conflicts between multiple sources. Without reconciliation rules, the system cannot maintain a single authoritative view of each CI.

Exam trap

The trap here is that candidates confuse the data import pipeline (transform maps, data sources) with the identification and reconciliation engine, which only includes identification rules, reconciliation rules, and data sources as the three core components.

Full explanation →

MCQhard

An organization is planning to implement CMDB for a large-scale environment with multiple data sources. They need to ensure that the most trustworthy data source takes precedence when conflicts occur. Which feature should they use?

A.Identification & Reconciliation engine

B.Reconciliation

C.Set source precedence in the CI class manager for each CI

D.Data Source Priority

AnswerD

This feature allows setting precedence for data sources.

Why this answer

Data Source Priority (Option D) is the correct feature because it allows administrators to define a hierarchy of data sources in the CMDB, ensuring that when multiple sources provide conflicting attribute values for the same CI, the source with the highest priority (lowest numeric value) is trusted and its data is used. This directly addresses the requirement to make the most trustworthy data source take precedence in a large-scale, multi-source environment.

Exam trap

The trap here is that candidates often confuse the Identification & Reconciliation engine (which performs the conflict detection) with the Data Source Priority feature (which dictates which source wins), leading them to select Option A instead of D.

How to eliminate wrong answers

Option A is wrong because the Identification & Reconciliation engine is responsible for identifying CIs and reconciling them against existing records, but it does not itself set a priority order among data sources; it relies on the Data Source Priority configuration to resolve conflicts. Option B is wrong because 'Reconciliation' is a broad process within the CMDB that includes identification, merging, and conflict resolution, but it is not a specific feature that assigns precedence to data sources. Option C is wrong because setting source precedence in the CI class manager for each CI is not a valid operation; source precedence is configured globally or per data source in the Data Source Priority settings, not per CI class or individual CI.

Full explanation →

MCQeasy

A company imports employee data from an HR system weekly. The import set table always retains the data from previous imports, causing storage issues. The administrator wants to automatically delete the import set rows after a successful transform to free up space. Which configuration should be made?

A.Select the 'Cleanup after transform' checkbox on the transform map.

B.Create a scheduled job to delete old import set rows.

C.Set a retention policy on the import set table.

D.Use a business rule to delete the import set row after transform.

AnswerA

This native option automatically deletes import set rows after a successful transform.

Why this answer

Selecting the 'Cleanup after transform' checkbox on the transform map instructs the platform to automatically delete the import set rows from the staging table once the transform has completed successfully. This directly addresses the storage issue caused by retaining all historical import data, without requiring manual or scheduled cleanup.

Exam trap

The trap here is that candidates may over-engineer a solution by choosing a scheduled job or business rule, not realizing that ServiceNow provides a simple, built-in checkbox on the transform map to handle automatic cleanup after transform.

How to eliminate wrong answers

Option B is wrong because creating a scheduled job to delete old import set rows is an unnecessary workaround; the platform provides a built-in mechanism for automatic cleanup after transform, making a scheduled job redundant and less efficient. Option C is wrong because setting a retention policy on the import set table is not a native feature of ServiceNow for import set tables; retention policies are typically used for syslog or other log tables, not for import set staging tables. Option D is wrong because using a business rule to delete the import set row after transform is overly complex and error-prone; the 'Cleanup after transform' checkbox achieves the same result declaratively without custom scripting.

Full explanation →

Multi-Selecteasy

Which two statements about UI Policies are true? (Choose two.)

Select 2 answers

A.They are always executed on form load.

B.They can be used to cancel a form submission.

C.They can be used to set field values.

D.They run on the client side.

E.They run on the server side.

AnswersC, D

UI Policies can set the value of fields using the 'Set value' action.

Why this answer

UI Policies can set field values on the client side using the 'Set field values' section within the UI Policy configuration. This allows administrators to automatically populate or modify field values based on conditions, such as setting a category field when a certain priority is selected, without requiring a server round trip.

Exam trap

The trap here is that candidates often confuse UI Policies with Client Scripts or Business Rules, mistakenly thinking UI Policies can cancel submissions (which is a Client Script function) or run server-side (which is a Business Rule function), leading them to select options B or E.

Full explanation →

MCQeasy

A company frequently imports data from an external HR system into the Employee [hr_employee] table using an import set. The import set runs nightly and maps fields correctly. Recently, the import started failing with the error 'Field 'manager' not found in table 'hr_employee''. The manager field exists in the import set rows but not in the target table. What is the most likely cause?

A.The transform map has a field mapping that references 'manager' as a target field, but the hr_employee table does not have a 'manager' column.

B.The import set row table (sys_import_set_row) does not have a 'manager' column.

C.The source CSV file contains a column named 'manager' that is misspelled.

D.The manager field in the target table is of a different data type (e.g., string vs reference).

AnswerA

The transform map attempts to map to a non-existent field.

Why this answer

The error 'Field 'manager' not found in table 'hr_employee'' indicates that the transform map is attempting to map a source field to a target column that does not exist in the hr_employee table. Since the import set rows contain the 'manager' field, the mapping in the transform map must be referencing 'manager' as a target field, but the target table lacks that column. This is the most likely cause because the transform map defines the field-to-field mapping between the import set row and the target table, and if the target field name is incorrect or missing from the table, the import will fail.

Exam trap

ServiceNow often tests the distinction between source-side errors (e.g., missing column in import set row or CSV) and target-side errors (e.g., missing column in the target table), and candidates may confuse the error message's reference to 'table' as the import set row table rather than the target table.

How to eliminate wrong answers

Option B is wrong because the import set row table (sys_import_set_row) stores the raw data from the source; the error specifically states the field is not found in the target table, not the import set row table. Option C is wrong because a misspelled column in the source CSV would cause a different error (e.g., 'Field not found in source') or a mapping failure, but the error explicitly says the field is not found in the target table, not the source. Option D is wrong because a data type mismatch would produce a different error (e.g., 'Cannot convert data type'), not a 'field not found' error; the error is about the existence of the column, not its type.

Full explanation →

MCQeasy

Refer to the exhibit. This condition script is used in a notification. For which states will the notification trigger?

A.Only state 3

B.Both state 2 and state 3

C.Only state 2

D.Neither state 2 nor state 3

AnswerB

The logical OR returns true for either condition.

Why this answer

The condition script uses `current.state.changesTo(3)` which returns true only when the state transitions to 3 from a different state. Since the script also includes `current.state == 2`, the notification triggers for state 2 as well. Therefore, both state 2 and state 3 will cause the notification to fire.

Exam trap

The trap here is that candidates often confuse `changesTo()` with a static state check, assuming it behaves like `current.state == 3`, and thus incorrectly think the notification only triggers for state 2 or only for state 3.

How to eliminate wrong answers

Option A is wrong because it ignores the `current.state == 2` condition, which independently triggers the notification for state 2. Option C is wrong because it overlooks the `current.state.changesTo(3)` condition, which triggers the notification when the state changes to 3. Option D is wrong because both conditions are met for state 2 (direct equality) and state 3 (on change to 3), so the notification will trigger for both states.

Full explanation →

Multi-Selecthard

Which TWO of the following are valid ways to trigger a workflow from a catalog item? (Choose two.)

Select 2 answers

A.On the catalog item form, go to the 'Workflow' tab and select a workflow.

B.Write a Business Rule on the 'sc_request' table that starts a workflow.

C.Set the 'Workflow' field on the catalog item to the desired workflow.

D.In the workflow editor, add a 'Execute Workflow' activity pointing to the catalog item.

E.Create a Flow in Flow Designer that triggers on 'Record Created' for the 'Request' table.

AnswersC, E

The Workflow field directly associates a workflow.

Why this answer

The 'Workflow' field on the catalog item record directly associates a workflow with that item. When a user submits the catalog item, the platform automatically triggers the associated workflow on the generated sc_request record. This is the standard declarative method for linking a catalog item to a workflow without custom scripting.

Exam trap

The trap here is that candidates often confuse the 'Workflow' tab (which does not exist) with the 'Workflow' field, or they think a Business Rule on the sc_request table is a direct catalog item trigger, when it is actually a secondary scripted method not listed as a valid direct trigger in the exam objectives.

Full explanation →

Multi-Selecthard

Which THREE of the following statements about ACL evaluation are true? (Choose three.)

Select 3 answers

A.An ACL with type 'deny' will override all other ACLs.

B.ACLs are evaluated in alphabetical order by name.

C.An ACL's 'Requires role' field can have multiple roles separated by commas.

D.Multiple ACLs that grant access are ORed together.

E.If no ACL exists for an operation, access is denied by default.

AnswersC, D, E

Correct: User needs any one of the roles.

Why this answer

Options C, D, and E are correct. C: An ACL's 'Requires role' field can have multiple roles separated by commas; users need only one of those roles to satisfy the requirement. D: Multiple ACLs that grant access are ORed together; if any ACL grants access, the user is allowed.

E: If no ACL exists for an operation, access is denied by default. Option A is incorrect because 'deny' ACLs do not exist in ServiceNow; ACLs either grant or require conditions. Option B is incorrect because ACLs are evaluated by order of type (table, record, column, etc.) and then by the order specified in the 'Order' field, not alphabetically by name.

Full explanation →

MCQmedium

An administrator wants to allow end users to reset their own passwords using the 'Forgot Password' feature. Which configuration is required to enable this?

A.Assign the 'password_reset' role to end users.

B.Configure an email notification for reset password.

C.Set the 'Allow password reset' property to true.

D.Activate the 'Password Reset' plugin.

AnswerD

The plugin must be activated to provide password reset functionality.

Why this answer

The 'Forgot Password' feature in ServiceNow is implemented via a plugin called 'Password Reset' (com.snc.password_reset). This plugin must be activated to enable the self-service password reset functionality. Without activating this plugin, the feature is not available regardless of other configurations.

Exam trap

The trap here is that candidates often confuse the 'Forgot Password' feature with a simple system property or role assignment, but ServiceNow requires the specific plugin to be activated to enable this self-service functionality.

How to eliminate wrong answers

Option A is wrong because there is no built-in 'password_reset' role in ServiceNow; the feature relies on plugin activation and user access to the public portal, not a specific role assignment. Option B is wrong because configuring an email notification for reset password is a step that can be done after the plugin is activated, but it is not the required configuration to enable the feature itself. Option C is wrong because there is no 'Allow password reset' property in ServiceNow; the feature is controlled by the plugin, not a system property.

Full explanation →

MCQhard

A catalog item uses a workflow that includes a 'Wait for Condition' activity. The condition checks if a custom table record 'approval_status' equals 'approved'. Requests are not progressing past this activity even though the record is updated. What could be the issue?

A.The 'Wait for Condition' activity is not in the same application scope as the custom table.

B.The user updating the record does not have the 'workflow_admin' role.

C.The 'Check Condition' property of the activity is set to 'After Update', but the record was already updated before the workflow reached this activity.

D.The custom table record is not related to the catalog item.

AnswerC

Activity only evaluates when the record is updated after it begins waiting.

Why this answer

The 'Wait for Condition' activity's 'Check Condition' property determines when the condition is evaluated. If set to 'After Update', the condition is only checked when the record is updated after the workflow reaches this activity. If the record was already updated before the workflow reached the 'Wait for Condition' activity, the condition will never be re-evaluated, causing the workflow to stall indefinitely.

Exam trap

ServiceNow often tests the nuance of the 'Check Condition' property timing, where candidates assume the condition is evaluated immediately upon reaching the activity, ignoring that the 'After Update' setting requires a subsequent update event to trigger re-evaluation.

How to eliminate wrong answers

Option A is wrong because the 'Wait for Condition' activity does not require being in the same application scope as the custom table; scoping affects access to tables but not the condition evaluation logic. Option B is wrong because the 'workflow_admin' role is not required to update a record that triggers a workflow condition; any user with write access to the table can update the record, and the workflow engine evaluates conditions based on the record state, not the user's role. Option D is wrong because the custom table record does not need to be directly related to the catalog item; the 'Wait for Condition' activity can check any table record as long as the condition is properly defined, and the workflow context provides the record's sys_id.

Full explanation →

MCQmedium

An organization needs to ensure that when a catalog item is ordered, a task is created for the IT team to provision the requested software. They want to use a flow to automate this. Which configuration should be used?

A.Use a Record Producer to create a task upon catalog item submission.

B.Add a 'Task' variable to the catalog item.

C.Create a Flow that triggers on 'Catalog Task' record creation.

D.Configure an approval rule to create a task.

AnswerA

Correct: Record Producer is the standard method to auto-create records from catalog items.

Why this answer

A Record Producer can be configured on a catalog item to automatically create a task (e.g., a Catalog Task or a custom task) upon submission. This is the native, out-of-box approach for generating tasks from catalog requests without requiring a separate flow or approval rule.

Exam trap

The trap here is that candidates often confuse the purpose of a Record Producer (which creates records) with a Flow (which automates processes), leading them to incorrectly select a Flow-based trigger that fires after the task already exists.

How to eliminate wrong answers

Option B is wrong because adding a 'Task' variable to a catalog item does not create a task; variables are for collecting user input, not for triggering record creation. Option C is wrong because a Flow that triggers on 'Catalog Task' record creation would only fire after the task already exists, not when the catalog item is ordered. Option D is wrong because approval rules are designed to manage approval processes, not to create tasks; they can trigger notifications or state changes but do not generate new task records.

Full explanation →

Multi-Selecthard

Which THREE of the following are true regarding Business Rules?

Select 3 answers

A.They are executed on the client side to improve performance

B.They automatically fire on every record in the database when created

C.They can be used to perform data validation before a record is saved

D.They can be configured to run asynchronously to avoid impacting user response time

E.They can be set to fire on insert, update, delete, or query

AnswersC, D, E

Before business rules can validate data and abort the save if needed.

Why this answer

Business Rules in ServiceNow are server-side scripts that execute before or after a database operation, and they are commonly used to validate data before the record is saved. By using the 'Before' order, a business rule can check field values and abort the save if validation fails, ensuring data integrity.

Exam trap

ServiceNow often tests the misconception that Business Rules are client-side, but the trap here is that candidates confuse Business Rules with Client Scripts, which actually run on the client side.

Full explanation →

MCQmedium

A system administrator wants to add a choice list to a field that shows options depending on the value of another field. Which feature should be used?

A.Reference field with cascading

B.Dependent choices

C.Client Script with GlideAjax

D.UI Policy with onChange

AnswerB

Dependent choices allow a choice field to change its options based on another field's value, configured declaratively.

Why this answer

Dependent choices is a built-in feature that dynamically filters a choice list based on the value of a parent field. Option A (Reference field with cascading) is not a standard ServiceNow feature for choice lists. Option C (Client Script with GlideAjax) could be used but is not the built-in best practice for simple dependencies.

Option D (UI Policy with onChange) can show or hide fields but cannot dynamically populate choice lists.

Full explanation →

MCQhard

You are the ServiceNow administrator for a large enterprise with over 10,000 users. The company uses the Employee Center portal for self-service. Recently, users have reported that when they submit a catalog item, the confirmation page takes over 30 seconds to load, and sometimes they receive a timeout error. The issue only occurs for catalog items that have a workflow attached. The workflows are complex with multiple approval stages and notifications. The server logs show no errors, but the average response time for catalog item submissions with workflows is 45 seconds, compared to 5 seconds for items without workflows. The instance is running on a medium-sized node with default settings. You need to resolve the performance issue without changing the workflow logic or the user interface. What should you do?

A.Disable all approval stages in the workflows

B.Configure the workflows to run asynchronously

C.Upgrade the instance to a larger node size

D.Move the workflows to a separate instance

AnswerB

Asynchronous execution prevents the user interface from waiting for the workflow to complete.

Why this answer

Configuring workflows to run asynchronously decouples the workflow execution from the synchronous HTTP request-response cycle. This means the catalog item submission completes immediately (within seconds), while the workflow runs in the background. This directly addresses the 45-second response time for items with workflows without altering the workflow logic or UI.

Exam trap

The trap here is that candidates often assume performance issues are always solved by scaling up infrastructure (Option C) or by removing features (Option A), rather than recognizing that the default synchronous execution model is the bottleneck.

How to eliminate wrong answers

Option A is wrong because disabling approval stages removes required business logic and does not address the root cause of synchronous workflow execution; it also violates the constraint of not changing workflow logic. Option C is wrong because upgrading to a larger node size may improve overall throughput but does not fix the synchronous blocking behavior that causes the 30-second timeout; the issue is architectural, not resource-based. Option D is wrong because moving workflows to a separate instance does not change the synchronous execution model; the submission request would still wait for the remote workflow to complete, potentially adding network latency.

Full explanation →

MCQmedium

A company has a custom application that automatically updates the CMDB via web services. After a recent update, several CI records were incorrectly modified, causing incorrect relationships. The administrator does not know exactly which web service calls caused the issue. What is the best way to identify the source of the incorrect updates and prevent future occurrences?

A.Enable the 'Data Integrity' feature to log all web service updates.

B.Revert the CMDB to a previous state using a backup.

C.Review the cmdb_ci table audit history to see changes.

D.Restrict web service access to only necessary roles and review logs.

AnswerC

Audit logs capture who or what changed each field, enabling identification of the problematic web service calls.

Why this answer

The cmdb_ci table audit history captures detailed records of all changes made to CI records, including the source of the update (e.g., web service call, user, or script). By reviewing this audit trail, the administrator can identify which specific web service calls modified the CIs incorrectly, even without prior logging enabled. This approach leverages ServiceNow's built-in auditing for CMDB tables, which is enabled by default for critical CI tables.

Exam trap

The trap here is that candidates may confuse the 'Data Integrity' feature with auditing or logging, assuming it captures change history, when in fact it only validates data quality rules and does not record transactional changes.

How to eliminate wrong answers

Option A is wrong because the 'Data Integrity' feature in ServiceNow is designed to detect and report data quality issues (e.g., missing mandatory fields, orphaned CIs) but does not log web service updates or provide a historical record of changes. Option B is wrong because reverting the CMDB to a previous backup would undo all changes, including legitimate updates, and does not help identify the source of the incorrect modifications; it is a reactive measure, not a diagnostic one. Option D is wrong because restricting web service access and reviewing logs is a preventive measure that does not help identify which specific past web service calls caused the issue; it addresses future occurrences but not the immediate need to trace the source of the incorrect updates.

Full explanation →

MCQmedium

An administrator needs to send an email notification to the manager of the caller when an incident is assigned to a specific group. Which combination of notification configuration is correct?

A.Condition: 'Record is inserted'; Recipient: Manager of the assignment group.

B.Condition: 'Assigned to changes to Caller's manager'; Recipient: Caller.

C.Condition: 'State changes'; Recipient: Caller via email client.

D.Condition: 'Assignment group changes to <group>'; Recipient: Caller's manager.

AnswerD

Correct: Fires when group changes and sends to manager.

Why this answer

The requirement is to notify the caller's manager when an incident is assigned to a specific group. The condition 'Assignment group changes to <group>' triggers the notification precisely when the assignment group changes to the target group, and the recipient 'Caller's manager' ensures the email goes to the manager of the person who reported the incident. This matches the exact business need without extraneous conditions or incorrect recipients.

Exam trap

The trap here is that candidates often confuse 'Caller's manager' with 'Manager of the assignment group' or think a generic condition like 'State changes' will suffice, missing the precise condition and recipient required by the scenario.

How to eliminate wrong answers

Option A is wrong because 'Record is inserted' triggers on creation of a new incident, not on assignment to a specific group, and 'Manager of the assignment group' sends the email to the group's manager, not the caller's manager. Option B is wrong because 'Assigned to changes to Caller's manager' is a condition that triggers when the assigned user changes to the caller's manager, which is unrelated to the assignment group change, and the recipient is 'Caller' instead of the caller's manager. Option C is wrong because 'State changes' triggers on any state change (e.g., from New to In Progress), not specifically when the assignment group changes, and 'Caller via email client' sends to the caller, not their manager.

Full explanation →

MCQmedium

An administrator wants to create a dashboard with multiple reports that automatically refresh every 5 minutes. Which feature should be used?

A.Homepage with iframe

B.Dashboard with auto-refresh property

C.Performance Analytics indicator

D.Report scheduling

AnswerB

Dashboards support auto-refresh intervals.

Why this answer

A dashboard in ServiceNow can have its auto-refresh property set to a specific interval, such as every 5 minutes, which automatically refreshes all reports on the dashboard simultaneously. This meets the administrator's requirement without manual intervention or additional scheduling.

Exam trap

The trap here is that candidates often confuse report scheduling (which sends static snapshots) with dashboard auto-refresh (which updates the live view), or mistakenly think an iframe can achieve the same result without understanding its limitations in ServiceNow.

How to eliminate wrong answers

Option A is wrong because a homepage with an iframe embeds external content and does not provide native auto-refresh capability for ServiceNow reports; it would require custom scripting or external page refresh. Option C is wrong because Performance Analytics indicators are designed for tracking KPIs and trends over time, not for refreshing multiple reports on a dashboard at a fixed interval. Option D is wrong because report scheduling sends reports via email or stores them as snapshots, but does not automatically refresh a live dashboard view for users.

Full explanation →

MCQmedium

An administrator needs to create a new CI class for 'Database Instance' that extends the existing 'cmdb_ci' table. Which tool should be used?

A.System Definition > Tables

B.CMDB Data Manager

C.CI Class Manager

D.Studio

AnswerC

CI Class Manager is designed to create and manage CI classes.

Why this answer

The CI Class Manager is the dedicated tool in ServiceNow for creating and managing Configuration Item (CI) classes, including extending existing tables like 'cmdb_ci' to create a new 'Database Instance' class. It provides a guided interface to define class hierarchy, attributes, and relationships specific to CMDB, ensuring proper alignment with the Common Service Data Model (CSDM).

Exam trap

The trap here is that candidates confuse general table creation (System Definition > Tables) with CMDB-specific class creation, not realizing that CI Class Manager enforces CSDM compliance and proper CI lifecycle management.

How to eliminate wrong answers

Option A is wrong because System Definition > Tables is used for creating or modifying database tables in general, not specifically for CMDB CI class hierarchy or CSDM-compliant CI class creation. Option B is wrong because CMDB Data Manager is a tool for importing, exporting, and reconciling CI data, not for defining new CI class structures or extending the cmdb_ci table. Option D is wrong because Studio is an application development environment for building scoped applications and customizing modules, but it is not the recommended or direct tool for creating a new CI class that extends cmdb_ci; that task is specifically handled by CI Class Manager.

Full explanation →

Drag & Dropmedium

Drag and drop the steps to activate a plugin 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

Activating a plugin in ServiceNow requires following the correct sequence: first navigate to the plugin list via System Applications > All, then locate the desired plugin, select it, and finally click the Activate button. Any deviation from this order will result in an error or missing functionality.

Full explanation →

MCQhard

A UI Policy is intended to make a field mandatory when another field equals 'Yes', but the mandatory condition is not working. What is a common cause?

A.UI Policy order is too high

B.Field type is not string

C.UI Policy is set to 'Run script' only

D.Condition script has syntax error

AnswerD

A syntax error will break the condition evaluation, preventing the UI Policy from applying its actions.

Why this answer

A syntax error in the condition script will cause the UI Policy to fail silently. When the script encounters an error (e.g., a missing semicolon, undefined variable, or incorrect operator), the entire condition evaluates to false, so the mandatory field action never triggers. UI Policies execute client-side in the browser, and syntax errors prevent the script from running at all, making the mandatory condition appear non-functional.

Exam trap

The trap here is that candidates often assume a UI Policy with a syntax error will show an error message or that the 'Run script' option (Option C) is the culprit, but in reality, the condition script executes first and a syntax error prevents the entire policy from applying, including mandatory actions.

How to eliminate wrong answers

Option A is wrong because UI Policy order determines the sequence of execution when multiple policies apply to the same field, but a high order does not prevent a policy from running; it only affects priority. Option B is wrong because field type does not affect whether a UI Policy can make it mandatory; UI Policies can set mandatory on any field type (string, choice, reference, etc.) as long as the condition is met. Option C is wrong because 'Run script' only means the policy runs its script but does not apply the 'Mandatory' or 'Visible' actions; however, the condition itself still executes, so a syntax error in the condition script would still break it, and the 'Run script' setting does not cause the mandatory condition to fail.

Full explanation →

MCQmedium

During an import, a transform field mapping uses a script to generate a value. The script runs but the target field is empty. What is the first thing to check?

A.The script returns a value.

B.The field mapping's 'Field name' is correct.

C.The script is in the correct script include.

D.The staging table has the field.

AnswerA

If the script does not return a value, the target field remains empty.

Why this answer

The most common reason a script runs but the target field remains empty is that the script does not return a value. In ServiceNow transform maps, the script must explicitly use the `return` statement to output a value that will be written to the target field. If the script executes but lacks a return, or returns null/undefined, the field will be empty regardless of other correct configurations.

Exam trap

The trap here is that candidates assume the script 'running' means it is correctly producing output, but ServiceNow requires an explicit return value for the mapping to populate the field, and the exam tests this distinction between execution and output.

How to eliminate wrong answers

Option B is wrong because if the field mapping's 'Field name' were incorrect, the import would either fail with a field-not-found error or populate a different field, not leave the target field empty after the script runs. Option C is wrong because the script for a transform field mapping is written directly in the 'Script' field of the mapping, not in a separate Script Include; checking a Script Include is irrelevant. Option D is wrong because the staging table field is only used to store the source value before transformation; the target field being empty is a post-transform issue, not a staging table schema issue.

Full explanation →

MCQeasy

In the CMDB, what is the purpose of the 'cmdb_ci' table?

A.It stores the discovery schedule and probes.

B.It is the base table for all hardware and software CI classes.

C.It contains the CMDB health rules.

D.It stores relationships between configuration items.

AnswerB

cmdb_ci is the parent table for all CI classes.

Why this answer

The 'cmdb_ci' table is the base (or parent) table for all hardware and software Configuration Item (CI) classes in the ServiceNow CMDB. It defines common fields such as name, serial number, and operational status, which are inherited by all child CI tables (e.g., cmdb_ci_server, cmdb_ci_software_product). This design follows a single-table inheritance model, ensuring consistency across all CI types.

Exam trap

The trap here is that candidates often confuse the 'cmdb_ci' base table with the 'cmdb_rel_ci' relationship table, assuming that the base table stores relationships rather than being the parent for all CI classes.

How to eliminate wrong answers

Option A is wrong because discovery schedules and probes are stored in the 'discovery_schedule' and 'discovery_probe' tables, not in 'cmdb_ci'. Option C is wrong because CMDB health rules are stored in the 'cmdb_health_rule' table, which defines conditions for CI health scoring. Option D is wrong because relationships between CIs are stored in the 'cmdb_rel_ci' table, which links two CIs via a relationship type defined in 'cmdb_rel_type'.

Full explanation →

MCQmedium

Refer to the exhibit. A user reports that the category field is not becoming mandatory on the incident form even when priority is set to '3' and the system property 'myapp.high_priority' is set to 'true'. What is the most likely cause?

A.The system property 'myapp.high_priority' is set to 'false'.

B.The condition script uses 'g_form.getValue' which is not available in a UI Policy condition.

C.The UI Policy is set to run on load only, and the priority field change does not trigger re-evaluation.

D.The user must refresh the page after changing priority for the UI Policy to take effect.

AnswerC

Correct: Without the priority field in the UI Policy's 'Fields' list, changing priority does not re-trigger the condition.

Why this answer

UI Policies have a 'Run on load' and 'Run on change' setting. By default, UI Policies run only when the form loads. If the policy is set to run on load only, changing the priority field after the form has loaded will not trigger re-evaluation, so the category field will not become mandatory even when the condition is met.

Exam trap

The trap here is that candidates often assume UI Policies automatically re-evaluate on any field change, but ServiceNow tests the distinction between 'Run on load' and 'Run on change' settings, which is a key nuance in UI Policy behavior.

How to eliminate wrong answers

Option A is wrong because the question states the system property 'myapp.high_priority' is set to 'true', so it is not false. Option B is wrong because 'g_form.getValue' is actually available in UI Policy condition scripts; it is a client-side API that works in UI Policies. Option D is wrong because refreshing the page would reload the form and trigger the UI Policy on load, but the issue is that the policy does not re-evaluate on priority change, not that the user needs to manually refresh.

Full explanation →

MCQeasy

What is the purpose of the 'Operational Status' field on a CMDB CI?

A.To indicate the CI's current operational health.

B.To track the CI's maintenance schedule.

C.To define the CI's business criticality.

D.To record the CI's last discovery date.

AnswerA

Operational Status reflects whether the CI is functioning properly.

Why this answer

The 'Operational Status' field on a CMDB CI in ServiceNow indicates the current operational health of the configuration item, such as whether it is functioning normally, in a degraded state, or down. This field is used to quickly assess the real-time status of a CI, enabling IT operations to prioritize incident response and change management based on the CI's operational condition.

Exam trap

The trap here is that candidates confuse 'Operational Status' with 'Business Criticality' or 'Maintenance Schedule', as all three fields relate to CI management but serve distinct purposes in the CMDB.

How to eliminate wrong answers

Option B is wrong because the 'Operational Status' field does not track maintenance schedules; maintenance schedules are managed via the 'Maintenance Schedule' related list or a separate field on the CI form. Option C is wrong because business criticality is defined by the 'Business Criticality' field, not the 'Operational Status' field, which focuses on technical health rather than business impact. Option D is wrong because the last discovery date is recorded in the 'Last Discovered' field, which is separate from the 'Operational Status' field that reflects the CI's current operational state.

Full explanation →

100

MCQmedium

A company wants to allow managers to approve requests on behalf of their team members using the mobile app. What is the best way to enable this self-service capability?

A.Configure delegation in user preferences so managers can be set as delegates

B.Enable the 'Approval Delegation' feature in the mobile app settings

C.Grant the 'Impersonate' role to managers

D.Assign the 'Delegate' role to all users and managers

AnswerA

Users can set delegates in their preferences, allowing managers to approve on their behalf.

Why this answer

ServiceNow's delegation feature allows users to designate delegates (e.g., managers) to approve requests on their behalf directly from the mobile app. This is configured in user preferences under 'Delegates', enabling a self-service capability without granting elevated roles or modifying app settings.

Exam trap

ServiceNow often tests the distinction between delegation (a user-configured preference for temporary authority) and impersonation (a privileged role for full system access), tempting candidates to choose the more powerful but incorrect impersonation option.

How to eliminate wrong answers

Option B is wrong because there is no 'Approval Delegation' feature toggle in mobile app settings; delegation is managed via user preferences, not app-level settings. Option C is wrong because the 'Impersonate' role allows a user to fully act as another user, which is overly permissive and not intended for approval delegation; it bypasses approval workflows and audit trails. Option D is wrong because there is no 'Delegate' role in ServiceNow; delegation is a user preference setting, not a role assignment.

Full explanation →

101

Multi-Selecteasy

Which THREE are true about Service Portal widgets?

Select 3 answers

A.Widgets must be written in JavaScript only.

B.Widgets can be secured through roles.

C.Widgets can only display data from the Service Portal tables.

D.Widgets can be embedded in other widgets.

E.Widgets use a client controller and server script.

AnswersB, D, E

Widget instances can have role restrictions via the 'Roles' field.

Why this answer

Service Portal widgets can be secured by assigning roles to them. When a widget is configured with a specific role, only users who have that role can see or interact with the widget on the portal. This is done via the 'Roles' field on the widget record, which enforces access control at the widget level.

Exam trap

The trap here is that candidates assume widgets can only use JavaScript or only access Service Portal tables, but ServiceNow's widget architecture is flexible and supports multiple languages and any table access via server-side GlideRecord.

Full explanation →

102

Multi-Selectmedium

Which two of the following are built-in actions in Flow Designer that require no script to configure? (Choose two.)

Select 2 answers

A.Execute a JavaScript script

B.Schedule a flow trigger

C.Create a report

D.Send an email

E.Update a record

AnswersD, E

The Send Email action can be configured with no script.

Why this answer

The Send Email action in Flow Designer is a pre-built, out-of-box action that requires no scripting. It allows you to configure email recipients, subject, and body using a graphical interface, leveraging the platform's notification engine without any JavaScript.

Exam trap

The trap here is that candidates often confuse Flow Designer actions with triggers or modules outside of Flow Designer, such as assuming 'Create a report' is a flow action or that 'Schedule a flow trigger' is an action rather than a trigger.

Full explanation →

103

Multi-Selectmedium

Which TWO actions can an administrator perform using the 'Application Navigator' module (sys_app_module)? (Choose two.)

Select 2 answers

A.Change the order of modules within a menu.

B.Create a UI Policy that shows or hides the module.

C.Define a filter condition for the module's menu.

D.Define a link to a specific URL or report.

E.Set the default view for a form.

AnswersA, D

Order can be set via the 'Order' field.

Why this answer

The 'Application Navigator' module (sys_app_module) allows administrators to reorder modules within a menu by adjusting the 'Order' field. This directly controls the sequence in which modules appear in the application navigator, enabling customization of the user interface hierarchy.

Exam trap

The trap here is that candidates confuse the Application Navigator module (sys_app_module) with other navigational or form configuration tools, such as UI Policies or table-level settings, leading them to select options that are technically valid for other areas but not for sys_app_module.

Full explanation →

104

MCQhard

A large enterprise has deployed ServiceNow for employee onboarding. The onboarding workflow includes several manual tasks, approvals, and automated steps. The workflow is designed to run as the 'System' user. Recently, the workflow stops at a point where it tries to update a record in the HR table, but the update fails. The administrator checks the workflow context and finds that the user running the workflow is 'System', but the HR table has an ACL that restricts write access to the 'hr_integration' role only. The 'System' user does not have this role. The administrator needs to resolve the issue without granting the 'System' user additional roles. What is the best solution?

A.Change the variable assignment level to 'Catalog item' and ensure the variable appears only when the parent option is selected.

B.Create a separate catalog item for users who already have a laptop.

C.Set the variable to read-only so it always shows the default value.

D.Leave the variable as is and add a client script to reset the variable if the user selects 'No'.

AnswerB

Creating a separate catalog item enables a workflow that runs as a user with the 'hr_integration' role, bypassing the ACL restriction without granting extra roles to 'System'.

Why this answer

The provided options do not address the ACL issue described in the stem. The correct solution would be to change the execution context of the workflow step that updates the HR table to a user with the 'hr_integration' role, for example by using a 'Run as' action. None of the given options are valid for this scenario.

Exam trap

The trap here is that candidates may think granting the 'System' user the 'hr_integration' role is the only solution, but the question explicitly prohibits that, and the correct approach is to change the execution context of the workflow or specific actions to a user with the required permissions.

How to eliminate wrong answers

Option B is wrong because creating a separate catalog item does not address the underlying permission issue; it only changes the user interface and does not alter the user context under which the workflow runs. Option C is wrong because setting the variable to read-only does not affect the workflow's ability to update the HR table; it only prevents users from modifying the variable value in the catalog item. Option D is wrong because adding a client script to reset the variable does not change the user context or permissions; the workflow still runs as 'System' and will fail when trying to update the HR table due to the ACL restriction.

Full explanation →

105

Multi-Selectmedium

Which two statements are true about CMDB relationships? (Select two.)

Select 2 answers

A.Relationship types are defined in the cmdb_rel_type table.

B.Relationships are stored in the cmdb_rel_ci table.

C.Relationships can only be created manually.

D.A CI can have only one relationship of a given type.

E.The 'Depends on' relationship is default for all CIs.

AnswersA, B

The cmdb_rel_type table defines all relationship types.

Why this answer

The `cmdb_rel_type` table stores the definitions of all relationship types in the ServiceNow CMDB, such as 'Depends on' and 'Used by'. Each record in this table defines a unique relationship type with its name, direction, and cardinality constraints. This table is the authoritative source for the relationship types available in the system.

Exam trap

The trap here is that candidates often confuse the `cmdb_rel_type` table (which defines relationship types) with the `cmdb_rel_ci` table (which stores actual relationships), and mistakenly think relationships are stored in the type table or that all CIs automatically have a 'Depends on' relationship.

Full explanation →

106

Multi-Selectmedium

Which THREE are valid ways to bring data into a catalog item variable?

Select 3 answers

A.Lookup select box that references a table

B.Workflow context variable

C.Record producer variable mapping

D.Catalog client script on submit

E.Variable default value from a script

AnswersA, C, E

Choices from a lookup select box populate the variable with values from a table.

Why this answer

A Lookup Select Box variable type can be configured to reference a table, allowing the user to select a record from that table, which brings data into the variable. This is a standard way to populate a catalog item variable with data from a ServiceNow table, such as selecting a user from the sys_user table.

Exam trap

The trap here is that candidates often confuse client-side scripts (like on submit) with data population mechanisms, thinking they can bring data into a variable, when in fact they only modify or validate existing variable values after the variable is already populated.

Full explanation →

107

Multi-Selecthard

A CMDB administrator is planning to use the CMDB Data Manager to perform data imports. Which THREE statements about the Data Manager are true? (Select exactly 3)

Select 3 answers

A.It can create relationships between CIs during import.

B.It automatically reconciles imported CIs with existing CIs.

C.It can transform data using transform maps.

D.It can directly import data from external databases.

E.It supports scheduled imports from CSV files.

AnswersA, C, E

Transform maps can populate relationship fields, creating relationships.

Why this answer

The CMDB Data Manager can create relationships between Configuration Items (CIs) during the import process. When importing data, you can specify relationship definitions in the import source or transform map, allowing the Data Manager to automatically link CIs (e.g., 'Runs on', 'Depends on') based on the imported data, which is essential for maintaining a complete and accurate CMDB.

Exam trap

The trap here is that candidates confuse the Data Manager's ability to create relationships during import (which is true) with automatic reconciliation (which is a separate process), leading them to incorrectly select Option B.

Full explanation →

108

MCQmedium

A company has a catalog item 'Travel Authorization' with a workflow that requires approval from the user's manager and the finance department if the travel cost is above $1000. The workflow is set up with two 'Approval - User' activities: one for the manager and one for a finance user. However, when a request with cost $1500 is submitted, only the manager approval is triggered; the finance approval is skipped. The workflow has a condition on the finance approval activity that checks 'variable_cost > 1000'. The variable 'cost' is defined as a monetary value and is being passed correctly. What is the most likely cause?

A.The condition on the finance approval activity uses the variable while the workflow is still in the 'default' stage before variable values are committed.

B.The 'cost' variable has a default value of 0, so the condition never passes.

C.The 'Approval - User' for finance is placed before the manager approval in the workflow.

D.The workflow is configured with a 'Starting Condition' that blocks the finance activity.

AnswerA

The variable may not be fully committed when the workflow first evaluates the condition. Ensure the condition references the request item's variable correctly after submission.

Why this answer

The most likely cause is that the condition on the finance approval activity is evaluated while the workflow is still in the 'default' stage, before the variable values from the catalog item request are committed. In ServiceNow, workflow variables are not populated until the workflow enters the appropriate stage or the variable is explicitly set. Since the condition checks 'variable_cost > 1000' but the variable hasn't been assigned yet, the condition evaluates to false, causing the finance approval to be skipped.

Exam trap

The trap here is that candidates assume variables are immediately available in the workflow, but ServiceNow delays variable commitment until after the default stage, causing conditions to fail silently.

How to eliminate wrong answers

Option B is wrong because if the 'cost' variable had a default value of 0, the condition 'variable_cost > 1000' would still evaluate to false, but the core issue is that the variable is not yet committed, not its default value. Option C is wrong because the order of approval activities does not affect whether a condition is evaluated; the condition on the finance activity is evaluated independently of its position relative to the manager approval. Option D is wrong because a 'Starting Condition' would prevent the entire workflow from starting, not selectively skip a single activity; the workflow is running and the manager approval is triggered, so no starting condition is blocking the finance activity.

Full explanation →

109

MCQeasy

A user cannot see any records in a module. What is the first thing to check?

A.User roles

B.User's browser cache

C.Module active flag

D.ACLs on the table

AnswerA

If the user lacks the role that grants access to the module, they will not see any records.

Why this answer

User roles define the set of permissions and access rights a user has within ServiceNow. If a user cannot see any records in a module, the most fundamental and first check is their role assignment, because without the appropriate role (e.g., 'snc_internal' or a custom role granting read access), the user will have no visibility into any records, regardless of other settings.

Exam trap

The trap here is that candidates often jump to ACLs as the first check, forgetting that roles are the gatekeeper for module access and record visibility in ServiceNow.

How to eliminate wrong answers

Option B is wrong because browser cache issues typically affect UI rendering or form behavior, not the complete absence of records in a module; clearing cache might resolve display glitches but not permission-based invisibility. Option C is wrong because the module active flag controls whether the module appears in the application navigator, not whether records within that module are visible; a deactivated module simply hides the menu entry. Option D is wrong because ACLs (Access Control Lists) on the table control record-level read permissions, but they are evaluated after role-based access; if the user lacks the required role, ACLs are never checked, making role verification the logical first step.

Full explanation →

110

Multi-Selecteasy

A ServiceNow administrator needs to create a form section that is only visible to users with the 'itil' role. Which TWO configuration options can achieve this? (Choose two.)

Select 2 answers

A.Configure a client script to hide the section on load based on the user's role.

B.Set the 'Role' field on the form section to 'itil'.

C.Use a role-based ACL on the table to restrict access to the fields in that section.

D.Apply a UI Policy that sets the section's visible attribute to false for non-itil users.

E.Set the 'Visible' condition on the form section using `g_user.hasRole('itil')`.

AnswersD, E

Correct: A UI Policy can dynamically set a section's visible attribute based on conditions.

Why this answer

A UI Policy can conditionally set the 'visible' attribute of a form section to false based on a condition like `g_user.hasRole('itil')`, effectively hiding the section from non-itil users. Option E is correct because the 'Visible' condition on a form section directly accepts a script expression, and `g_user.hasRole('itil')` evaluates to true for itil users, making the section visible only to them. Both approaches leverage client-side role checking to control section visibility without requiring server-side ACLs or client scripts.

Exam trap

The trap here is that candidates often confuse the 'Role' field on a form section (which does not exist) with the role field on a field or table ACL, or they mistakenly think a client script is a proper configuration for role-based section visibility when UI Policies or the Visible condition are the intended methods.

Full explanation →

111

Multi-Selectmedium

Which three of the following are valid methods to control field visibility on a form based on user input? (Choose three.)

Select 3 answers

A.Data Policies with conditions.

B.Dynamic Form Configuration.

C.Client scripts that set field attributes.

D.Role-based ACLs on the field.

E.UI Policies with visibility actions.

AnswersB, C, E

Dynamic Form Configuration allows conditionally showing or hiding fields in form views.

Why this answer

Dynamic Form Configuration (B) is correct because it allows form fields to be shown, hidden, or made mandatory based on conditions evaluated against user input or other field values, directly controlling field visibility on a form without requiring server-side processing. Client scripts that set field attributes (C) are correct because they can manipulate field visibility by setting the 'visible' attribute dynamically in response to user input. UI Policies with visibility actions (E) are correct because they are client-side scripts that can show or hide fields based on conditions evaluated on the browser.

Data Policies (A) are incorrect because they are server-side enforcement rules that control data integrity and do not directly control form field visibility. Role-based ACLs on the field (D) are incorrect because they control access to the field based on user roles, not visibility based on user input.

Exam trap

The trap here is confusing Data Policies (server-side data enforcement) with UI Policies (client-side visibility control), leading candidates to incorrectly select Data Policies as a method for form field visibility.

Full explanation →

112

MCQmedium

An administrator wants to send an automatic follow-up email to users who have not completed their catalog request within 24 hours. Which feature should be used?

A.Email Notification with condition based on 'Requested for date'.

B.Escalation rule on the requested item.

C.Scheduled job to run a report and send email.

D.Flow Designer with a 'Wait for condition' step.

AnswerD

Flow Designer can wait for a specified time and then send an email.

Why this answer

Flow Designer with a 'Wait for condition' step is correct because it allows the administrator to create a flow that triggers when a catalog request is submitted, waits for a specified duration (e.g., 24 hours), and then checks whether the request is still in an incomplete state. If the condition is met, the flow can automatically send a follow-up email. This approach provides a real-time, event-driven automation without relying on scheduled jobs or external reporting.

Exam trap

The trap here is that candidates often confuse Escalation rules (which are for SLA or assignment escalation) with time-based notifications, or they assume a scheduled job is the only way to implement a delay, missing the event-driven 'Wait for condition' capability in Flow Designer.

How to eliminate wrong answers

Option A is wrong because an Email Notification with a condition based on 'Requested for date' cannot dynamically wait for a 24-hour period; it would only fire at the moment the condition is evaluated, typically upon record creation or update, not after a delay. Option B is wrong because an Escalation rule on the requested item is designed to escalate a record to a higher priority or assignee based on time thresholds, not to send automatic follow-up emails to users. Option C is wrong because a Scheduled job to run a report and send email is a batch-oriented, polling-based approach that introduces latency and inefficiency, whereas the requirement is for a real-time, condition-based follow-up after exactly 24 hours.

Full explanation →

113

Multi-Selecthard

Which TWO are best practices for managing catalog items in a ServiceNow instance?

Select 2 answers

A.Assign each catalog item to exactly one category

B.Test catalog items in a sub-production instance before moving to production

C.Clone production catalog items to test instance for testing

D.Use database views to display catalog item details

E.Use variables to capture dynamic information

AnswersB, E

Testing prevents issues in production.

Why this answer

Testing catalog items in a sub-production instance (e.g., a development or test instance) before moving them to production is a fundamental best practice in ServiceNow. This allows you to validate variable behavior, workflow logic, and UI policies without risking disruption to live users. ServiceNow recommends using update sets or application repositories to promote tested catalog items from a sub-production instance to production.

Exam trap

The trap here is that candidates often assume catalog items must have exactly one category (Option A) due to a misunderstanding of the category assignment model, but ServiceNow allows multiple categories per item, and the exam tests this flexibility.

Full explanation →

114

Matchingmedium

Match each ServiceNow user role to its typical permission.

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

Concepts

Matches

Full access to all records and configurations

Access to ITIL processes like incident, problem, change management

ServiceNow internal use, not assigned to customers

Basic access to create and view own records

Manage service catalog items and categories

Why these pairings

Roles in ServiceNow define user permissions. Admin has full access, ITIL handles ITIL processes, User has basic self-service, Approver can approve requests. Common confusion is mixing admin with approver or user with ITIL.

Full explanation →

115

MCQhard

An administrator inspects the IRE log and sees the exhibit. The IRE created a new CI despite finding a match on serial_number. What is the most likely reason?

A.The identification rule for cmdb_ci_server includes serial_number.

B.The IRE is configured to always create new records regardless of matches.

C.The identification rule for cmdb_ci_server does NOT include serial_number.

D.The existing CI has a different name, so IRE considers it a different CI.

AnswerC

Without serial_number in the rule, the IRE treats it as a new CI.

Why this answer

The IRE uses identification rules to determine which attributes are used for matching CIs. If the identification rule for cmdb_ci_server does NOT include serial_number, then even though a match on serial_number exists, the IRE will not consider it a match and will create a new CI. The IRE only reconciles based on the attributes defined in the identification rule.

Exam trap

The trap here is that candidates assume the IRE automatically uses all unique fields (like serial_number) for matching, but in reality, only the attributes explicitly listed in the identification rule are used for reconciliation.

How to eliminate wrong answers

Option A is wrong because if the identification rule for cmdb_ci_server included serial_number, the IRE would have matched the incoming CI to the existing one and would not have created a new CI. Option B is wrong because the IRE does not have a global setting to always create new records; its behavior is governed by identification and reconciliation rules. Option D is wrong because the IRE does not consider the CI name as a matching attribute unless it is explicitly included in the identification rule; the name alone does not cause the IRE to treat it as a different CI.

Full explanation →

116

MCQhard

A user reports that when they click 'Order Now' on a catalog item, the request is submitted but they receive an error message: 'Item is not available for the requested quantity.' The catalog item has a quantity variable. What is the most likely cause?

A.The item's 'Quantity' field in the record is set to 1.

B.The quantity variable is defined as 'Single line text'.

C.The item has a 'Delivery plan' that restricts quantity.

D.The user does not have the 'order_quantity' role.

AnswerA

If the max quantity is 1, requesting more than 1 gives this error.

Why this answer

The error 'Item is not available for the requested quantity' occurs because the catalog item's 'Quantity' field in the record is set to 1, meaning only one unit of the item can be ordered at a time. When the user attempts to order a quantity greater than 1, the system checks the maximum allowed quantity from the item record and rejects the request. This is a common configuration in ServiceNow where the 'Quantity' field defines the maximum orderable quantity per request.

Exam trap

The trap here is that candidates often confuse the 'Quantity' field on the catalog item record with the quantity variable on the form, or assume the error is related to inventory or roles, when in fact it is a simple maximum quantity enforcement set on the item record itself.

How to eliminate wrong answers

Option B is wrong because defining the quantity variable as 'Single line text' would cause a data type mismatch, but the error message specifically references quantity availability, not a type conversion issue. Option C is wrong because a 'Delivery plan' restricts delivery schedules or fulfillment methods, not the quantity that can be ordered; it would not produce this exact error message. Option D is wrong because there is no 'order_quantity' role in ServiceNow; roles control access to modules or records, not the validation of order quantities against a catalog item's field.

Full explanation →

117

Multi-Selecthard

Which THREE of the following are benefits of using Flow Designer over traditional Workflow for automation in ServiceNow?

Select 3 answers

A.Requires advanced scripting

B.Built-in error handling and retry logic

C.Low-code visual interface

D.Provides better performance than Workflow

E.Can be triggered by multiple event types

AnswersB, C, E

Flow Designer includes error handling actions.

Why this answer

Flow Designer provides built-in error handling and retry logic, which automatically retries failed actions (e.g., REST calls, database operations) based on configurable conditions. This reduces the need for custom error-handling scripts compared to traditional Workflow, where developers must manually implement retry mechanisms using activities like 'Run Script' or 'Conditional' branches.

Exam trap

The trap here is that candidates may confuse 'low-code' with 'no-code' or assume Flow Designer always outperforms Workflow, but ServiceNow does not officially claim universal performance superiority; the exam tests understanding of documented benefits like visual interface, multiple triggers, and built-in error handling.

Full explanation →

118

MCQeasy

A large enterprise has implemented ServiceNow CMDB with multiple discovery sources including Service Mapping, Cloud Management, and manual imports. Over the past six months, the CMDB has grown to over 2 million CI records, and users are reporting that CMDB queries and reports take a long time to load. The administrator checks the database and finds that the cmdb_ci table has over 1.5 million records, including many retired and historical CIs. The average query time for reports on active hardware CIs is 30 seconds. The instance is hosted on a standard mid-range node. The administrator has verified that no duplicate CIs exist and that all CI classes are properly configured. The instance's performance dashboard shows high database contention. Which action should the administrator take first to improve CMDB performance?

A.Request a ServiceNow upgrade to a higher performance tier.

B.Create a new database view that combines cmdb_ci with other tables to improve report efficiency.

C.Disable all discovery sources except Service Mapping to reduce data inflow.

D.Run the 'CMDB - Data Archiving' scheduled job to move retired CIs older than 6 months to the archive table.

AnswerD

Archiving reduces the active table size, directly improving query performance.

Why this answer

The primary issue is high database contention caused by an excessive number of historical and retired CI records in the active cmdb_ci table. Running the 'CMDB - Data Archiving' scheduled job moves retired CIs older than 6 months to the archive table, reducing the active table size and query load. This directly addresses the root cause without requiring infrastructure changes or disabling critical discovery sources.

Exam trap

The trap here is that candidates often jump to scaling the infrastructure (Option A) or modifying discovery (Option C) without recognizing that CMDB performance degradation is typically caused by data bloat in the active table, which is resolved by archiving rather than by hardware or process changes.

How to eliminate wrong answers

Option A is wrong because requesting a ServiceNow upgrade to a higher performance tier treats the symptom (slow queries) rather than the cause (bloated active table), and is an expensive, unnecessary step when data archiving can resolve the issue. Option B is wrong because creating a new database view that combines cmdb_ci with other tables would likely increase query complexity and execution time, worsening performance rather than improving it. Option C is wrong because disabling all discovery sources except Service Mapping would stop data inflow but does nothing to address the existing 1.5 million records causing contention, and would break critical CMDB population processes.

Full explanation →

119

MCQhard

A transform map for importing incidents uses a co-paste field mapping for 'short_description' that references the source field 'caller_id'. The import fails with the error shown. What is the most likely cause?

A.The 'caller_id' field in the target table is read-only

B.The import set does not contain a column named 'caller_id'

C.The target table 'incident' does not have a 'caller_id' field

D.The co-paste function cannot combine more than two fields

AnswerB

The error indicates the source table lacks the field.

Why this answer

The error indicates that the transform map is trying to reference a source field named 'caller_id' via a co-paste field mapping, but the import set table does not contain a column with that name. Co-paste mappings combine source fields from the import set row, so if 'caller_id' is missing from the import set columns, the transform engine cannot find the data and fails. Option B correctly identifies that the import set lacks the required column.

Exam trap

The trap here is that candidates often confuse 'source field' (from the import set) with 'target field' (on the destination table), leading them to incorrectly blame the target table's schema or field permissions instead of recognizing the import set column absence.

How to eliminate wrong answers

Option A is wrong because the error is about a missing source field, not about the target field being read-only; a read-only target field would cause a different error during field assignment. Option C is wrong because the 'caller_id' field is a standard reference field on the Incident table, and the error message does not indicate a missing target field. Option D is wrong because the co-paste function can combine multiple fields (up to 10 by default), and the error is not about exceeding a field limit but about a missing source column.

Full explanation →

120

Multi-Selecteasy

Which TWO of the following are valid ways to add variables to a catalog item?

Select 2 answers

A.Variable Set

B.Catalog Client Script

C.Variable Editor

D.Order Guide

E.UI Policy

AnswersA, C

Variable sets allow adding predefined groups of variables to a catalog item.

Why this answer

Variable Sets are a primary method for grouping and adding multiple variables to a catalog item, allowing reuse across items. Option C is correct because the Variable Editor is the direct interface within a catalog item's record where you define and add individual variables to the item's variable list.

Exam trap

The trap here is that candidates often confuse UI Policies or Catalog Client Scripts with the ability to add variables, when in fact they only modify the behavior of variables that already exist on the catalog item.

Full explanation →

121

MCQhard

An administrator configures a UI Policy to display a warning message when a reference field is empty. The warning message does not appear. The UI Policy is set to run on both load and submit. What is the most likely cause?

A.The condition uses the wrong operator

B.The UI Policy is set to run on submit only

C.The UI Policy is inactive

D.The warning message is not enabled on the UI Policy

AnswerC

An inactive UI Policy will not execute, so no message appears regardless of settings.

Why this answer

An inactive UI Policy will not execute any of its actions, including displaying warning messages, regardless of its configuration to run on load and submit. The UI Policy must be set to active in its property to be evaluated by the platform.

Exam trap

The trap here is that candidates often overlook the 'Active' checkbox on the UI Policy form, assuming that if the policy is configured to run on load and submit, it will automatically execute, but ServiceNow requires the policy to be explicitly set to active.

How to eliminate wrong answers

Option A is wrong because an incorrect operator in the condition would cause the condition to evaluate to false, but the warning message would still appear if the condition were true; the issue here is that the message does not appear at all, indicating the policy is not running. Option B is wrong because the question states the UI Policy is set to run on both load and submit, so it cannot be set to run on submit only; this would contradict the given configuration. Option D is wrong because UI Policies do not have a separate 'enable warning message' toggle; the warning message is defined as an action within the UI Policy, and if the policy is active and conditions are met, the message will display.

Full explanation →

122

MCQhard

An import set transform map has a field mapping that uses a 'Run script' action. The script sets a reference field by querying the target table. However, the import fails with a 'Null reference' error. What is the most likely issue?

A.The script is not using the correct record identifier

B.The target field is read-only

C.The transform map is set to 'Atomic update'

D.The coalesce field is set incorrectly

AnswerA

Script likely fails to find the record, returning null.

Why this answer

The import fails with a 'Null reference' error because the script in the field mapping uses a query that does not find a matching record in the target table, resulting in a null value for the reference field. Option A is correct: the script is likely not using the correct record identifier (e.g., sys_id or a unique field) to locate the target record, so the query returns no results. Option B is incorrect because read-only fields do not cause null reference errors; they prevent field updates.

Option C is incorrect because 'Atomic update' mode is unrelated to reference field errors; it affects how transforms are processed. Option D is incorrect because the coalesce field determines how source rows are matched to target rows, but the error here occurs during field mapping execution, not during coalescing.

Full explanation →

123

MCQeasy

A service desk manager wants to create a report showing the number of incidents resolved within SLA for each assignment group over the last 30 days. Which report type should be used?

A.Bar chart grouped by assignment group with color for SLA status

B.Line chart of daily resolved incidents

C.Bar chart showing total incidents per group

D.Pie chart showing SLA compliance percentage

AnswerA

Shows both group comparison and SLA status per group.

Why this answer

A bar chart grouped by assignment group with color for SLA status allows the manager to see both the count of incidents per group and how many were resolved within versus outside SLA. This directly answers the requirement to show 'the number of incidents resolved within SLA for each assignment group' over the last 30 days.

Exam trap

The trap here is that candidates often pick a chart type that shows either the grouping (Option C) or the SLA compliance (Option D) but miss that the question requires both dimensions simultaneously, leading them to overlook the grouped bar chart with color encoding.

How to eliminate wrong answers

Option B is wrong because a line chart of daily resolved incidents shows a trend over time but does not break down by assignment group or SLA compliance, missing the key grouping requirement. Option C is wrong because a bar chart showing total incidents per group lacks the SLA status dimension, so it cannot distinguish within-SLA from breached incidents. Option D is wrong because a pie chart showing overall SLA compliance percentage aggregates all groups together, failing to provide per-assignment-group breakdown.

Full explanation →

124

MCQhard

A company has a catalog item that allows users to request a new laptop. The item has a variable for 'Laptop Model' which is a reference to the 'cmdb_ci_computer' table. Recently, users have been complaining that they are seeing laptops that are not available (e.g., already assigned or retired). The administrator wants to filter the variable to show only laptops that are in stock and not assigned. Which approach should the administrator take?

A.Add a reference qualifier to the variable that filters by 'install_status' and 'assigned_to' is empty.

B.Configure ACLs to hide assigned laptops from users.

C.Set a default value on the variable to a valid laptop.

D.Create a business rule that deletes assigned laptops from the table.

AnswerA

Reference qualifiers filter the available records in the variable.

Why this answer

A reference qualifier on the variable allows the administrator to define a condition that filters the records shown in the reference field. By setting the qualifier to filter where 'install_status' indicates 'In Stock' and 'assigned_to' is empty, only available laptops are displayed to users. This directly addresses the requirement without altering data or permissions.

Exam trap

The trap here is that candidates may confuse ACLs or business rules as solutions for filtering reference field options, when in fact reference qualifiers are the correct and non-destructive method for controlling which records appear in a reference variable.

How to eliminate wrong answers

Option B is wrong because ACLs control access to records or fields based on user roles, but they do not filter the list of records shown in a reference variable; they would either hide the entire field or prevent access to the table, not dynamically filter based on availability. Option C is wrong because setting a default value only pre-selects a specific laptop; it does not prevent users from seeing or selecting unavailable laptops from the reference list. Option D is wrong because creating a business rule that deletes assigned laptops would permanently remove data from the table, which is destructive and unnecessary; the requirement is only to filter the view, not to delete records.

Full explanation →

125

MCQmedium

An administrator needs to automate the process of sending a welcome email to new users after their account is created in ServiceNow. The process should also create a 'New Hire Orientation' task assigned to the manager. Which automation method should be used to implement this requirement?

A.Flow Designer

B.Scheduled Job

C.Workflow

D.Business Rule

AnswerA

Flow Designer can be triggered on user creation, send emails, and create tasks efficiently.

Why this answer

Flow Designer is the correct choice because it provides a no-code, event-driven automation framework specifically designed for ServiceNow. It can trigger on the 'User Created' event, send a welcome email via the 'Send Email' action, and create a 'New Hire Orientation' task assigned to the manager using the 'Create Record' action, all within a single flow. This aligns with the requirement for real-time, record-based automation without custom scripting.

Exam trap

The trap here is that candidates often choose Business Rule because it runs on record creation, but they overlook that Business Rules are for simple server-side logic, not for orchestrating multi-step automations like sending emails and creating tasks, which is the core requirement.

How to eliminate wrong answers

Option B (Scheduled Job) is wrong because it runs on a time-based schedule, not in response to a record creation event, so it cannot send the welcome email immediately when a new user account is created. Option C (Workflow) is wrong because while it can automate processes, it is a legacy tool that is being phased out in favor of Flow Designer; it requires a workflow context and is less efficient for simple event-driven tasks like this. Option D (Business Rule) is wrong because although it can run on record creation, it is designed for server-side logic and data manipulation, not for orchestrating multi-step automations like sending emails and creating tasks; it would require complex scripted actions and lacks the visual flow capabilities of Flow Designer.

Full explanation →

126

MCQmedium

A company uses ServiceNow CMDB and wants to ensure that CI attribute updates from a discovery tool are not overwritten by manual changes made by administrators. Which configuration best achieves this?

A.Set the CI source to 'Manual' to prevent discovery updates.

B.Create a business rule to prevent updates from discovery.

C.Configure the 'Preserve manual changes' setting in the CMDB CI Class Manager.

D.Disable the reconciliation process for the affected CIs.

AnswerC

This setting ensures that manual changes are not overwritten by automated updates.

Why this answer

The 'Preserve manual changes' setting in the CMDB CI Class Manager ensures that when a CI attribute is manually updated by an administrator, subsequent discovery runs will not overwrite that specific attribute. This setting works at the class level and compares the source of the last update; if the source is 'Manual', the attribute is preserved even if the discovery tool reports a different value. This directly addresses the requirement to prevent discovery from overwriting manual changes without disabling discovery entirely.

Exam trap

The trap here is that candidates often confuse the 'Preserve manual changes' setting with the 'Ignore changes' flag or assume that disabling reconciliation is the only way to stop overwrites, when in fact the setting is a granular, attribute-level protection mechanism built into the CMDB CI Class Manager.

How to eliminate wrong answers

Option A is wrong because setting the CI source to 'Manual' prevents discovery from updating the CI at all, which is too restrictive and would block legitimate automated updates from the discovery tool. Option B is wrong because creating a business rule to prevent updates from discovery would require custom scripting and maintenance, and it is not the recommended or supported approach for preserving manual changes in the CMDB. Option D is wrong because disabling the reconciliation process would stop all CI attribute updates from discovery, not just preserve manual changes, and it would break the intended CMDB data flow and identification/reconciliation rules.

Full explanation →

127

MCQeasy

A company needs to make a field mandatory only when a checkbox is checked. Which feature should the administrator use?

A.Client Script

B.UI Policy

C.Data Policy

D.Business Rule

AnswerB

UI Policies are designed for client-side form behavior, including conditional mandatory fields.

Why this answer

UI Policy is the correct choice because it allows an administrator to make a field mandatory, visible, or read-only based on a condition evaluated on the client side without a server round-trip. When the checkbox is checked, the UI Policy condition triggers the mandatory attribute on the target field, providing immediate user feedback. This is the standard approach for client-side conditional mandatory fields in ServiceNow.

Exam trap

The trap here is that candidates confuse Data Policy (server-side) with UI Policy (client-side), assuming any mandatory rule must be enforced on the server, when in fact the requirement for immediate client feedback dictates a client-side solution.

How to eliminate wrong answers

Option A is wrong because a Client Script runs JavaScript on the client but cannot directly set a field's mandatory attribute; it would require additional code to manipulate the g_form object, which is less efficient and not the intended use for simple mandatory conditions. Option C is wrong because Data Policy enforces mandatory fields on the server side during database operations, which does not provide immediate client-side feedback and requires a server round-trip to evaluate. Option D is wrong because a Business Rule runs server-side after a record is saved, so it cannot make a field mandatory before submission, and it would not provide the real-time client-side behavior needed for a checkbox-driven mandatory field.

Full explanation →

128

Multi-Selecteasy

Which TWO of the following are valid ways to control the visibility of a field on a form for specific users?

Select 2 answers

A.Create a UI Policy that sets the field's 'visible' attribute to false based on user role

B.Create a Data Policy with a read condition

C.Create an ACL with type 'field' and operation 'read' set to 'no access' for unwanted roles

D.Create a Client Script that sets g_form.setVisible() on load

E.Create a Business Rule that hides the field

AnswersA, C

UI Policies run client-side and can modify field visibility.

Why this answer

A UI Policy runs on the client side and can set the 'visible' attribute of a field to false based on conditions such as user role. This directly controls the field's visibility on the form for specific users without affecting server-side access.

Exam trap

The trap here is that candidates often confuse Data Policies (which control mandatory/read-only behavior) with UI Policies (which control visibility), or assume that server-side Business Rules can directly manipulate client-side form visibility without a client-side trigger.

Full explanation →

129

MCQmedium

A company wants to display a custom field on the incident form only when the incident state is 'In Progress'. Which configuration should be used?

A.Modify the Dictionary Override to set a default visibility condition

B.Configure an Access Control Rule (ACL) on the field

C.Create a UI Policy with a condition on state and set field visibility

D.Write a Business Rule that updates the field visibility attribute

AnswerC

UI Policies allow conditional client-side actions like hiding/showing fields.

Why this answer

UI Policies allow you to define a condition (e.g., incident.state == 'In Progress') and then set field-level actions such as making a field visible or mandatory. This is the intended declarative mechanism for controlling field visibility based on form state without writing code.

Exam trap

The trap here is confusing server-side controls (ACLs, Business Rules) with client-side form behavior, leading candidates to select an option that controls data access or server logic instead of UI visibility.

How to eliminate wrong answers

Option A is wrong because Dictionary Overrides are used to modify field-level properties like label or type for a specific table, not to set dynamic visibility conditions based on record state. Option B is wrong because Access Control Rules (ACLs) control data access (read/write permissions), not UI visibility on a form. Option D is wrong because Business Rules run server-side and cannot directly update a field's visibility attribute on the client-side form; visibility is a client-side concern.

Full explanation →

130

MCQeasy

An administrator wants to ensure that when a user deletes a CI, all its relationships are also deleted to maintain data integrity. What should the administrator configure?

A.A cascade delete rule on the relationship table

B.An ACL that denies delete unless relationships are removed first

C.A CMDB health rule that flags orphaned relationships

D.A business rule on the CI table that deletes relationships on delete

AnswerA

Cascade delete rules are designed for this purpose.

Why this answer

A cascade delete rule on the relationship table (sys_cmdb_rel_ci) ensures that when a CI is deleted, all associated relationship records are automatically removed. This maintains referential integrity in the CMDB without requiring custom scripting or manual cleanup.

Exam trap

The trap here is that candidates often choose a business rule (Option D) because it seems logical, but ServiceNow's native cascade delete on reference fields is the correct and simpler approach, avoiding the need for custom scripting.

How to eliminate wrong answers

Option B is wrong because an ACL that denies delete unless relationships are removed first would prevent the deletion entirely, not automate the cleanup, and would require manual intervention. Option C is wrong because a CMDB health rule can only flag orphaned relationships after they exist, not prevent them from occurring. Option D is wrong because a business rule on the CI table that deletes relationships on delete would work but is not the recommended or native approach; cascade delete rules are the built-in, declarative mechanism for this purpose.

Full explanation →

131

MCQeasy

An administrator wants to create a notification that sends an email to the 'Assignment group' members whenever an incident is assigned to that group. Which of the following should the administrator configure in the notification's 'Who will receive' list?

A.Group members (on the record)

B.Caller

C.Assignment group members

D.Assigned user

AnswerC

Correct: Sends to all members of the assignment group.

Why this answer

The 'Assignment group members' option in the notification's 'Who will receive' list dynamically resolves to all users who are members of the group currently populated in the 'Assignment group' field on the incident record. This ensures that when an incident is assigned to a specific group, every member of that group receives the email notification, which matches the administrator's requirement exactly.

Exam trap

The trap here is that candidates confuse 'Group members (on the record)' with 'Assignment group members', not realizing that ServiceNow treats these as separate fields with different notification behaviors, and the question specifically requires notification based on the 'Assignment group' field.

How to eliminate wrong answers

Option A is wrong because 'Group members (on the record)' refers to members of the group that is selected in the 'Group' field (if present), not the 'Assignment group' field; this is a different field and would not trigger based on assignment changes. Option B is wrong because 'Caller' is the user who reported the incident, not the group members who should be notified upon assignment. Option D is wrong because 'Assigned user' sends the notification only to the individual user assigned to the incident, not to the entire group; this would miss notifying other group members.

Full explanation →

132

MCQeasy

A knowledge base article with 'Work in Progress' state is not appearing in the service portal search results. What is the most likely reason?

A.The article has no attachments.

B.The article category is not set.

C.The article is not published.

D.The article is not assigned to a knowledge base.

AnswerC

Only articles in 'Published' state are visible in search.

Why this answer

In ServiceNow, knowledge base articles must have a state of 'Published' to be visible in service portal search results. Articles in 'Work in Progress' or 'Draft' states are intentionally excluded from public-facing searches because they are not yet finalized or approved for end-user consumption. This ensures that only authoritative, reviewed content is accessible to users.

Exam trap

ServiceNow often tests the misconception that missing metadata (like category or attachments) prevents search visibility, but the core requirement is the article's state being 'Published'.

How to eliminate wrong answers

Option A is wrong because attachments are not a requirement for an article to appear in search results; articles without attachments still appear if they are published. Option B is wrong because while a category helps organize articles, it is not a prerequisite for search visibility; an article without a category can still be published and found. Option D is wrong because an article must be assigned to a knowledge base to exist at all; if it were not assigned, it would not be created or stored, but the question states the article exists with a 'Work in Progress' state, so it is already in a knowledge base.

Full explanation →

133

MCQmedium

A catalog item uses a variable that should be mandatory only if the user selects a specific option in a previous variable. Which approach is best?

A.Use a catalog client script with onChange

B.Use a default value

C.Use a variable set

D.Use a UI policy

AnswerD

UI policies allow declarative conditional mandatory, visible, and read-only settings without scripting.

Why this answer

A UI policy is the correct approach because it allows you to make a variable mandatory conditionally based on the value of another variable, without requiring a server round-trip. UI policies run client-side and can show, hide, or set mandatory status on variables dynamically when a specific option is selected in a previous variable.

Exam trap

The trap here is that candidates often confuse catalog client scripts with UI policies, thinking that client scripts are needed for conditional mandatory logic, but UI policies are the correct declarative tool for this specific requirement.

How to eliminate wrong answers

Option A is wrong because a catalog client script with onChange can perform actions when a variable changes, but it cannot directly set the mandatory attribute of another variable; it would require additional scripting to manipulate the UI, whereas a UI policy is the declarative, built-in mechanism for this. Option B is wrong because a default value only pre-populates a field and does not control mandatory behavior based on user selection. Option C is wrong because a variable set is a reusable group of variables, but it does not provide conditional logic to make a variable mandatory based on another variable's value.

Full explanation →

134

MCQeasy

The widget is not displaying the user's groups on the portal. The server script returns the correct data. What is the most likely cause?

A.The response data structure does not match the expected 'groups' property.

B.The $scope variable is not updated correctly.

C.The server script is not invoked because the client controller does not have a 'sp' prefix.

D.The client controller is not using the correct scope.

AnswerA

If the property name differs, the data won't be assigned correctly.

Why this answer

The client-side widget expects the server script to return a data object with a property named 'groups', but the server script is returning the data in a different structure (e.g., an array or a property named 'userGroups'). ServiceNow client controllers use the `c` object to access server response data, and if the property name does not match, the widget will not display the groups even though the server script executes successfully.

Exam trap

The trap here is that candidates often assume the server script is not running or the client controller has a syntax error, when in fact the server returns data correctly but the property name in the response does not match what the client controller expects.

How to eliminate wrong answers

Option B is wrong because `$scope` is not used in ServiceNow Service Portal widgets; client controllers use the `c` (client) object to bind data to the UI, not `$scope`. Option C is wrong because the server script is invoked regardless of the client controller's prefix; the 'sp' prefix is required for client controllers to be recognized by the Service Portal framework, but the server script invocation is not dependent on the client controller's name. Option D is wrong because the client controller does not use a 'scope' in the AngularJS sense; it uses the `c` object, and the issue is about data property mismatch, not scope binding.

Full explanation →

135

MCQmedium

A ServiceNow administrator notices that some users are able to see and request services in the service portal that they should not have access to. Which of the following should the administrator check first?

A.The category's 'Available For' condition.

B.The user's role assignments.

C.The catalog item's 'Available For' condition.

D.The portal's 'Available For' condition.

AnswerC

The 'Available For' condition on the catalog item directly controls who can view and request it.

Why this answer

The catalog item's 'Available For' condition directly controls which users can see and request that specific item in the service portal. Since the issue is that users are seeing services they should not have access to, the most immediate and granular check is the catalog item's availability condition, not broader category or portal settings.

Exam trap

The trap here is that candidates often check user roles first (Option B) because they assume access is role-based, but the 'Available For' condition on the catalog item is the direct control for item visibility and is the first place to look when users see items they shouldn't.

How to eliminate wrong answers

Option A is wrong because the category's 'Available For' condition controls visibility at the category level, but individual catalog items can override or inherit this; the problem is item-specific, not category-wide. Option B is wrong because user role assignments determine overall permissions but do not directly control which catalog items appear in the portal; a user might have the correct roles but still see items if the 'Available For' condition is misconfigured. Option D is wrong because the portal's 'Available For' condition controls access to the entire portal, not individual catalog items; if the portal itself were restricted, the user would not see the portal at all, not just specific items.

Full explanation →

136

Multi-Selecthard

An import set row is being transformed but the target record is not updated. Which two possible causes should the administrator investigate? (Choose two.)

Select 2 answers

A.The staging table's 'Target table' field is set to the wrong table.

B.The transform map's 'Action' field is set to 'Create' instead of 'Create or Update'.

C.The transform script has a syntax error that prevents the update.

D.The transform map has the 'Coalesce' field set but no matching record exists.

E.The import set row has a 'state' value that is invalid.

AnswersB, C

If action is 'Create', it will only create, not update.

Why this answer

The transform map's 'Action' field determines whether the import set row creates a new record or updates an existing one. If set to 'Create', the system will never attempt to update an existing target record, even if a matching record is found. Setting it to 'Create or Update' allows the transform to update the target record when a match exists.

Exam trap

The trap here is that candidates often confuse the 'Coalesce' field with update logic, but coalesce only prevents empty import set values from overwriting existing data, not from preventing updates entirely.

Full explanation →

137

MCQmedium

An administrator wants to improve the performance of a report that aggregates data from a large custom table. Which database administration technique is most effective?

A.Use a glide aggregate query with a group by clause.

B.Create a database view that pre-aggregates the data.

C.Schedule a job to archive old records.

D.Add an index on the table's sys_updated_by field.

AnswerA

GlideAggregate processes the aggregation efficiently on the server.

Why this answer

A glide aggregate query with a GROUP BY clause is the most effective technique because it offloads the aggregation work to the database server, reducing the amount of data transferred to the application tier and minimizing processing overhead. This approach leverages the database's native ability to compute sums, counts, or averages directly on the large custom table, which is far more efficient than retrieving all rows and aggregating in memory.

Exam trap

The trap here is that candidates often confuse a database view (Option B) with a materialized view or pre-aggregated table, but ServiceNow does not support materialized views, so a standard view provides no performance benefit for aggregation.

How to eliminate wrong answers

Option B is wrong because creating a database view that pre-aggregates the data does not improve performance; a view is merely a stored query that runs each time it is accessed, so it does not precompute or cache results, and it still requires scanning the full table. Option C is wrong because scheduling a job to archive old records reduces the table size over time but does not address the immediate performance of aggregating data from the current large table; it is a long-term maintenance strategy, not a direct performance optimization for the report. Option D is wrong because adding an index on the sys_updated_by field would only speed up queries filtering or sorting by that column, but it does not help with aggregation operations like SUM or COUNT, which require full table scans or specialized indexes like columnstore indexes, which ServiceNow does not support.

Full explanation →

138

MCQeasy

A system administrator has added new fields to the Incident table through the dictionary. Users report that they cannot see these fields when they open an incident record. The administrator confirms the fields exist and are correctly configured. What should the administrator check first?

A.Inspect client scripts on the Incident table for hiding logic.

B.Verify the access controls (ACLs) for the new fields.

C.Check the form layout for the Incident table form view.

D.Review the data policy configuration for the table.

AnswerC

Fields must be added to the form layout to appear on the form. This is the most direct and common cause.

Why this answer

The form layout determines which fields are visible on a given form view. Even if fields exist in the dictionary and are correctly configured, they will not appear on the form unless they have been added to the form layout for the specific view (e.g., the default form view). The administrator should check the form layout by navigating to the Incident table's form view and ensuring the new fields are placed on the form.

Exam trap

The trap here is that candidates often jump to ACLs or client scripts as the cause of missing fields, but the most fundamental check is the form layout, which directly controls field visibility on the form.

How to eliminate wrong answers

Option A is wrong because client scripts can hide or show fields dynamically, but the first step should be to verify the form layout, as client scripts are typically used for conditional logic and not for initial field visibility. Option B is wrong because access controls (ACLs) control read/write permissions, not field visibility on the form; users would see the fields but may be unable to interact with them if ACLs restrict access. Option D is wrong because data policies enforce data consistency and validation rules, not field visibility; they would not prevent fields from appearing on the form.

Full explanation →

139

MCQhard

A large organization uses a weekly scheduled report to analyze incident trends. The report queries a database view that joins several tables. The report has filters: ((category=Network OR category=Database) AND priority<=2) OR (assigned_to in (specific group)). The report takes over 30 minutes to run and often times out. The administrator wants to improve performance without altering the report's output. Which action should be taken?

A.Create summary fields on the incident table to pre-calculate counts and sums for the relevant filters.

B.Remove the OR condition and split the report into two separate reports.

C.Increase the report's timeout value to 60 minutes.

D.Add indexes to the fields used in the filters.

AnswerA

Summary fields pre-aggregate data periodically, greatly speeding up report execution for large datasets.

Why this answer

Creating summary fields on the incident table pre-calculates aggregate values for the filters (category, priority, assigned_to), allowing the report to read precomputed data instead of scanning and joining large tables each time. This directly addresses the performance bottleneck without altering the report's output, as summary fields are updated incrementally and maintain the same logical results.

Exam trap

The trap here is that candidates often assume indexing is the universal solution for slow queries, but ServiceNow's summary fields are the designed mechanism for optimizing report performance on complex filters involving joins and aggregations.

How to eliminate wrong answers

Option B is wrong because splitting the report into two separate reports changes the output — the original OR condition produces a combined result set, and two separate reports would require manual merging, altering the report's output. Option C is wrong because increasing the timeout does not improve performance; it only allows the report to fail later, leaving the underlying slow query unchanged. Option D is wrong because adding indexes on filter fields may help with simple lookups but does not address the performance cost of joining multiple tables and aggregating large datasets; indexes are less effective for complex joins and aggregate queries compared to pre-computed summary fields.

Full explanation →

140

MCQeasy

Refer to the exhibit. A scheduled report is configured as shown but does not execute. What is the most likely cause?

A.The time_of_day is set incorrectly.

B.The frequency is set to daily but the report is not scheduled.

C.The report lacks required roles.

D.The state is set to 'ready' instead of 'active'.

AnswerD

Scheduled reports require state='active' to run.

Why this answer

A scheduled report must have its state set to 'active' to execute. The 'ready' state indicates the report is configured and ready to run but is not yet enabled for automatic execution. Only reports in the 'active' state will trigger based on their schedule.

Exam trap

ServiceNow often tests the distinction between 'ready' and 'active' states, as candidates may assume 'ready' means the report is ready to run, but ServiceNow requires the explicit 'active' state for scheduled execution.

How to eliminate wrong answers

Option A is wrong because the time_of_day setting is used to specify when the report runs; an incorrect value would cause it to run at the wrong time, not fail to execute entirely. Option B is wrong because the frequency being set to 'daily' is valid and does not require additional scheduling; the schedule is defined by the frequency and time_of_day fields. Option C is wrong because roles are not required for a report to execute; roles control access to the report, not its scheduling or execution.

Full explanation →

141

MCQmedium

A system administrator needs to allow end users to add a 'Mobile Phone' field to the incident form without modifying the form layout for all users. Which feature should be used?

A.Create a new form section

B.Configure a UI policy

C.Set an ACL to allow field addition

D.Enable personalization on the form

AnswerD

Personalization allows users to customize their own form view by adding or removing fields.

Why this answer

Personalization allows individual users to add fields to a form without affecting the form layout for all users. By enabling personalization on the incident form, the system administrator grants end users the ability to add the 'Mobile Phone' field to their own view of the form, which is stored per user in the sys_user_preference table.

Exam trap

The trap here is that candidates often confuse ACLs (which control data access) with form layout customization, or assume UI policies can add fields, when in fact UI policies only modify existing field properties like visibility or mandatory status.

How to eliminate wrong answers

Option A is wrong because creating a new form section modifies the form layout for all users globally, not just for individual end users. Option B is wrong because a UI policy controls field visibility, mandatory status, or read-only behavior based on conditions, but it does not allow users to add new fields to the form. Option C is wrong because ACLs control access to records and fields (read/write permissions), but they do not provide a mechanism for users to add fields to the form layout.

Full explanation →

142

Multi-Selecteasy

A new administrator needs to view the relationships between CIs. Which TWO tables store information about CI relationships? (Select two.)

Select 2 answers

A.cmdb_ci_service

B.cmdb_rel_type

C.cmdb_rel_ci

D.cmdb_ci

E.cmdb_ci_relationship

AnswersB, C

Stores the types of relationships (e.g., 'Connected to', 'Depends on').

Why this answer

The `cmdb_rel_type` table defines the types of relationships that can exist between configuration items (CIs), such as 'Depends on' or 'Runs on'. Option C is correct because the `cmdb_rel_ci` table stores the actual relationship instances, linking two CIs together with a specific relationship type. Together, these two tables provide the schema and data for CI relationships in the ServiceNow CMDB.

Exam trap

The trap here is that candidates often confuse the `cmdb_ci_relationship` table (which does not exist) with the correct `cmdb_rel_ci` table, or they mistakenly think that `cmdb_ci` itself stores relationship data instead of just CI attributes.

Full explanation →

143

MCQeasy

An organization wants to allow managers to approve requests from their direct reports through the mobile app. Which type of approval rule should be configured?

A.Approval - Manager

B.User approval

C.Role approval

D.Group approval

AnswerA

This rule automatically determines and sends to the manager of the requestor.

Why this answer

The Approval - Manager rule is correct because it automatically routes approval requests to the manager of the requester based on the manager relationship defined in the user record. This rule is specifically designed for scenarios where managers need to approve requests from their direct reports, leveraging the built-in manager hierarchy in ServiceNow.

Exam trap

The trap here is that candidates often confuse 'Approval - Manager' with 'Role approval' because both involve authority, but 'Role approval' does not enforce the manager-report relationship and can be assigned to any user with the role, leading to incorrect routing.

How to eliminate wrong answers

Option B (User approval) is wrong because it requires specifying a particular user as the approver, which does not dynamically resolve to the requester's manager and would require manual configuration for each request. Option C (Role approval) is wrong because it routes approval to any user with a specified role, not specifically to the requester's manager, which could allow unauthorized users to approve requests. Option D (Group approval) is wrong because it routes approval to a group, not to an individual manager, and does not enforce the direct report relationship.

Full explanation →

144

MCQeasy

Refer to the exhibit. A UI Policy is configured with the above condition to make the 'resolution_notes' field mandatory when the variable 'state' is 2. When state is set to 2, the field is still not mandatory. What is the most likely issue?

A.The field is not in the form layout

B.The condition uses 'state' instead of 'variables.state'

C.The UI Policy is inactive

D.The UI Policy is set to run on submit only

AnswerB

In a catalog UI Policy, variables are accessed using the 'variables' prefix; 'state' is not a valid variable reference.

Why this answer

In ServiceNow UI Policies, when referencing a variable on a catalog item or record producer, you must prefix the variable name with 'variables.' (e.g., 'variables.state') because the condition is evaluated against the variable map, not the field directly. Using 'state' alone refers to the field on the current table (e.g., the task table), which is not the same as the catalog variable 'state'. Therefore, the condition never matches when the variable is set to 2, so the UI Policy does not fire.

Exam trap

ServiceNow often tests the distinction between table fields and catalog variables, and the trap here is that candidates assume 'state' refers to the variable because it is displayed on the form, but without the 'variables.' prefix, the condition references the underlying table field instead.

How to eliminate wrong answers

Option A is wrong because if the field were not in the form layout, it would not appear at all, but the question states the field is present yet not mandatory. Option C is wrong because an inactive UI Policy would never run, but the question implies the policy is configured and expected to work; the issue is a condition mismatch, not inactivity. Option D is wrong because a UI Policy set to 'run on submit only' would still enforce mandatory on submit, but the field is not mandatory at any point when state is 2, indicating the condition never evaluates to true.

Full explanation →

145

MCQhard

Refer to the exhibit. A server provisioning request is in progress. The network configuration task is waiting for the VM creation task to provide an IP address, but no IP is passed. What is the most likely cause?

A.The IP address is manually entered by the VM team and they forgot to update it.

B.The network team does not have access to the VM task output.

C.The VM creation task did not run successfully despite being closed complete.

D.The flow did not capture the output variable from the VM creation task and pass it to the network task.

AnswerD

Full explanation →

146

Multi-Selecthard

Which TWO conditions must be true for an SLA to start tracking on an incident? (Choose two.)

Select 2 answers

A.The SLA definition is set to Active

B.The incident is assigned to a group

C.The incident is in a state of 'New'

D.The incident meets the SLA condition defined on the definition

E.The SLA definition has a business schedule attached

AnswersA, D

An inactive SLA definition will not start tracking.

Why this answer

An SLA definition must be set to 'Active' for it to start tracking on an incident. Only active SLA definitions are evaluated and applied to records; inactive definitions are ignored by the system. This ensures that only intended and configured SLAs are enforced.

Exam trap

The trap here is that candidates often confuse the 'Active' flag with the 'Start condition' or assume that an incident must be in a specific state like 'New' for an SLA to begin, when in fact the condition is fully customizable.

Full explanation →

147

Multi-Selectmedium

Which TWO statements about ServiceNow CMDB identification and reconciliation are correct?

Select 2 answers

A.The 'Source' field on a CI can be set per attribute.

B.The Identification and Reconciliation (IRE) engine processes incoming CI data.

C.Reconciliation rules are used to identify duplicate CIs.

D.Reconciliation rules define which source has priority for updating CI attributes.

E.The CMDB automatically deletes duplicate CIs when detected.

AnswersB, D

The IRE handles identification and reconciliation of CI data.

Why this answer

The Identification and Reconciliation (IRE) engine is the ServiceNow component responsible for processing incoming CI data from sources like Discovery, Service Mapping, or integrations. It applies identification rules to determine if a CI already exists and reconciliation rules to resolve attribute conflicts, ensuring data integrity in the CMDB.

Exam trap

The trap here is that candidates often confuse the roles of identification rules (which find duplicates) with reconciliation rules (which resolve attribute conflicts), leading them to incorrectly select option C as correct.

Full explanation →

148

MCQmedium

Refer to the exhibit. An administrator sets the system properties as shown. What is the result?

A.It decreases security by disabling HTML escaping in UI.

B.It increases security by escaping all text in UI.

C.It enables cross-site scripting protection.

D.It has no effect on security.

AnswerA

Disabling HTML escaping allows malicious scripts to be rendered, increasing XSS risk.

Why this answer

Disabling HTML escaping in UI system properties (e.g., glide.ui.escape_text) means user-supplied input is rendered as raw HTML. This directly reduces security by making the instance vulnerable to cross-site scripting (XSS) attacks, as malicious scripts in input fields will not be escaped before display.

Exam trap

ServiceNow often tests the misconception that disabling a security feature like HTML escaping somehow 'enables' protection or has no effect, when in reality it removes a critical XSS safeguard.

How to eliminate wrong answers

Option B is wrong because disabling HTML escaping does not increase security; it removes a key XSS defense. Option C is wrong because disabling HTML escaping actually weakens cross-site scripting protection, not enables it. Option D is wrong because disabling HTML escaping has a significant negative effect on security by allowing stored XSS vectors to execute.

Full explanation →

149

Multi-Selectmedium

Which TWO best practices should be followed when designing forms in ServiceNow? (Choose two.)

Select 2 answers

A.Use a consistent order of fields across similar tables

B.Group related fields into sections with clear headings

C.Hide mandatory fields using UI policies to reduce clutter

D.Use many-to-many fields instead of reference fields for better relationships

E.Include as many fields as possible on one form to minimize navigation

AnswersA, B

Consistency reduces cognitive load.

Why this answer

Options A and B are correct. A: Using a consistent field order across similar tables improves user experience and makes forms predictable. B: Grouping related fields into sections with clear headings enhances form readability and helps users find information quickly.

C is incorrect because mandatory fields should always be visible, not hidden via UI policies, as hiding them can cause submission errors. D is incorrect because many-to-many fields are not inherently better than reference fields; the choice depends on the relationship requirements, and using many-to-many fields incorrectly can complicate data model. E is incorrect because including too many fields on one form can overwhelm users and degrade performance.

Full explanation →

150

MCQmedium

A catalog item has a variable 'category' (choice) and 'subcategory' (select box). When a user selects 'hardware' for category, the subcategory dropdown shows laptop and desktop. When 'software' is selected, it shows Operating System and Office Suite. However, users report that after selecting category, the subcategory dropdown does not update. What is the most likely cause?

A.The 'subcategory' variable is not a select box but a reference field

B.The script returns on isLoading, which prevents the update

C.The script incorrectly uses g_form.getControl instead of g_form.setOptions on the variable

D.The onChange event is not triggered because the category field is a choice list

AnswerC

The correct method is g_form.setOptions('subcategory', ...) to update the choice list.

Why this answer

The script must use `g_form.setOptions()` to dynamically update the choices of a select box variable (subcategory) based on the selected category. Using `g_form.getControl()` only retrieves the DOM element but does not modify the variable's options; it is typically used for UI manipulation like disabling or styling, not for updating choice lists. The failure to call `setOptions` means the subcategory dropdown never receives the new list of options, so it remains unchanged.

Exam trap

The trap here is that candidates often assume `g_form.getControl` can be used to set options by manipulating the DOM directly, but ServiceNow requires the specific `setOptions` API to update variable choices, and using `getControl` will silently fail to update the dropdown.

How to eliminate wrong answers

Option A is wrong because if the subcategory were a reference field, the behavior would differ (e.g., it would use a table lookup), but the question states it is a select box, and the issue is about updating options, not field type. Option B is wrong because returning on `isLoading` would prevent the script from running entirely during initial page load, but the user is interacting after the page is loaded, so the onChange event would still fire; the problem is specifically about the script logic, not the loading state. Option D is wrong because choice list fields do trigger onChange events when the user selects a value; the event is not suppressed by the field type itself, so the script should execute.

Full explanation →

ServiceNow Certified System Administrator CSA (SNOW-CSA) — Questions 76–150