Application development using ServiceNow Studio practice questions

Develop the application in global scope and manually copy components to target instances.

Why wrong: Manual copying is error-prone and not a best practice.

Use the 'Application' module in the navigator to create a new application without scope.

Why wrong: Applications without scope are global and can cause conflicts.

Create the application in the global scope and use update sets for distribution.

Why wrong: Updating global applications can cause conflicts in other instances.

Navigate to 'Tables' module, create a new table, and then assign it to the application.

Why wrong: The table should be created within the application scope from the start.

Open Studio, select the application, navigate to 'System Definition' > 'Tables' and create the table.

Why wrong: Studio provides a dedicated 'Create Table' option within the application.

Open Studio, go to 'Application Files', click 'New', select 'Table' and configure.

Why wrong: While possible, the recommended path is through the application's Data Model.

The condition 'current.state == 1' is incorrect syntax.

Why wrong: The syntax is valid for a before query business rule.

Another business rule with higher order is preventing execution.

Why wrong: Order only affects sequence, not whether a rule runs.

The business rule is scoped and cannot access the table.

Why wrong: Scoped business rules can access tables within the same scope.

onChange client script

Why wrong: onChange triggers on field value change, not on form load.

onSubmit client script

Why wrong: onSubmit runs on form submission.

onCellEdit client script

Why wrong: onCellEdit is for list views, not forms.

Set up a REST API endpoint that external cron jobs call every hour.

Why wrong: This introduces unnecessary external dependency.

Create a Business Rule that runs on 'after' insert and update to check for overdue tasks.

Why wrong: Business Rules run on database operations, not on a schedule.

Use Flow Designer to create a scheduled flow that runs every hour.

Why wrong: While possible, a Scheduled Job is simpler and more appropriate for this task.

Scoped applications can create records in global tables via GlideRecord without restrictions.

Why wrong: Creating records requires update rights.

Scoped applications can call global script includes by default.

Why wrong: Access to global script includes requires explicit granting.

Scoped applications can update global tables without any additional configuration.

Why wrong: Update requires the application to be granted the 'global' application scope or specific rights.

Use update sets to move the application to production.

Why wrong: Scoped applications should be exported as .snc files, not update sets.

Publish the application to the ServiceNow Store for deployment.

Why wrong: Publishing to the Store is optional and not required for internal deployment.

The ACLs on the table restrict access for the script's user.

Why wrong: ACLs would cause a read/write error, not a 'does not exist' error.

The business rule is trying to access a table in a different scope without using the 'global.' prefix.

Why wrong: The table is in the same scope, so no prefix is needed.

The application was installed via an update set and the table was not included.

Why wrong: The error occurs in the current instance, not during installation.

The script has a syntax error.

Why wrong: The script appears syntactically correct.

The business rule runs after the record is saved, so updates are ignored.

Why wrong: A 'before' business rule runs before save, so updates are applied.

The business rule condition is incorrect.

Why wrong: The condition is valid for state 0.

Clone the Incident table and rename it, then modify the clone.

Why wrong: Cloning is not a standard practice for this scenario; it may cause maintenance issues and duplicate data.

Create a new table from scratch and manually add all necessary fields and business rules.

Why wrong: This would require reimplementing all existing incident functionality, which is inefficient and error-prone.

Use the Configuration Management Database (CMDB) to store the records.

Why wrong: The CMDB is for configuration items, not for incident-like records with custom fields.

Studio requires a separate HI (High-Impact) instance to develop applications.

Why wrong: Studio is available on all instances, not just HI instances.

When creating a new application in Studio, a new scope is automatically generated without user input.

Why wrong: The developer must specify the application scope; it is not automatic.

Studio can only be used by users with the admin role.

Why wrong: Any user with the appropriate application developer role can use Studio.

Replace gs.yearsAgoStart(5) with gs.yearsAgoEnd(5) to get the end of the year 5 years ago.

Why wrong: gs.yearsAgoEnd(5) returns the last day of the year 5 years ago, which is not what is needed.

Change the table from 'Asset' to 'Asset [new]' as the business rule may be on the wrong table.

Why wrong: The table name 'Asset' is correct; changing it would break the rule.

Increase the order of the business rule to 200 to ensure it runs after other rules.

Why wrong: The order does not affect the logic; the condition is the issue.

Write a Business Rule to populate a manager field.

Why wrong: Incorrect: Business Rules automate tasks, not define relationships.

Configure an Access Control Rule (ACL) to filter records.

Why wrong: Incorrect: ACLs control access, not relationships.

Use the GlideRecord API to join the tables in a script.

Why wrong: Incorrect: GlideRecord is for data retrieval, not defining relationships.

Navigate to System Applications > Studio and click 'Create Application'.

Why wrong: System Applications is deprecated.

Use the Application Navigator to create a new application.

Why wrong: No such option in Application Navigator.

Go to Application Files > New and select 'Application'.

Why wrong: Creates a file, not an application.

The developer needs to set the 'Update Set' field on each record to 'Default Update Set'.

Why wrong: Automatic association.

Update sets are not used for scoped applications; only for global scope.

Why wrong: Scoped applications also use update sets.

The developer must manually create a new update set and assign it to the application scope.

Why wrong: Not required; Studio handles it.

The client script is set to run on the 'Load' event instead of 'Change'.

Why wrong: Could be, but hide field typically works on load if condition is evaluated; not most likely.

The script is using a deprecated API.

Why wrong: Deprecation likely not the issue.

The script is not running due to a missing 'Run As' role.

Why wrong: Client scripts don't have Run As.

The field is not part of the application scope.

Why wrong: Fields can be referenced across scopes.

A global scope update set

Why wrong: Not a role.

No special role; any user can create applications

Why wrong: Requires admin.

Application Creator role

Why wrong: Not a standard role.

Set the table's 'Accessible from' field to include the other application scope.

Why wrong: No such field exists.

Export the table definition as XML and import into the other application.

Why wrong: Not a real-time sharing method.

Use a web service to expose the table data.

Why wrong: Overly complex.