Select Two (Multi-Select) Questions

current.state == 'Resolved'

Why wrong: Incorrect; this is true on load even if already resolved, not just on change.

current.state.changes()

Why wrong: Incorrect; this triggers on any state change, not just to Resolved.

current.state.changesFrom() != 'Resolved'

Why wrong: Incorrect; this checks if the previous state was not Resolved, but does not check the new state.

From the Business Rules list, right-click and select 'New'.

Why wrong: Right-click on list does not have 'New' option.

Type 'business_rule.do' in the navigator filter.

Why wrong: This opens the list but does not create a new record.

Create a Client Script and convert it to a Business Rule.

Why wrong: There is no conversion functionality.

The assignment group field is read-only on the form but can be set via business rule

Why wrong: Read-only status on the form does not prevent business rules from setting the field value; therefore this is not a cause.

The business rule is set to run only in the global scope

Why wrong: The scope of the business rule does not affect its ability to run on update; this is not a likely cause.

Return a specific error code as a flow variable.

Why wrong: Error handling is done via error blocks, not return variables directly.

Send an email notification to the system administrator using a notification action.

Why wrong: While possible via a separate notification step, the action itself does not send email; you would add a subsequent action.

Set the action to automatically retry on failure without configuration.

Why wrong: Retry must be explicitly configured; there is no automatic retry.

Database views can reference tables from different instances or databases

Why wrong: Views are limited to tables within the same instance.

Database views can be updated via business rules

Why wrong: Views are read-only; data modifications are not allowed.

Configure email notifications.

Why wrong: Incorrect. Email notifications are configured in the global scope, not Studio.

Run a scheduled job.

Why wrong: Incorrect. Scheduled jobs are managed in the Scheduled Jobs module.

Define a workflow.

Why wrong: Incorrect. Workflows are deprecated and not part of Studio.

Use access control lists (ACLs) on each record.

Why wrong: ACLs can provide security but may not prevent all cross-tenant data access if misconfigured.

Create database views that filter data by company.

Why wrong: Views do not enforce data isolation at the application layer.

Add a condition to every GlideRecord query to filter by company.

Why wrong: Requires strict adherence by all developers; not architectural.

The business rule is set to run on every update, but the script does not check the previous state

Why wrong: Incorrect. The method current.state.changes() correctly detects state changes. The problem is not about checking the previous state.

The business rule's condition field is set to 'state changes'

Why wrong: Incorrect. Setting the condition to 'state changes' would limit execution to state changes, not cause duplicates.

The business rule runs on both insert and update

Why wrong: Incorrect. This would cause an extra email on insert, not multiple emails during a single update.

They run on the server and are called via server-side includes.

Why wrong: Client controllers run in the browser.

They must define a $scope variable explicitly to bind data to the template.

Why wrong: $scope is automatically available via AngularJS.

Reports

Why wrong: Incorrect. Reports are not part of the application file structure.

System Properties

Why wrong: Incorrect. System properties are not exported as XML from Studio.

Homepages

Why wrong: Incorrect. Homepages are not exported as application files.

Use a REST API with a periodic flow that calls an external endpoint.

Why wrong: This requires the external system to expose a REST API; not universally available.

Write a business rule that triggers on an external event via web service.

Why wrong: Business rules execute on ServiceNow events, not external triggers.

Use an email inbound action to parse CSV attachments from the external system.

Why wrong: Email is not reliable for recurring scheduled imports.

Enable the 'Run as advanced' checkbox on the Import Set Row.

Why wrong: This option is used for advanced scripting and not necessary for basic update/insert functionality.

Configure a data source to define the external system connection.

Why wrong: While a data source is needed for the import, it is not specifically required for the update/insert behavior.

Define a Transform Map that maps source fields to target fields.

Why wrong: Mapping is necessary for any import, but not specifically for the update/insert behavior; the question asks for actions required for that behavior.

Create a single 'Department' field on the Contract table and use it to store all department records

Why wrong: A single reference field can only store one record; it cannot handle multiple associations.

Use a 'String' field on the Contract table to store a comma-separated list of department sys_ids

Why wrong: Storing sys_ids as a string violates data normalization and makes querying and reporting difficult.

On submit

Why wrong: On submit is not a UI Policy type.

On delete

Why wrong: On delete is not a UI Policy type.

On query

Why wrong: On query is not a UI Policy type.

Use the 'Application Creator' UI page to define a new scope via REST API.

Why wrong: There is no such UI page; REST API can be used but not via a standard UI page named 'Application Creator'.

Import a v1 update set that includes an application definition.

Why wrong: v1 update sets do not contain application scope definitions; only v2 update sets can create scopes.

Navigate to 'All' > 'Scopes' and click 'New'.

Why wrong: There is no 'Scopes' module under 'All'.

Use GlideAggregate for performance in the API script.

Why wrong: While GlideAggregate can be used, it's not a design consideration for consumption; it's an implementation detail.

Always use OAuth 2.0 for authentication.

Why wrong: OAuth is common but not always required; API keys or basic auth may be used based on requirements.

current.assignment_group.isValidRecord()

Why wrong: This checks if the assignment group record exists, which is not necessary for the condition.

current.assignment_group.changes()

Why wrong: This would only fire when the assignment group changes, not when it is set to the specific group.

gs.getUser().getManager() == 'admin'

Why wrong: This checks the manager of the logged-in user, not related to the assignment group.

Avoid using synchronous GlideAjax calls.

Why wrong: GlideAjax is client-side, not in Business Rules.

Set the Business Rule to run on 'before' if possible.

Why wrong: Not a performance consideration.

They can only be used in scoped applications.

Why wrong: They can be used in global as well.

They cannot be used in UI policies.

Why wrong: They can be used in UI policies via GlideAjax.

They can be called directly without GlideAjax if marked as synchronous.

Why wrong: There is no synchronous call; GlideAjax is async.

Use gs.sleep() to wait for other processes

Why wrong: gs.sleep() is not recommended as it blocks the thread.

Use GlideAggregate for updating records

Why wrong: GlideAggregate is for queries, not updates.