Courseiva

ServiceNow Certified System Administrator CSA (SNOW-CSA) — Questions 376–450

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

Take a mock examExam hub
Page 5

Page 6 of 7

Page 7
376
Multi-Selectmedium

Refer to the exhibit. A ServiceNow administrator has created an SLA definition for critical incidents. Which TWO statements accurately describe the behavior of this SLA?

Select 2 answers
A.The SLA will reset if the incident priority changes to a higher value.
B.The SLA will start when an incident with priority 1 is created.
C.The SLA will pause when the incident is placed on hold (state=3).
D.The SLA applies to incidents with priority 1 and priority 2.
E.The SLA will stop when the incident state is set to 6 (Resolved).
AnswersB, E

The start condition is 'priority=1'. Correct.

Why this answer

The SLA definition is configured to start when an incident is created with priority 1, as indicated by the 'Start condition' set to 'Priority is 1' and 'Start type' set to 'Created'. Option E is correct because the 'Stop condition' is set to 'State is 6 (Resolved)', which means the SLA timer will stop once the incident reaches the Resolved state.

Exam trap

ServiceNow often tests the misconception that an SLA automatically pauses on hold or resets on priority escalation, but in ServiceNow, these behaviors require explicit conditions to be configured in the SLA definition.

Full explanation →
377
MCQeasy

A user wants to add a shortcut to an often-used module on their application navigator. Which feature should they use?

A.Add the module to the 'Configurable Workspace'
B.Right-click the module and select 'Create Favorites'
C.Right-click the module and select 'Personalize'
D.Use the 'Personalize Form' option from the hamburger menu
AnswerB

Favorites provide easy access to frequently used modules.

Why this answer

To add a shortcut to a frequently used module on the application navigator, users can right-click the module and select 'Create Favorites'. This adds the module to their favorites list, which appears at the top of the navigator for quick access. Option A is incorrect because 'Configurable Workspace' is a different interface and not used for adding navigator shortcuts.

Option C is incorrect because 'Personalize' allows users to hide modules but does not create shortcuts. Option D is incorrect because 'Personalize Form' is used to customize form layouts, not the navigator.

Full explanation →
378
Multi-Selectmedium

Which TWO conditions must be met for a business rule to execute on a table? (Choose TWO.)

Select 2 answers
A.The business rule must be associated with a table.
B.The condition script must evaluate to true (or be empty).
C.The business rule must have at least one role specified in the 'Condition' tab.
D.The business rule must have an 'Advanced' script defined.
E.The business rule must have an order less than 100.
AnswersA, B

Business rules are table-specific.

Why this answer

A business rule in ServiceNow is always scoped to a specific table; it cannot execute without being associated with one. The rule's 'Table' field defines the database table on which the rule triggers, and the platform checks this association before any execution logic runs.

Exam trap

The trap here is that candidates often confuse optional configuration fields (like roles or advanced scripts) with mandatory requirements, leading them to select options C or D as necessary conditions for execution.

Full explanation →
379
MCQmedium

A large enterprise uses ServiceNow for IT Service Management. They have recently configured SLA definitions for incident management with a 4-hour resolution time during business hours (Monday-Friday, 8 AM to 6 PM, excluding holidays). The SLA is triggered when an incident is created with priority=2 and assigned to the 'Hardware Support' group. After one week, the IT manager notices that some priority=2 incidents assigned to 'Hardware Support' are not showing any SLA timer. Upon investigation, you find that the incidents were created on weekends and the SLA condition includes 'Assigned to group is Hardware Support'. The SLA definition has 'Start condition' set to 'State changes to In Progress' and 'Pause condition' set to 'State changes to On Hold'. The incidents were created with state 'New' and then assigned to the group, but they remain in 'New' state. How should you fix the issue so that the SLA starts correctly?

A.Remove the pause condition so the SLA continues even when on hold
B.Change the start condition to trigger on incident creation or when assigned to group
C.Update the condition to include 'Assigned to group is Hardware Support AND Priority is 2'
D.Modify the SLA schedule to include weekends
AnswerB

The SLA should start when the incident meets the criteria, regardless of state.

Why this answer

The SLA start condition is currently set to 'State changes to In Progress', but the incidents remain in 'New' state after being assigned to the group. Since the SLA is not starting, you need to change the start condition to trigger on incident creation or when assigned to the group, ensuring the SLA timer begins even if the state does not change to In Progress.

Exam trap

The trap here is that candidates focus on the pause condition or schedule, missing that the SLA never starts because the start condition is tied to a state change that never occurs.

How to eliminate wrong answers

Option A is wrong because removing the pause condition would not fix the issue; the SLA never starts because the start condition is not met, and pausing is irrelevant when the timer hasn't begun. Option C is wrong because the condition already includes 'Assigned to group is Hardware Support' and priority=2 is part of the SLA definition; updating the condition to include both again does not address the start condition problem. Option D is wrong because the SLA schedule defines business hours and excluding weekends is correct for the 4-hour resolution time; modifying it to include weekends would change the SLA's intended behavior and not fix the start condition issue.

Full explanation →
380
MCQhard

Refer to the exhibit. A flow is configured as shown. When will this flow trigger?

A.On every update of a request item regardless of stage.
B.Only on update when stage changes to approved.
C.On insert or update when stage is submitted or approved.
D.Only on insert with stage submitted.
AnswerC

The record trigger fires on insert and update when the condition is met.

Why this answer

The flow trigger configuration shown in the exhibit specifies both 'Insert' and 'Update' as trigger conditions, and the stage condition is set to 'Stage is submitted' OR 'Stage is approved'. This means the flow will execute when a record is inserted with stage 'submitted' or when an existing record is updated to either 'submitted' or 'approved' stage.

Exam trap

ServiceNow often tests the distinction between 'trigger on update when condition is met' versus 'trigger on update when condition changes to', and candidates mistakenly assume the flow only fires when the stage changes to a specific value, rather than when the record is updated and the stage matches the condition at that moment.

How to eliminate wrong answers

Option A is wrong because the flow does not trigger on every update regardless of stage; it only triggers when the stage condition (submitted or approved) is met, not on arbitrary field updates. Option B is wrong because the flow triggers on both insert and update, not only on update, and it triggers when stage changes to 'submitted' as well as 'approved', not exclusively to 'approved'. Option D is wrong because the flow triggers on both insert and update, not only on insert, and it triggers for stage 'approved' in addition to 'submitted'.

Full explanation →
381
MCQhard

An organization has a Service Level Agreement (SLA) defined on the Incident table with a condition of 'Category is Network' and a duration of 4 hours. The SLA is triggered when the incident state changes from 'New' to 'In Progress'. A network incident is created and assigned to the Network Support group. The incident state is changed to 'In Progress' immediately. After 3 hours, the incident is resolved. However, the SLA shows a breach despite the resolution being within 4 hours. What is the most likely cause?

A.The SLA stop condition is set to 'State is Resolved', but the SLA was paused due to a schedule (e.g., after-hours pause) and the pause time was not counted, causing the actual working time to exceed 4 hours.
B.The SLA is assigned to the Network Support group, but the assignment group was changed during the incident.
C.The SLA duration is defined in business hours, and the incident was created after business hours, so the elapsed time counted only business hours, making the 4-hour window longer in real time.
D.The SLA condition 'Category is Network' was not evaluated correctly because the category field was updated after the SLA was triggered.
AnswerA

If the SLA has a schedule that pauses during non-business hours, the elapsed business time may exceed 4 hours even if real time is less.

Why this answer

The most likely cause is that the SLA stop condition is set to 'State is Resolved', but the SLA timer was paused due to a schedule (e.g., after-hours) at the time the incident was resolved. Because the timer was paused, the stop condition was not evaluated immediately. When the schedule resumed, the working timer continued to run, and by the time the stop condition was evaluated, the accumulated working time had already exceeded the 4-hour duration, resulting in a breach.

In ServiceNow, SLA timers that are paused do not trigger stop conditions until they resume, which can cause breaches even when the incident is resolved within the expected real-time window.

Exam trap

The trap here is that candidates assume the SLA timer runs continuously from trigger to stop, ignoring the impact of schedules and pause conditions that can cause a breach even when the actual working time is within the defined duration.

How to eliminate wrong answers

Option B is wrong because changing the assignment group does not affect the SLA timer or breach calculation unless the SLA definition is scoped to a specific group and the group change triggers a re-evaluation, but the scenario does not indicate that. Option C is wrong because if the SLA duration is defined in business hours, the 4-hour window would be longer in real time, not shorter, so resolving in 3 real hours would not cause a breach. Option D is wrong because the SLA condition 'Category is Network' is evaluated when the SLA is triggered; updating the category field after the trigger does not retroactively invalidate the SLA, as the condition is checked at the time of trigger.

Full explanation →
382
MCQmedium

You are responsible for the CMDB at a large enterprise. The CMDB is used for change management and incident management. Recently, during a major incident, it was found that several critical CIs were missing from the CMDB, causing delays in troubleshooting. Further analysis reveals that the Discovery probes were not running on those devices due to schedule conflicts. You need to ensure that all critical devices are discovered regularly. What is the most effective solution?

A.Manually add the missing CIs and set a reminder to check every week.
B.Use horizontal discovery to prioritize critical devices.
C.Create a dedicated Discovery schedule for critical devices with a higher frequency.
D.Increase the frequency of Discovery schedules for all devices.
AnswerC

A dedicated schedule ensures critical devices are discovered consistently regardless of other schedules.

Why this answer

Creating a dedicated Discovery schedule for critical devices ensures they are discovered at a higher frequency without being affected by schedule conflicts that impact the general discovery schedule. This approach guarantees that critical CIs are consistently updated in the CMDB, which is essential for effective change and incident management. By isolating critical devices into their own schedule, you avoid the overhead of increasing frequency for all devices while meeting the specific requirement for regular discovery of critical assets.

Exam trap

The trap here is that candidates may confuse 'horizontal discovery' (which expands discovery scope) with 'prioritization' or 'scheduling,' leading them to select Option B, when in fact horizontal discovery does not address frequency or schedule conflicts.

How to eliminate wrong answers

Option A is wrong because manually adding missing CIs and setting a weekly reminder is a reactive, labor-intensive approach that does not address the root cause of schedule conflicts and does not ensure ongoing, automated discovery of critical devices. Option B is wrong because horizontal discovery is a pattern used to discover devices across multiple network segments or IP ranges, not a mechanism to prioritize or schedule discovery for specific critical devices; it does not resolve schedule conflicts or guarantee regular discovery. Option D is wrong because increasing the frequency of Discovery schedules for all devices would unnecessarily consume system resources and network bandwidth, and it may still not resolve schedule conflicts if the same schedule is shared; it is not a targeted solution for critical devices.

Full explanation →
383
MCQeasy

A catalog item has a variable 'Country' and another 'State'. The State variable should be mandatory only when Country is 'USA'. What is the most efficient way to achieve this?

A.Catalog UI policy with condition on Country
B.Workflow with a 'Set Mandatory' activity
C.Variable set with mandatory condition
D.Catalog client script on Country's onChange event
AnswerA

UI Policy actions include setting mandatory based on conditions, which is clean and efficient.

Why this answer

The most efficient way is to use a Catalog UI Policy (Option A). A Catalog UI Policy can set the mandatory attribute of a variable based on a condition on another variable, such as making 'State' mandatory when 'Country' equals 'USA'. This is declarative and requires no scripting.

Option B (Workflow with a 'Set Mandatory' activity) acts after submission and cannot make a field mandatory before submission. Option C (Variable set with mandatory condition) is for grouping variables and does not enforce mandatory conditions. Option D (Catalog client script on Country's onChange event) is possible but requires more coding and is less supportable than a UI Policy.

Full explanation →
384
MCQmedium

A user wants to view a daily trend of incidents created over the past month. Which report type is most appropriate?

A.Bar chart grouped by day
B.List report
C.Pie chart
D.Line chart with date series on x-axis and count on y-axis
AnswerD

Line chart with date series on x-axis and count on y-axis: This is the most appropriate report type for viewing a daily trend, as it clearly shows how the number of incidents changes over the month.

Why this answer

A line chart with date series on the x-axis and count on the y-axis is the most appropriate report type for viewing a daily trend of incidents over the past month. Line charts are specifically designed to display data points over time, making trends clearly visible. While a bar chart could also show daily counts, line charts are more effective for trend analysis.

List reports show raw data in tabular form and do not visualize trends. Pie charts are unsuitable because they represent proportions at a single point in time.

Exam trap

Candidates may confuse 'report type' with 'chart type' and incorrectly select a list report, thinking it can effectively display trends. However, list reports are for tabular data, not visual trend analysis.

How to eliminate wrong answers

Option A is wrong because a bar chart grouped by day is a visual representation, but the question asks for a report type, not a chart type; ServiceNow list reports can display grouped data without requiring a chart. Option C is wrong because a pie chart shows proportions of a whole at a single point in time, not a trend over time. Option D is wrong because a line chart with date series on x-axis and count on y-axis is a chart type, not a report type; ServiceNow reports can include charts, but the most appropriate report type for viewing a trend is a list report with grouping.

Full explanation →
385
MCQmedium

A CMDB administrator runs a report and finds that the count of CIs in a certain class is unexpectedly low. They suspect that some CIs were deleted accidentally. How can they verify this?

A.Check the sys_audit table for delete records.
B.Query the sys_archive table.
C.Use the CMDB Rollback feature.
D.Restore from backup.
AnswerA

sys_audit records all deletions, providing user and timestamp.

Why this answer

The sys_audit table records all insert, update, and delete operations on CMDB CIs. By querying this table for records with the operation type 'delete' and the affected CI class, the administrator can confirm whether CIs were deleted and identify when and by whom. This is the standard method for auditing historical changes in ServiceNow.

Exam trap

The trap here is that candidates confuse the sys_archive table (which stores retired CIs) with the sys_audit table (which logs deletions), leading them to choose Option B instead of the correct audit trail approach.

How to eliminate wrong answers

Option B is wrong because the sys_archive table stores archived (retired) CIs, not deleted records; deletion removes the record entirely, whereas archiving preserves it. Option C is wrong because the CMDB Rollback feature restores a CI to a previous state from a snapshot, but it does not provide a log of deletions or verify that deletions occurred. Option D is wrong because restoring from backup is a disaster recovery procedure that would overwrite current data and is not a targeted method to verify specific accidental deletions.

Full explanation →
386
MCQhard

A user reports that the 'My Tasks' module they frequently use has disappeared from the left navigation. Other users can still see it. What is the most likely cause?

A.The user accidentally used 'Personalize' and hid the module from their navigation
B.A system property was changed that hides the module for all users
C.The module was deleted from the application menu by an admin
D.The user's role was changed and they no longer have access to the module
AnswerA

Users can right-click on a module and choose 'Personalize' to hide it, which only affects their own view.

Why this answer

The 'Personalize' feature in ServiceNow allows users to hide modules from their own left navigation without affecting other users. When a user right-clicks a module and selects 'Personalize', they can choose to hide it, which removes it only from their view. Since other users can still see the module, this indicates a user-specific change rather than a global or role-based one.

Exam trap

ServiceNow often tests the distinction between user-specific personalization and global or role-based changes, and the trap here is that candidates may assume a role change or admin action is the cause when the symptom is isolated to a single user.

How to eliminate wrong answers

Option B is wrong because a system property change would affect all users, not just one, and the question states other users can still see the module. Option C is wrong because deleting the module from the application menu by an admin would remove it for all users, not just one. Option D is wrong because if the user's role was changed and they lost access, the module would be hidden for them, but other users with the same role would also be affected unless the role change was unique to that user; however, the most likely cause given the user-specific nature is the Personalize feature, not a role change.

Full explanation →
387
Multi-Selecthard

A company wants to ensure that only authorized changes to the CMDB are allowed. Which THREE of the following mechanisms can help enforce this?

Select 3 answers
A.The Identification and Reconciliation Engine (IRE)
B.CMDB Health Definitions with remediation tasks
C.Scheduled Discovery jobs
D.Access Control Lists (ACLs) on CMDB tables
E.Business rules on the cmdb_ci table
AnswersB, D, E

Health rules can detect and correct unauthorized changes.

Why this answer

CMDB Health Definitions can include remediation tasks that automatically or manually enforce compliance by correcting unauthorized changes to CI attributes. These tasks are triggered when a health score falls below a threshold, ensuring that only authorized modifications persist in the CMDB.

Exam trap

The trap here is that candidates often confuse the ServiceNow IRE's role in data reconciliation with change authorization, or assume that ServiceNow Discovery jobs inherently enforce change control, when in fact neither mechanism validates whether a change is authorized before applying it.

Full explanation →
388
MCQhard

An admin has set up an SLA on the Incident table with a condition 'Priority = 1' and a duration of 1 hour. The SLA is triggered when the incident state becomes 'In Progress'. The SLA definition includes a business schedule that only counts business hours (9 AM to 5 PM, Monday-Friday). An incident with Priority 1 is created at 4:30 PM on Friday and state is changed to 'In Progress' at 4:45 PM. At what time will the SLA breach if it is not resolved?

A.9:45 AM Monday.
B.5:45 PM Friday.
C.4:45 PM Saturday.
D.4:45 PM Monday.
AnswerA

Correct calculation based on business hours.

Why this answer

The SLA has a duration of 1 hour but uses a business schedule that only counts hours between 9 AM and 5 PM, Monday through Friday. The incident entered 'In Progress' at 4:45 PM on Friday, so only 15 minutes of business time remain that day (4:45 PM to 5:00 PM). The remaining 45 minutes of SLA duration must be fulfilled starting Monday at 9:00 AM, pushing the breach time to 9:45 AM Monday.

Exam trap

The trap here is that candidates forget to account for the partial business hour consumed on Friday and instead assume the entire SLA duration starts fresh on Monday, leading them to pick 4:45 PM Monday.

How to eliminate wrong answers

Option B is wrong because it ignores the business schedule and assumes the SLA counts all calendar hours, which would incorrectly place the breach at 5:45 PM Friday. Option C is wrong because it incorrectly assumes the SLA runs through Saturday, but the business schedule excludes weekends entirely. Option D is wrong because it assumes the SLA pauses entirely over the weekend and resumes at 9:00 AM Monday, but fails to account for the 15 minutes of business time already consumed on Friday, leading to a breach at 4:45 PM Monday instead of the correct 9:45 AM Monday.

Full explanation →
389
MCQeasy

A ServiceNow administrator needs to create a report that shows all incidents with a priority of '1 - Critical' that have been assigned to the 'Hardware' assignment group. The report should only include incidents that were created in the last 30 days. Which approach should the administrator take to create this report?

A.Create a report using the 'Tasks' table, filter by 'Incident' and then apply the conditions for priority, assignment group, and created on.
B.Create a report using the 'Incidents' module, add a condition for 'Priority equals 1 - Critical' AND 'Assignment group equals Hardware' AND 'Created on is relative today - 30 days'.
C.Create a report using the 'Assignment groups' module, then filter incidents with priority critical.
D.Create a report using the 'Incidents' module, add a condition for 'Priority equals 1 - Critical' AND 'Assignment group equals Hardware', then use the 'Created on' condition with 'On or after (relative) today - 30 days'.
AnswerD

Correctly uses the Incidents module, proper conditions, and the correct relative date condition.

Why this answer

It uses the 'Incidents' module (which automatically restricts the report to the Incident table) and applies the correct condition syntax for a relative date range: 'On or after (relative) today - 30 days'. This ensures only incidents created within the last 30 days are included, while the other conditions filter for priority '1 - Critical' and assignment group 'Hardware'.

Exam trap

The trap here is that candidates often confuse the 'Created on is relative' condition (which does not exist) with the correct 'On or after (relative)' syntax, or they mistakenly use the 'Tasks' table thinking it will automatically filter to incidents, when in fact it requires an explicit 'Type = Incident' condition.

How to eliminate wrong answers

Option A is wrong because using the 'Tasks' table would include all task types (e.g., incidents, problems, changes) and requires an additional filter for 'Incident', which is unnecessary and can lead to performance issues or inclusion of unintended records. Option B is wrong because 'Created on is relative today - 30 days' is not a valid condition syntax in ServiceNow; the correct relative condition is 'On or after (relative) today - 30 days'. Option C is wrong because the 'Assignment groups' module is a configuration table for groups, not a data table containing incidents; it cannot be used to report on incident records directly.

Full explanation →
390
MCQhard

A large enterprise with over 15,000 users reporting to ServiceNow has a catalog item 'Request New Laptop' that is popular. Recently, users have complained that the form takes a long time to load in the Service Portal. The administrator notices that the catalog item has 20 variables, 3 variable sets, and 5 catalog client scripts. Performance metrics show that the 'sc_cat_item' view is slow. Additionally, the 'Before Order' script contains a loop that queries the user's previous requests. Which corrective action should the administrator take to improve performance?

A.Enable 'Caching' for the catalog item in the 'sys_properties' table.
B.Move the heavy script from the 'Before Order' script to a workflow 'Run Script' activity and simplify client scripts.
C.Increase the number of Service Portal widgets to distribute the load.
D.Remove all variable sets and create individual variables to reduce complexity.
AnswerB

Moving server-side logic from client-triggered scripts to workflows reduces form load time and improves user experience.

Why this answer

Simplifying catalog client scripts reduces the JavaScript executed during form rendering in the Service Portal, directly addressing the slow load time. The Before Order script runs at order submission, not during form load, so moving it to a workflow does not improve form load performance. The corrective action that targets the root cause of slow form loading is simplifying client scripts.

Exam trap

The trap here is that candidates may think caching (Option A) is a universal performance fix, but ServiceNow's caching for catalog items is not controlled via 'sys_properties' and does not address synchronous script execution in the 'Before Order' script.

How to eliminate wrong answers

Option A is wrong because enabling caching in the 'sys_properties' table does not apply to catalog items; caching is typically configured for specific system properties or via the 'sys_cs_cache' table for Service Portal, not per catalog item. Option C is wrong because increasing the number of Service Portal widgets does not distribute load for a single catalog item's form; widgets are for UI components, not for backend processing or view rendering. Option D is wrong because removing variable sets and creating individual variables increases complexity and does not improve performance; variable sets actually reduce overhead by grouping related variables and sharing common configurations.

Full explanation →
391
MCQmedium

A notification is configured to send an email when a new incident is created. The email template uses the field 'Short Description', but the email shows empty for that field. The template is correct. What is the most likely cause?

A.The notification is not set to fire on create
B.The email template has a syntax error
C.The 'Short Description' field is read-only on the form
D.The 'Short Description' field is not populated at the time the notification is sent
AnswerD

Notifications often fire asynchronously; if the field is required but not yet filled, it could be empty.

Why this answer

The notification fires when the incident is created, but the 'Short Description' field may not yet be populated at that exact moment if the record is saved before the field is filled. Notifications are triggered by the database write operation, and if the field is empty at that time, the email template will render it as blank, even though the template itself is correct.

Exam trap

The trap here is that candidates often assume a field is always populated at the time of record creation, but ServiceNow notifications fire immediately upon the database insert, before any post-save business rules or user input may fill the field.

How to eliminate wrong answers

Option A is wrong because the notification is explicitly configured to send an email when a new incident is created, so it does fire on create; the issue is not about the trigger event. Option B is wrong because the question states the template is correct, so a syntax error is not the cause. Option C is wrong because the 'Short Description' field being read-only on the form does not affect its value in the database; the field can still be populated via other means (e.g., inbound email, script), and read-only status does not cause an empty value in the notification.

Full explanation →
392
Multi-Selectmedium

A ServiceNow administrator is configuring a catalog item that requires end users to provide their department and cost center. The administrator wants the 'Cost Center' variable to appear only when the 'Department' variable is set to 'Finance'. Which ONE configuration would enable this behavior?

Select 1 answer
A.Set the 'Cost Center' variable Order field to a value higher than the 'Department' variable.
B.Create a Variable visibility condition on the 'Cost Center' variable that checks when 'Department' equals 'Finance'.
C.Set the 'Cost Center' variable Default value to 'Finance'.
D.Set the 'Cost Center' variable Read only field to true.
E.Set the 'Cost Center' variable Mandatory field to true.
AnswersB

Creating a variable visibility condition that checks when Department equals Finance directly controls the visibility of the Cost Center variable, enabling the required behavior.

Why this answer

To make the 'Cost Center' variable appear only when 'Department' is 'Finance', the correct configuration is to create a Variable visibility condition on the 'Cost Center' variable that checks when 'Department' equals 'Finance'. This directly controls the visibility based on the condition. Option A, setting the Order field, only determines the sequence of fields on the form and does not affect visibility.

Exam trap

Candidates may mistakenly think that the Order field controls visibility, but it only affects the order in which variables appear on the form. The actual visibility is controlled by conditions or client scripts.

Full explanation →
393
Multi-Selecthard

Which THREE factors should be considered when customizing navigation in ServiceNow? (Choose three.)

Select 3 answers
A.Session timeout settings for inactive users
B.Performance impact of custom UI16 navigation
C.Application scope of the modules
D.How personalization affects module ordering
E.Security roles required to access modules
AnswersB, D, E

Heavy navigation can slow down the system.

Why this answer

Custom UI16 navigation items, such as custom modules or menus, can introduce performance overhead due to additional server-side processing, ACL evaluations, and UI rendering. ServiceNow recommends evaluating the number and complexity of custom navigation elements to avoid degrading page load times and user experience.

Exam trap

The trap here is that candidates confuse system-level settings (like session timeout) with navigation customization factors, or assume application scope directly controls navigation ordering, when in fact scope only affects module ownership and update set isolation.

Full explanation →
394
Multi-Selecthard

Which TWO options are true regarding import set transform maps?

Select 2 answers
A.Transform scripts can access both source and target records
B.Coalesce is used to update existing records instead of inserting new ones
C.Transform maps run in the context of the source table
D.Each field mapping can have a unique coalesce field
E.Import sets automatically deduplicate based on sys_id
AnswersA, B

Scripts have access to source and target objects.

Why this answer

Transform scripts in ServiceNow run during the transform map execution and have access to both the source record (via the 'source' object) and the target record (via the 'target' object). This allows scripts to read, compare, and modify data from both sides, enabling complex data transformation logic.

Exam trap

The trap here is that candidates often confuse the transform map execution context (source vs. target) and mistakenly think coalesce is per-field, when in fact it is a map-level setting that controls record matching for the entire import.

Full explanation →
395
MCQeasy

Your organization uses multiple data sources to populate the CMDB, including ServiceNow Discovery, manual imports, and integrations with an external asset management system. Recently, you have noticed that some CIs appear to be duplicated despite having identification rules configured. Investigation reveals that the identification rules are not correctly matching CIs from the external system. What should you do to resolve the duplication without losing existing relationships?

A.Delete all CIs from the external system and re-import.
B.Manually merge all duplicate CIs using the UI.
C.Disable the external integration to prevent further duplicates.
D.Modify the identification rule to include a unique identifier from the external system.
AnswerD

This ensures that the IRE can match CIs from the external system to existing records.

Why this answer

Modifying the identification rule to include a unique identifier from the external system will allow the Identification and Reconciliation Engine (IRE) to correctly match existing CIs and prevent duplicates. Option A is wrong because deleting and re-importing could remove change history and relationships. Option B is wrong because manual merging is time-consuming and may not prevent recurrence.

Option C is wrong because disabling the integration stops data flow and does not fix the existing duplicates.

Full explanation →
396
MCQeasy

A ServiceNow administrator is troubleshooting a notification issue. The company has a 'Customer Satisfaction Survey' notification that is supposed to send an email to the 'caller' of an incident when the incident state changes to 'Resolved' (state=6). The notification is configured with table 'incident', condition 'state changes to 6', and recipient 'caller'. However, the email is not being sent. The administrator checks the system log and finds no errors. The notification has an advanced script that checks if the 'caller' has a valid email address. The script is: if (current.caller_id.email == '') { return false; }. The administrator confirms that the caller's email field is populated. What is the most likely reason the notification is not sending?

A.The advanced script should be removed because it is blocking valid emails.
B.The notification condition should be 'state is 6' rather than 'state changes to 6'.
C.The script should check for null instead of empty string.
D.The recipient field should use the email field directly instead of the reference 'caller'.
AnswerA

Correct. The script lacks an explicit return true, so it blocks all notifications.

Why this answer

The advanced script in the notification must explicitly return true to send the email. If no value is returned, the notification is suppressed. The script only returns false when the email is an empty string; otherwise it falls through without returning a value, which blocks the notification even when the caller has a valid email.

Removing the script eliminates this blockage and allows the notification to send as intended. The condition 'state changes to 6' correctly triggers on transition to Resolved, and the recipient field 'caller' is properly configured. The other options suggest changes that would not fix the real issue.

Exam trap

Candidates often forget that a notification advanced script must explicitly return true to allow sending. Omitting the return (or only returning on error) silently blocks the notification, a subtle mistake that can be hard to spot.

How to eliminate wrong answers

Option A is wrong because the advanced script correctly checks for an empty email string; removing it would not fix the issue since the email is populated and the script returns true. Option C is wrong because checking for null instead of empty string is unnecessary; the email field is a string and an empty string is the correct check for a missing email. Option D is wrong because using the reference field 'caller' is the standard way to access the caller's email via dot-walking (current.caller_id.email); the recipient field expects a user reference, not a direct email string.

Full explanation →
397
Multi-Selectmedium

Which THREE are components of the Employee Center portal?

Select 3 answers
A.Knowledge Base
B.Company News
C.Flow Designer
D.Service Catalog
E.Instance Dashboard
AnswersA, B, D

Users can search knowledge articles from the portal.

Why this answer

The Employee Center portal is a dedicated self-service portal in ServiceNow that provides employees with a unified interface to access common services. The Knowledge Base is a core component because it allows employees to search for and read articles to resolve issues without creating a ticket, directly supporting self-service and deflection.

Exam trap

ServiceNow often tests the distinction between portal components (end-user features) and platform tools (admin/developer features), so candidates mistakenly select Flow Designer or Instance Dashboard because they are familiar ServiceNow modules, but they are not part of the Employee Center portal.

Full explanation →
398
MCQmedium

A business rule is set to run on 'before update' on the 'incident' table. The script updates 'current.description' and then calls 'current.update()'. What is the likely outcome?

A.The description is updated and no error occurs.
B.The script causes a recursion error or multiple updates.
C.The script fails silently because current.update() is not allowed in before business rules.
D.The script runs but the description is not updated.
AnswerB

current.update() triggers the same business rule again.

Why this answer

In ServiceNow, calling `current.update()` inside a 'before update' business rule triggers a recursive loop because the update operation re-invokes the same business rule. The platform detects this recursion and typically throws an error or causes multiple updates, leading to the described outcome. Option B is correct because the script explicitly calls `current.update()`, which is prohibited in before business rules to prevent infinite loops.

Exam trap

The trap here is that candidates assume `current.update()` is always safe or that it simply updates the record once, but ServiceNow's before business rules are designed to avoid explicit update calls to prevent recursion.

How to eliminate wrong answers

Option A is wrong because calling `current.update()` in a before update business rule does not simply update the description without issue; it causes recursion or multiple updates. Option C is wrong because `current.update()` is technically allowed in before business rules (the script will execute), but it is strongly discouraged due to recursion; it does not fail silently. Option D is wrong because the description is updated by the script, but the recursion or error prevents a clean single update.

Full explanation →
399
MCQmedium

An administrator notices that a scheduled import set runs successfully, but the imported records do not appear in the target table. The import log shows no errors. What is the most likely cause?

A.The coalesce field is set incorrectly
B.The import set run was scheduled during off-hours
C.The data source has been aborted
D.The transform map has no field mappings defined
AnswerD

With no field mappings, no data is inserted into target.

Why this answer

When an import set runs successfully with no errors but records do not appear in the target table, the most likely cause is that the transform map has no field mappings defined. Without field mappings, the transform map cannot map source fields to target table columns, so no data is written to the target table even though the import set job completes without errors.

Exam trap

The trap here is that candidates often assume a successful import set run guarantees data in the target table, but ServiceNow separates the import set load (which always succeeds if the source file is valid) from the transform map execution (which requires field mappings to actually populate the target table).

How to eliminate wrong answers

Option A is wrong because an incorrect coalesce field would cause duplicate records or update failures, not a complete absence of records in the target table; the import log would typically show warnings or errors about coalesce mismatches. Option B is wrong because scheduling an import set during off-hours does not affect whether records appear in the target table; it only affects when the import runs. Option C is wrong because if the data source had been aborted, the import set would not run successfully and the import log would show an aborted status or error, not a successful completion.

Full explanation →
400
MCQmedium

An administrator notices that a flow that runs when a catalog item is submitted is failing because the flow tries to update a record that the flow's user (system) does not have permission to update. What is the best practice to address this?

A.Change the flow to run as the requestor
B.Use a business rule instead
C.Grant the flow's user the necessary roles
D.Use a run script action
AnswerA

Running as the requestor uses their permissions and ensures correct access.

Why this answer

Flows can be configured to run as a specific user. Setting the flow to run as the requestor ensures permissions are based on the user who submitted the request, which typically has appropriate access. Granting additional roles to the system user is not recommended.

Using a run script action or business rule does not address the permission issue directly.

Full explanation →
401
Matchingmedium

Match each ServiceNow feature to its primary purpose.

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

Concepts
Matches

Server-side logic triggered by record operations

Client-side logic triggered by UI events

Control field visibility, mandatory, and read-only states

Define user permissions on records and fields

Enforce data consistency and validation rules

Why these pairings

Correct matches: Business Rules are server-side scripts on database events; Client Scripts are browser-side form scripts; ACLs manage access; Script Includes are reusable server functions. Common confusions: UI Policies are client-side dynamic form behaviors, not server-side; Data Policies are server-side data validation rules, not client-side.

Full explanation →
402
MCQhard

An administrator needs to provide a custom view for the Incident table that hides the 'Description' field and reorders fields for a specific group of users. The view should be accessible from the form context menu. Which approach should the administrator take?

A.Create a UI Policy that hides the 'Description' field and reorders fields for the specific group.
B.Use the 'Personalize Form' option to rearrange fields and share the view with the group.
C.Create a new view for the Incident table and assign it to a user criteria that includes the group.
D.Write a Business Rule that updates the form configuration when the group members open a record.
AnswerC

Views can be scoped to user criteria.

Why this answer

Creating a new view for the Incident table and assigning it to a user criteria that includes the group allows the administrator to define a custom form layout (hiding the 'Description' field and reordering fields) that is automatically applied to all members of that group. Views are the native mechanism in ServiceNow for providing different form configurations to different users based on user criteria, and they are accessible from the form context menu via the 'View' option.

Exam trap

The trap here is that candidates often confuse UI Policies (which can hide fields) with views (which control the entire form layout including field order and visibility), leading them to select option A despite UI Policies being unable to reorder fields.

How to eliminate wrong answers

Option A is wrong because UI Policies are designed to dynamically show/hide fields or make them mandatory based on conditions, but they cannot reorder fields on a form; field reordering is a layout function that requires a view or form section configuration. Option B is wrong because 'Personalize Form' allows an individual user to rearrange fields for their own session, but sharing a personalized view with a group is not a supported feature; it does not create a persistent, group-specific view accessible from the context menu. Option D is wrong because Business Rules run server-side and cannot directly modify the client-side form layout (field order or visibility) for a specific group; they are used for data manipulation and validation, not for UI configuration.

Full explanation →
403
MCQmedium

An administrator notices that a CMDB CI class is not visible in the class hierarchy. The class exists in the database but cannot be selected when creating a new CI. What is the likely cause?

A.The class is retired.
B.The class is marked as 'abstract'.
C.The class has no parent.
D.The class has a missing table extension.
AnswerB

Abstract classes cannot be instantiated, so they are not available for creating new CIs.

Why this answer

In ServiceNow, a CI class marked as 'abstract' exists in the database but is not intended for direct instantiation. Abstract classes serve as templates for inheritance and are hidden from the 'New CI' selection list, which is why the administrator cannot select it when creating a new CI.

Exam trap

The trap here is that candidates often confuse 'abstract' with 'retired' or assume a missing parent causes visibility issues, but ServiceNow specifically uses the abstract flag to hide classes from selection while keeping them in the database for inheritance purposes.

How to eliminate wrong answers

Option A is wrong because a retired class is typically removed from the class hierarchy and may not appear in the database at all, whereas the question states the class exists in the database. Option C is wrong because a class without a parent would still be visible in the hierarchy (as a root class) and selectable for new CI creation. Option D is wrong because a missing table extension would cause the class to not function properly or throw errors, but it would not hide the class from the selection list; the class would still appear in the hierarchy.

Full explanation →
404
MCQeasy

A user reports that they are unable to submit a catalog request because the 'Submit' button is grayed out. The form has mandatory variables. What is the most likely cause?

A.The catalog item is inactive.
B.A mandatory variable is not filled in.
C.The service catalog is not in the user's home page.
D.The user does not have the 'catalog_admin' role.
AnswerB

Correct: Mandatory fields must be completed to enable submission.

Why this answer

The 'Submit' button being grayed out typically indicates that the form has not passed client-side validation. Since the question states the form has mandatory variables, the most likely cause is that one or more of these required fields have not been filled in, preventing submission.

Exam trap

The trap here is that candidates may confuse a disabled Submit button with permission issues (like missing roles) or catalog availability, when in fact the grayed-out state is a direct result of client-side validation for mandatory fields.

How to eliminate wrong answers

Option A is wrong because an inactive catalog item would not display the form at all or would show an error, not a grayed-out Submit button. Option C is wrong because the service catalog's presence on the home page is irrelevant to form submission; the user can access the catalog via the module navigator. Option D is wrong because the 'catalog_admin' role is for managing catalog items, not for submitting requests; any user with the appropriate roles (e.g., 'snc_internal' or 'user') can submit catalog requests.

Full explanation →
405
MCQmedium

A workflow includes an 'Approval' activity that requires approval from the user's manager. However, the approval is not being assigned to the manager. What should be checked first?

A.The user's delegation settings in the user profile
B.The workflow stage before the approval activity
C.The 'Approver' field in the approval activity properties
D.The conditions on the approval activity
AnswerC

This field defines the source of the approver; it should be set to a dynamic value like 'Manager'.

Why this answer

The 'Approver' field in the approval activity properties defines who receives the approval request. If it is not set to the user's manager (e.g., using the 'Manager' field from the sys_user table or a reference to the user's manager), the approval will not route correctly. This is the most direct and likely cause, so it should be checked first before investigating other potential issues.

Exam trap

The trap here is that candidates often jump to checking conditions or delegation settings first, overlooking the most fundamental cause—the 'Approver' field being misconfigured or empty—because they assume the manager relationship is automatically resolved.

How to eliminate wrong answers

Option A is wrong because delegation settings control temporary reassignment of approvals for a specific user, not the default routing to a manager; checking delegation is a secondary step after verifying the approver configuration. Option B is wrong because the workflow stage before the approval activity does not determine who receives the approval; it only affects the flow logic (e.g., conditions or transitions) leading to the activity. Option D is wrong because conditions on the approval activity control whether the activity runs at all, not who the approver is; if the activity runs but the approver is missing, conditions are not the root cause.

Full explanation →
406
MCQmedium

A company wants to automatically route catalog requests to the manager of the requestor for approval. Which configuration should be used in the catalog item's approval settings?

A.Use an approval rule with a condition
B.Set the approval type to 'Manager'
C.Configure delegated approval
D.Create a group approval
AnswerB

This built-in option routes approval to the manager of the requestor.

Why this answer

Setting the approval type to 'Manager' in the catalog item's approval settings automatically routes the request to the manager of the requestor, as defined in the sys_user table's manager field. This configuration leverages the out-of-box approval engine to look up the user's manager and send the approval request to that person, fulfilling the requirement without additional rules or conditions.

Exam trap

The trap here is that candidates often confuse 'approval type' with 'approval rule' or 'delegated approval', thinking they need a condition or delegation to achieve manager routing, when the built-in 'Manager' type directly accomplishes this.

How to eliminate wrong answers

Option A is wrong because an approval rule with a condition is used to trigger approval based on specific criteria (e.g., cost > $1000), not to route to the requestor's manager directly. Option C is wrong because delegated approval allows a user to designate another person to approve on their behalf, but it does not automatically route to the manager of the requestor. Option D is wrong because group approval sends the request to a group for collective approval, not specifically to the requestor's manager.

Full explanation →
407
Multi-Selectmedium

A company wants to ensure that when a high-priority catalog request is submitted, the IT manager receives an immediate notification. Which two methods can achieve this? (Choose two.)

Select 2 answers
A.Add an email template to the catalog item.
B.Use a Business Rule to send a notification via email.
C.Use a Flow to send an email when the record matches the condition.
D.Configure an approval rule that sends an email when the request is submitted.
E.Create a notification on the Requested Item table with a condition for priority=High.
AnswersC, E

Correct: Flow can send emails based on conditions.

Why this answer

A Flow can be configured to trigger when a record matches a specific condition (e.g., priority=High) and then send an email notification immediately. This provides a flexible, event-driven automation without requiring additional approval logic or manual templates.

Exam trap

The trap here is that candidates often confuse Business Rules (which are server-side scripts) with the native Notification system, thinking any scripted email qualifies as a 'method' for immediate notification, when the exam expects the use of dedicated notification features like Notifications or Flows.

Full explanation →
408
MCQmedium

A company has a catalog item that includes a variable set for employee information. The variable set has a variable 'Department' that should default to the user's department from their sys_user record. However, the default value is not being applied when a user orders the item. Which of the following is the most likely cause?

A.The 'Default Value' field on the variable set is blank or contains incorrect script.
B.The variable set is configured to 'Display to' only certain roles.
C.The variable is of type 'Reference' instead of 'String'.
D.The user's department is not populated in their user profile.
AnswerA

The default value must be set via script to populate from the user record.

Why this answer

The 'Default Value' field on the variable set is the correct place to define a default value for a variable. If it is blank or contains incorrect script, the system will not populate the 'Department' variable with the user's department from the sys_user record. This directly explains why the default is not being applied.

Exam trap

The trap here is that candidates often confuse the 'Default Value' field with other configuration options like 'Display to' roles or variable type, assuming that a missing user profile field would prevent the default from being applied, when in fact the default script runs regardless of whether the user's department is populated.

How to eliminate wrong answers

Option B is wrong because the 'Display to' roles setting controls visibility of the variable set, not the default value logic. Option C is wrong because the variable type (Reference vs. String) does not affect whether a default value is applied; both types support default values.

Option D is wrong because even if the user's department is not populated, the default value script would still execute and could return null, but the question states the default is not being applied at all, which points to a configuration issue in the 'Default Value' field, not a data issue.

Full explanation →
409
Drag & Dropmedium

Drag and drop the steps to configure a new Catalog Item in ServiceNow into the correct order.

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

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

The correct order to configure a new Catalog Item in ServiceNow is: first create the catalog item record to establish the basic structure; then add variables to define the questions users will answer; next, optionally define a workflow or approval process to handle fulfillment; finally, set the availability to make the item active and submit. This sequence ensures all necessary components are in place before making the item visible to users.

Full explanation →
410
MCQmedium

A scheduled report is set to run daily but does not execute. What is the most likely cause?

A.The schedule is not active.
B.The report is not shared.
C.The report contains too many rows.
D.The user who created the schedule is inactive.
AnswerD

Inactive users cause scheduled jobs to stop.

Why this answer

ServiceNow schedules are tied to the user who created them. If that user becomes inactive, the system disables the schedule to prevent unauthorized execution. The scheduled report will not run until the user is reactivated or the schedule is reassigned to an active user.

Exam trap

ServiceNow often tests the misconception that schedule inactivity is the primary cause, but the trap here is that a schedule can be active yet fail to execute if its creator is inactive, a subtle distinction that candidates overlook.

How to eliminate wrong answers

Option A is wrong because an inactive schedule would show as 'Inactive' in the schedule record, and the question states the schedule is 'set to run daily'—implying it was configured but not executing, not that it was manually deactivated. Option B is wrong because sharing a report affects visibility and access, not the execution of a scheduled job; schedules run regardless of sharing settings. Option C is wrong because ServiceNow does not limit scheduled report execution based on row count; large reports may take longer or hit system limits, but they will still attempt to run and fail with an error, not silently not execute.

Full explanation →
411
MCQeasy

Which of the following best describes the purpose of a 'Script Include' in ServiceNow?

A.To run automated actions on a schedule
B.To set field values dynamically based on conditions
C.To define client-side behavior when a form loads
D.To encapsulate reusable server-side logic
AnswerD

Script Includes are used for server-side code reuse.

Why this answer

A Script Include in ServiceNow is designed to encapsulate reusable server-side logic that can be called from other server-side scripts, such as Business Rules, Scheduled Jobs, or other Script Includes. It promotes code modularity and reusability by defining functions or classes that execute on the server instance, not on the client. Option D correctly identifies this core purpose.

Exam trap

ServiceNow often tests the distinction between server-side and client-side execution contexts, and the trap here is that candidates confuse Script Includes with Client Scripts or Business Rules, failing to recognize that Script Includes are purely for reusable server-side logic and not for direct UI or scheduled automation.

How to eliminate wrong answers

Option A is wrong because running automated actions on a schedule is the purpose of a Scheduled Job, not a Script Include; Script Includes are invoked programmatically, not by a time-based trigger. Option B is wrong because setting field values dynamically based on conditions is typically handled by Business Rules (server-side) or Client Scripts (client-side), not by Script Includes, which are reusable libraries. Option C is wrong because defining client-side behavior when a form loads is the role of a Client Script (e.g., onLoad), whereas Script Includes execute exclusively on the server and cannot directly manipulate the client DOM or browser events.

Full explanation →
412
MCQeasy

A small business uses ServiceNow for internal services. The catalog item 'New Employee Onboarding' includes a variable set with a variable 'Start Date'. The workflow sends an email notification to HR when the start date is within 7 days of submission. Currently, the notification is sent immediately upon request submission even if the start date is months away. The workflow has a 'Send Event' activity that triggers a notification. How should the administrator fix this?

A.Add a condition on the 'Send Event' activity to only proceed if the 'Start Date' variable is within 7 days of now.
B.Modify the notification record to include a condition on the 'Start Date' field.
C.Add a 'Mandatory Condition' on the 'Start Date' variable to require it to be within 7 days.
D.Create a business rule on the 'sc_req_item' table that checks the start date and sends the notification.
AnswerA

This ensures the notification is only sent when the condition is met.

Why this answer

The 'Send Event' activity in a workflow can have a condition that evaluates the 'Start Date' variable against the current date and time. By adding a condition that checks if the start date is within 7 days of now, the workflow will only proceed to send the event (and trigger the notification) when the condition is met, preventing premature notifications.

Exam trap

The trap here is that candidates often confuse the notification record's condition with the workflow activity's condition, or they incorrectly assume that a mandatory condition on the variable can control notification timing, when in fact the workflow's 'Send Event' activity is the correct place to add a time-based condition.

How to eliminate wrong answers

Option B is wrong because modifying the notification record's condition would not affect the workflow's 'Send Event' activity; the notification is triggered by the event, and the condition on the notification record would only filter which events trigger the notification, but the event is still sent immediately. Option C is wrong because a 'Mandatory Condition' on a variable only enforces that the variable must meet the condition at submission time, which would incorrectly block the catalog item from being submitted if the start date is more than 7 days away, rather than controlling the notification timing. Option D is wrong because creating a business rule on the 'sc_req_item' table would run on the server side after the request item is created, but it would not integrate with the workflow's 'Send Event' activity and would require additional logic to send the notification, which is less efficient and not the standard approach for workflow-driven notifications.

Full explanation →
413
MCQhard

Refer to the exhibit. An administrator created a catalog item using a record producer. When a user submits the request, the record producer fails to create the requested item. The log shows a missing mandatory field error. What is the most likely cause?

A.The record producer is not mapped to the correct table.
B.The 'model' variable is not mapped to a field in the target table.
C.A mandatory field in the target table is not mapped by the record producer.
D.The record producer is inactive.
AnswerC

Correct: If a mandatory field (e.g., 'requested_for') is not mapped, the record creation fails.

Why this answer

The error message 'missing mandatory field' directly indicates that a field in the target table, which is required (mandatory), has not been mapped by the record producer. In ServiceNow, when a record producer creates a record, it must map variables or fields to all mandatory fields in the target table; if any mandatory field is left unmapped, the system will fail to insert the record and log this specific error.

Exam trap

ServiceNow often tests the distinction between a record producer being inactive versus having unmapped mandatory fields; the trap here is that candidates may assume the error is about the producer being inactive or misconfigured at a high level, rather than recognizing the specific 'missing mandatory field' log message as a direct indicator of an unmapped mandatory field.

How to eliminate wrong answers

Option A is wrong because if the record producer were not mapped to the correct table, the error would typically be about an invalid table or a missing table, not a missing mandatory field. Option B is wrong because the 'model' variable is a specific variable type used for configuration items; while it could be unmapped, the generic 'missing mandatory field' error points to any unmapped mandatory field, not specifically the model variable. Option D is wrong because if the record producer were inactive, the catalog item would not appear to users or would not be processed at all, and the log would show an 'inactive' or 'not found' error, not a missing mandatory field error.

Full explanation →
414
Multi-Selecteasy

An administrator needs to enforce data consistency in the CMDB. Which two methods are effective for ensuring CI data quality? (Choose two.)

Select 2 answers
A.Configuring data certification policies.
B.Enabling CMDB Data Manager dashboards.
C.Exporting CMDB data to CSV for manual review.
D.Running the CI Class Manager regularly.
E.Setting up reconciliation rules.
AnswersA, B

Certification policies require CI owners to regularly attest to the accuracy of their data.

Why this answer

Data certification policies in ServiceNow require CI owners to periodically attest to the accuracy of their CI data, ensuring accountability and ongoing data quality. CMDB Data Manager dashboards provide real-time visibility into data quality metrics, such as completeness and compliance, enabling administrators to identify and address issues proactively. Together, these methods enforce data consistency without manual CSV exports or regular CI Class Manager runs.

Exam trap

The trap here is that candidates often confuse reconciliation rules (which handle data source conflicts) with data certification policies (which enforce quality standards), leading them to select option E instead of A.

Full explanation →
415
MCQhard

A catalog item has a variable called 'cost_center' that references the 'cost_centers' table. The variable is mandatory and must be filled before submission. However, users report that they can submit the item without selecting a cost center. The mandatory attribute is set to true. What is the most likely cause?

A.A client script sets the mandatory attribute to false on load
B.The reference qualifier is too restrictive
C.The variable is not in the correct order on the form
D.A UI Policy with mandatory set to false is overriding the variable mandatory setting
AnswerD

UI Policies can override variable mandatory settings, especially if they fire on submit.

Why this answer

A UI Policy with mandatory set to false runs on the client side and can override the mandatory attribute defined on the variable itself. When the UI Policy executes, it sets the variable's mandatory property to false, allowing the catalog item to be submitted without selecting a cost center, even though the variable's mandatory attribute is true.

Exam trap

The trap here is that candidates often assume the mandatory attribute on the variable definition is absolute and cannot be overridden, but ServiceNow allows UI Policies and client scripts to change field properties at runtime, which can cause the observed behavior.

How to eliminate wrong answers

Option A is wrong because a client script that sets the mandatory attribute to false on load would also cause the issue, but the question states the mandatory attribute is set to true and users can submit without selecting; a client script could do this, but UI Policies are the more common and direct mechanism for overriding mandatory settings on variables. Option B is wrong because a restrictive reference qualifier would limit which cost centers appear in the list, but it would not allow submission without selecting any cost center; the variable would still require a selection if mandatory is true. Option C is wrong because the order of variables on the form does not affect whether a mandatory variable can be submitted without a value; order only affects visual layout and flow.

Full explanation →
416
MCQhard

Refer to the exhibit. An administrator imports these system properties into a ServiceNow instance. After the import, what is the expected impact on the UI?

A.Rich text fields will no longer have the ability to insert/edit tables
B.It will prevent users from editing list records in a UI16 form
C.Buttons will lose their shadow effect
D.No change because system properties are not used in UI
AnswerA

List editor refers to table insertion.

Why this answer

The exhibit shows system properties that disable the 'glide.ui.richtext[2].table' and 'glide.ui.richtext[3].table' properties. These properties control whether the table insert/edit button is available in rich text fields. Setting them to 'false' removes the table functionality from the rich text editor toolbar, so users can no longer insert or edit tables in rich text fields.

Exam trap

The trap here is that candidates may think system properties have no UI impact or confuse rich text toolbar properties with other UI settings like list editing or button styling, but the question specifically tests knowledge of how rich text editor features are toggled via system properties.

How to eliminate wrong answers

Option B is wrong because UI16 forms and list editing are controlled by different system properties (e.g., 'glide.ui.list_edit' or 'glide.ui.form_edit') and not by rich text table properties. Option C is wrong because button shadow effects are controlled by CSS or theme properties, not by rich text configuration system properties. Option D is wrong because system properties directly affect UI behavior; in this case, the rich text editor reads these properties to determine which toolbar buttons to display.

Full explanation →
417
MCQeasy

A catalog item has a variable 'Department' and another 'Cost Center'. The Cost Center should only be visible when Department is 'IT'. Which configuration is most efficient?

A.Workflow stage that sets visibility after submission
B.Catalog client script on the Cost Center variable's onChange event
C.Catalog UI policy with a condition on Department
D.Variable set with a condition on Department
AnswerC

UI Policy directly controls visibility based on conditions and is the standard approach.

Why this answer

A Catalog UI Policy can conditionally show or hide variables on a catalog item based on the value of another variable (e.g., Department = 'IT') without requiring a record to exist or a submission to occur. It runs client-side in real-time as the user fills out the form, making it the most efficient and immediate approach for controlling visibility based on a field value.

Exam trap

The trap here is that candidates often confuse Catalog Client Scripts (which run on variable events) with Catalog UI Policies (which run on conditions), leading them to choose an onChange script that cannot react to changes in a different variable.

How to eliminate wrong answers

Option A is wrong because a workflow stage that sets visibility after submission would only apply the visibility change after the request is submitted, which is too late for the user to see or interact with the Cost Center variable during the ordering process. Option B is wrong because a catalog client script on the Cost Center variable's onChange event would only fire when the Cost Center itself changes, not when the Department changes, so it cannot dynamically show/hide the Cost Center based on Department selection. Option D is wrong because a variable set with a condition on Department would apply the condition to the entire set, not to an individual variable, and it would not allow granular control over a single variable's visibility within the set.

Full explanation →
418
MCQhard

A company is implementing Virtual Agent to handle common password reset requests. The conversation flow should ask the user to verify their identity using their employee ID and date of birth. Which Virtual Agent topic design should be used to collect this information?

A.Create a flow that uses user input via flow variables
B.Use a record producer to capture the information
C.Use a topic with variables to prompt for employee ID and date of birth
D.Configure a catalog item with variables and embed it in Virtual Agent
AnswerC

The topic can have variables that collect input from the user as part of the conversation flow.

Why this answer

Virtual Agent topics are designed to handle conversational flows by using topic-level variables to prompt users for information step by step. This allows the bot to collect the employee ID and date of birth in a structured, interactive manner, which is exactly what the password reset scenario requires.

Exam trap

ServiceNow often tests the distinction between Virtual Agent topics (which use topic variables for conversational input) and other ServiceNow components like flows, record producers, or catalog items, leading candidates to confuse the appropriate tool for interactive data collection.

How to eliminate wrong answers

Option A is wrong because flow variables are used within a flow action, not at the topic level, and they do not provide the conversational prompting needed for a Virtual Agent dialog. Option B is wrong because a record producer is designed for catalog-based submissions and does not support the interactive, step-by-step conversation flow of Virtual Agent. Option D is wrong because embedding a catalog item with variables in Virtual Agent is possible but is not the standard or recommended design for a conversational identity verification flow; topics with variables are the native and correct approach.

Full explanation →
419
Multi-Selectmedium

Which THREE of the following are true about Service Catalog variables? (Choose three.)

Select 3 answers
A.All catalog variables are stored in the 'sys_variable' table.
B.Once created, the order of variables cannot be changed.
C.Variables can have default values that reference other variables.
D.The variable type determines how the variable is displayed on the form.
E.Variables can be reordered using the 'Order' field in the variable list.
AnswersC, D, E

Default values can be scripted to reference other variables.

Why this answer

Service Catalog variables can have default values that reference other variables using syntax like '${variable_name}'. This allows dynamic default values based on user input or system data, which is a key feature for creating adaptive catalog forms.

Exam trap

ServiceNow often tests the distinction between variable definition tables (sys_variable) and variable value storage tables (sys_variable_value), and the misconception that variable order is immutable once set.

Full explanation →
420
Multi-Selecteasy

Which TWO data sources are commonly used to import data into ServiceNow via Import Sets? (Choose two.)

Select 2 answers
A.Email
B.REST
C.CSV
D.JDBC
E.LDAP
AnswersC, D

CSV files are one of the most common data sources.

Why this answer

CSV files are a standard data source for Import Sets in ServiceNow because they provide a simple, structured format that can be easily mapped to target tables via the Import Set Row (sys_import_set_row) and Staging Table (sys_import_set) mechanism. The Import Set functionality natively supports CSV parsing, allowing administrators to upload comma-separated values directly through the UI or via the Import Set REST API endpoint.

Exam trap

The trap here is that candidates often confuse REST as a data source for Import Sets because ServiceNow has a REST API for importing data, but the REST API is a separate integration method (e.g., Table API, Import Set API) and not a native Import Set data source type like CSV or JDBC.

Full explanation →
421
MCQmedium

A company uses a customized service catalog form. Recently, after a patch application, several catalog variables that were configured as drop-downs (choice fields) are now displaying as plain text fields on the order form. The administrator checks the variable definitions in the catalog item and confirms that they are still set to 'Choice' type and that the choice list values are intact. The catalog form is using the default 'Order' view. No UI Policies or client scripts are modifying the variable types on the form. What is the most likely cause and resolution?

A.Check the form layout for the variable editor.
B.Re-import the catalog variables from a saved XML backup.
C.Check any UI Policies that may be converting the variable type.
D.Clear the system cache (e.g., via 'Cache Flush' in System Diagnostics) and test again.
AnswerD

Clearing cache removes stale data and forces reload of variable definitions, often fixing rendering issues after patches.

Why this answer

The most likely cause is that the system cache still holds the old form configuration from before the patch, causing the choice fields to render as plain text despite the correct variable definitions. Clearing the cache (via 'Cache Flush' in System Diagnostics) forces the platform to rebuild the form metadata from the current database state, resolving the display issue. This is a common post-patch symptom in ServiceNow because cached form layouts can become stale.

Exam trap

The trap here is that candidates assume the problem is with the variable definition or a UI Policy, when in fact the patch likely introduced a new form layout version that the cache is ignoring, making cache flush the correct first diagnostic step.

How to eliminate wrong answers

Option A is wrong because the variable editor is used to configure variable definitions and choice lists, but the question states those definitions are intact; the issue is with the form's runtime rendering, not the variable's stored configuration. Option B is wrong because re-importing from XML would overwrite the current (correct) variable definitions with potentially outdated data, and the problem is not data corruption but a cached form layout. Option C is wrong because the question explicitly states that no UI Policies or client scripts are modifying the variable types, and UI Policies cannot change a field's type from 'Choice' to 'Plain text'—they can only hide, show, or make fields mandatory.

Full explanation →
422
Multi-Selectmedium

Which THREE of the following are true regarding business rules and their execution order?

Select 3 answers
A.After business rules run after the database write operation.
B.Before business rules cannot prevent the record from being saved.
C.Before business rules run before the database write operation.
D.Before display business rules run when the record is loaded into a form.
E.Async business rules run in the same transaction as the triggering event.
AnswersA, C, D

After rules execute post-insert/update.

Why this answer

'After' business rules are configured to execute after the database write operation has completed. This means they run once the record has been successfully saved to the database, allowing them to perform actions that depend on the record's existence, such as triggering notifications or updating related records.

Exam trap

The trap here is that candidates often confuse 'Async' business rules as running in the same transaction as the triggering event, but they actually run in a separate transaction, which can lead to unexpected behavior if not accounted for.

Full explanation →
423
MCQhard

Refer to the exhibit. The script runs but no output is produced. What is the most likely cause?

A.The table 'cmdb_ci' has no records with sys_class_name='cmdb_ci_server'.
B.The orderByDesc method is misspelled (should be orderByDescending).
C.The script lacks point number of rows (no rows with condition).
D.The field 'u_environment' does not exist on records with sys_class_name='cmdb_ci_server'.
AnswerD

A missing field causes the query to return no results.

Why this answer

The script uses `getValue('u_environment')` on a GlideRecord query for `cmdb_ci` with `sys_class_name='cmdb_ci_server'`. If the field `u_environment` does not exist on that table or class, `getValue` returns null, and the `gs.print` statement outputs nothing (or an empty string). The script runs without error, but no output is produced because the field is missing, not because the query returns zero rows.

Exam trap

The trap here is that candidates assume 'no output' means 'no records matched the query' (Option A), but the real issue is that the script runs successfully yet prints nothing because the field being accessed does not exist on the queried records.

How to eliminate wrong answers

Option A is wrong because if the table had no records, the `while` loop would never execute, and no output would be produced — but the question states the script runs, implying the loop iterates; the issue is that `getValue` returns null for each record, not that there are no records. Option B is wrong because `orderByDesc` is a valid GlideRecord method in ServiceNow (it sorts descending); there is no `orderByDescending` method — this is a common confusion with .NET or other languages. Option C is wrong because 'point number of rows' is not a ServiceNow concept; the script does not use `setLimit` or any row-limiting method, so the query returns all matching rows; the lack of output is due to the missing field, not a row limit.

Full explanation →
424
MCQmedium

A company uses ServiceNow to manage office supply requests. The process involves a catalog item with variables for item name, quantity, and delivery location. The delivery location is a reference variable to the 'Location' table. The administrator wants to automatically set the delivery location to the user's default location if no location is selected. The user's default location is stored on the user record (sys_user table). The administrator has already added a default value on the variable that is supposed to pull from the user record, but it does not work. What is the most likely reason?

A.The variable is not marked as mandatory.
B.The user record does not have a location field.
C.The default value is set as a static value instead of a script.
D.The variable type should be 'select box', not reference.
AnswerC

To dynamically set default from user record, a scripted default is needed.

Why this answer

A default value on a catalog variable that needs to dynamically pull data from the user record must be a script (e.g., `g_user.location` or `GlideRecord` lookup), not a static value. The administrator likely set a static default, which does not evaluate per-user context, so the field remains empty when no selection is made.

Exam trap

The trap here is that candidates often assume a static default value will work for dynamic user-specific data, or they confuse mandatory settings with default value logic, leading them to incorrectly select option A or D.

How to eliminate wrong answers

Option A is wrong because marking the variable as mandatory would force the user to select a location, which contradicts the requirement to auto-set it from the user record when left blank. Option B is wrong because the sys_user table does have a 'location' field by default (a reference to the Location table), and the question states the user's default location is stored there. Option D is wrong because a reference variable is the correct type for linking to the Location table; a select box would require manual population of choices and would not leverage the reference relationship.

Full explanation →
425
MCQmedium

A company wants to ensure that when a user submits a catalog item for a new laptop, the request is automatically approved if the cost is under $1,000 and the user's department has sufficient budget. What is the best way to implement this requirement?

A.Configure a notification to inform the user of the approval status.
B.Set up a Business Rule to approve all requests under $1,000.
C.Use a Flow to send an approval request to the manager every time.
D.Create an Approval rule with conditions on cost and department budget.
AnswerD

Approval rules can auto-approve based on conditions.

Why this answer

Approval rules in ServiceNow are specifically designed to automate approval decisions based on conditions like cost and department budget. By creating an Approval rule on the catalog item, you can evaluate the requested cost against a threshold and check the department's budget balance via a condition script or reference to the budget table, enabling automatic approval without manual intervention.

Exam trap

The trap here is that candidates confuse Business Rules (which run on database operations) with Approval rules (which are part of the approval engine), leading them to choose Option B despite Business Rules not being able to trigger automatic approval decisions in the approval workflow.

How to eliminate wrong answers

Option A is wrong because a notification only informs users of status; it does not perform any approval logic or automatic approval. Option B is wrong because a Business Rule runs on the server side but is not designed for approval workflows; it could set a field but cannot trigger the approval engine's automatic approval action. Option C is wrong because using a Flow to send an approval request to the manager every time defeats the requirement for automatic approval; it always requires manual manager action rather than checking conditions for auto-approval.

Full explanation →
426
MCQhard

Refer to the exhibit. A script include returns false for a user with the admin role. Which is the most likely reason?

A.The user's session is expired.
B.The user does not have the admin role.
C.The user is not a member of the specified group.
D.The GlideRecord query failed due to a missing table.
AnswerC

Correct; the script requires membership in that specific group.

Why this answer

The script include explicitly checks group membership, likely using a method like `gs.getUser().isMemberOf('some_group')`. Even if the user has the admin role, the script returns false if the user is not a member of the specified group, as admin roles do not automatically grant group membership in ServiceNow.

Exam trap

ServiceNow often tests the misconception that admin roles imply group membership, but ServiceNow treats roles and groups as separate entities, so a script checking group membership will return false for an admin not in the group.

How to eliminate wrong answers

Option A is wrong because an expired session would cause a login prompt or a null session, not a false return from a script include that runs within an active session. Option B is wrong because the question states the user has the admin role, so the script include is not checking for the admin role; it is checking group membership. Option D is wrong because a GlideRecord query failure due to a missing table would throw an error or return an empty GlideRecord, not simply return false from the script include.

Full explanation →
427
MCQhard

Refer to the exhibit. An administrator runs Discovery on a switch and receives this payload. However, the CI is not created in the CMDB. The Discovery log shows 'Identification rule did not match any CI. Creating new CI failed because of duplicate serial number?'. What is the most likely cause?

A.The class 'Network Gear' is invalid.
B.There is already a CI with the same serial number.
C.The identification rule is misconfigured.
D.The serial number field is missing from the payload.
AnswerB

The log explicitly states 'duplicate serial number', indicating a serial conflict.

Why this answer

The error message 'Creating new CI failed because of duplicate serial number' directly indicates that a CI with the same serial number already exists in the CMDB. ServiceNow enforces uniqueness on the serial number field for hardware CIs; when Discovery attempts to create a new CI but finds a matching serial number, the operation fails. This is why option B is correct.

Exam trap

ServiceNow often tests the distinction between identification rule failures (which produce 'no match' or 'multiple match' errors) and database constraint violations (like duplicate serial numbers), leading candidates to incorrectly blame the identification rule configuration when the real issue is a unique key conflict.

How to eliminate wrong answers

Option A is wrong because if the class 'Network Gear' were invalid, Discovery would fail earlier with a class-not-found error, not a duplicate serial number error. Option C is wrong because a misconfigured identification rule would cause a 'no match' or 'multiple match' error, not a duplicate serial number failure; the identification rule itself is working (it found no match), but the creation attempt fails due to the serial number constraint. Option D is wrong because if the serial number field were missing from the payload, Discovery would not be able to check for duplicates and would likely create the CI without a serial number, or log a different error about missing mandatory fields.

Full explanation →
428
MCQmedium

When configuring a form, you want to add a new section. What is the correct approach?

A.Modify the default view
B.Use the form designer
C.Create a UI action
D.Edit the table schema
AnswerB

Form designer provides a drag-and-drop interface to add and arrange sections.

Why this answer

The form designer allows you to add sections directly. Options A, C, and D are not standard methods for adding sections.

Full explanation →
429
MCQmedium

When creating a new form section, which configuration ensures the section appears on the form for all users?

A.Visibility set to 'Everyone'
B.Roles field left blank
C.Condition set to true
D.Order set to 1
AnswerB

A blank Roles field means no role restriction, so all users can see the section.

Why this answer

Leaving the Roles field blank on a form section means no role restrictions are applied, making the section visible to all users by default. In ServiceNow, form sections are controlled by the 'Roles' field; if it is empty, the section is not filtered by any role and appears for everyone. This is the standard configuration for universal visibility.

Exam trap

The trap here is that candidates may confuse the 'Roles' field behavior with other visibility mechanisms like UI policies or client scripts, or assume that leaving a field blank means the section is hidden, when in fact it means no restrictions are applied.

How to eliminate wrong answers

Option A is wrong because 'Visibility set to Everyone' is not a valid configuration in ServiceNow form sections; there is no such field or setting. Option C is wrong because 'Condition set to true' refers to a client script or UI policy condition, not a form section property; form sections do not have a 'Condition' field for visibility. Option D is wrong because 'Order set to 1' only controls the section's position on the form, not its visibility to users.

Full explanation →
430
MCQmedium

A company has a custom table 'u_asset' and wants the 'Asset' module in the application navigator to show only records where 'active=true'. How can this be achieved?

A.Use an ACL to restrict access
B.Set a condition on the 'Filter' property of the module
C.Create a UI policy on the table
D.Add a client script to the list
AnswerB

The filter property allows defining a condition for the module's list.

Why this answer

The 'Filter' property on a module in the application navigator allows you to define a condition (e.g., 'active=true') that restricts which records from the underlying table are displayed when the module is clicked. This is the standard method for scoping module results without altering security or user interface behavior globally.

Exam trap

ServiceNow often tests the distinction between server-side record filtering (module Filter property) and client-side or security-based restrictions (ACLs, UI policies, client scripts), leading candidates to confuse access control with data scoping.

How to eliminate wrong answers

Option A is wrong because ACLs (Access Control Lists) control record-level security (create, read, write, delete) based on user roles and conditions, but they do not filter the records shown in a module's list view; a user with read access would still see all records unless a filter is applied. Option C is wrong because UI policies run on the client side to control field visibility, mandatory status, or values on a form, not to filter the list of records displayed in a module. Option D is wrong because a client script executes on the client side (e.g., onLoad, onChange) and cannot modify the server-side query that populates a module's list view; it can only affect the current form or list client-side behavior.

Full explanation →
431
Multi-Selectmedium

Which two actions should be taken to ensure a dashboard is visible to all members of the 'service_desk' role? (Choose two.)

Select 2 answers
A.Set the dashboard's visibility to 'Public'.
B.Add the dashboard to a module in the application menu.
C.Publish the dashboard to a homepage.
D.Set the dashboard's 'Can read' ACL to include the service_desk role.
E.Grant the 'report_admin' role to all service desk members.
AnswersA, D

Public dashboards are visible to all users, including service_desk members.

Why this answer

Setting a dashboard's visibility to 'Public' (Option A) makes it accessible to all users, including those in the 'service_desk' role, without requiring individual ACL entries. This is the simplest method to ensure universal visibility within the instance. Additionally, configuring the 'Can read' ACL (Option D) to explicitly include the 'service_desk' role grants read-level access, which is necessary when the dashboard is not set to Public but must be restricted to specific roles.

Together, these actions ensure the dashboard is visible to all members of the 'service_desk' role.

Exam trap

The trap here is confusing visibility settings (Public vs. role-based ACL) with navigation or homepage placement, leading candidates to think that adding a dashboard to a module or publishing it to a homepage automatically grants read access.

Full explanation →
432
MCQmedium

Refer to the exhibit. An administrator runs this script in a background script. The script runs without errors but does not output any CI names. All servers exist in the CMDB. What could be the issue?

A.The sys_class_name should be 'Server' instead of 'cmdb_ci_server'.
B.The GlideRecord is not properly initialized.
C.The administrator does not have read access to the cmdb_ci table.
D.The script does not have a condition to check the number of records.
AnswerC

Correct. Lack of read access to the cmdb_ci table would cause the script to return no records silently, matching the described behavior.

Why this answer

The script runs without errors but returns no records, indicating a permission issue. In ServiceNow, if the administrator lacks read access to the 'cmdb_ci' table (or the specific table being queried), GlideRecord will not return any records even if they exist. The other options are incorrect: A is wrong because 'cmdb_ci_server' is the correct sys_class_name value for server CIs; B is false because the script runs without errors, so initialization is fine; D is false because the condition is not necessary for record output—the query itself would return all records without a condition.

Exam trap

Candidates often forget that security roles and ACLs can silently prevent GlideRecord from returning records. A script that runs without errors but yields no results should always prompt a check of access permissions before assuming the query logic is flawed.

How to eliminate wrong answers

Option B is wrong because the GlideRecord is properly initialized with 'new GlideRecord('cmdb_ci_server')' — the syntax is correct, but the table name is invalid. Option C is wrong because if the administrator lacked read access to the cmdb_ci table, the script would either throw a security exception or return zero records silently, but the question states the script runs without errors, implying access is granted. Option D is wrong because checking the number of records is not required for the script to output CI names; a query that returns records will iterate correctly without an explicit count check.

Full explanation →
433
MCQeasy

A company is implementing ServiceNow Service Portal for employee self-service. They want to display a list of recent requests on the homepage. Which widget is most appropriate for this purpose?

A.'SC Category' widget
B.'Widget Container'
C.'My Requests' widget
D.'List V2' widget
AnswerC

This widget is designed to show the user's own requests.

Why this answer

The 'My Requests' widget is specifically designed to display a list of requests associated with the current logged-in user, making it the most appropriate choice for showing recent requests on a Service Portal homepage. It automatically filters records from the 'Request' (sc_request) table based on the user's sys_id and provides built-in sorting and status indicators.

Exam trap

The trap here is that candidates often choose the 'List V2' widget because it is a flexible list widget, but they overlook that it requires custom configuration to filter by the current user, whereas the 'My Requests' widget is purpose-built for this exact use case and is the correct, out-of-the-box solution.

How to eliminate wrong answers

Option A is wrong because the 'SC Category' widget is used to display a list of service catalog categories, not user-specific requests. Option B is wrong because the 'Widget Container' is a layout widget that holds other widgets and does not itself display any data. Option D is wrong because the 'List V2' widget is a generic list widget that requires manual configuration of a data source and filters, and it does not automatically scope to the current user's requests like the 'My Requests' widget does.

Full explanation →
434
MCQmedium

A business rule runs on 'before update' of the 'incident' table and sets the 'assigned_to' field to the current user if the assignment group is empty. The rule is in the global scope. However, when a user from another application scope updates an incident via a web service, the field is not being set. What is the most likely cause?

A.The user making the web service call does not have the 'itil' role.
B.The business rule is not configured to run in the 'System' (global) scope across all applications.
C.The business rule runs after the web service update and the field is already committed.
D.The business rule condition is incorrect for web service updates.
AnswerB

Correct: Business rules need appropriate application access to run cross-scope.

Why this answer

The business rule is in the global scope, but by default, business rules in the global scope only run for updates made within the global scope itself. When a user from another application scope updates an incident via a web service, the update originates from that other scope, and the global-scope business rule does not execute unless it is explicitly configured to run in the 'System' (global) scope across all applications. This is controlled by the 'Run in all scopes' checkbox on the business rule record.

Exam trap

The trap here is that candidates assume 'global scope' means the rule runs everywhere, but ServiceNow's scoping model requires an explicit 'Run in all scopes' flag for global rules to execute across application boundaries.

How to eliminate wrong answers

Option A is wrong because the 'itil' role is not required for a business rule to execute; business rules run based on table operations, not user roles, and the rule's condition does not check for roles. Option C is wrong because the business rule is set to run 'before update', so it executes before the database commit, not after; the web service update would still trigger the before-update event. Option D is wrong because the business rule condition (assignment group empty) is straightforward and does not differentiate between UI updates and web service updates; the issue is scope, not the condition logic.

Full explanation →
435
MCQhard

Refer to the exhibit. An incident is created with state 'New' and assigned_to is empty. Later, the state is changed to 'In Progress' and assigned_to is set to 'user1'. The notification does not fire. Which is the most likely reason?

A.The notification's condition includes 'state changes' which is evaluated at the time the trigger runs, not at the time of the update. The trigger may be waiting for a future time, but the condition is re-evaluated then. If the state hasn't changed since the update, it might not fire.
B.The notification's 'Who will receive' is set to assignment group, but the assignment group is empty.
C.The notification condition requires the state field to change, but the state changed from 'New' to 'In Progress', so it should fire. The trigger is scheduled for later, so it will fire at that time.
D.The notification is configured to send only on insert, not on update.
AnswerA

For timed notifications, the condition is evaluated when the trigger executes. If the state hasn't changed (i.e., it still is 'In Progress'), the condition 'state changes' will be false because it compares to previous value. Since the state changed earlier, at trigger time the field may not have changed from the last value. Actually, 'state changes' is a condition that checks if the field changed during the update that caused the trigger. For timed notifications, the condition is evaluated at the time of the trigger, and 'state changes' might not be true if the field hasn't changed since the trigger was created. This is a common pitfall.

Why this answer

The notification's condition includes 'state changes', which is evaluated at the time the trigger runs, not at the time of the update. In ServiceNow, when a notification is configured with a condition that checks for a field change (e.g., 'state changes'), the condition is evaluated when the scheduled trigger executes, not when the record is updated. If the trigger is scheduled for a later time (e.g., via an asynchronous business rule or scheduled job), the condition may no longer be true because the state has already changed and is no longer 'changing' at that moment, causing the notification to not fire.

Exam trap

A common trap is the misconception that notification conditions are evaluated at the time of the record update, when in reality they are evaluated at the time the notification trigger executes, which can be asynchronous and cause conditions based on field changes to fail.

How to eliminate wrong answers

Option B is wrong because the 'Who will receive' setting being set to assignment group with an empty assignment group would cause the notification to not send, but the question states the notification does not fire, meaning the trigger itself does not execute; an empty recipient list would still generate a notification record but with no recipients, which is different from not firing. Option C is wrong because it assumes the notification should fire immediately when the state changes, but the trigger is scheduled for later, and the condition is re-evaluated at that later time; if the state has already changed and is no longer in the process of changing, the condition fails. Option D is wrong because the question describes an update (state changed from 'New' to 'In Progress' and assigned_to set to 'user1'), not an insert, so a notification configured to send only on insert would not fire on an update, but the scenario explicitly involves an update, making this option irrelevant to the core issue of condition evaluation timing.

Full explanation →
436
MCQmedium

A pivot table report shows 'Number' as the column and 'Assigned to' as the row. The 'Value' field is set to 'Count'. What does each cell represent?

A.The average number of incidents per group
B.The number of tasks closed by each user
C.The total number of incidents in the system
D.The number of incidents assigned to that user
AnswerD

Count of records where assigned to matches the person.

Why this answer

In a ServiceNow pivot table, when 'Number' is the column and 'Assigned to' is the row with 'Value' set to 'Count', each cell counts the number of records (incidents) that have a specific 'Number' value and are assigned to a specific user. This directly corresponds to the number of incidents assigned to that user for that particular number value, making D correct.

Exam trap

The trap here is that candidates confuse 'Count' with 'Sum' or 'Average', or assume the pivot table inherently reflects task closure status, when in fact it simply counts all records in the intersection without any state filtering.

How to eliminate wrong answers

Option A is wrong because 'Count' does not compute an average; it counts occurrences, and the pivot table does not include a division operation. Option B is wrong because the pivot table is based on incidents, not tasks, and 'Count' of 'Number' does not indicate closure status; it merely counts records regardless of state. Option C is wrong because each cell represents a subset of incidents (filtered by user and number), not the total count across the entire system.

Full explanation →
437
MCQeasy

An administrator needs to archive old incident records to reduce the size of the incident table. Which approach is recommended for optimal performance?

A.Use the 'Delete Records' module to remove records older than 6 months.
B.Use the 'Archive' functionality in the Application Navigator.
C.Delete records older than 6 months directly from the database.
D.Create a scheduled job to copy records to a custom table and then delete from incident table.
AnswerB

Archive is the recommended method to safely move old records to an archive table.

Why this answer

ServiceNow's built-in Archive functionality is the recommended approach to reduce table size. It automatically moves old records to a separate archive table, preserving referential integrity and application logic, while freeing up space in the incident table. Option A is incorrect because the 'Delete Records' module permanently removes records, not archives them.

Option C is incorrect because direct database deletion bypasses ServiceNow's safeguards and can corrupt data. Option D is incorrect because manually copying and deleting records is complex, error-prone, and not scalable; the Archive feature handles this efficiently.

Full explanation →
438
Multi-Selectmedium

A company uses SLAs on Incident records. They want to notify the assignment group when an SLA is about to breach (within 10 minutes). Which THREE actions can be used to achieve this?

Select 3 answers
A.Create a notification that triggers on the 'SLA Warning' event.
B.Add a script action to the SLA definition that sends an email via the Event Management system.
C.Create a business rule on the Incident table that checks the SLA percentage.
D.Configure an 'on warning' event on the SLA definition.
E.Create a scheduled job that runs every minute to check SLA percentages.
AnswersA, B, D

Notifications can be associated with SLA events like warning.

Why this answer

The 'SLA Warning' event is a predefined event that fires when an SLA is within its warning threshold. By creating a notification that triggers on this event, you can send an alert to the assignment group when the SLA is about to breach within 10 minutes, as the warning threshold can be configured on the SLA definition.

Exam trap

The trap here is that candidates often think they need to use a scheduled job or business rule to manually check SLA conditions, when in fact the platform provides built-in event-driven mechanisms like the 'SLA Warning' event and 'on warning' configuration that are more efficient and aligned with best practices.

Full explanation →
439
MCQhard

Refer to the exhibit. This is a script used in an ACL on the 'incident' table with 'type' set to 'record' and 'operation' set to 'read'. What is the effect of this ACL?

A.Grants read access only to admin
B.Denies read access to everyone
C.Denies read access to non-admin users
D.Grants read access to everyone
AnswerC

Non-admin users get false, so they are denied read access.

Why this answer

The ACL script uses `gs.getUser().hasRole('admin')` to check if the current user has the 'admin' role. If the user is not an admin, the script returns `false`, which denies read access. This effectively restricts read access to admin users only, denying it to all non-admin users.

Option C correctly describes this behavior.

Exam trap

The trap here is that candidates often misinterpret a deny rule as a grant rule, thinking the ACL 'grants read access to admin' when it actually denies access to non-admin users, with admin access being the default behavior when no deny applies.

How to eliminate wrong answers

Option A is wrong because the ACL does not 'grant' read access to admin; it denies access to non-admin users, which implicitly allows admin access, but the ACL itself is a deny rule, not a grant. Option B is wrong because the ACL does not deny read access to everyone; it only denies non-admin users, while admin users can still read. Option D is wrong because the ACL explicitly denies read access to non-admin users, so it does not grant read access to everyone.

Full explanation →
440
MCQmedium

After importing data, some records show as 'Ignored' in the import log. What is the most likely cause?

A.The source field was empty and the target field is optional.
B.A field mapping script returned null for a mandatory target field.
C.Coalesce matched an existing record and the transform map action is 'Insert only'.
D.The transform map condition evaluated to false.
AnswerC

If the action is 'Insert only' and coalesce finds a matching record, the row is ignored to avoid duplicate insertion.

Why this answer

When a transform map uses the 'Insert only' action and the Coalesce function finds a match on the source and target fields, the import engine ignores the record to prevent duplicates. This is a standard behavior in ServiceNow where coalesce is used to identify existing records, and if the action is set to 'Insert only', no update occurs, resulting in an 'Ignored' status in the import log.

Exam trap

The trap here is that candidates often confuse 'Ignored' with 'Skipped' or 'Error', not realizing that 'Ignored' specifically results from a coalesce match combined with an 'Insert only' action, rather than from field-level issues or condition failures.

How to eliminate wrong answers

Option A is wrong because an empty source field with an optional target field does not cause an 'Ignored' status; it typically results in a successful import with a null value in the target field. Option B is wrong because a field mapping script returning null for a mandatory target field would cause an error or a skipped record, not an 'Ignored' status; the import log would show a failure or error, not 'Ignored'. Option D is wrong because if the transform map condition evaluates to false, the record is skipped entirely and not processed, which would not appear as 'Ignored' in the import log; instead, it would be omitted from the import results.

Full explanation →
441
Multi-Selecthard

Which THREE statements about Access Control Lists (ACLs) are true? (Choose THREE.)

Select 3 answers
A.ACLs can be defined for tables, records, fields, and scripts.
B.ACLs can use condition scripts to grant or deny access.
C.If 'requires role' is checked and no roles are listed, only users with the 'admin' role can access.
D.An ACL can only have one role specified.
E.An ACL must have a script to evaluate conditions.
AnswersA, B, C

ACL types include table, record, field, and script.

Why this answer

In ServiceNow, Access Control Lists (ACLs) can be defined to control access at multiple granularity levels: tables (entire table operations), records (specific rows), fields (individual columns), and scripts (execution of business rules or script includes). This allows administrators to enforce security policies precisely where needed.

Exam trap

ServiceNow often tests the misconception that ACLs must have a script to evaluate conditions, but in ServiceNow, conditions can be purely role-based or use simple field comparisons without any scripting.

Full explanation →
442
MCQeasy

A user wants to create a report that shows the number of incidents by category for each month. Which report type best achieves this?

A.Bar chart with category on X-axis, count on Y-axis, and group by month.
B.Bar chart with category on X-axis and count on Y-axis.
C.List report with category and month columns.
D.Pie chart by category.
E.Line chart with date on X-axis and count on Y-axis.
AnswerA

A bar chart with category on the X-axis, count on the Y-axis, and grouping by month directly visualizes the number of incidents per category for each month. This report type uses a grouped bar chart, which allows the viewer to compare incident counts across categories while seeing the monthly breakdown side by side, fulfilling the user's requirement to show both dimensions clearly.

Why this answer

A bar chart with category on the X-axis, count on the Y-axis, and grouping by month directly visualizes the number of incidents per category for each month. This report type uses a grouped bar chart, which allows the viewer to compare incident counts across categories while seeing the monthly breakdown side by side, fulfilling the user's requirement to show both dimensions clearly.

Exam trap

The trap here is that candidates often choose a pie chart or line chart because they focus on one dimension (category or time) without realizing that a grouped bar chart is required to simultaneously display both the category breakdown and the monthly comparison.

How to eliminate wrong answers

Option B is wrong because it is identical to Option A and listed as a duplicate, but the question requires selecting the best report type; since A is already correct, B is redundant and not a distinct valid choice. Option C is wrong because a list report with category and month columns only displays raw data in rows, lacking any visual aggregation or grouping to show the count of incidents by category per month; it requires manual interpretation. Option D is wrong because a pie chart by category shows the proportion of incidents across categories for the entire dataset, but it cannot represent the monthly dimension, failing to meet the requirement for per-month breakdown.

Option E is wrong because a line chart with date on the X-axis and count on the Y-axis shows trends over time for a single series, but it does not group by category, so it cannot display incident counts by category for each month.

Full explanation →
443
Multi-Selecteasy

Which two of the following are true about Service Catalog variables? (Choose two.)

Select 2 answers
A.Variables can be reused across multiple catalog items.
B.Variables can only be of type 'Single Line Text'.
C.Variable order can be changed via the 'Reorder' button.
D.Variables are stored in the 'sys_attachment' table.
E.Variables cannot be made mandatory.
AnswersA, C

Variables can be defined in variable sets and reused.

Why this answer

Service Catalog variables are defined once in the variable catalog and can be reused across multiple catalog items via the 'Variable Editor' or by referencing the same variable record. This promotes consistency and reduces administrative overhead when the same input (e.g., 'Department' or 'Location') is needed in different items.

Exam trap

The trap here is that candidates often assume variables are stored in the same table as attachments or that only text types are available, but ServiceNow's variable system is highly flexible with many types and a dedicated storage model separate from attachments.

Full explanation →
444
MCQhard

Your organization has implemented ServiceNow CMDB with multiple data sources including ServiceNow Discovery, SCCM, and manual imports. You notice that for a critical group of Windows servers, the 'os_version' attribute is being overwritten frequently. Upon investigation, you find that Discovery reports the correct version, but SCCM imports an older version that overwrites it. The Discovery source runs daily at 2 AM, and SCCM imports run at 4 AM. Currently, all data sources have equal priority. You need to ensure that the Discovery value is the authoritative source for os_version on these servers, but you do not want to block SCCM from updating other attributes. What is the best course of action?

A.Remove SCCM as a data source for these servers.
B.Disable reconciliation for the Windows Server CI class.
C.Set the 'Preserve manual changes' flag on the CI class.
D.Create a reconciliation rule that gives Discovery higher priority than SCCM for the os_version attribute on the Windows Server CI class.
AnswerD

This targets the specific attribute and source priority.

Why this answer

Reconciliation rules allow you to define attribute-level priority between data sources without blocking SCCM from updating other attributes. By creating a rule that gives Discovery higher priority than SCCM specifically for the os_version attribute on the Windows Server CI class, Discovery's value will be authoritative for that attribute while SCCM can still update other attributes. This approach preserves the multi-source CMDB integrity without disabling reconciliation or removing SCCM entirely.

Exam trap

The trap here is that candidates may confuse reconciliation rules with disabling reconciliation entirely or assume that removing a data source is the only way to prevent overwrites, missing the attribute-level granularity that reconciliation rules provide.

How to eliminate wrong answers

Option A is wrong because removing SCCM as a data source would prevent it from updating any attributes on these servers, which is overly restrictive and contradicts the requirement to allow SCCM to update other attributes. Option B is wrong because disabling reconciliation for the Windows Server CI class would stop all conflict resolution, meaning the last data source to write (SCCM at 4 AM) would always win, which does not solve the overwrite issue. Option C is wrong because the 'Preserve manual changes' flag only protects manually entered data from being overwritten by automated sources; it does not affect priority between automated sources like Discovery and SCCM.

Full explanation →
445
MCQmedium

Refer to the exhibit. A user selects 'Full Tunnel' and sees the info message, but the request is auto-approved. What is the most likely cause?

A.The client script runs on load and overrides the workflow condition.
B.The workflow condition is evaluated before the user selects the variable value.
C.The workflow condition is based on the variable 'u_vpn_type' but the condition is incorrectly configured to use '==' instead of '==='.
D.The workflow condition uses the variable value from the request, which may be set to 'Split Tunnel' due to a default.
AnswerD

Why this answer

The most likely cause is option D: The workflow condition uses the variable value from the request, which may be set to 'Split Tunnel' due to a default. When a catalog item variable has a default value, that default is used in the workflow condition if the user's selection is not properly captured or if the condition is evaluated before the variable is updated. In this case, even though the user selects 'Full Tunnel', the workflow condition might be checking the initial default value of 'Split Tunnel', causing the condition to fail and leading to auto-approval.

Option A is unlikely because client scripts typically run on load and can set values, but they would not normally override the workflow condition after submission. Option B is incorrect because workflow conditions are evaluated at submission time, after the user selects the variable. Option C is irrelevant because workflow conditions in ServiceNow do not use JavaScript equality operators like '==='.

Full explanation →
446
MCQmedium

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
447
MCQeasy

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

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

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

Why this answer

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

Exam trap

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

How to eliminate wrong answers

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

Full explanation →
448
Multi-Selectmedium

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

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

Widgets provide modular functionality and can be added to pages.

Why this answer

Widgets are the primary building blocks of a Service Portal page; you can add, remove, and configure them via the portal designer to change both appearance and functionality without writing code. Option E is correct because applying a theme from the theme library instantly changes the visual styling (colors, fonts, layout) across the entire portal, which is a supported customization method for self-service users.

Exam trap

The trap here is that candidates often assume direct HTML or CSS editing is a valid customization method, but ServiceNow enforces a widget-based architecture where such direct edits are unsupported and would be overwritten by platform upgrades or portal refreshes.

Full explanation →
449
MCQeasy

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

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

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

Why this answer

ServiceNow dashboards have a configurable layout property that allows administrators to set the number of columns (e.g., 1, 2, or 3) without needing to rebuild the dashboard. By editing the dashboard's layout and changing the column count to 2, the existing reports will automatically rearrange into a side-by-side format, preserving all report configurations and data sources.

Exam trap

The trap here is that candidates often assume they must rebuild the dashboard from scratch (Option C) or use a complex customization (Option A), when ServiceNow provides a simple built-in layout property to adjust column count on existing dashboards.

How to eliminate wrong answers

Option A is wrong because UI Macros are used for custom UI elements or reusable server-side code, not for dynamically arranging report positions within a dashboard; they cannot modify dashboard column layouts. Option B is wrong because the 'report output format' (e.g., list, pie chart) controls how data is displayed within a single report, not the spatial arrangement of multiple reports on a dashboard. Option C is wrong because while creating a new dashboard with a two-column template would work, it is unnecessary and inefficient—the administrator can simply edit the existing dashboard's layout property to change the column count, avoiding the need to recreate and re-add reports.

Full explanation →
450
MCQmedium

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

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

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

Why this answer

The Report gauge widget is specifically designed to display a single metric, such as a count of open incidents, in a real-time gauge format on a dashboard. It allows the manager to configure a report that counts incidents assigned to their team with a status of 'Open', and the gauge updates automatically as data changes. This widget is part of the standard dashboard toolkit in ServiceNow for visualizing key performance indicators.

Exam trap

The trap here is that candidates often confuse the Report gauge widget with the HTML widget, thinking they can embed a custom gauge via HTML, but the Report gauge widget is the only one that natively binds to a ServiceNow report for automatic data refresh and formatting.

How to eliminate wrong answers

Option A is wrong because the Mashup widget is used to embed external web content or applications into a dashboard, not to display a real-time gauge of ServiceNow data. Option C is wrong because the HTML widget allows custom HTML content but does not natively connect to ServiceNow reports or provide real-time data updates without additional scripting. Option D is wrong because the Filter widget is used to apply filters to other widgets on a dashboard, not to display a gauge or metric itself.

Full explanation →
Page 5

Page 6 of 7

Page 7

All pages

1234567

Practice SNOW-CSA by domain

Target a specific domain to shore up weak areas.

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