Courseiva

ServiceNow Certified System Administrator CSA (SNOW-CSA) — Questions 151–225

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

Take a mock examExam hub
Page 2

Page 3 of 7

Page 4
151
MCQhard

A system administrator notices that users in the 'itil' role can see the 'cost' field on the 'cmdb_ci_server' table, but the requirement is to hide it from all except users with the 'cmdb_admin' role. The administrator has already created an ACL with 'read' operation, type 'record', condition 'current.cost' (no script) and granted 'no access' to all roles. However, the field is still visible. What is missing?

A.The ACL condition should use a script instead of a condition
B.The ACL must be set to 'mandatory'
C.The user must be removed from the 'itil' role
D.The ACL type must be 'field' instead of 'record'
AnswerD

Field ACLs control read/write access to individual fields.

Why this answer

A 'record' ACL controls access to the entire record, but the requirement is to hide a specific field ('cost') from certain roles. To control visibility at the field level, the ACL type must be 'field', not 'record'. A 'record' ACL determines whether a user can see or interact with the whole record, while a 'field' ACL governs access to individual fields.

Since the 'cost' field is still visible, the existing 'record' ACL is not applied to the field itself, allowing the 'itil' role to see it via default field-level access.

Exam trap

The trap here is that candidates often confuse 'record' ACLs with 'field' ACLs, assuming a record ACL with a condition on a field will hide that field, when in reality only a field ACL can control individual field visibility.

How to eliminate wrong answers

Option A is wrong because the condition 'current.cost' is a valid condition that checks if the field has a value; using a script is not required to hide a field, and the issue is the ACL type, not the condition format. Option B is wrong because 'mandatory' is a property for UI policies, not ACLs; ACLs do not have a 'mandatory' setting, and making an ACL mandatory would not change the type from record to field. Option C is wrong because removing the user from the 'itil' role would hide the field but does not address the root cause—the ACL is misconfigured as a record ACL instead of a field ACL, and the requirement is to hide the field from all except 'cmdb_admin', not to remove users from roles.

Full explanation →
152
MCQhard

A scheduled job runs a transform map to import data into the CMDB from an external asset management system. The transform map has a field mapping that uses script to derive the CI class based on asset type. Recently, imports have been failing with a 'GlideRecord: Invalid table name' error. What is the most likely cause?

A.The external system is sending malformed data.
B.The scheduled job does not have the right roles.
C.The script in the field mapping is returning a value that does not correspond to an existing table name.
D.The target table name in the transform map is misspelled.
AnswerC

If the script sets sys_class_name to a non-existent table, GlideRecord will throw 'Invalid table name'.

Why this answer

The error 'GlideRecord: Invalid table name' indicates that the script in the field mapping is returning a string that does not match any existing table (class) in the CMDB. When a transform map uses a script to derive the CI class, the returned value must be a valid table name (e.g., 'cmdb_ci_server'). If the script returns a misspelled, malformed, or non-existent table name, GlideRecord fails to instantiate the record, causing the import to fail.

Exam trap

The trap here is that candidates often confuse 'Invalid table name' with a data quality issue (Option A) or a configuration error in the transform map target (Option D), but the error is specifically tied to the dynamic table name returned by the script, not static configuration or external data format.

How to eliminate wrong answers

Option A is wrong because malformed data from the external system would typically cause parsing or validation errors, not a 'GlideRecord: Invalid table name' error, which is specific to table name resolution within ServiceNow. Option B is wrong because role issues would result in security or permission errors (e.g., 'Security restricted'), not a table name error; the scheduled job runs with the system's privileges, not a specific user's roles. Option D is wrong because the target table name in the transform map is used only for the overall import target; the error occurs during field mapping script execution, not at the transform map level, and a misspelled target table would cause a different error at import configuration time.

Full explanation →
153
MCQhard

You are a ServiceNow administrator for a healthcare organization. The CMDB contains sensitive patient data under strict compliance rules. You need to ensure that only authorized users can view the full details of certain CIs, while still allowing change management to reference the CIs. What is the best practice to achieve this?

A.Move the sensitive CIs to a separate CMDB instance.
B.Use Access Controls (ACLs) to restrict read access to the sensitive CI records.
C.Encrypt the fields containing sensitive data.
D.Remove the sensitive CIs from the CMDB and maintain them externally.
AnswerB

ACLs can grant selective read access, ensuring only authorized users see sensitive details.

Why this answer

Access Controls (ACLs) are the correct mechanism to restrict read access to sensitive CI records while still allowing Change Management to reference them. ACLs can be configured to grant read access only to authorized users or roles, and the cmdb_ci table or specific CI records can be targeted. This ensures compliance with data privacy rules without removing the CIs from the CMDB or breaking downstream processes like change requests that need to link to those CIs.

Exam trap

The trap here is that candidates often confuse encryption with access control, assuming that encrypting sensitive fields prevents unauthorized viewing, but encryption in ServiceNow does not enforce read permissions—it only protects data at rest, and users with read access can still decrypt and view the data unless ACLs are applied.

How to eliminate wrong answers

Option A is wrong because moving sensitive CIs to a separate CMDB instance would break the single CMDB architecture, requiring complex cross-instance integrations and potentially violating the principle of a single source of truth for configuration data. Option C is wrong because field-level encryption in ServiceNow is primarily for data at rest and does not control user-level read permissions; encrypted fields can still be visible to users with read access unless combined with ACLs, and encryption alone does not prevent authorized users from viewing the data. Option D is wrong because removing sensitive CIs from the CMDB and maintaining them externally would break Change Management's ability to reference those CIs, as change records require CI relationships to be tracked within the CMDB for impact analysis and compliance.

Full explanation →
154
MCQhard

An administrator creates a new ACL for the 'incident' table with type 'record', operation 'read', condition script 'current.assignment_group == gs.getUser().getMyGroups()', and requires role 'snc_internal'. A user with role 'snc_internal' who is a member of group 'Service Desk' can view incidents assigned to 'Service Desk' but cannot view incidents assigned to 'Network Support'. What is the most likely reason?

A.The condition script uses 'current.assignment_group' which returns a sys_id, but 'gs.getUser().getMyGroups()' returns a list of group names.
B.The condition script should use 'current.assignment_group.isOneOf(gs.getUser().getMyGroups())' instead.
C.The user does not have the 'snc_internal' role.
D.Another ACL with higher order denies read access to all incidents not matching the condition.
AnswerD

ACL order matters; a deny rule could be overriding.

Why this answer

ACLs in ServiceNow are evaluated in order of their 'order' field, and the first matching ACL (either allowing or denying access) determines the outcome. If another ACL with a higher order (lower numeric value) denies read access to incidents not matching the condition, that deny rule will take precedence over the new ACL, preventing the user from viewing incidents assigned to 'Network Support' even though the new ACL would allow it. The user's role and group membership are satisfied, so the issue lies in ACL ordering and a conflicting deny rule.

Exam trap

The trap here is that candidates focus on the syntax error in the condition script (options A and B) and overlook the ACL evaluation order, which is a more fundamental concept in ServiceNow that explains why the user can see some incidents but not others despite the flawed condition.

How to eliminate wrong answers

Option A is wrong because 'current.assignment_group' returns a sys_id (a reference to the sys_user_group table), and 'gs.getUser().getMyGroups()' returns a list of group sys_ids, not group names, so the comparison is technically valid but fails because it compares a single sys_id to a list of sys_ids (the condition script should use an array method like indexOf or isOneOf). Option B is wrong because while 'isOneOf' is a valid method for comparing a field to a list, the condition script as written would still fail due to the type mismatch (single value vs list), and the question asks for the 'most likely reason' given the described behavior—option D better explains why the user cannot see 'Network Support' incidents despite having the correct role and group membership. Option C is wrong because the user has the 'snc_internal' role, as stated in the question, so this is not the issue.

Full explanation →
155
MCQhard

Refer to the exhibit. A UI Policy is configured with the above condition script to make the 'work_notes' field mandatory when state is 1 and caller_id is valid. When the state is 1 and caller_id is empty, the mandatory attribute is not applied. What is the cause?

A.The condition uses '&&' instead of '||'
B.There is a syntax error in the script
C.The isValid() method is not available in UI Policy context
D.The caller_id field is empty
AnswerC

UI Policy scripts run client-side and cannot use server-side methods like isValid().

Why this answer

The `isValid()` method is a GlideRecord method that operates on the server side, not a client-side method available in UI Policy scripts. UI Policies run on the client side (in the browser), so `isValid()` is not defined in that context, causing the condition to fail silently or not behave as expected. This is why the mandatory attribute is not applied when `caller_id` is empty, even though the script intends to check for a valid record.

Exam trap

ServiceNow exams often test the distinction between client-side and server-side scripting contexts in ServiceNow, and the trap here is that candidates assume `isValid()` is a generic JavaScript method available everywhere, when in fact it is a GlideRecord method restricted to server-side execution.

How to eliminate wrong answers

Option A is wrong because using '&&' (AND) is correct for requiring both conditions (state is 1 AND caller_id is valid) to be true; using '||' (OR) would incorrectly apply the mandatory attribute if either condition is true, which is not the intended logic. Option B is wrong because there is no syntax error in the script; the issue is a runtime error due to an undefined method, not a syntax issue. Option D is wrong because the caller_id field being empty is the scenario described in the question, not the cause of the failure; the cause is that the script cannot evaluate the condition correctly when caller_id is empty due to the missing method.

Full explanation →
156
MCQmedium

You are troubleshooting an issue with the Virtual Agent chatbot. Users report that when they ask the chatbot 'How do I reset my password?', the chatbot responds with 'I'm sorry, I don't understand that question.' However, the chatbot correctly answers other questions like 'What is the IT support number?' The password reset topic is configured with a user input of 'password reset' and a response that provides instructions. The chatbot's NLU model has been trained with over 50 utterances for the password reset topic. The issue started after a recent update to the chatbot's configuration. What is the most likely cause?

A.The password reset topic is inactive
B.The password reset topic was deleted
C.The NLU model needs more training utterances
D.The user input does not match any utterances exactly
AnswerA

An inactive topic will not respond.

Why this answer

The issue started after a recent configuration update, and the password reset topic is correctly configured with a user input and response. The most likely cause is that the topic was accidentally set to inactive, which prevents the chatbot from matching any user utterances to it, even though the NLU model is trained. An inactive topic will not be considered during intent classification, resulting in the fallback response.

Exam trap

The trap here is that candidates may assume the NLU model needs more training data (Option C) when the real issue is a simple configuration toggle (topic inactive), which is a common oversight after updates.

How to eliminate wrong answers

Option B is wrong because if the topic were deleted, the chatbot would not have any configuration for password reset, but the question states the topic is still configured with a user input and response. Option C is wrong because the NLU model has already been trained with over 50 utterances, which is typically sufficient; the issue appeared after a configuration change, not due to lack of training data. Option D is wrong because the user input 'password reset' does not need to match utterances exactly—the NLU model uses natural language understanding to match variations, and the chatbot correctly answers other questions, indicating the NLU engine is working.

Full explanation →
157
MCQhard

A system administrator needs to allow users with the 'incident_manager' role to delete incidents only if the incident state is 'New' or 'Work in Progress'. They create an ACL with the following conditions: type='record', operation='delete', name='incident', condition: gs.hasRole('incident_manager') && current.state == 1 || current.state == 2. After testing, users with the role can delete incidents in any state. What is the most likely cause?

A.The ACL is set on the 'incident' table but should be on the 'task' table.
B.The condition lacks parentheses to group the state checks.
C.The ACL should be created using the condition builder instead of script.
D.The condition does not check for the 'incident_manager' role.
AnswerB

Without parentheses, the OR binds weaker than AND, allowing state 2 to bypass role check.

Why this answer

The condition `gs.hasRole('incident_manager') && current.state == 1 || current.state == 2` is evaluated by JavaScript operator precedence, where `&&` binds tighter than `||`. This means it is parsed as `(gs.hasRole('incident_manager') && current.state == 1) || current.state == 2`. Consequently, any user (even without the role) can delete incidents in state 2 (Work in Progress), and users with the role can delete incidents in any state because the role check only applies to state 1.

Adding parentheses—`gs.hasRole('incident_manager') && (current.state == 1 || current.state == 2)`—fixes the logic.

Exam trap

ServiceNow often tests operator precedence in ACL conditions, tricking candidates into overlooking that `&&` binds tighter than `||`, which causes the role check to apply only to the first state condition.

How to eliminate wrong answers

Option A is wrong because the ACL is correctly set on the 'incident' table; the 'task' table is a parent table and would not apply to incident-specific state values. Option C is wrong because the condition builder is a UI wrapper that generates the same script; the issue is operator precedence, not the method of creation. Option D is wrong because the condition does check for the 'incident_manager' role via `gs.hasRole('incident_manager')`, but the lack of parentheses causes the role check to be bypassed for state 2.

Full explanation →
158
MCQhard

Refer to the exhibit. A workflow includes a 'Run Script' activity with the above configuration. What will happen when the workflow reaches this activity?

A.The script will cause an error because current is not defined in workflow.
B.The script runs but current.update() is unnecessary because state is set automatically.
C.The script runs and updates the current record's state to pending.
D.The script only runs when the workflow is started, not when the activity is reached.
AnswerC

The script uses current to set state and update the record.

Why this answer

The 'Run Script' activity in a ServiceNow workflow executes the provided script when the workflow reaches that activity. The script uses the 'current' GlideRecord object, which is automatically available in workflow scripts and represents the record that triggered the workflow. The 'current.state = 3' line sets the state field to the value for 'pending' (typically 3 in the standard incident or task table), and 'current.update()' commits this change to the database, so the record's state is updated to pending.

Exam trap

The trap here is that candidates assume 'current.update()' is optional or that 'current' is not available in workflow scripts, when in fact it is always available and update() is required to save changes.

How to eliminate wrong answers

Option A is wrong because 'current' is a predefined variable in ServiceNow workflow scripts, representing the record that triggered the workflow, so it is always defined. Option B is wrong because 'current.update()' is necessary to persist the state change to the database; setting the field value alone does not commit the change. Option D is wrong because the 'Run Script' activity executes the script each time the workflow reaches that activity, not only when the workflow is started.

Full explanation →
159
MCQeasy

A scheduled report is generated but not sending email notifications to recipients. What should the administrator check first?

A.Check the report source definition.
B.Check the report filter to ensure data exists.
C.Check the report output format (e.g., PDF, CSV).
D.Check the email notification configuration for the scheduled report.
AnswerD

The email notification settings control whether and to whom the report is sent; misconfiguration here would prevent delivery.

Why this answer

The most likely cause of a scheduled report generating but not sending email notifications is a misconfiguration in the email notification settings for that specific schedule. The administrator should first verify that the 'Send email' checkbox is enabled, that valid recipients are listed, and that the notification is not being suppressed by a condition or an inactive email account. Checking the email notification configuration directly addresses the delivery mechanism, which is the immediate point of failure.

Exam trap

The trap here is that candidates often jump to checking the report's data or filters (Options A or B) because they assume the report is empty or broken, when in fact the report generates correctly but the email delivery mechanism is misconfigured.

How to eliminate wrong answers

Option A is wrong because the report source definition determines what data the report queries, not how the results are delivered; if the report generates successfully, the source definition is working. Option B is wrong because checking the report filter for data existence is irrelevant if the report already generated; the issue is with notification delivery, not data population. Option C is wrong because the output format (PDF, CSV, etc.) affects the file attached to the email, but if the email is not being sent at all, the format is not the root cause.

Full explanation →
160
Multi-Selecthard

Which TWO of the following are true about the Application Navigator in the UI16 interface?

Select 2 answers
A.Module visibility is controlled by roles via the 'Requires role' field
B.Modules are grouped under 'modules' in the navigator
C.Personalizing a module removes it from the navigator for all users
D.The navigator can be customized by any user to reorganize modules
E.Users can add a module to their 'Favorites' by right-clicking the module
AnswersA, E

Modules can be restricted to specific roles.

Why this answer

In the UI16 interface, module visibility is controlled by roles through the 'Requires role' field on the module record. When a user does not have the specified role, the module is hidden from their Application Navigator. This is a core access control mechanism in ServiceNow.

Exam trap

The trap here is confusing personalization (which only affects the current user) with global configuration (which affects all users), leading candidates to incorrectly select option C or D.

Full explanation →
161
Multi-Selectmedium

Which TWO of the following are valid ways to trigger an SLA in ServiceNow? (Choose exactly 2.)

Select 2 answers
A.When a task is not updated for 24 hours
B.When a new incident is created with a specific category
C.When a scheduled job runs at a specific time each day
D.Automatically for every record in the incident table
E.When an incident is reassigned to a different assignment group
AnswersB, E

SLA definitions can have start conditions based on record creation and field values.

Why this answer

ServiceNow SLAs can be triggered by a condition defined in an SLA definition, such as when a new incident is created with a specific category. This is achieved by configuring the 'Start Condition' on the SLA definition to evaluate field values like 'Category' upon record creation.

Exam trap

The trap here is confusing SLA start conditions with SLA breach conditions or time-based triggers, leading candidates to select options that describe when an SLA is breached (A) or a recurring job (C) rather than how an SLA is initiated.

Full explanation →
162
Multi-Selecthard

An administrator is troubleshooting an import that is failing silently. The import set rows show 'Processed' with no errors, but no records are created or updated in the target table. Which THREE areas should the admin investigate?

Select 3 answers
A.Check if the coalescing field is set correctly in the transform map.
B.Check if the target table has a 'sys_id' field.
C.Check if the field mappings are complete and correct.
D.Check if the import set table is set as the target table.
E.Check if there is a transform script that conditionally skips record creation.
AnswersA, C, E

If coalescing is set to a field that does not match, no updates may occur.

Why this answer

The coalescing field in the transform map determines how ServiceNow matches incoming records to existing records in the target table. If the coalescing field is misconfigured or missing, the import may appear to process successfully (rows show 'Processed') but no records are created or updated because the system cannot identify which records to insert or update, leading to a silent failure.

Exam trap

ServiceNow often tests the misconception that 'Processed' status means records were successfully created or updated, when in fact it only indicates the transform map ran without throwing an error, not that data was committed to the target table.

Full explanation →
163
MCQmedium

The section 'Assignment Information' currently displays two fields in one row. An administrator wants to add a new field 'due_date' to this section, placing it in a new row below the existing fields. What should the administrator do?

A.Set the order of 'due_date' to 3 in the Dictionary Override
B.Change the number of columns in the section to 1
C.Create a new section named 'Due Date' and place the field there
D.Use Form Designer to drag the 'due_date' field into the section and drop it below the current fields
AnswerD

Form Designer allows precise placement of fields in rows and columns.

Why this answer

The Form Designer allows administrators to visually rearrange fields within a section, including moving a field to a new row below existing fields. By dragging the 'due_date' field into the 'Assignment Information' section and dropping it below the current fields, the field will automatically be placed in a new row, as the section's column layout (default 2 columns) will wrap fields into rows based on their order. This is the standard method for adding fields to existing sections without altering the section's column configuration.

Exam trap

The trap here is that candidates often confuse the 'order' property in the Dictionary Override (which controls field sequence across the entire form) with the visual row placement within a section, leading them to incorrectly believe that setting order to 3 will automatically place the field in a new row, when in fact the section's column count and the Form Designer's drag-and-drop are the correct mechanisms for controlling row placement.

How to eliminate wrong answers

Option A is wrong because setting the order of 'due_date' to 3 in the Dictionary Override only controls the field's position within the form's field order, but does not guarantee it will appear in a new row below existing fields; the section's column layout determines row wrapping, and simply changing the order may cause the field to appear in the same row as other fields if the column count allows. Option B is wrong because changing the number of columns in the section to 1 would force all fields into a single column, which would place 'due_date' in a new row but would also restructure the entire section, potentially breaking the existing two-field-per-row layout and causing unintended layout changes for other fields. Option C is wrong because creating a new section named 'Due Date' would separate the field from the 'Assignment Information' section, which is not what the administrator wants; the requirement is to add the field to the existing section, not to create a separate section.

Full explanation →
164
MCQhard

An administrator discovers that a scheduled discovery job is creating duplicate CI records for the same physical server. The server has two IP addresses (one for management, one for production). What is the most likely cause?

A.The discovery schedule is set to run too frequently.
B.The discovery job is configured to scan only the management IP.
C.The identification rule for the CI class does not include a unique hardware identifier like serial number.
D.The server has too many IP addresses for discovery to handle.
AnswerC

Without a unique identifier, each IP may create a separate CI.

Why this answer

ServiceNow's CMDB uses identification rules to determine whether a discovered CI is new or matches an existing record. For a physical server with multiple IP addresses, the identification rule must include a unique hardware identifier such as a serial number (e.g., from SMBIOS) to prevent duplicate CIs. Without that, the system may treat each IP address as a separate CI, even though they belong to the same server.

Exam trap

The trap here is that candidates often assume duplicate CIs are caused by scheduling or scanning frequency, when the real issue is the absence of a proper unique identifier in the identification rule, which is a core CMDB concept tested in the SNOW-CSA exam.

How to eliminate wrong answers

Option A is wrong because the frequency of the discovery schedule does not cause duplicate CI records; it only affects how often the scan runs. Option B is wrong because scanning only the management IP would not create duplicates—it would simply discover one IP, not two. Option D is wrong because ServiceNow discovery can handle multiple IP addresses on a single server; the issue is not the number of IPs but the lack of a unique identifier in the identification rule.

Full explanation →
165
MCQhard

An administrator needs to create a UI action that appears on the form context menu for the Incident table, but only when the record is in 'In Progress' state. Which configuration is required?

A.Create a UI policy that changes the form when state is 'In Progress'
B.Write an ACL on the UI action table
C.Set the condition on the UI action to 'current.state == 2'
D.Assign the UI action to a role that only users in this state have
AnswerC

Condition script on UI action shows/hides it based on state.

Why this answer

UI actions can have a condition field that evaluates server-side JavaScript. Setting the condition to 'current.state == 2' ensures the UI action appears only when the Incident record's state field equals the 'In Progress' value (typically 2 in the default state model). This is the standard, built-in mechanism for controlling UI action visibility based on record data.

Exam trap

The trap here is confusing UI actions with UI policies or ACLs, leading candidates to select options that control field behavior or security instead of the direct condition field on the UI action itself.

How to eliminate wrong answers

Option A is wrong because UI policies control field visibility, mandatory status, and read-only behavior on forms; they do not control the appearance of UI actions in the context menu. Option B is wrong because ACLs (Access Control Lists) control data access and security permissions, not the conditional display of UI actions on a form context menu. Option D is wrong because roles control which users can see or use a UI action, not the state of the current record; a user with the role would see the action regardless of the record's state.

Full explanation →
166
MCQhard

A business rule set to run 'async' is supposed to update a large number of child records. The administrator notices that the updates are not being applied consistently. What is the most likely reason?

A.The business rule condition is incorrect
B.The system property 'glide.sys.schedulers.max_threads' is set too low
C.The async queue processes multiple instances simultaneously, causing race conditions
D.The business rule is running 'before' instead of 'after'
AnswerC

Async rules are queued and may run in parallel, leading to race conditions.

Why this answer

When a business rule is set to run 'async', it executes asynchronously via the system's queue. If the business rule updates a large number of child records, multiple instances of the same async business rule can be processed simultaneously by different queue workers. This concurrency can lead to race conditions, where one instance reads stale data or overwrites changes made by another instance, resulting in inconsistent updates.

Exam trap

The trap here is that candidates often confuse 'async' execution with simple timing or thread limits, overlooking the fundamental concurrency issue of race conditions in asynchronous processing.

How to eliminate wrong answers

Option A is wrong because an incorrect condition would cause the business rule to either not run at all or run on the wrong records, not to apply updates inconsistently across a large set of child records. Option B is wrong because the system property 'glide.sys.schedulers.max_threads' controls the maximum number of scheduler threads, not the async queue processing; the async queue uses a separate worker mechanism. Option D is wrong because the 'before' vs 'after' timing affects when the rule runs relative to the database operation, but does not cause inconsistency in updates when the rule is set to run asynchronously.

Full explanation →
167
MCQeasy

A record producer is configured to create a task when a user submits a form from the service portal. The task is created but the variables from the form are not mapped. What is the most likely cause?

A.The record producer's mandatory fields are not all filled
B.The target table does not have the same fields as the source
C.The 'Variable mapping' section of the record producer is not configured
D.The service portal is not configured to pass variables to the record producer
AnswerC

Variable mapping specifies which source fields map to which target fields.

Why this answer

The record producer's 'Variable mapping' section is responsible for explicitly mapping form variables to fields on the target table. When this section is left unconfigured, the system creates the task record but does not transfer variable values from the service portal form, even if the form is submitted successfully. This is a common oversight because the record producer itself is triggered correctly, but the variable data is not passed without explicit mapping.

Exam trap

The trap here is that candidates assume the service portal automatically passes variable values to the target table fields, but ServiceNow requires explicit variable mapping in the record producer to transfer form data to the task record.

How to eliminate wrong answers

Option A is wrong because mandatory fields being unfilled would prevent the record producer from creating the task at all, not create it without variable mapping. Option B is wrong because the target table does not need to have the same fields as the source; variable mapping is what bridges the form variables to target table fields, and mismatched field names are handled by mapping, not by field existence. Option D is wrong because the service portal inherently passes all form variables to the record producer upon submission; the issue is that the record producer is not configured to consume those variables via the Variable mapping section.

Full explanation →
168
MCQeasy

The SLA condition script above is used in an SLA definition. Standard incident states are: 1=New, 2=In Progress, 3=On Hold, 6=Resolved, 7=Closed. What is the effect of this condition?

A.The SLA does not start for any state
B.The SLA starts when the incident state is 'Active'
C.The SLA starts when the incident state is 'In Progress'
D.The SLA starts when the incident state is 'New'
AnswerB

The SLA starts when the incident state is 'Active'. This is correct because the condition script excludes standard numeric states (1,2,3,6,7), so it returns true for non-standard states like a custom 'Active' state, allowing the SLA to start.

Why this answer

The condition script evaluates the incident state and returns true when the state is not 1 (New), 2 (In Progress), 3 (On Hold), 6 (Resolved), or 7 (Closed). Since the standard states are numeric, any state value that does not match these numbers—such as a custom state labeled 'Active' with a value like 4 or 5—will cause the script to return true, starting the SLA. This is why option B is correct: the SLA starts when the incident state is 'Active', assuming 'Active' is a custom state not in the standard list.

Exam trap

The trap here is that candidates assume the SLA starts on the first standard state (New) or on 'In Progress', but the condition explicitly excludes those values, so the SLA only starts for non-standard states—often a custom 'Active' state that is not listed in the standard incident state values.

How to eliminate wrong answers

Option A is wrong because the condition script does not prevent the SLA from starting for all states; it only prevents starting for the explicitly listed standard states (1,2,3,6,7), meaning the SLA will start for any other state. Option C is wrong because 'In Progress' corresponds to state value 2, which is explicitly excluded by the condition (currentState != 2), so the SLA does not start when the incident is in 'In Progress'. Option D is wrong because 'New' corresponds to state value 1, which is also excluded by the condition (currentState != 1), so the SLA does not start when the incident is in 'New'.

Full explanation →
169
MCQeasy

A system administrator wants to add a new section to a form. Which component should they edit?

A.Dictionary
B.Table
C.UI Page
D.Form Layout
AnswerD

Form Layout allows adding, removing, and ordering sections on a form.

Why this answer

The Form Layout component is the correct choice because it directly controls the arrangement and visibility of fields, sections, and related lists on a ServiceNow form. Editing the Form Layout allows the administrator to add a new section by dragging and dropping a section placeholder or by configuring the form's structure through the Form Layout UI.

Exam trap

The trap here is that candidates often confuse the Dictionary (which defines field metadata in ServiceNow) with the Form Layout (which controls visual arrangement), leading them to incorrectly select Dictionary when the question is about adding a section to a ServiceNow form.

How to eliminate wrong answers

Option A is wrong because the Dictionary defines the properties of individual fields (e.g., type, length, reference) but does not control the layout or sections on a form. Option B is wrong because a Table is a database object that stores records; editing the table schema does not affect the visual form layout or add sections. Option C is wrong because UI Pages are used to create custom standalone pages or widgets, not to modify the standard form layout or add sections to an existing form.

Full explanation →
170
MCQeasy

An administrator creates a notification for the 'incident' table to send an email when the state changes to 'resolved'. The notification works for most users, but some users report not receiving the email. What is the most likely cause?

A.The notification weight is set too high.
B.The notification is not set to 'Active'.
C.The notification does not have an email template selected.
D.The users have set their 'Notification' preference to 'Do not send' for that type.
AnswerD

Individual user preferences can suppress emails.

Why this answer

The most likely cause is that the users have configured their personal Notification preference to 'Do not send' for that notification type. In ServiceNow, users can override system-level notification settings by setting their preference to suppress specific notification types, which would prevent the email from being sent even though the notification is active and properly configured.

Exam trap

The trap here is that candidates often assume the issue is a global configuration error (like inactive notification or missing template) rather than recognizing that user-level preferences can selectively block notifications for some users while others receive them.

How to eliminate wrong answers

Option A is wrong because notification weight controls the order in which notifications are processed, not whether they are sent; a high weight would not prevent delivery. Option B is wrong because if the notification were not active, no users would receive the email, contradicting the scenario where most users do receive it. Option C is wrong because if no email template were selected, the notification would fail for all users, not just a subset; the system requires a template to generate the email body.

Full explanation →
171
Matchingmedium

Match each ServiceNow UI element to its description.

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

Concepts
Matches

Displays and allows editing of a single record

Shows multiple records in a table view

Displays reports and metrics on a single page

Customizable landing page for users

Menu for accessing modules and applications

Why these pairings

These are fundamental UI components in ServiceNow. The Application Navigator is the left panel providing access to modules, the Application Menu is a dropdown showing installed applications, Modules are components within applications, and Favorites are bookmarked items for quick access. Common confusions include swapping the Application Navigator and Application Menu.

Full explanation →
172
MCQeasy

A company wants to ensure that critical servers in the CMDB have accurate operational status. Which CMDB feature should the administrator configure to automatically update the operational status based on monitoring tools?

A.CI Relationships
B.Application Services
C.CMDB Health Score
D.Identification and Reconciliation
AnswerD

This feature automatically updates CI attributes from authorized sources.

Why this answer

The Identification and Reconciliation (IRE) engine is the correct feature because it processes incoming data from monitoring tools and automatically updates the operational status of CIs in the CMDB. It uses identification rules to match incoming data to existing CIs and reconciliation rules to resolve conflicts, ensuring the operational status reflects real-time monitoring data without manual intervention.

Exam trap

The trap here is that candidates often confuse CMDB Health Score (a reporting metric) with the IRE engine (an automated data processing feature), leading them to select Option C instead of the correct Identification and Reconciliation feature.

How to eliminate wrong answers

Option A is wrong because CI Relationships define how CIs are connected (e.g., 'Depends on' or 'Runs on'), but they do not update operational status based on monitoring tools. Option B is wrong because Application Services represent a logical grouping of CIs that deliver a business service, but they do not automatically update CI operational status from monitoring data. Option C is wrong because CMDB Health Score is a metric that measures the overall quality and completeness of the CMDB, not a mechanism to update individual CI operational status.

Full explanation →
173
MCQeasy

A user reports that they are unable to see any records in the 'incident' table, even though they have the itil role. The administrator checks the ACLs and finds that there are no read ACLs defined for the incident table. What will happen?

A.The system will create a default read ACL that grants access to the itil role.
B.All users can read all incident records.
C.No users can read any incident records.
D.Only users with the admin role can read incident records.
AnswerC

Correct: No read ACL denies all read access.

Why this answer

In ServiceNow, if no read ACLs are defined for a table, the system defaults to a 'deny all' behavior. This means that no users, including those with the itil role, can read any records in the incident table. The itil role grants access to incident records only when a read ACL explicitly allows it; without any read ACL, the implicit denial takes effect.

Exam trap

The trap here is that candidates often assume the itil role provides blanket read access to the incident table, but ServiceNow requires explicit read ACLs to grant that access; without them, the implicit deny blocks all users, including itil role holders.

How to eliminate wrong answers

Option A is wrong because ServiceNow does not automatically create a default read ACL that grants access to the itil role; instead, the absence of any read ACL results in an implicit deny for all users. Option B is wrong because without any read ACLs, the system does not allow all users to read records; it denies access to everyone. Option D is wrong because even users with the admin role are subject to the same implicit deny when no read ACLs exist; however, admin users can bypass ACLs via the 'admin' role's inherent 'security_admin' privilege, but the question's scenario implies standard ACL behavior without admin bypass being the default for all users.

Full explanation →
174
Multi-Selecthard

Which TWO are valid methods to configure a service catalog item to require an approval only if the cost exceeds $500?

Select 2 answers
A.Add a condition on the approval rule that checks the requested item's cost.
B.Create a business rule on the request that triggers approval for high-cost items.
C.Use a workflow that checks the variable and conditionally runs an approval activity.
D.Use Flow Designer to send for approval only when cost > $500.
E.Set the 'Approval' field on the catalog item to 'Required' and add a cost condition.
AnswersA, C

Approval rules support conditions on the requested item, such as cost.

Why this answer

Approval rules in Service Catalog can include conditions that evaluate the requested item's cost. By adding a condition such as 'cost > 500', the rule triggers approval only when the cost exceeds $500, without requiring a workflow or Flow Designer. This is a native, low-code method for conditional approvals.

Exam trap

The trap here is that candidates confuse the 'Approval' field on the catalog item (which is a simple yes/no toggle for mandatory approval) with the ability to add conditions, when in reality conditions are only available on approval rules, not on that field.

Full explanation →
175
MCQeasy

Which table field in a notification record defines the email subject?

A.Short description
B.Subject
C.Title
D.Name
AnswerB

This field holds the email subject line.

Why this answer

In ServiceNow notification records, the 'Subject' field (option B) directly defines the email subject line. This field supports template variables and scripted expressions to dynamically generate the subject content based on the record data. The other fields serve different purposes: Short description is a summary of the notification, Title is not a standard field in notification records, and Name is the unique identifier for the notification record itself.

Exam trap

ServiceNow often tests the distinction between the 'Subject' field and the 'Short description' field, as candidates may confuse the email subject with the notification's internal summary, especially when both fields appear similar in the UI.

How to eliminate wrong answers

Option A is wrong because the 'Short description' field in a notification record is used for internal identification or summary purposes, not for the email subject line. Option C is wrong because 'Title' is not a standard field in notification records; it may appear in other record types like knowledge articles or reports. Option D is wrong because the 'Name' field is the unique identifier for the notification record (e.g., 'Incident Notification'), not the email subject.

Full explanation →
176
Multi-Selectmedium

An administrator wants to ensure that the CMDB remains accurate after a change management process. Which TWO actions should the administrator take? (Select two.)

Select 2 answers
A.Use CI Change Request to link CIs to change requests.
B.Create a business rule to update CI status when a change request is approved.
C.Set up CMDB Data Manager to automatically update CIs based on change requests.
D.Enable CMDB CI Class Manager to enforce class hierarchy.
E.Configure CMDB Health Verification to run daily on all CIs.
AnswersA, E

CI Change Request automatically associates CIs with changes, helping keep relationships accurate.

Why this answer

Running CMDB Health Verification helps identify stale or incorrect CIs, ensuring accuracy. Using CI Change Request links CIs to change requests, automatically updating status. Option B (creating a business rule) is a custom approach, not a standard best practice.

Option C (Data Manager) is for bulk updates, not accuracy. Option D (CI Class Manager) enforces class hierarchy but does not directly ensure accuracy after change management.

Full explanation →
177
MCQmedium

A company uses Service Operations Workspace to manage incidents. They have configured an SLA definition for 'Resolution' with a stop condition when the incident state is 'Resolved'. However, the SLA is not stopping when the incident is resolved. The administrator checks the SLA log and sees that the SLA is still running. The SLA definition is active and attached to a specific SLA definition record. The administrator notices that the incident state is indeed set to 'Resolved', and the SLA timeline is set to 24x7. What should the administrator do to fix the issue?

A.Ensure the SLA definition's timeline is set to '24x7'.
B.Create a business rule to stop the SLA when the incident resolves.
C.Review and correct the stop condition in the SLA definition to properly reference the incident state field.
D.Set the SLA definition's 'Stop on Resolution' field to true.
AnswerC

The stop condition must be syntactically correct and reference the correct field (e.g., state == 3).

Why this answer

The SLA stop condition is a condition script that must evaluate to true for the SLA to stop. If the stop condition does not correctly reference the incident state field (e.g., using 'state' instead of 'incident_state' or a wrong value), the SLA will continue running even when the incident is resolved. The administrator must review and correct the stop condition script to ensure it properly checks for the 'Resolved' state.

Exam trap

The trap here is that candidates may assume a simple checkbox or field like 'Stop on Resolution' exists, or that changing the timeline will fix the issue, when in reality the stop condition is a script that must be correctly configured.

How to eliminate wrong answers

Option A is wrong because the timeline is already set to 24x7, as noted in the scenario, so changing it again will not fix the stop condition issue. Option B is wrong because creating a business rule to stop the SLA is unnecessary and not the standard approach; SLA stop conditions are handled natively within the SLA definition itself. Option D is wrong because there is no 'Stop on Resolution' field in SLA definitions; the stop behavior is controlled entirely by the stop condition script.

Full explanation →
178
Multi-Selecteasy

A notification should be sent to the change manager when a change request is submitted. Which TWO fields must be configured? (Choose TWO.)

Select 2 answers
A.Set the notification to active.
B.Set a weight value.
C.Set the condition 'State changes to new' in 'When to send' tab.
D.Add 'Change manager' role to 'Recipients' in 'Who will receive' tab.
E.Select an email template.
AnswersC, D

Defines the trigger.

Why this answer

The 'When to send' tab defines the trigger condition for the notification. Setting the condition to 'State changes to new' ensures the notification is sent exactly when a change request is submitted (i.e., when its state transitions to 'new'). Option D is correct because the 'Who will receive' tab specifies the recipients; adding the 'Change manager' role ensures that all users with that role receive the notification.

Exam trap

ServiceNow often tests the distinction between mandatory configuration fields and optional enhancements; the trap here is that candidates mistakenly select 'active' or 'email template' as required, when only the trigger condition and recipient definition are essential for the notification to function as intended.

Full explanation →
179
Multi-Selectmedium

Which TWO scenarios would require a Catalog UI Policy instead of a Catalog Client Script?

Select 2 answers
A.Displaying a warning message when a variable is invalid
B.Hiding a variable based on another variable's value
C.Setting a variable's value from a record producer mapping
D.Making a variable read-only after the catalog item is submitted
E.Making a variable mandatory only when a condition is met
AnswersB, E

UI Policy can control visibility declaratively without scripting.

Why this answer

Catalog UI Policies are server-side scripts that run before the form is rendered, making them ideal for conditionally hiding variables based on other variable values. Unlike Catalog Client Scripts, which run client-side and can be bypassed, UI Policies enforce visibility and mandatory rules on the server, ensuring compliance even if JavaScript is disabled.

Exam trap

ServiceNow often tests the misconception that UI Policies can show messages or set values, when in fact they only control visibility, mandatory, and read-only states, while messages and value setting require Client Scripts or other mechanisms.

Full explanation →
180
MCQmedium

A catalog item variable has a reference qualifier that limits the choices to active users only. However, users can still select inactive users. What is the most likely cause?

A.The variable is set to allow 'any' value
B.The user has admin role and ignores qualifier
C.The reference qualifier uses JavaScript that runs on the client but not server
D.The reference qualifier is written incorrectly
AnswerD

Correct: The reference qualifier is most likely written incorrectly, failing to properly filter out inactive users.

Why this answer

Reference qualifiers in ServiceNow are always server-side. They are evaluated when the catalog item is loaded and when the record is saved. If inactive users are still selectable, the most likely cause is that the reference qualifier script is incorrectly written or missing.

Therefore, option D is correct. Option A is incorrect because the 'any' setting does not bypass reference qualifiers. Option B is incorrect because admin role does not ignore reference qualifiers for variables.

Option C is incorrect because reference qualifiers do not run on the client side; they are server-side only.

Exam trap

Candidates may assume that a reference qualifier that appears to work in the UI is correctly enforced on submission, but the real issue is often a misconfiguration (e.g., a script error or incorrect condition) in the server-side qualifier. Another trap is thinking that the admin role or the 'allow any' setting can bypass reference qualifiers.

How to eliminate wrong answers

Option A is wrong because setting a variable to allow 'any' value removes all restrictions, but the question states the reference qualifier is present and limits choices to active users, so the issue is not about allowing any value. Option B is wrong because admin roles do not ignore reference qualifiers on catalog item variables; admins may bypass ACLs but reference qualifiers are enforced for all users unless explicitly overridden. Option D is wrong because the qualifier is written correctly (it limits to active users in the UI), but the problem is that it is not enforced server-side, not that the syntax is incorrect.

Full explanation →
181
MCQeasy

Refer to the exhibit. An administrator is trying to import data into a custom CI table but receives this error. What is the most likely cause?

A.The transform map is referencing a table that hasn't been created.
B.The import set has incorrect column mappings.
C.The user does not have permission to write to the table.
D.The CMDB is locked for maintenance.
AnswerA

The error indicates the target table is missing; the table must be created first.

Why this answer

The error indicates that the transform map is trying to populate a custom CI table that does not yet exist in the CMDB. In ServiceNow, a transform map must reference an existing target table; if the table has not been created (e.g., via the 'Create Table' module), the import will fail with this specific error. This is the most likely cause because the error message directly points to a missing table reference.

Exam trap

ServiceNow often tests the distinction between transform map errors (missing table) versus import set row errors (column mapping or permission issues), and the trap here is that candidates confuse a missing table error with a column mapping problem.

How to eliminate wrong answers

Option B is wrong because incorrect column mappings would produce a different error, such as 'Column not found' or 'Invalid field', not a missing table error. Option C is wrong because permission errors typically result in 'Access denied' or 'Insufficient rights' messages, not a table-not-found error. Option D is wrong because a locked CMDB would prevent all imports with a maintenance lock message, not a table-specific error.

Full explanation →
182
MCQmedium

An administrator wants to send an email notification to the user's manager when a specific catalog item is requested. Which approach is most efficient?

A.Configure an approval rule that sends email.
B.Create a notification on the Requested Item table with a condition on the catalog item.
C.Add a notification to the catalog item directly.
D.Use a Flow to send email after the record is created.
AnswerB

Correct: This is the best practice for sending emails based on catalog item.

Why this answer

Creating a notification on the Requested Item [sc_req_item] table with a condition on the catalog item is the most efficient approach. It leverages the platform's native event-based notification system, which triggers directly on the table where the record is created, without requiring additional configuration like approval rules or flows. This method minimizes overhead and ensures the notification fires only when the specific catalog item is requested.

Exam trap

The trap here is that candidates often confuse the location where notifications are configured—thinking they can attach a notification directly to a catalog item (Option C) or that approval rules are the correct mechanism for sending emails (Option A), when in fact notifications must be defined on the underlying table with a condition to filter the specific record.

How to eliminate wrong answers

Option A is wrong because approval rules are designed to manage approval processes, not to send general email notifications; configuring an approval rule solely for email adds unnecessary complexity and may interfere with actual approval workflows. Option C is wrong because catalog items do not have a direct notification configuration; notifications must be defined on a table (like Requested Item) and then scoped via conditions, so adding a notification 'to the catalog item directly' is not a supported mechanism. Option D is wrong because while a Flow could send an email, it is less efficient than a native notification for this simple use case—flows introduce additional overhead (e.g., Flow Designer triggers, execution context) and are better suited for multi-step automation, not a single email trigger.

Full explanation →
183
MCQhard

During a catalog item checkout, the system fails to create the requested item record. The flow that triggers on 'Requested' state runs but fails. Which log should be examined first?

A.System log > Security
B.System log > Flow
C.System log > Workflow
D.System log > Scripts
AnswerB

Flow Designer logs contain detailed information about flow executions and errors.

Why this answer

The flow that runs on the 'Requested' state is a Flow Designer flow, and its execution details—including errors, inputs, outputs, and step failures—are logged in System Log > Flow. This log provides the most direct and granular view of why the flow failed, such as a missing reference or a script action error.

Exam trap

The trap here is that candidates confuse Flow Designer flows with legacy Workflow Engine workflows, leading them to select System Log > Workflow instead of System Log > Flow, even though the question explicitly mentions a 'flow' triggering on a state change.

How to eliminate wrong answers

Option A is wrong because the Security log records authentication and authorization events (e.g., login attempts, ACL violations), not flow execution failures. Option C is wrong because the Workflow log is for legacy Workflow Engine workflows (wf_ tables), not for Flow Designer flows, which use a different execution engine. Option D is wrong because the Scripts log captures errors from server-side scripts (e.g., Business Rules, Script Actions) but does not aggregate the full flow execution context, including flow-level state transitions and step-by-step results.

Full explanation →
184
MCQhard

An ACL has a condition script that returns true if the user is a member of the 'service_desk' group and the record's 'state' is 'New'. The ACL type is 'read'. A user in the 'service_desk' group reports that they cannot see a record with state 'New'. What is the most likely cause?

A.The ACL is defined on a different table that extends 'incident'.
B.The script uses gs.hasRole('service_desk') which checks role, not group membership.
C.The condition script does not have a default return false statement, so it returns undefined.
D.Another read ACL exists that explicitly denies read access to the 'service_desk' group.
AnswerC

Correct: A missing explicit false return causes undefined, which is falsy.

Why this answer

In ServiceNow, ACL condition scripts that lack an explicit return statement will return undefined, which is a falsy value. When the condition script returns undefined, the ACL does not grant read access, effectively denying the user from seeing the record even though they meet the intended group and state criteria. This is a common pitfall where developers forget to add a default return true or return false at the end of the script.

Exam trap

The trap here is that candidates assume a condition script without a return statement will default to true or false, but ServiceNow treats undefined as false, causing the ACL to deny access unexpectedly.

How to eliminate wrong answers

Option A is wrong because if the ACL were defined on a different table that extends 'incident', it would still apply to the record via inheritance, so it would not prevent the user from seeing the record. Option B is wrong because gs.hasRole('service_desk') checks for the role, not group membership, but the question states the user is in the 'service_desk' group, and if the script used gs.hasRole, it would still return true if the user has the corresponding role, which is typically granted by group membership. Option D is wrong because another read ACL that explicitly denies read access would override the grant only if it has a higher priority (e.g., a deny ACL with a condition that matches), but the question says the user cannot see the record, and a deny ACL would be a plausible cause only if it existed and matched; however, the most likely cause given the condition script behavior is the missing return statement.

Full explanation →
185
MCQhard

Based on the exhibit, why did the identification rule fail?

A.The serial_number field is empty, but the rule requires it to be non-empty.
B.The name field is missing from the payload.
C.The rule has a dependency that is not satisfied.
D.The ip_address field is not included in the identification rule.
AnswerA

The rule condition demands a non-empty serial_number.

Why this answer

The identification rule fails because the serial_number field, which is defined as a required identifier field in the rule configuration, is empty in the incoming payload. ServiceNow CMDB identification rules use a set of fields to uniquely identify CI records; if any required field is missing or null, the rule cannot match or create a record, resulting in a failure. In this case, the payload contains the serial_number field but with no value, which the rule treats as a violation of its non-empty constraint.

Exam trap

The trap here is that candidates assume a field being 'present' in the payload is sufficient, but ServiceNow requires the field to be non-empty for identification rules, and an empty string is treated as a missing value.

How to eliminate wrong answers

Option B is wrong because the name field is present in the payload (as shown in the exhibit), and the identification rule does not require it to be non-empty for matching. Option C is wrong because the exhibit shows no dependency conditions configured on the rule; dependencies are used for CI relationships, not for field-level identification. Option D is wrong because the ip_address field is not listed as a required identifier in the rule; the rule only requires serial_number and possibly other fields, but ip_address is optional or used elsewhere.

Full explanation →
186
Multi-Selectmedium

Which TWO of the following are benefits of using Service Catalog record producers to automate request fulfillment?

Select 2 answers
A.They automatically create knowledge articles from user submissions.
B.They are delivered as pre-configured items in the base system.
C.They enforce SLA compliance automatically.
D.They allow administrators to define variables to capture user input.
E.They can automatically generate catalog tasks for fulfillment activities.
AnswersD, E

Variables are a key feature of record producers.

Why this answer

Service Catalog record producers allow administrators to define variables (e.g., single-line text, reference, or choice fields) that capture user input when a request is submitted. This input can then be used to populate fields on the target record or drive conditional logic in the fulfillment workflow. Option E is correct because record producers can automatically generate catalog tasks via the 'Create task for each selected option' or 'Create task for each variable' settings, enabling structured fulfillment activities without manual intervention.

Exam trap

The trap here is that candidates confuse the automatic generation of tasks (a genuine record producer feature) with SLA enforcement or knowledge article creation, which are separate capabilities not inherent to record producers.

Full explanation →
187
MCQeasy

A user reports that a form loads slowly. The administrator notices several UI Policies and Client Scripts are running on the form. What is the best practice to improve form performance?

A.Use only one UI Policy per form
B.Set the UI Policy and Client Script to run only when needed using conditions
C.Disable all client-side scripts
D.Convert all UI Policies to Business Rules
AnswerB

Conditional execution reduces unnecessary client scripts, speeding up form loading.

Why this answer

UI Policies and Client Scripts execute client-side in the browser, and their conditions determine whether they run on a given form. By setting them to run only when needed (e.g., based on a specific field value or form load event), you reduce unnecessary JavaScript execution, which directly improves form load and interaction performance. This is a best practice in ServiceNow to avoid processing scripts that are irrelevant to the current context.

Exam trap

The trap here is that candidates assume 'fewer scripts' always means better performance, but ServiceNow tests the understanding that conditional execution (not just reducing count) is the correct optimization strategy.

How to eliminate wrong answers

Option A is wrong because there is no platform limit of one UI Policy per form; you can have multiple UI Policies, and the issue is not the count but the conditions under which they execute. Option C is wrong because disabling all client-side scripts would break essential form functionality like validation, dynamic visibility, and field behavior; the goal is to optimize, not eliminate, client-side logic. Option D is wrong because converting UI Policies to Business Rules moves logic server-side, which does not improve form load performance (client-side rendering) and can introduce latency for real-time user interactions; Business Rules are for server-side operations, not for optimizing client-side form performance.

Full explanation →
188
MCQhard

Based on the sys_audit output, which CI has undergone the most recent change to its operational_status?

A.Both CI001 and CI002
B.CI002
C.Cannot be determined
D.CI001
AnswerB

Record 5 is the most recent and shows a change to CI002.

Why this answer

The sys_audit table records the timestamp of each change to a CI's operational_status field. CI002 has the most recent sys_audit record for operational_status, indicating it was changed last. The correct answer is B because the audit trail shows CI002's status was updated after CI001's.

Exam trap

The trap here is that candidates may assume the most recently created CI (based on sys_created_on) is the most recently changed, but the question specifically asks about changes to operational_status, which requires checking the sys_audit table for that field's update history.

How to eliminate wrong answers

Option A is wrong because both CIs did not have their operational_status changed at the same time; the audit records show different timestamps, with CI002 being more recent. Option C is wrong because the sys_audit table provides clear timestamps for each change, so the most recent change can be determined. Option D is wrong because CI001's last operational_status change occurred before CI002's, making CI002 the most recently changed.

Full explanation →
189
Multi-Selectmedium

Which TWO conditions must be met for a UI Policy to run on a form?

Select 2 answers
A.The form must be in edit mode
B.The user must have the admin role
C.The condition script must return true
D.The UI Policy must be active
E.The UI Policy must be set to 'Run on load'
AnswersC, D

If the condition returns false, the UI Policy does not execute its actions.

Why this answer

A UI Policy's condition script must evaluate to true for the policy to execute its actions on the form. The condition script is a server-side script that returns a boolean value; if it returns true, the UI Policy's actions (such as setting fields mandatory, visible, or read-only) are applied. Without a true condition, the UI Policy will not run, regardless of other settings.

Exam trap

The trap here is that candidates often confuse the 'Run on load' property as a mandatory condition for execution, when in fact it is just one of several trigger options, and the core requirement is that the condition script must return true and the UI Policy must be active.

Full explanation →
190
MCQeasy

A system administrator wants to ensure that a mandatory field on a form is always visible, even if the form section collapses. Which form layout option should be used?

A.Configure the field as 'Mandatory' and set 'Always visible' in the section
B.Add a UI policy to show the field on load
C.Use 'glide.mandatory.visible' system property
D.Set the field to read-only
AnswerA

This ensures visibility even when section collapses.

Why this answer

The 'Always visible' option on a form section ensures that mandatory fields remain displayed even when the section is collapsed. This is a native form layout configuration in ServiceNow that overrides the default behavior of hiding fields in collapsed sections, guaranteeing user visibility for required data entry.

Exam trap

The trap here is that candidates confuse the 'Always visible' section property with UI policies or system properties that control field highlighting or read-only behavior, rather than recognizing it as a distinct form layout option for collapsed sections.

How to eliminate wrong answers

Option B is wrong because a UI policy can show or hide fields based on conditions, but it does not inherently keep a field visible when its parent section collapses; the 'Always visible' setting is a section-level property, not a UI policy action. Option C is wrong because the 'glide.mandatory.visible' system property controls whether mandatory fields are highlighted with a red asterisk, not whether they remain visible in collapsed sections. Option D is wrong because setting a field to read-only prevents editing but does not affect its visibility when the section collapses; the field could still be hidden.

Full explanation →
191
MCQhard

Refer to the exhibit. A user submits a Laptop Request but receives the error shown. The user's session does not have a location set. What is the most likely cause?

A.The user's role does not have access to u_location variable.
B.The flow is incorrectly configured to require u_location before submission.
C.The catalog item is configured to use a mandatory variable without a default value.
D.The variable u_location is missing from the catalog item form.
AnswerC

Why this answer

The error indicates that a mandatory variable is missing a value at submission. Since the catalog item is configured with a mandatory variable that has no default value, and the user's session lacks a location, the system cannot auto-populate the variable, causing the submission to fail. This is the most common cause of such errors in Service Catalog flows.

Exam trap

ServiceNow often tests the distinction between a variable being missing from the form versus being present but empty due to a missing default value or session context, leading candidates to incorrectly choose that the variable is missing from the form.

How to eliminate wrong answers

Option A is wrong because the user's role does not need access to the u_location variable for the catalog item to function; role-based access controls apply to records and modules, not to variable usage in catalog items. Option B is wrong because the flow does not require u_location before submission; the error occurs at the catalog item level due to a mandatory variable, not from a flow condition. Option D is wrong because the variable u_location is present on the form (as indicated by the error referencing it), but it is missing a value; the issue is not that it is missing from the form.

Full explanation →
192
Multi-Selectmedium

Which TWO elements are mandatory when defining an SLA definition in ServiceNow?

Select 2 answers
A.Condition
B.Breach timers
C.Schedule
D.Metrics
E.Escalation
AnswersA, C

The condition determines when the SLA should start; without it, the SLA won't apply to any record.

Why this answer

An SLA definition in ServiceNow requires a Condition to determine which records are covered by the SLA. Without a condition, the SLA would apply to all records or none, making it impossible to scope the SLA to specific criteria like priority or category. The condition is a mandatory field that defines the filter for when the SLA should start tracking.

Exam trap

The trap here is that candidates often confuse optional enhancements like breach timers or escalations as mandatory, while the exam tests the core required fields: Condition and Schedule, which are the only two mandatory elements when creating an SLA definition.

Full explanation →
193
Multi-Selectmedium

Which THREE options are valid fields in an SLA definition?

Select 3 answers
A.Reset condition
B.Breach condition
C.Exclusion condition
D.Stop condition
E.Start condition
AnswersB, D, E

Defines when SLA is breached.

Why this answer

In ServiceNow SLA definitions, the 'Breach condition' is a valid field that defines the condition under which the SLA is considered breached, typically based on a time threshold. This field is essential for triggering breach notifications and escalations when the SLA target is not met.

Exam trap

ServiceNow often tests the misconception that 'Reset condition' or 'Exclusion condition' are valid fields, when in fact ServiceNow only uses 'Start condition', 'Stop condition', and 'Breach condition' as the core condition fields in an SLA definition.

Full explanation →
194
MCQeasy

A user wants to quickly filter the incident list to show only high-priority incidents. What is the fastest way to apply this filter?

A.Use the filter condition builder above the list
B.Modify the query business rule for the incident table
C.Create a new report with a filter condition
D.Personalize the list view to add a filter condition
AnswerA

The filter condition builder provides immediate filtering.

Why this answer

The filter condition builder above the list provides a quick, ad-hoc way to apply a filter directly to the current list view without any configuration changes. In ServiceNow, this builder allows users to add conditions like 'Priority is High' in seconds, making it the fastest method for a one-time filter.

Exam trap

The trap here is that candidates may confuse the quick ad-hoc filter with more permanent configuration options like personalizing the list view or modifying business rules, thinking they need to 'set up' a filter rather than just applying it on the fly.

How to eliminate wrong answers

Option B is wrong because modifying a query business rule would permanently alter the underlying query for all users and all views of the incident table, which is not a quick filter and would affect system-wide behavior. Option C is wrong because creating a new report is a separate module designed for data visualization and analysis, not for filtering the list view in place; it requires extra steps and does not apply the filter to the list. Option D is wrong because personalizing the list view to add a filter condition involves configuring a saved filter for that specific view, which is a more permanent setup and not the fastest way to apply a temporary filter.

Full explanation →
195
MCQmedium

An ACL on the Incident table has a script condition that returns true if the user is in the role 'incident_manager'. A user with the 'incident_manager' role still cannot update incidents. What could be the issue?

A.The ACL is set to 'read' instead of 'write'.
B.The user also has a role that explicitly denies access.
C.The script has a syntax error but is still returning false.
D.The ACL has a condition order that is not correct.
AnswerC

A syntax error in the script may cause it to return false, denying access.

Why this answer

If the script condition has a syntax error, it will not execute properly and will return false by default, even if the user has the 'incident_manager' role. In ServiceNow, ACL script conditions that fail due to syntax errors are treated as false, denying access. The user's role is irrelevant if the condition itself does not evaluate to true.

Exam trap

The trap here is that candidates assume a valid role assignment guarantees access, overlooking that ACL script conditions must execute without errors and return true for the ACL to grant access.

How to eliminate wrong answers

Option A is wrong because the question states the user cannot update incidents, implying the ACL is intended for update operations; if it were set to 'read', the user would still be able to update if a separate write ACL existed, but the issue is specifically about update access. Option B is wrong because while explicit deny roles can override, the question does not mention any such role, and the scenario focuses on the script condition not working. Option D is wrong because condition order only matters when multiple ACLs match; a single ACL with a script condition that returns false will deny access regardless of order.

Full explanation →
196
MCQhard

A custom table called 'u_cmdb_ci_application' has been created to extend cmdb_ci. After importing data into this table, the new records do not appear in the 'Configuration Items' module. What is the most likely reason?

A.The 'sys_class_name' field was not set to 'u_cmdb_ci_application' during import.
B.The import set used the wrong transform map.
C.The table was created in the wrong application scope.
D.The user does not have access to the custom table.
AnswerA

Without the correct sys_class_name, the records may appear in the base table or not be recognized as the proper class.

Why this answer

The 'Configuration Items' module filters records based on the 'sys_class_name' field to display only those belonging to the cmdb_ci class or its subclasses. When importing data into a custom table that extends cmdb_ci, if the 'sys_class_name' field is not explicitly set to 'u_cmdb_ci_application', the records will inherit a default value (often the base class name) and thus be excluded from the module's view. This is a common requirement for CMDB extension tables to ensure proper classification and visibility.

Exam trap

A common misconception is that the Configuration Items module shows all records from any table extending cmdb_ci automatically, but the trap here is that the module relies on the 'sys_class_name' field to filter records, so failing to set this field during import will hide the records even if the table extension is correct.

How to eliminate wrong answers

Option B is wrong because the transform map controls field mapping and transformation logic, but even a correct transform map will not cause records to appear in the Configuration Items module if the 'sys_class_name' is not set to the custom table name; the transform map does not automatically set the class. Option C is wrong because the application scope affects visibility and access control, but it does not prevent records from appearing in the Configuration Items module as long as the table extends cmdb_ci and the class is correctly set; scope does not filter the module's display. Option D is wrong because user access to the custom table determines whether the user can view or edit records directly, but the Configuration Items module uses its own ACLs and filters based on class; lack of table access would not hide records from the module if the user has the cmdb_ci role, though it might prevent opening the record.

Full explanation →
197
MCQmedium

An organization has a notification configured to send an email to the caller's manager when an incident is resolved. The notification is active, uses the 'Email - Incident' template, and has a condition script: 'current.state.changesTo(6)'. The email properties (SMTP, etc.) are working correctly for other notifications. Recently, managers are not receiving these resolved-incident emails. The administrator checks that the 'Manager' field on the caller's user record is populated for all callers. The notification's 'Who will receive' list is set to 'Caller and caller's manager' and the 'Operation' is 'record updated'. The 'Advanced' view shows that the 'Recipients' tab includes the email field 'mail' for the caller and the manager. What should the administrator investigate next?

A.Add a condition script to verify that the manager exists before sending.
B.Check the notification template for the correct email field reference for the manager.
C.Change the notification to 'event-based' using a business rule.
D.Verify that the 'Manager' field on the user record has a read ACL that allows the system user to access it.
AnswerB

The template must correctly reference the manager's email, e.g., ${user.manager.email}. If it uses an incorrect field or literal text, the email will not be sent to the manager.

Why this answer

The notification is configured correctly to send to the caller and caller's manager, and the condition script triggers on state change to 6 (Resolved). Since other notifications work, SMTP is fine. The issue likely lies in the notification template: if the template references an incorrect email field for the manager (e.g., 'email' instead of 'mail'), the system cannot resolve the manager's email address, causing the email not to be sent.

Option B directly addresses this by checking the template's field reference.

Exam trap

The trap here is that candidates assume the issue is with the notification condition or ACLs, overlooking that the template's field reference for the manager's email could be incorrect even when the 'Who will receive' list is set correctly.

How to eliminate wrong answers

Option A is wrong because the notification already has a condition script ('current.state.changesTo(6)') and the 'Who will receive' list includes the manager; adding a script to verify manager existence is redundant and would not fix a template field reference issue. Option C is wrong because changing to event-based notification would not resolve the problem; the current 'record updated' operation is appropriate and the issue is with template field mapping, not the notification trigger mechanism. Option D is wrong because the 'Manager' field is populated and other notifications work, indicating ACLs are not blocking access; the system user typically has full read access, and a read ACL issue would affect all notifications, not just this one.

Full explanation →
198
Multi-Selecteasy

Which THREE actions can be performed using the 'Service Catalog' module without additional plugins? (Choose three.)

Select 3 answers
A.Add a catalog item to a category.
B.Create a record producer.
C.Create a catalog item.
D.Import records from Excel.
E.Define variable sets.
AnswersA, C, E

Items can be assigned to categories within the module.

Why this answer

The Service Catalog module natively allows administrators to organize catalog items by adding them to categories. This is a core out-of-box function that does not require any additional plugins, as categories are a fundamental part of the catalog structure.

Exam trap

ServiceNow often tests the distinction between out-of-box catalog management actions and those that require plugins, so the trap here is assuming that record producers or Excel imports are part of the base Service Catalog module when they actually depend on additional plugins or separate modules.

Full explanation →
199
MCQeasy

Refer to the exhibit. What action should the administrator take to improve the completeness score?

A.Use a scheduled job to populate common fields with default values.
B.Manually edit each CI that has missing fields.
C.Configure a data certification policy with required fields.
D.Increase the CMDB Health weight for completeness.
AnswerC

Data certification enforces completeness by requiring those fields during periodic review.

Why this answer

A data certification policy in ServiceNow allows administrators to define required fields for CI classes. When a data certification policy is configured with required fields, the system automatically validates that those fields are populated during certification runs, directly improving the completeness score by ensuring critical data is present. This is a proactive, automated approach that aligns with CMDB Health best practices.

Exam trap

The trap here is that candidates often confuse adjusting the CMDB Health weight (a scoring mechanism) with actually fixing data quality issues, leading them to select option D instead of recognizing that a data certification policy directly enforces data population.

How to eliminate wrong answers

Option A is wrong because using a scheduled job to populate common fields with default values does not address missing fields that require specific, context-dependent data; it only fills generic defaults, which may not improve the actual completeness of meaningful attributes. Option B is wrong because manually editing each CI that has missing fields is not scalable for large CMDBs and does not provide a sustainable, automated mechanism to prevent future completeness gaps. Option D is wrong because increasing the CMDB Health weight for completeness only changes the scoring impact of completeness in the overall health score, but does not actually populate missing fields or enforce data population; it merely adjusts the metric's importance without fixing the underlying data quality issue.

Full explanation →
200
Multi-Selecthard

Which TWO conditions are necessary for a catalog item to trigger a workflow automatically upon submission?

Select 2 answers
A.The workflow must be in 'Published' state
B.The catalog item must be in a category that allows workflow execution
C.The workflow must be subscribed to the catalog item
D.The workflow must contain a 'Begin' activity
E.The catalog item's 'Workflow' field must be populated with a workflow
AnswersA, E

Only published workflows can execute.

Why this answer

A workflow must be in the 'Published' state to be available for execution. Only published workflows can be triggered automatically by a catalog item submission. Option E is correct because the catalog item's 'Workflow' field must be explicitly populated with a reference to a workflow; otherwise, no workflow will be associated with the item, and no automatic trigger will occur.

Exam trap

The trap here is that candidates often think a workflow must be 'subscribed' to the catalog item (Option C) or that a 'Begin' activity is mandatory (Option D), but ServiceNow uses a direct reference from the catalog item to the workflow, and the workflow can start with any activity type.

Full explanation →
201
Multi-Selecteasy

An administrator wants to send an email notification when a change request state changes to 'scheduled'. The notification should be sent to the change manager. Which two fields must be configured in the notification record?

Select 2 answers
A."Advanced" tab: register an event to trigger the notification
B."Email template" tab: select an existing template
C."Who will receive" tab: add 'Change manager' role to 'Recipients'
D."When to send" tab: set condition to 'State changes to scheduled'
AnswersC, D

This ensures the notification is sent to the change manager.

Why this answer

The 'Who will receive' tab allows you to specify the recipients of the notification by role, user, or group. Adding the 'Change manager' role ensures that all users with that role receive the email when the notification triggers. Option D is correct because the 'When to send' tab defines the condition that must be met for the notification to fire; setting it to 'State changes to scheduled' ensures the notification is sent precisely when the change request state transitions to 'scheduled'.

Exam trap

The trap here is that candidates often think an email template is mandatory for a notification to work, but ServiceNow will use a default template if none is selected, making option B incorrect as a required field.

Full explanation →
202
Multi-Selecthard

Which THREE factors influence the order of fields on a form?

Select 3 answers
A.Form section order
B.Role-based field visibility
C.User preference for field order
D.Field order in form layout
E.Field order in dictionary
AnswersA, C, D

Sections are ordered, and fields are placed within sections.

Why this answer

The order of sections in a form determines the sequence in which fields are grouped and displayed. The form section order directly influences the overall layout and flow of the form, as fields are organized within sections that appear in the order defined by the section order.

Exam trap

The trap here is that candidates often confuse the dictionary field order with the form layout field order, assuming that changing the dictionary order will automatically reorder fields on the form, when in fact the form layout order is independent and must be modified separately.

Full explanation →
203
MCQeasy

Which of the following is NOT a valid type of UI action?

A.tab
B.context_menu
C.button
D.link
AnswerA

Tab is not a UI action type; it's a form element.

Why this answer

In ServiceNow, UI actions are defined as scripts that execute when a user interacts with a UI element such as a button, link, or context menu item. The 'tab' type is not a valid UI action type; UI actions can be of type 'button', 'context_menu', or 'link', but not 'tab'. Tabs are separate UI elements managed through form layouts or UI policies, not through the UI Actions table.

Exam trap

The trap here is that candidates may confuse UI actions with other UI elements like tabs or UI policies, assuming 'tab' is a valid UI action type because tabs are common in ServiceNow forms, but ServiceNow explicitly restricts UI action types to button, context_menu, and link.

How to eliminate wrong answers

Option B is wrong because 'context_menu' is a valid UI action type that adds an option to the context menu (right-click menu) on a form or list. Option C is wrong because 'button' is a valid UI action type that creates a button on a form or list. Option D is wrong because 'link' is a valid UI action type that creates a clickable link on a form or list.

The only invalid type among the options is 'tab', which is not a UI action type in ServiceNow.

Full explanation →
204
MCQhard

During form submission, a mandatory field is not highlighted in red, and the form submits without requiring it. The field is made mandatory by a UI Policy that checks a condition set by a Client Script on form load. What is the most likely issue?

A.A Data Policy overrides the mandatory attribute
B.The UI Policy is set to OnSubmit
C.The UI Policy runs after the Client Script
D.The UI Policy runs before the Client Script
AnswerD

UI Policies execute earlier in the form load sequence; if the condition depends on a client script value, it may be missed.

Why this answer

The UI Policy runs before the Client Script, so when the UI Policy evaluates its condition to determine whether to make the field mandatory, the Client Script has not yet set the condition variable. As a result, the UI Policy condition fails, the mandatory attribute is not applied, and the form submits without requiring the field. The correct order of execution is UI Policy conditions first, then Client Scripts, then UI Policy actions.

Exam trap

The trap here is that candidates often assume UI Policies and Client Scripts run in the order they appear in the application navigator, but ServiceNow explicitly evaluates UI Policy conditions before Client Scripts, regardless of the order they are created.

How to eliminate wrong answers

Option A is wrong because a Data Policy cannot override the mandatory attribute set by a UI Policy; Data Policies enforce data integrity on the server side and do not interact with UI Policy mandatory attributes in this way. Option B is wrong because a UI Policy set to OnSubmit would only apply its actions at form submission, but the issue occurs during form load and submission without the field being required, indicating the condition never set the mandatory attribute. Option C is wrong because if the UI Policy ran after the Client Script, the condition would see the variable set by the Client Script and correctly apply the mandatory attribute, which contradicts the described behavior.

Full explanation →
205
MCQhard

A company has an enterprise ServiceNow instance with a CMDB that contains over 50,000 CIs. The instance is integrated with multiple discovery tools: ServiceNow Discovery, a third-party IPAM tool, and a cloud management platform. Recently, the CMDB health score dropped significantly due to an increase in duplicate CIs. Upon investigation, you find that many CIs from the IPAM tool have the same serial number as CIs discovered by ServiceNow Discovery, but with slight differences in the hardware model field. Also, the cloud management platform creates CIs with the same name but different serial numbers. The business requires that each physical device should have only one CI record, and the serial number is the authoritative identifier. The current reconciliation rules are set to merge based on name and IP address, but they are not effectively resolving duplicates. What should the administrator do to resolve this issue most effectively?

A.Create an approval workflow for every new CI creation to manually check for duplicates
B.Add a unique constraint on the serial number field to prevent future duplicates
C.Modify the reconciliation rule to match on serial number instead of name and IP
D.Disable the IPAM tool and cloud management platform integrations to stop duplicate creation
AnswerC

Serial number is the authoritative identifier; matching on it will accurately identify duplicates across sources.

Why this answer

The business requirement states that serial number is the authoritative identifier for physical devices. By modifying the reconciliation rule to match on serial number instead of name and IP, the system will correctly identify and merge duplicate CIs that share the same serial number, even if other fields like hardware model differ. This directly addresses the root cause of the duplicate CIs from the IPAM tool and cloud management platform.

Exam trap

The trap here is that candidates may think adding a unique constraint (Option B) is sufficient, but they overlook that existing duplicates must be resolved first, and a unique constraint alone does not handle the reconciliation of CIs from multiple discovery sources with differing non-key attributes.

How to eliminate wrong answers

Option A is wrong because creating an approval workflow for every new CI creation is not scalable for over 50,000 CIs and would introduce manual overhead without fixing the underlying reconciliation logic. Option B is wrong because adding a unique constraint on the serial number field would prevent future duplicates but would not resolve the existing duplicate CIs that are already causing the health score drop. Option D is wrong because disabling the IPAM tool and cloud management platform integrations would stop duplicate creation but also eliminate valuable data sources, violating the business requirement for integrated discovery.

Full explanation →
206
MCQmedium

A company wants to allow users to submit requests via email. What must be configured?

A.Outbound email action
B.Inbound email action
C.Email notifications
D.Email client plugin
AnswerB

Inbound email actions parse incoming emails and create records like requests.

Why this answer

To allow users to submit requests via email, an inbound email action must be configured. This action processes incoming emails and creates or updates records (e.g., incidents or service catalog requests) based on the email content. Outbound email actions are for sending emails, not receiving them.

Exam trap

The trap here is that candidates confuse inbound email actions (receiving) with outbound email actions (sending), or assume that email notifications alone can handle user submissions, but notifications only send messages and cannot process incoming requests.

How to eliminate wrong answers

Option A is wrong because an outbound email action is used to send emails from ServiceNow (e.g., notifications or approvals), not to receive and process user-submitted requests. Option C is wrong because email notifications are outbound messages triggered by system events, not a mechanism for ingesting user emails. Option D is wrong because the email client plugin is a deprecated feature for integrating with email servers; inbound email actions are the modern, supported method for processing incoming emails.

Full explanation →
207
MCQhard

An administrator notices that a catalog client script is not firing when a variable changes. The script is set to 'onChange' and the variable reference is correct. The script uses g_form.setValue to update another variable. However, the other variable does not get updated. What could be the issue?

A.The variable being updated has a catalog client script that clears it
B.The other variable's value is protected by a UI policy
C.The script is running on the server side
D.The script is using g_form.setValue incorrectly for that variable type
AnswerA

If the target variable has an onChange script that sets its value back, it will override the change.

Why this answer

When a catalog client script uses g_form.setValue to update another variable, that action triggers the onChange event for the target variable. If the target variable has its own onChange catalog client script that clears its value, that script will execute after the setValue, effectively overriding the update. This creates a conflict where the first script sets a value, but the second script immediately clears it, resulting in the variable appearing unchanged.

Exam trap

The trap here is that candidates assume g_form.setValue always works without side effects, but they forget that setting a value programmatically triggers the onChange event of the target variable, which can execute another script that overrides the change.

How to eliminate wrong answers

Option B is wrong because UI policies do not protect variable values from being changed by client scripts; they only control visibility, mandatory status, or read-only state based on conditions, and a read-only UI policy would prevent the user from editing the field but g_form.setValue can still update it programmatically. Option C is wrong because the script is explicitly set to 'onChange' and runs on the client side (catalog client scripts are client-side by default), so it is not running on the server side. Option D is wrong because g_form.setValue is a standard method that works for all variable types in Service Catalog; there is no incorrect usage specific to variable types that would silently fail without an error.

Full explanation →
208
MCQmedium

A ServiceNow administrator wants to create a new form section that appears only when the 'State' field is set to 'In Progress'. Which configuration should be used?

A.Create an Access Control Rule (ACL) on the form section.
B.Create a Business Rule that sets the section visibility.
C.Create a UI Action with a condition on the 'State' field.
D.Create a UI Policy with a condition on the 'State' field.
AnswerD

UI Policies control form visibility and field states.

Why this answer

A UI Policy is the correct configuration because it allows an administrator to define conditions (e.g., 'State' is 'In Progress') that dynamically show or hide form sections, fields, or make fields mandatory/read-only on the client side without requiring a server round trip. This is the standard mechanism for controlling form section visibility based on field values in ServiceNow.

Exam trap

The trap here is that candidates often confuse UI Policies with Business Rules or ACLs, mistakenly thinking server-side logic or access controls can manage client-side form visibility, when in fact UI Policies are the dedicated feature for conditional UI rendering based on field values.

How to eliminate wrong answers

Option A is wrong because Access Control Rules (ACLs) control data access and record-level permissions, not UI element visibility; they cannot show or hide form sections based on field values. Option B is wrong because Business Rules run server-side and cannot directly control client-side form section visibility; they would require additional client-side scripting or a UI Policy to achieve the same effect. Option C is wrong because UI Actions are buttons or links that execute actions (e.g., scripts, redirects) and are not designed to conditionally show or hide form sections based on field state.

Full explanation →
209
MCQmedium

A company is using multiple data sources (Discovery, SCCM, and manual imports) to populate the CMDB. They notice that some CI attributes are being overwritten incorrectly. Which feature should be used to define which data source is authoritative for specific attributes?

A.Identification and Reconciliation Engine (IRE) with reconciliation rules
B.CMDB Data Source rules
C.Import set transform maps
D.Business rules with condition on source field
AnswerA

IRE reconciliation rules define which source is authoritative for each attribute.

Why this answer

The Identification and Reconciliation Engine (IRE) with reconciliation rules is the correct feature because it allows administrators to define which data source is authoritative for specific CI attributes. When multiple sources populate the CMDB, reconciliation rules determine the priority of data sources, ensuring that attributes from a higher-priority source overwrite those from lower-priority sources, preventing incorrect overwrites.

Exam trap

The trap here is that candidates confuse 'Data Source' configuration with reconciliation rules, assuming that simply defining a data source will automatically resolve conflicts, when in fact the IRE's reconciliation rules are required to explicitly set attribute-level authority.

How to eliminate wrong answers

Option B is wrong because CMDB Data Source rules do not exist as a feature in ServiceNow; the correct term is 'Data Source' definitions, which are used to configure import sources but not to define attribute-level authority. Option C is wrong because Import set transform maps handle data transformation and mapping during import, but they do not resolve conflicts between multiple data sources for attribute authority. Option D is wrong because Business rules with condition on source field can modify data during transactions but are not designed to manage authoritative source priority for CI attributes in the CMDB reconciliation process.

Full explanation →
210
MCQmedium

An administrator has configured a report on the Incident table showing the count of incidents by assignment group. The report shows data for the current week, but the numbers seem too low. The administrator suspects that incidents resolved before the current week are not being included. What should the administrator check first?

A.Check the 'Time scale' setting and ensure it is set to 'All' instead of 'Current week'.
B.Check the type of the report (e.g., bar chart vs pie chart) as some types only show aggregated data.
C.Check the condition (prompt) filter of the report to see if there is a time-based filter that limits to the current week.
D.Check the 'Group by' field to ensure it is set to 'Assigned to' instead of 'Assignment group'.
AnswerC

The filter may be set to 'Created on this week' which excludes older incidents.

Why this answer

The report's condition filter (often called a 'prompt' or 'filter condition') directly controls which records are included. If a time-based condition like 'Opened > Current week' or 'Resolved > Current week' is applied, it would exclude incidents resolved before the current week, causing the low count. The administrator should first inspect the filter conditions to see if such a restriction exists.

Exam trap

The trap here is that candidates confuse the 'Time scale' setting (which controls time-based grouping on the x-axis) with the report filter (which controls which records are included), leading them to incorrectly select Option A.

How to eliminate wrong answers

Option A is wrong because the 'Time scale' setting in a report controls how time is displayed on the x-axis (e.g., grouping by day, week, month), not which records are filtered out; it does not limit the data to the current week. Option B is wrong because the type of report (bar chart, pie chart, etc.) affects visualization, not the underlying data set; all report types show the same aggregated data from the same filtered records. Option D is wrong because the 'Group by' field determines how data is categorized (e.g., by assignment group vs. assigned to), not the time range of records; changing it would not resolve the issue of missing resolved incidents.

Full explanation →
211
MCQhard

Refer to the exhibit. The business rule is set to run 'before' update. When a user changes the state to 'Resolved' (value 3), the comments field is updated. However, the change does not appear on the form after save. What is the most likely reason?

A.The state condition is incorrect because state 3 is not 'Resolved'.
B.The script uses current.update() causing recursion and rollback.
C.The script should use current.setValue() instead of assignment.
D.The business rule should be 'after' instead of 'before'.
AnswerB

update() inside before rule triggers the rule again, causing recursion.

Why this answer

Calling current.update() inside a 'before' business rule triggers the same business rule again, causing recursion. ServiceNow detects this recursion and rolls back the update to prevent an infinite loop, so the comment field change is not saved. A 'before' business rule should modify fields directly without calling update(), as the system handles the save automatically.

Exam trap

ServiceNow often tests the misconception that calling current.update() is necessary to save changes in a 'before' business rule, when in fact it causes recursion and rollback, and direct field assignment is sufficient.

How to eliminate wrong answers

Option A is wrong because state 3 is indeed the 'Resolved' state in the default Incident table, so the condition is correct. Option C is wrong because using assignment (e.g., current.comments = 'text') is valid in a 'before' business rule; setValue() is also acceptable but not required. Option D is wrong because an 'after' business rule would still need to call current.update() to persist changes, and the recursion issue would persist; the core problem is the update() call, not the timing.

Full explanation →
212
MCQhard

An administrator notices that a UI policy on the Incident form is not firing for a specific user role. The UI policy is set to 'Run script' and has conditions on the 'State' field. The script uses g_form.setValue to set a field. What is the most likely reason the UI policy fails to execute for that role?

A.The UI policy is configured to run on the server side
B.The role does not have read access to the field being set
C.The UI policy is set to 'Run script' but the script has a syntax error
D.The UI policy condition uses a field that the role cannot see due to field-level security
AnswerD

If the condition depends on a hidden field, the policy may not evaluate correctly.

Why this answer

UI policies execute client-side, and if a field used in the condition (e.g., 'State') is hidden from the user's role due to field-level security (FLS), the client-side script cannot read the field's value. This causes the condition to evaluate as false or undefined, preventing the UI policy from firing. The g_form.setValue call in the script would also fail silently if the target field is not visible or accessible to the role.

Exam trap

The trap here is that candidates confuse field-level security with ACLs or assume that g_form.setValue requires read access, when in fact the issue is that the condition field is invisible to the role, causing the UI policy to never trigger.

How to eliminate wrong answers

Option A is wrong because UI policies are inherently client-side scripts that run in the browser; there is no 'server side' execution mode for UI policies. Option B is wrong because g_form.setValue does not require read access to the field being set—it only requires write access, and the question states the script uses setValue, not getValue. Option C is wrong because a syntax error would cause the script to fail for all roles, not just a specific role, and the question specifies the failure is role-specific.

Full explanation →
213
Multi-Selecteasy

Which TWO of the following are valid CI relationship types in ServiceNow?

Select 2 answers
A.Uses
B.Connects to
C.Member of
D.Owns
E.Depends on
AnswersC, E

'Member of' is a standard membership relationship.

Why this answer

'Member of' is a predefined CI relationship type in ServiceNow's CMDB, used to indicate that a CI belongs to a group or cluster, such as a server being a member of a cluster. This relationship is part of the standard CMDB relationship model and is commonly used for grouping CIs like applications, clusters, or business services.

Exam trap

The trap here is that candidates often confuse 'Uses' or 'Connects to' with valid relationship types, but ServiceNow strictly uses 'Depends on' and 'Connected to' (with 'Connected to' being a valid type, not 'Connects to'), and 'Owns' is a field attribute, not a relationship type.

Full explanation →
214
MCQeasy

A ServiceNow administrator deployed an Access Control Rule (ACL) to restrict access to the 'u_employee_salary' field on the 'u_employee' table. The ACL is defined as type 'field', with condition 'current.roles.contains("admin")', and 'read' and 'write' operations set to 'requires role'. After activating the ACL, non-admin users with the 'employee' role can still see the 'u_employee_salary' field on forms and lists. The administrator has verified that the 'employee' role does not have any other ACLs granting access to this field. Which of the following is the most likely cause of the issue?

A.A higher-priority ACL with the same name is overriding this ACL.
B.The ACL is applied to the wrong table or the field name is misspelled.
C.The ACL is missing a script condition that returns false for non-admin users.
D.The ACL is of type 'record' instead of 'field'.
AnswerB

If the ACL does not match the exact table or field name, it will not be enforced, allowing default access.

Why this answer

The most likely cause is that the ACL is applied to the wrong table or the field name is misspelled. If the ACL's table or field name does not exactly match the target field, the ACL will not enforce on that field, allowing non-admin users to see it. The administrator verified no other ACLs grant access, so a mismatch in the ACL definition is the primary suspect.

Exam trap

The trap here is that candidates often assume the ACL logic (condition or role requirement) is flawed, when in reality the ACL is simply not being applied due to a table/field name mismatch, which is a common oversight in ACL troubleshooting.

How to eliminate wrong answers

Option A is wrong because ACLs do not have a priority system based on name; they are evaluated by order of specificity (e.g., field-level overrides record-level) and by the 'order' property, not by name. Option C is wrong because the ACL already has a condition 'current.roles.contains("admin")' which is a script condition that returns false for non-admin users; adding another script condition is unnecessary and would not fix a table/field mismatch. Option D is wrong because the ACL is already of type 'field' as stated, and changing it to 'record' would affect the entire record, not just the field, which would not resolve the issue of the field being visible.

Full explanation →
215
Matchingmedium

Match each ServiceNow module to its function.

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

Concepts
Matches

Restore normal service operation as quickly as possible

Control the lifecycle of all changes to the IT environment

Identify and manage root causes of incidents

Provide a menu of services for users to request

Capture and share knowledge articles

Why these pairings

Correct matches: Incident Management restores service, Problem Management finds root causes, Change Management manages changes. Distractors swap Service Catalog and Knowledge Management definitions.

Full explanation →
216
Multi-Selecthard

A company is implementing a CMDB cleanup strategy and needs to identify CIs that are no longer in use. Which THREE methods can help identify outdated CIs? (Select three.)

Select 3 answers
A.Reviewing CI last discovered date.
B.Using the 'Stale CI' indicator in CMDB Health.
C.Running a CMDB Health report on compliance.
D.Checking CI status field for 'Retired'.
E.Manually auditing each CI in the CMDB.
AnswersA, B, C

A very old last discovered date suggests the CI may be out of use.

Why this answer

The 'Last Discovered' date field on a CI record indicates when the CI was last seen by a discovery probe. If this date is significantly old, it suggests the CI may no longer be active or in use, making it a reliable method for identifying outdated CIs during a CMDB cleanup.

Exam trap

The trap here is that candidates confuse the 'Retired' status (a manual state) with an automated detection method, or think manual auditing is a valid scalable approach, when the exam expects automated, health-based indicators like last discovered date, stale CI flags, and compliance reports.

Full explanation →
217
MCQeasy

A system administrator needs to prevent users from deleting any records in the 'incident' table. Which method will achieve this most effectively?

A.Create a write ACL on the incident table with condition 'false'
B.Create a read ACL on the incident table with condition 'false'
C.Set the incident table 'Update' access to 'none' in the table configuration
D.Create an application ACL on the incident table with the 'delete' operation set to 'no access'
AnswerD

Application ACLs can control delete operation and 'no access' denies it.

Why this answer

An Application ACL with the 'delete' operation set to 'no access' explicitly denies the delete operation on the 'incident' table, regardless of any other ACLs or user roles. This is the most effective method to prevent record deletion because it directly targets the delete operation at the table level, overriding any inherited or role-based permissions.

Exam trap

The trap here is that candidates often confuse 'write' ACLs with delete permissions, assuming that blocking write access also blocks deletions, but ServiceNow treats delete as a separate operation requiring its own ACL.

How to eliminate wrong answers

Option A is wrong because a write ACL controls update and insert operations, not delete operations; setting its condition to 'false' would block updates and inserts but not deletions. Option B is wrong because a read ACL controls read access (viewing records), not delete operations; setting it to 'false' would prevent users from seeing records but not from deleting them. Option C is wrong because setting 'Update' access to 'none' in table configuration only restricts update operations, not delete operations; delete is a separate action controlled by ACLs or table-level delete permissions.

Full explanation →
218
MCQeasy

An import set row shows as 'Error' with message 'Invalid table name'. What is the cause?

A.The staging table is not defined.
B.The import set source file is corrupt.
C.The transform map references a missing table.
D.The target table does not exist.
AnswerD

The error 'Invalid table name' means the target table is not found.

Why this answer

The 'Invalid table name' error occurs when the import set row references a target table that does not exist in the ServiceNow instance. The import set table stores the raw data, but the transform map must map to an existing target table (e.g., 'incident', 'cmdb_ci_server'). If the target table name is misspelled, deleted, or never created, the system cannot resolve it and throws this error.

Exam trap

ServiceNow often tests the distinction between errors that occur at the import set row level versus errors that occur during transform map execution, leading candidates to incorrectly attribute the 'Invalid table name' error to a missing transform map reference.

How to eliminate wrong answers

Option A is wrong because a missing staging table would cause a different error, such as 'Staging table not found' or a failure during the import set creation, not an 'Invalid table name' error. Option B is wrong because a corrupt source file would typically result in parse errors or malformed data, not a table name validation error. Option C is wrong because a transform map referencing a missing table would cause an error during transform map execution, but the 'Invalid table name' error occurs at the import set row level, before the transform map runs.

Full explanation →
219
MCQeasy

A ServiceNow administrator notices that a CI record in the CMDB is not being updated by a scheduled discovery job. The CI is a Linux server that is reachable on the network. Which is the most likely cause?

A.The discovery source is not configured for this IP range.
B.The Identification and Reconciliation Engine (IRE) is disabled.
C.The cmdb_ci table ACL is set to private.
D.The CI is classified under a different CI class in the CMDB.
AnswerD

If the CI is misclassified, discovery may update a different record or create a duplicate.

Why this answer

When a CI is classified under a different CI class in the CMDB, the scheduled discovery job may not update it because discovery uses the IRE to match incoming data against existing CIs based on identification rules. If the CI's class differs from what the discovery payload expects, the IRE may fail to reconcile the record, or the update may be directed to a different class table, leaving the original CI unchanged. This is a common cause of apparent update failures when the CI is reachable and the discovery source is correctly configured.

Exam trap

The trap here is that candidates assume a reachable CI with a configured discovery source guarantees updates, overlooking how the IRE's class-specific identification rules can prevent reconciliation when the CI class in the CMDB does not match the discovery payload.

How to eliminate wrong answers

Option A is wrong because if the discovery source were not configured for the IP range, the CI would not be discovered at all, but the question states the CI is reachable and the discovery job is scheduled, implying the source is configured. Option B is wrong because disabling the IRE would prevent all CI identification and reconciliation, causing discovery to fail for all CIs, not just this specific one. Option C is wrong because the cmdb_ci table ACL set to private would block user access to view or modify the table, but discovery runs with system-level privileges and is not affected by table ACLs.

Full explanation →
220
MCQmedium

A company uses the Employee Center portal. Users report that they cannot find a specific service when using the search bar. The service exists and is active. What is the most likely cause?

A.The service is inactive
B.The search index is not built for that service
C.The service is not in a valid category
D.The service owner has restricted visibility
AnswerB

Items must be indexed to appear in search results.

Why this answer

The Employee Center portal relies on a search index to surface services. Even if a service is active and properly configured, the search index must be built or rebuilt for that specific service to appear in search results. Without an up-to-date index, the search bar will not return the service, which directly matches the reported symptom.

Exam trap

ServiceNow often tests the misconception that a service must be in a valid category to be searchable, but in reality, the search index is independent of category assignment, and the index build process is the critical factor.

How to eliminate wrong answers

Option A is wrong because the question explicitly states the service exists and is active, so inactivity is not the cause. Option C is wrong because a service not being in a valid category does not prevent it from appearing in search results; categories primarily affect portal navigation and filtering, not the search index. Option D is wrong because service owner visibility restrictions control who can view or request the service, but they do not prevent the service from appearing in search results for authorized users; if a user has permission, the service would still be indexed and searchable.

Full explanation →
221
MCQhard

An administrator is designing a catalog item for software requests. The item must capture the user's department automatically and pre-populate the cost center. Which feature should be used to achieve this?

A.Catalog Client Script
B.UI Policy
C.Variable default value using system properties
D.Client Script
AnswerC

Defaults can be set to user's department and cost center from user record.

Why this answer

Using a variable default value with a system property allows the catalog item to automatically populate the department and cost center fields based on the logged-in user's data. System properties can reference user attributes (e.g., sys_user.department) to dynamically set default values without requiring client-side scripts or UI policies.

Exam trap

The trap here is that candidates often confuse client-side scripts (Catalog Client Scripts or Client Scripts) with server-side default value logic, assuming scripts are needed for pre-population when system properties provide a simpler, no-code solution.

How to eliminate wrong answers

Option A is wrong because Catalog Client Scripts run on the client side (browser) and are used for validation or dynamic behavior, not for pre-populating default values from system properties. Option B is wrong because UI Policies control field visibility, read-only state, or mandatory status, but they do not set default values automatically. Option D is wrong because Client Scripts (on forms) are for client-side interactions and cannot directly reference system properties to pre-populate catalog item variables.

Full explanation →
222
MCQeasy

A user reports that the 'My Tickets' module in the ITIL application does not show any records, even though the user has incidents assigned. What is the most likely cause?

A.The module is set to 'Personalize' mode
B.The module is configured as a report, not a list
C.The module's filter condition does not include the 'Assigned to' field for the current user
D.The user does not have the 'incident_read' role
AnswerC

Without proper condition, records may not appear.

Why this answer

The 'My Tickets' module is a filtered list based on the Incident table, typically using a condition such as 'Assigned to = current user' to display only records assigned to the logged-in user. If this filter condition is missing or incorrectly configured, the module will show no results even when the user has assigned incidents. Option A is incorrect because 'Personalize' mode allows users to customize column layout, not hide records.

Option B is incorrect because the module is a list filter, not a report; reports display aggregated data. Option D is incorrect because the module is accessible (it appears in the menu), so the user has the necessary 'incident_read' role; the issue is with the filter condition.

Full explanation →
223
Multi-Selecteasy

Which three are components of CMDB Reconciliation? (Select three.)

Select 3 answers
A.Identification rules
B.Data Source definitions
C.Reconciliation rules
D.CMDB Health Score
E.CI Class Manager
AnswersA, B, C

Identification rules determine how CIs are matched to data sources.

Why this answer

Identification rules are a core component of CMDB Reconciliation because they define how ServiceNow uniquely identifies CIs across multiple data sources. They use specific attributes (like serial number or MAC address) to match CIs and prevent duplicates during the reconciliation process.

Exam trap

The trap here is that candidates confuse CMDB Health Score (a reporting feature) with an active reconciliation component, or assume CI Class Manager is involved in reconciliation when it only handles class structure, not data matching.

Full explanation →
224
MCQmedium

An administrator is asked to make the 'State' field read-only on the incident form after the record is saved. Which configuration should be used?

A.Create a UI Policy with condition 'always true' and set 'Read only' action, with 'On load' and 'After update' options
B.Write a Business Rule that sets the field read-only after update
C.Create an ACL that denies write access to the field
D.Use a Client Script that runs on load and makes the field read-only if the record has a sys_id
AnswerA

UI Policies can set read-only and apply after update, making the field read-only after save.

Why this answer

A UI Policy with the condition 'always true' and the 'Read only' action, with both 'On load' and 'After update' options selected, ensures the 'State' field becomes read-only immediately after the record is saved. The 'After update' option triggers the UI Policy to re-evaluate and apply the read-only state after the record is committed, while 'On load' ensures it is also read-only when the form is first opened. This is the only declarative client-side configuration that enforces the field state both on initial load and after every save.

Exam trap

The trap here is that candidates often confuse UI Policies (which can run after update) with Client Scripts (which cannot), leading them to choose option D, not realizing that a Client Script's 'onLoad' event does not reapply after a save.

How to eliminate wrong answers

Option B is wrong because a Business Rule runs server-side and cannot directly set a field as read-only on the client form; it can only modify field values or perform server-side logic, not control client-side UI behavior. Option C is wrong because an ACL that denies write access prevents the field from being updated via any channel (including REST, SOAP, or direct database writes), which is too broad and would block legitimate updates from other processes or integrations, not just the form. Option D is wrong because a Client Script that runs on load and checks for a sys_id only makes the field read-only when the form is first loaded, but it does not reapply the read-only state after the record is saved (since the 'After update' option is not available in Client Scripts), so the field would become editable again after a save.

Full explanation →
225
Drag & Dropmedium

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

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

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

Why this order

The correct sequence for creating a new application scope in ServiceNow starts with opening Application Studio, then clicking the 'Create Application' button to display the creation form. Next, you enter the application name and optional description, and finally click 'Submit' to complete the process. This order ensures all necessary UI components are available at each step.

Full explanation →
Page 2

Page 3 of 7

Page 4

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 →