SNOW-CSA Practice Test 23 — 15 Questions

Question 1

A catalog item has a variable named 'justification' that should only be visible and mandatory when the variable 'request_type' is set to 'Hardware'. The administrator has already created a UI policy to set the variable visibility and mandatory state. However, users report that the 'justification' variable is still visible and not mandatory when they change 'request_type' to 'Hardware'. What is the most likely cause?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

The UI policy condition is incorrect or the UI policy is not active.. UI policies are the correct mechanism to dynamically change variable visibility and mandatory state on a catalog item form. If they are not functioning, the most common reasons are an incorrect condition or the policy being inactive. Other options involve unrelated concepts such as variable sets, workflows, or user roles, which do not control client-side variable behavior.

Answer

The catalog item's workflow is overriding the variable states.

Answer

The user does not have the 'catalog_admin' role.

Answer

The variable 'justification' is not included in the catalog item's variable set.

Question 2

A ServiceNow administrator needs to ensure that when a user without the 'itil' role attempts to read a record in the 'problem' table, they are denied access, but users with 'itil' can read. The administrator creates an ACL on the 'problem' table for the 'read' operation with a role condition of 'itil'. However, after testing, users without 'itil' can still read problem records. What is the most likely cause?

Accepted Answer

There is a higher-priority ACL on the 'problem' table that grants read access to all users, overriding the new ACL.. ACL evaluation in ServiceNow considers all applicable ACLs. If a more permissive ACL exists that grants read access to a broader audience, it can override a restrictive ACL. The administrator must review all ACLs on the table, including those inherited from parent tables, to ensure no conflicting rules exist. The new ACL may be correct, but a pre-existing ACL could be granting access.

Answer

The 'itil' role is not properly assigned to the users who should have access, so the ACL is not matching.

Answer

The ACL is set to 'Allow if' instead of 'Deny unless', so it only grants access to itil users but does not deny others.

Answer

The ACL does not have the 'Requires role' check box selected, so the role condition is ignored.

Question 3

A workflow on a catalog item includes a 'Catalog Task' activity that creates a task assigned to the 'Network' group. The workflow also has a 'Wait for condition' activity that waits until the catalog task state is 'Closed Complete'. Users report that after the network team closes the task, the workflow does not proceed. Which configuration issue is the most likely cause?

Accepted Answer

The 'Wait for condition' activity is configured to check the task state on the sc_req_item table instead of the sc_task table.. A 'Wait for condition' activity must reference the correct table and field. If it checks the request item's state instead of the catalog task's state, closing the sc_task record never satisfies the condition, and the workflow remains paused. Correcting the condition to evaluate sc_task.state is the likely fix.

Answer

The workflow is not published, so the wait condition is evaluated only once at the start.

Answer

The workflow's 'Catalog Task' activity is set to create the task only after the wait condition is met.

Answer

The catalog task's assignment group 'Network' does not have the workflow context role required to update the task.

Question 4

A workflow on a catalog item includes a 'Create Task' activity that assigns a task to the 'Network' group. The workflow then proceeds to a 'Wait for Condition' activity that waits until the task state is 'Closed Complete'. However, the workflow is not resuming even after the task is closed. What is the most likely reason?

Accepted Answer

The 'Wait for Condition' activity is checking the wrong field or value.. The Wait for Condition activity pauses the workflow until a specified condition is met on a record. If the condition references the wrong field or value, the workflow will not resume even if the task is closed. Checking the condition configuration is the most direct troubleshooting step. Other options involve roles, task creation, or context, which are less likely given the task was closed.

Answer

The task was closed by a user who does not have the 'workflow_admin' role.

Answer

The workflow context is not set to 'Record' and therefore cannot evaluate conditions.

Answer

The 'Create Task' activity did not actually create a task record.

Question 5

A ServiceNow administrator needs to create a business rule that runs before a record is inserted into the 'incident' table to automatically set the 'priority' field based on the 'impact' and 'urgency' fields. The administrator wants to ensure the rule runs only when the record is inserted, not on updates. Which configuration should the administrator use?

Accepted Answer

Create a business rule with 'When' set to 'before' and 'Insert' checked, and write a script that sets the priority.. A before insert business rule runs before the new record is saved, allowing the script to set the priority field. This is the correct approach to automatically calculate and set a field value based on other fields during record creation without additional updates.

Answer

Create a business rule with 'When' set to 'after' and 'Insert' checked, and write a script that updates the priority.

Answer

Create a business rule with 'When' set to 'async' and 'Insert' checked, and write a script that sets the priority.

Answer

Create a business rule with 'When' set to 'before' and 'Update' checked, and write a script that sets the priority.

Question 6

A custom table 'u_purchase_order' has an ACL that grants read access to users with the 'procurement' role. A user with the 'procurement' role reports that they can see the list of purchase orders but cannot open any individual record. The administrator checks and finds that the ACL on the table level is correctly configured. What is the most likely cause of this issue?

Accepted Answer

The field-level ACLs on the table do not grant read access to the 'procurement' role.. When a user can see records in a list but cannot open them, it typically indicates that field-level ACLs are blocking access to the fields on the form. Table-level ACLs control access to the table and list views, while field-level ACLs control access to individual fields. To resolve the issue, the administrator should check the field-level read ACLs for the table and ensure they grant read access to the procurement role.

Answer

The 'procurement' role lacks the 'snc_read_only' role required to view record details.

Answer

The table's read ACL is set to 'Allow If' with a condition that evaluates to false for individual records.

Answer

The user's 'procurement' role is not inherited from a group, causing the ACL to fail.

Question 7

A ServiceNow administrator creates an Access Control Rule (ACL) on the 'incident' table with the operation 'write' and no role requirement. The ACL's script includes a condition that checks if the current user is the caller of the incident. A user with the 'itil' role attempts to update an incident where they are not the caller. What will happen?

Accepted Answer

The user will be denied update access because the ACL script condition evaluates to false.. ACLs are evaluated by combining role requirements and script conditions. If an ACL has no role requirement but has a script condition, the script must evaluate to true for access. In this scenario, the script checks if the user is the caller; since the user is not, the condition is false, and the write operation is denied. The 'itil' role does not override this specific ACL.

Answer

The user will be granted access because the 'itil' role has implicit write access to the incident table.

Answer

The user will be prompted to request access via an approval workflow.

Answer

The user will be able to update the incident because the ACL has no role requirement.

Question 8

A ServiceNow administrator creates a notification on the 'problem' table that sends an email when a problem's state changes to 'Known Error'. The notification includes a mail script that adds the problem's 'workaround' field to the email body. After testing, the administrator finds that the workaround is not appearing in the email. What is the most likely reason?

Accepted Answer

The mail script references the 'workaround' field, but the field is empty at the time the notification is generated.. Mail scripts in notifications execute in the context of the record that triggered the notification. If the referenced field is empty at the time the notification is generated, the script will produce no output. In this scenario, the workaround field might not be populated when the state changes to Known Error. The administrator should ensure the field is filled before the state change, or use a different trigger, such as when the workaround is updated.

Answer

The notification is set to 'Send to event creator' and therefore does not include record data.

Answer

The mail script must be placed in the 'Subject' field instead of the body.

Answer

The notification's 'Weight' is set to 0, causing the mail script to be ignored.

Question 9

A ServiceNow administrator needs to create a business rule that runs before a record is inserted into the 'problem' table. The rule should automatically set the 'Assigned to' field to the current user if it is empty. Which business rule configuration should the administrator use?

Accepted Answer

When: Before, Insert: true, Update: false, Script: if (current.assigned_to.nil()) { current.assigned_to = gs.getUserID(); }. A before insert business rule is the correct choice because it allows modification of the record before it is committed to the database. The script checks if 'assigned_to' is empty and sets it to the current user. This avoids an extra update and ensures the field is populated upon creation. After rules are used for post-save actions, not for setting field values.

Answer

When: After, Insert: false, Update: true, Script: if (current.assigned_to.nil()) { current.assigned_to = gs.getUserID(); current.update(); }

Answer

When: Before, Insert: false, Update: true, Script: if (current.assigned_to.nil()) { current.assigned_to = gs.getUserID(); }

Answer

When: After, Insert: true, Update: false, Script: if (current.assigned_to.nil()) { current.assigned_to = gs.getUserID(); current.update(); }

Question 10

An administrator is troubleshooting a form where a field labeled 'Customer impact' is not appearing for any user, even though it exists on the Incident table and has been added to the form layout. Which two configurations should the administrator verify first? (Choose two.)

Accepted Answer

A field-level read ACL that denies read access to the field for the affected users.. Field visibility on a form is governed primarily by field-level read ACLs and UI policies. An ACL that denies read access will strip the field from the form, and a UI policy action that sets visibility to false will hide it after the form loads. Both are evaluated for all users unless scoped by role or condition, making them the first things to inspect when a field on the layout is missing.

Answer

The field's dictionary entry has a default value that is empty.

Answer

The field is marked as inactive in the dictionary.

Answer

The form's section has more than the maximum allowed number of fields per section.

Question 11

An administrator wants to add a new field to the Incident form and ensure it appears in a specific position within an existing section. The field already exists on the Incident table. Which sequence of actions should the administrator perform in the Form Designer?

Accepted Answer

Open the Incident form in Form Designer, drag the field from the Field Navigator into the desired section and position, then save the layout.. Form Designer is the native drag-and-drop tool for modifying form layouts. Administrators can add fields from the Field Navigator, place them precisely within existing sections, and save the layout to update the underlying sys_ui_element records. Creating new sections, manually editing tables, or saving as a new view are either unnecessary or incorrect for this requirement.

Answer

Navigate to the sys_ui_element table, create a new record with the field name and the desired position number, then save.

Answer

Open the Incident form in Form Designer, create a new section, add the field to the new section, then move the section to the desired location.

Answer

Open the Incident form in Form Designer, drag the field from the Field Navigator into the desired section, then use the 'Save as new view' option to preserve the change.

Question 12

A ServiceNow administrator needs to ensure that whenever an incident is updated, the 'Closed' state can only be set if the 'Close notes' field is populated. The validation must run before the record is saved to the database. Which feature should the administrator configure?

Accepted Answer

A before business rule with a script that checks the state and close notes, then aborts the update if the condition fails.. A before business rule is the correct solution because it executes before the record is committed to the database, allowing the administrator to validate the state and close notes and abort the transaction if necessary. This ensures that the rule is enforced regardless of how the update is initiated, providing a robust server-side validation.

Answer

An after business rule that updates the record to revert the state if close notes are empty.

Answer

A data policy that sets the 'Close notes' field to mandatory when the state is 'Closed'.

Answer

A UI policy that makes the 'Close notes' field mandatory when the state is set to 'Closed'.

Question 13

A CMDB administrator must ensure that when a server CI is marked as retired, all related application CIs are reviewed for potential impact. The administrator wants to run a report that lists every CI directly related to a specific server. Which table should the report query to retrieve the relationship records?

Accepted Answer

cmdb_rel_ci. CI relationships are stored as records in the cmdb_rel_ci table, where each row references a parent CI, a child CI, and a relationship type. To list all CIs directly related to a server, the administrator filters cmdb_rel_ci on the server's sys_id in either the parent or child field. This table is the authoritative source for relationship reporting and dependency analysis.

Answer

cmdb_ci_rel

Answer

cmdb_ci

Answer

cmdb_relationship

Question 14

A ServiceNow administrator is asked to create a new view for the Incident form that shows only the 'Short description', 'Caller', and 'State' fields. This view will be used by the service desk for quick incident triage. Where should the administrator configure this?

Accepted Answer

Form Design for the Incident table, selecting the new view from the view selector.. Form views are managed through the Form Designer, where administrators can select an existing view or create a new one and then add or remove fields as needed. This creates a distinct layout for that view without altering the default view. List layouts, dictionary entries, and UI policies do not provide the ability to define a separate form view with a specific set of fields.

Answer

Dictionary Entries for the Incident table, setting the fields to appear only in the new view.

Answer

List Layout for the Incident table, applying a filter for the new view.

Answer

UI Policies for the Incident table, creating a policy that hides fields when the view is selected.

Question 15

An administrator is configuring the Incident form and wants to ensure that certain fields are automatically populated based on the value of the 'Category' field. The administrator plans to use a UI Policy to set the 'Assignment group' and 'Priority' fields when Category is 'Software'. Which two actions must the administrator perform to achieve this? (Choose two.)

Accepted Answer

Add UI Policy Actions to set the 'Assignment group' and 'Priority' fields to specific values.. To use a UI Policy to set field values, the administrator must define a condition that triggers the policy and then create UI Policy Actions that specify which fields to set and to what values. This approach provides a no-code, dynamic solution that responds immediately to user changes on the form. Client scripts, data policies, and scheduled jobs are alternative methods that do not align with the requirement or the chosen tool.

Answer

Write a client script that runs onLoad to set the field values.

Answer

Configure a scheduled job to update the fields based on Category.

Answer

Create a data policy to enforce the field values on the server.