SNOW-CAD Quick Quiz — 10 Questions

Question 1

Which THREE of the following are true about ACLs (Access Control Lists)? (Choose three.)

Accepted Answer

ACLs can include conditions that must be met for access.. Option A is correct because ACLs are rule sets whose individual entries (ACEs) contain conditions—such as matching user, group, role, source IP, or time—that must be satisfied before the requested access is granted. Option D is correct because ACLs define permissions that explicitly allow or deny operations like read (SELECT/view) and write (INSERT/UPDATE/DELETE) on records or objects, which is their core purpose. Option E is correct because ACLs can be attached to specific resources and scoped to a particular application or context, so permissions apply only within that application's scope. Option B is wrong because ACLs are enforced server-side (by the database, OS, or service), not evaluated on the client, which the client could bypass. Option C is wrong because ACLs apply broadly to many object types—tables, records, files, network interfaces, and other resources—not only to system tables.

Answer

ACLs are evaluated on the client side.

Answer

ACLs are only applicable to system tables.

Question 2

A report on the 'incident' table shows duplicate counts due to the 'active' field being true for some records that shouldn't be counted. The report is using a simple count. How can the admin ensure only active incidents are counted?

Accepted Answer

Add a filter condition: 'active = true'.. To ensure only active incidents are counted in a report on the incident table, the administrator should add a filter condition 'active = true'. This filters the report to include only records where the active field is true, thus excluding any records where active is false or empty.

Answer

Create a business rule to set active=false for certain records.

Answer

Remove the 'active' field from the report.

Answer

Group the report by the 'active' field.

Question 3

Which THREE of the following are features available in ServiceNow for integrating data with external systems? (Choose three.)

Accepted Answer

SOAP Web Service. Option A (SOAP Web Service) is correct because ServiceNow provides outbound SOAP web service support via SOAP Message and related modules, and inbound SOAP via Scripted SOAP Web Services, enabling XML-based integration with external systems. Option B (LDAP) is correct because ServiceNow offers an LDAP integration through the LDAP Server and LDAP OU configuration records, used to import user and group data from directory servers. Option D (REST API) is correct because ServiceNow exposes the REST API (Table API, Import Set API, Scripted REST APIs) and outbound REST Message functionality for integrating with external systems over HTTP. Option C (Email) is not one of the marked integration features here, since email is primarily a notification and inbound email action mechanism rather than a data integration API. Option E (Print) is incorrect because printing is a UI/output capability, not a data integration feature.

Answer

Email

Answer

Print

Question 4

A script include has a function that uses the 'GlideRecordSecure' class. When called from a Business Rule in a different scope, it throws a security exception. What is the most likely cause?

Accepted Answer

The script include does not have the 'Accessible from' property set to all scopes.. The 'Accessible from' property on a Script Include controls which scopes can invoke its functions. When this property is not set to 'All scopes', a Business Rule in a different scope cannot call the Script Include, resulting in a security exception. The GlideRecordSecure class itself is accessible across scopes, but the Script Include's access restriction prevents the call.

Answer

The function is not defined as a static function.

Answer

The GlideRecordSecure class is not accessible from other scopes.

Answer

The script include is not marked as public.

Question 5

When creating a new table using the 'Create Table' module, which setting determines whether the table will inherit fields from an existing table?

Accepted Answer

Extends. 'Extends,' is correct because it allows the new table to inherit fields from an existing parent table. Option A, 'Application,' defines the application scope, not inheritance. Option C, 'Table name,' is the system name. Option D, 'Table label,' is the display name.

Answer

Application

Answer

Table name

Answer

Table label

Question 6

An admin notices that a business rule on the 'incident' table that sets the 'assigned_to' field based on the caller's manager is not always firing. The rule is set to run 'Before' and 'Update'. What is the most likely reason?

Accepted Answer

The condition of the business rule is not met because it requires a specific field to change.. A before-update business rule only fires when the record is updated and the rule's condition evaluates to true. If the condition requires a specific field to change (for example, caller_id changes), then updates that do not modify that field will not trigger the rule, which explains why it is not always firing. This is the most likely cause given the rule is otherwise correctly configured.

Answer

The business rule is set to run asynchronously.

Answer

The user lacks the 'incident_edit' ACL.

Answer

The business rule order is set to 100, making it run too late.

Question 7

A developer is creating a new Service Portal page and wants to add a widget that displays a list of the current user's open incidents. The widget must be reusable across multiple pages. Where should the developer create the widget record?

Accepted Answer

In the Service Portal > Widgets module. Service Portal widgets are stored in the sp_widget table and are created via the Service Portal > Widgets module. This allows them to be defined once and reused across multiple pages, either directly or as embedded widgets. Creating a widget in this module ensures it is available for reuse.

Answer

In the sys_ui_page table via a UI Page record

Answer

In the UI Builder under the Components section

Answer

In the Widgets related list on the Service Portal page record

Question 8

A company is integrating with an external HR system using a REST API to create and update user records in the sys_user table. The API endpoint requires a token that expires every 24 hours. The integration is scheduled to run hourly. The token is stored in a credential record. After a few days, the integration fails with a 401 Unauthorized error. The error log shows "Invalid token". What is the most likely cause?

Accepted Answer

The token was refreshed but the credential record was not updated.. The token expires every 24 hours, so after the first day, the stored token becomes invalid. The integration runs hourly and likely attempts to refresh the token, but if the refreshed token is not saved back to the credential record, the old token persists and causes the 401 error. Option A is correct because the most likely cause is that the token was refreshed but the credential record was not updated. The other options are less likely: there's no evidence the URL changed (B), the credential record was deleted (C), or the IP changed (D).

Answer

The REST API endpoint URL changed.

Answer

The credential record was deleted.

Answer

The IP address of the external system changed.

Question 9

Drag and drop the steps to create a new Catalog Item in ServiceNow into the correct order.

Accepted Answer

Navigate to Maintain Items, then Create New, then Set Category and Details, then Add Variables, then Submit. The correct order: navigate to Maintain Items, create new, set category and details, add variables, and submit.

Answer

Navigate to Maintain Items, then Create New, then Add Variables, then Set Category and Details, then Submit

Answer

Set Category and Details, then Navigate to Maintain Items, then Create New, then Add Variables, then Submit

Answer

Navigate to Maintain Items, then Add Variables, then Create New, then Set Category and Details, then Submit

Question 10

A ServiceNow instance is configured to use LDAP for user authentication and role membership. After a recent LDAP schema change, users can authenticate but some users are missing their assigned roles. The LDAP server is returning all attributes correctly. What is the most likely cause of this issue?

Accepted Answer

The 'LDAP Group DN' format in the LDAP server configuration does not match the new schema. The LDAP Group DN format defines how ServiceNow maps LDAP groups to roles. After a schema change, if the DN structure for groups has been altered (e.g., OU names changed), the stored format in the LDAP server configuration will no longer match, causing role membership to fail even though user authentication (which uses a separate base DN and filter) still works. The LDAP server returning all attributes correctly confirms the issue is in the mapping configuration, not in data retrieval.

Answer

The LDAP server's base DN for user search has changed

Answer

The 'Use secure connection' checkbox is unchecked in the LDAP configuration

Answer

The LDAP server is not returning the 'memberOf' attribute for users