Scenario practice questions

A developer is debugging an issue where a Script Action in a Flow Designer flow is not triggering. The flow is configured to run when a record is created or updated in the incident table. The Script Action is supposed to set a field based on a condition, but it never executes. What should the developer check first?

Trap 1: Check if the flow is published.

Unpublished flows would not run at all; but if it's unpublished, no actions would run.

Trap 2: Check if the script include used in the Script Action is accessible.

This would cause an error, but the action would still be triggered.

Trap 3: Check if the Script Action script has syntax errors.

Syntax errors would raise an error, but the action would still attempt execution.

A
Check if the flow is published.
Why wrong: Unpublished flows would not run at all; but if it's unpublished, no actions would run.
B
Check if the script include used in the Script Action is accessible.
Why wrong: This would cause an error, but the action would still be triggered.
C
Check if the Script Action script has syntax errors.
Why wrong: Syntax errors would raise an error, but the action would still attempt execution.
D
Check the flow's trigger conditions to ensure they match the record update.
The most common issue is that the trigger conditions are not met for the specific record.

Question 2mediummultiple choice

A developer created a UI Script and a Client Script as shown. Both scripts set urgency and impact to '1' when priority is '1'. However, when the priority is changed to '1' on an existing record, the urgency and impact fields do not update. What is the most likely cause?

Exhibit

Refer to the exhibit.

// UI Script: myCustomUIScript
function onLoad() {
    var priority = g_form.getValue('priority');
    if (priority == '1') {
        g_form.setValue('urgency', '1');
        g_form.setValue('impact', '1');
    }
}

// Client Script: onChange - priority
function onChange(control, oldValue, newValue, isLoading) {
    if (newValue == '1') {
        g_form.setValue('urgency', '1');
        g_form.setValue('impact', '1');
    }
}

Trap 1: The priority field is not a choice field, so onChange does not fire

onChange fires for any field change, not just choice fields.

Trap 2: The Client Script function name is incorrect; it should be…

The function name 'onChange' is correct for a client script of type onChange.

Trap 3: The g_form API is deprecated and no longer works

g_form is still valid in ServiceNow.

A
The UI Script is not being called because it is not associated with any form or event
UI Scripts are not automatically executed; they must be called from a Client Script or UI Policy.
B
The priority field is not a choice field, so onChange does not fire
Why wrong: onChange fires for any field change, not just choice fields.
C
The Client Script function name is incorrect; it should be 'onChangePriority'
Why wrong: The function name 'onChange' is correct for a client script of type onChange.
D
The g_form API is deprecated and no longer works
Why wrong: g_form is still valid in ServiceNow.

Question 3mediummultiple choice

A company has a Service Portal that includes a custom widget for submitting hardware requests. The widget has a client controller that calls a server script to create a new record in the 'hardware_request' table. Recently, users have reported that when they click the 'Submit' button, the widget sometimes does not show a success message, and the record is not created. The developer reviews the server script, which uses gs.log to log errors, and sees no errors in the logs. The client controller uses $scope.server.get() to call the server. The widget template uses ng-show='data.success' to display a success message. Based on this scenario, what is the most likely cause of the intermittent issue?

Trap 1: The server script fails due to a mandatory field not being…

The developer checked logs and saw no errors.

Trap 2: The server script uses data.success = true; but the client…

The client controller receives data from the server.

Trap 3: The widget has a Client Script that conflicts with the server…

Client Scripts are not used in Service Portal widgets.

A
The server script fails due to a mandatory field not being provided, but the error is not logged.
Why wrong: The developer checked logs and saw no errors.
B
The server script uses data.success = true; but the client controller does not read it.
Why wrong: The client controller receives data from the server.
C
The widget has a Client Script that conflicts with the server script.
Why wrong: Client Scripts are not used in Service Portal widgets.
D
The client controller does not handle the asynchronous response properly; the success message depends on the promise resolving before the user might navigate away or click again.
Asynchronous calls require proper handling of promises to update scope.

Question 4easymultiple choice

A company is importing user records from a CSV file using an import set. The transform map is configured to update existing records and insert new ones based on the email field. After running the import, they notice that some existing records were not updated even though the email matched. The email field in the target user table is correctly populated and has a unique index. The source CSV file has no obvious formatting issues. The import set runs without errors. What is the most likely cause?

Trap 1: The source CSV has trailing spaces in the email field.

Incorrect: While trailing spaces could cause mismatches, the scenario indicates that 'some' records were not updated, which suggests a systemic issue rather than a data quality one.

Trap 2: The email field in the target table is not indexed.

Incorrect: Indexing improves performance but does not affect whether records are matched for update.

Trap 3: The import set table does not have a unique index on the email…

Incorrect: A unique index on the import set table is not required for matching to target records; it only helps detect duplicates within the same import.

A
The transform map's 'Coalesce' checkbox is not selected on the email field mapping.
Correct: Coalesce must be enabled for the system to match incoming records to existing target records based on that field.
B
The source CSV has trailing spaces in the email field.
Why wrong: Incorrect: While trailing spaces could cause mismatches, the scenario indicates that 'some' records were not updated, which suggests a systemic issue rather than a data quality one.
C
The email field in the target table is not indexed.
Why wrong: Incorrect: Indexing improves performance but does not affect whether records are matched for update.
D
The import set table does not have a unique index on the email field.
Why wrong: Incorrect: A unique index on the import set table is not required for matching to target records; it only helps detect duplicates within the same import.

Question 5easymultiple choice

An administrator sees that a client script on a catalog item is not firing. The script is defined in the catalog item's 'Variable Editor' as a 'onSubmit' script. Which is the most likely reason?

Trap 1: The script is set to run on 'onLoad', but the page is being cached

Incorrect; client scripts run even if the page is cached because they execute in the browser.

Trap 2: The script is defined on a variable, but the variable is not on the…

Incorrect; if the variable is not on the form, its client script still runs but may not have any effect.

Trap 3: The script uses 'g_form' but the form is not loaded yet

Incorrect; g_form is available after the form loads, so onLoad and onSubmit scripts have access to it.

A
The script is set to run on 'onLoad', but the page is being cached
Why wrong: Incorrect; client scripts run even if the page is cached because they execute in the browser.
B
The script is defined on a variable, but the variable is not on the order form
Why wrong: Incorrect; if the variable is not on the form, its client script still runs but may not have any effect.
C
The script is written as a 'Catalog Client Script' but is defined in the 'Variable Editor' of the variable
Correct; client scripts for catalog items must be defined in the Catalog Client Scripts related list, not inside a variable definition.
D
The script uses 'g_form' but the form is not loaded yet
Why wrong: Incorrect; g_form is available after the form loads, so onLoad and onSubmit scripts have access to it.

Question 6hardmultiple choice

A Business Rule uses 'current.setAbortAction(true)' to stop a record from being saved. However, the record is still saved under certain conditions. Which scenario could cause this?

Trap 1: The Business Rule is on a table that is extended from a table with…

Order does not affect abort ability.

Trap 2: Another Business Rule runs in the same order but sets abort to…

Once abort is set, it cannot be undone by another rule.

Trap 3: The Business Rule has a condition that is not met.

If condition not met, abort not triggered, but this is expected behavior.

A
The Business Rule runs after the database operation.
After rules cannot abort the operation.
B
The Business Rule is on a table that is extended from a table with a higher order Business Rule.
Why wrong: Order does not affect abort ability.
C
Another Business Rule runs in the same order but sets abort to false.
Why wrong: Once abort is set, it cannot be undone by another rule.
D
The Business Rule has a condition that is not met.
Why wrong: If condition not met, abort not triggered, but this is expected behavior.

Question 7mediummultiple choice

Refer to the exhibit. Which scenario most likely caused this error?

Exhibit

2023-10-01 12:34:56 Error: Script error: Cannot read property 'sys_id' of null
Script: Business Rule "Update Related Records" on Incident table
Line: 15

Trap 1: The Business Rule runs on delete and 'current' is null.

Current is never null on delete.

Trap 2: The Business Rule tries to access a field that doesn't exist.

Would give 'undefined' not 'null' error.

Trap 3: The Business Rule is not active.

Inactive rule would not produce error.

A
The Business Rule runs on delete and 'current' is null.
Why wrong: Current is never null on delete.
B
The Business Rule tries to access a field that doesn't exist.
Why wrong: Would give 'undefined' not 'null' error.
C
The Business Rule uses 'previous.sys_id' but the record is new.
On insert, previous is null.
D
The Business Rule is not active.
Why wrong: Inactive rule would not produce error.