Scenario practice questions

A company needs to import data from a CSV file into the User table. The CSV includes fields for first name, last name, email, and department. However, the import fails because some email addresses are invalid. Which feature in ServiceNow can be used to prevent invalid emails from being imported?

Trap 1: Data Source configuration

A Data Source defines the source file and field mapping, not validation rules.

Trap 2: Import Set Row

Import Set Row is a staging record; validation occurs during transform.

Trap 3: Import Set Table API

The Import Set Table API is used to insert records programmatically, not for validation.

A
Data Source configuration
Why wrong: A Data Source defines the source file and field mapping, not validation rules.
B
Import Set Row
Why wrong: Import Set Row is a staging record; validation occurs during transform.
C
Transform Map with condition scripts
Transform Maps can include condition scripts to skip or error on invalid data, such as invalid email addresses.
D
Import Set Table API
Why wrong: The Import Set Table API is used to insert records programmatically, not for validation.

Question 2easymultiple choice

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

Trap 1: User approval

User approval sends to a specific user, not the manager.

Trap 2: Role approval

Role approval sends to all users with a role, not just the manager.

Trap 3: Group approval

Group approval sends to a group, not specifically to the manager.

A
Approval - Manager
This rule automatically determines and sends to the manager of the requestor.
B
User approval
Why wrong: User approval sends to a specific user, not the manager.
C
Role approval
Why wrong: Role approval sends to all users with a role, not just the manager.
D
Group approval
Why wrong: Group approval sends to a group, not specifically to the manager.

Question 3hardmultiple choice

A user reports that after clicking 'New' on the incident module, the form loads but the 'Category' field is missing. Other users see the field. What is the most likely cause?

Trap 1: The field is hidden by a UI policy

A UI policy would affect all users, not just one.

Trap 2: The field is not in the default form view

If other users see it, the default view includes the field.

Trap 3: The user's role does not have read access to the field

ACLs would prevent access for all users with that role.

A
The field is hidden by a UI policy
Why wrong: A UI policy would affect all users, not just one.
B
The field is not in the default form view
Why wrong: If other users see it, the default view includes the field.
C
The user has a personal form layout that removed the field
Personalization can cause a field to be missing for an individual user.
D
The user's role does not have read access to the field
Why wrong: ACLs would prevent access for all users with that role.

Study the full ACL explanation →

Question 4mediummultiple choice

Your company uses ServiceNow for IT Service Management. The 'incident' table has a custom 'create' ACL that restricts creation of incidents to users with the 'snc_internal' role. However, external users with the 'snc_external' role should also be able to create incidents via a portal. The portal uses a REST message that authenticates as a specific integration user. The integration user has the 'snc_internal' role. Despite the REST API call being successful, external users report that they cannot submit incidents through the portal. The system logs show that the REST API call returns a success, but the incident record is not created. What is the most likely cause?

Trap 1: The integration user's session has expired during the request.

Wrong: The REST call is successful, indicating authentication is fine.

Trap 2: The portal widget is using a different table name in the API call.

Wrong: The API call returns success, so table name is correct.

Trap 3: The REST API endpoint is mapped to the wrong table.

Wrong: The API call is successful, so mapping is correct.

A
The integration user's session has expired during the request.
Why wrong: Wrong: The REST call is successful, indicating authentication is fine.
B
The portal widget is using a different table name in the API call.
Why wrong: Wrong: The API call returns success, so table name is correct.
C
The ACL is evaluated against the portal user, who lacks the 'snc_internal' role.
Correct: In portal, the user's session is used for ACL checks.
D
The REST API endpoint is mapped to the wrong table.
Why wrong: Wrong: The API call is successful, so mapping is correct.

Question 5hardmultiple choice

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?

Trap 1: A Data Policy overrides the mandatory attribute

Data Policies enforce server-side and do not affect client-side highlighting.

Trap 2: The UI Policy is set to OnSubmit

OnSubmit would validate on submit, but the symptom is lack of client-side highlighting.

Trap 3: The UI Policy runs after the Client Script

If it runs after, the value would be set and the condition would apply correctly.

A
A Data Policy overrides the mandatory attribute
Why wrong: Data Policies enforce server-side and do not affect client-side highlighting.
B
The UI Policy is set to OnSubmit
Why wrong: OnSubmit would validate on submit, but the symptom is lack of client-side highlighting.
C
The UI Policy runs after the Client Script
Why wrong: If it runs after, the value would be set and the condition would apply correctly.
D
The UI Policy runs before the Client Script
UI Policies execute earlier in the form load sequence; if the condition depends on a client script value, it may be missed.

Question 6hardmultiple choice

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

Trap 1: Create a flow that uses user input via flow variables

Flow variables are not triggered by conversation input directly.

Trap 2: Use a record producer to capture the information

Record producers are for catalog submissions, not for Virtual Agent conversations.

Trap 3: Configure a catalog item with variables and embed it in Virtual…

Catalog items are not intended for in-conversation input collection.

A
Create a flow that uses user input via flow variables
Why wrong: Flow variables are not triggered by conversation input directly.
B
Use a record producer to capture the information
Why wrong: Record producers are for catalog submissions, not for Virtual Agent conversations.
C
Use a topic with variables to prompt for employee ID and date of birth
The topic can have variables that collect input from the user as part of the conversation flow.
D
Configure a catalog item with variables and embed it in Virtual Agent
Why wrong: Catalog items are not intended for in-conversation input collection.

Question 7mediummulti select

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

Trap 1: Displaying a warning message when a variable is invalid

Warning messages are typically shown using client scripts (onSubmit or onChange) or UI Policy messages, but the question emphasizes 'scenarios that require UI Policy' and D is better done with client script for validation logic.

Trap 2: Setting a variable's value from a record producer mapping

Record producer mapping is configured in the record producer record, not via UI Policy.

Trap 3: Making a variable read-only after the catalog item is submitted

Post-submission behavior is not controlled by UI Policies which run on the form.

A
Displaying a warning message when a variable is invalid
Why wrong: Warning messages are typically shown using client scripts (onSubmit or onChange) or UI Policy messages, but the question emphasizes 'scenarios that require UI Policy' and D is better done with client script for validation logic.
B
Hiding a variable based on another variable's value
UI Policy can control visibility declaratively without scripting.
C
Setting a variable's value from a record producer mapping
Why wrong: Record producer mapping is configured in the record producer record, not via UI Policy.
D
Making a variable read-only after the catalog item is submitted
Why wrong: Post-submission behavior is not controlled by UI Policies which run on the form.
E
Making a variable mandatory only when a condition is met
UI Policy actions include setting mandatory based on conditions.

Question 8mediummultiple choice

A catalog item is configured to use an order guide. When a user submits the order guide, only the first catalog item in the guide appears. What is the most likely cause?

Trap 1: The workflow attached to the order guide is incomplete

Workflows run after submission; they don't control which items are generated.

Trap 2: The catalog items have mandatory variables that are not filled

Missing mandatory variables would cause submission failure, not omission of items.

Trap 3: The order guide is in a restricted category

Category restrictions affect visibility, not the number of items delivered.

A
The workflow attached to the order guide is incomplete
Why wrong: Workflows run after submission; they don't control which items are generated.
B
The order guide's 'Delivery method' is set to 'One at a time'
This setting causes items to be presented sequentially, so only the first item appears initially.
C
The catalog items have mandatory variables that are not filled
Why wrong: Missing mandatory variables would cause submission failure, not omission of items.
D
The order guide is in a restricted category
Why wrong: Category restrictions affect visibility, not the number of items delivered.