SNOW-CAD Platform Features and Integration — Timed 10 Questions

Question 1

A company is integrating ServiceNow with an external system using REST API. The integration is failing with a 401 Unauthorized error. The integration user's credentials are correct and the user has the 'rest_service' role. What is the most likely cause of the failure?

Accepted Answer

The OAuth token used for authentication has expired or is invalid.. A 401 Unauthorized error indicates that the request lacks valid authentication credentials. Since the integration user's credentials are correct and the user has the 'rest_service' role, the most likely cause is that the OAuth token used for authentication has expired or is invalid. ServiceNow REST API integrations commonly use OAuth 2.0 tokens, which have a finite lifetime and must be refreshed or reissued upon expiration.

Answer

The password for the integration user does not meet complexity requirements.

Answer

The integration user does not have the 'rest_api' role.

Answer

The integration is hitting a table ACL that denies read access.

Question 2

An administrator wants to enable inbound email integration to automatically create incidents from emails sent to support@company.com. What is the first step in configuring this?

Accepted Answer

Configure an email account (mailbox) to receive emails.. The first step in configuring inbound email integration is to set up an email account (mailbox) that the instance can connect to and retrieve emails from. Without a configured mailbox, the instance has no source from which to pull incoming messages, making subsequent steps like creating inbound email actions or enabling plugins meaningless. This mailbox configuration defines the IMAP or POP3 server, credentials, and folder settings that the platform uses to poll for new emails.

Answer

Enable the Email Integration plugin.

Answer

Create an inbound email action.

Answer

Create an ACL to allow email processing.

Question 3

A ServiceNow instance is being integrated with an external HR system using a SOAP message. The SOAP call is failing intermittently. The developer notices that the XML payload contains special characters like '&' and '<'. What is the best practice to handle these characters in SOAP messages?

Accepted Answer

Escape the characters using XML entities (e.g., & for &).. SOAP messages are XML-based, and special characters like '&' and '<' must be escaped using XML entities (e.g., & for &, < for <) to maintain valid XML syntax. This ensures the XML parser correctly interprets the payload without breaking the message structure, which is the standard practice per the XML specification and SOAP protocol.

Answer

Wrap the payload in a CDATA section.

Answer

Encode the entire payload in Base64.

Answer

Use URL encoding for the payload.

Question 4

A company wants to allow their customers to submit requests via email. The email should create a new record in the 'Request' table. Which component should be used to define the mapping of email fields to the ServiceNow table fields?

Accepted Answer

Inbound Email Action. An Inbound Email Action is the correct component because it defines the mapping of email fields (e.g., subject, body, sender) to ServiceNow table fields (e.g., 'Short description', 'Description', 'Caller'). It uses a script or condition to parse the incoming email and create or update records in a specified table, such as the 'Request' table. This is the standard mechanism for turning an email into a ServiceNow record.

Answer

Email Account

Answer

Inbound Email Script

Answer

Email Notification

Question 5

A developer is building a REST API endpoint in ServiceNow to return data from the 'incident' table. The API should only return incidents assigned to the caller. Which method should be used to filter the records based on the caller's user ID?

Accepted Answer

Use the 'sysparm_query' parameter with an encoded query.. Option B is correct because the 'sysparm_query' parameter allows you to pass an encoded query string to filter records in a REST API endpoint. By specifying a query like 'assigned_to=javascript:gs.getUserID()' or using the caller's sys_id directly, you can restrict the incident records returned to only those assigned to the caller. This is the standard method for applying dynamic filters in ServiceNow REST API calls.

Answer

Use the 'sysparm_display_value' parameter.

Answer

Use the 'sysparm_limit' parameter to limit results.

Answer

Use the 'sysparm_fields' parameter to specify fields.

Question 6

Which TWO of the following are valid methods to authenticate a REST API call to ServiceNow?

Accepted Answer

Basic Authentication with username and password.. Option C is correct because ServiceNow supports Basic Authentication, where the REST API call includes an HTTP Authorization header with a Base64-encoded string of 'username:password'. This is a straightforward method for authenticating API requests, though it requires HTTPS to avoid exposing credentials in plaintext.

Answer

SAML assertion authentication.

Answer

LDAP authentication.

Answer

API Key authentication.

Question 7

Which THREE of the following are valid components of the ServiceNow IntegrationHub?

Accepted Answer

Action steps. Action steps are a core component of IntegrationHub, representing individual, reusable actions that can be composed into a flow to perform specific tasks, such as making API calls or transforming data. They are the building blocks that define the logic and operations within an IntegrationHub flow, enabling complex integrations without custom scripting.

Answer

REST Message

Answer

Data Source

Question 8

Refer to the exhibit. A developer is making a REST API call to create an incident. The call returns a 201 Created response, but the incident record is not visible in the instance. What is the most likely cause?

Accepted Answer

The 'caller_id' sys_id is invalid or points to a non-existent user.. A 201 Created response indicates the REST API call was syntactically correct and the server accepted the payload, but the incident record is not visible. The most likely cause is an invalid caller_id sys_id, because ServiceNow validates the caller_id field against the sys_user table during record creation. If the sys_id does not exist or is malformed, the record is created but the caller_id reference fails silently, often causing the record to be hidden from standard views or filtered out by default queries.

Answer

The request method should be PUT instead of POST.

Answer

The field 'short_description' is misspelled.

Answer

The instance has an ACL that prevents creating incidents via REST.

Question 9

Refer to the exhibit. A developer created this Script Include to be used as a REST API endpoint. However, when calling the API, the response is empty. What is the most likely reason?

Accepted Answer

The Script Include is not marked as 'REST API endpoint' or does not extend the appropriate class.. Option D is correct because a Script Include used as a REST API endpoint must either extend the appropriate class (such as 'RESTAPI' or 'RESTAPIV2') or be explicitly marked as a REST API endpoint in its definition. Without this, the platform does not recognize it as a valid endpoint, resulting in an empty response when the API is called.

Answer

The Script Include is not marked as 'Client callable'.

Answer

The function name 'getOpenIncidents' is not exposed.

Answer

The GlideRecord query returns no results.

Question 10

A global company is using ServiceNow for IT Service Management. They have an external asset management system that needs to update asset records in ServiceNow in real-time. The integration is implemented using REST API calls from the external system to ServiceNow. Recently, the integration started failing intermittently with HTTP 429 (Too Many Requests) errors. The external system is sending a high volume of update requests (up to 1000 per minute) to the /api/now/table/alm_asset endpoint. The administrator noticed that the instance performance is degraded during peak times. The company wants to resolve the 429 errors while ensuring data is updated as quickly as possible, but without overloading the instance. Which course of action should the administrator take?

Accepted Answer

Implement a queue-based integration using Flow Designer to process updates asynchronously with a controlled rate.. Option C is correct because it addresses the root cause of the 429 errors—overwhelming the REST API endpoint with synchronous requests—by decoupling the external system from direct writes. Using Flow Designer with a queue (e.g., via the ServiceNow Queue or a custom table) allows the external system to submit requests asynchronously, and then a scheduled flow or script processes them at a controlled rate (e.g., using a rate limiter or batch size). This ensures data is updated as quickly as possible without exceeding the instance's API rate limits or degrading performance, as the processing is throttled server-side.

Answer

Increase the API rate limit in the instance's system properties.

Answer

Reduce the number of requests from the external system to 500 per minute.

Answer

Switch the authentication method from basic to OAuth to reduce overhead.