SNOW-CAD Platform Features and Integration — 30 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?

Choose an answer to begin — your selection is scored in the full session.

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

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

Accepted Answer

Basic Authentication with username and password.. 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 3

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 4

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.. 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 5

Match each ServiceNow feature to its primary service.

Accepted Answer

Virtual Agent: AI Search. The correct matches are: Virtual Agent to AI Search, Performance Analytics to Performance Analytics, Service Catalog to Service Portal, and Knowledge Base to Knowledge Management. Common confusions include mixing Virtual Agent with Service Portal or associating Performance Analytics with Knowledge Management.

Answer

Virtual Agent: Service Portal

Answer

Performance Analytics: Knowledge Management

Question 6

A company uses IntegrationHub to connect to an external CRM. The OAuth provider record and REST message are configured. When testing, authentication fails. What is the most likely cause?

Accepted Answer

The OAuth provider profile is not linked to the REST message.. The most likely cause of authentication failure is that the OAuth provider profile is not linked to the REST message. Without this linkage, the authentication configuration is not applied. Option A is incorrect because base64 encoding of the client secret is not a requirement for OAuth. Option C is incorrect because the grant_type parameter is sent in the request body, not in the URL. Option D is incorrect because although POST is the correct HTTP method for token requests, the method itself is not the likely cause of authentication failure.

Answer

The client secret is not base64 encoded.

Answer

The token URL is missing the grant_type parameter.

Answer

The REST message is set to POST instead of GET.

Question 7

A developer needs to import CSV data into a custom table using Import Sets. The data contains a reference field to a user record. Which configuration ensures that the user record is correctly matched?

Accepted Answer

Set the target field 'email' as coalesce on the transform map.. Setting the 'email' field as a coalesce field on the transform map tells the Import Set engine to use that field to match incoming records against existing target table records. When the reference field points to a user record, the coalesce field (e.g., email) is used to look up the sys_user table and automatically populate the correct sys_id, ensuring the reference is properly resolved without manual scripting.

Answer

Set the source field as coalesce on the transform map.

Answer

Configure the import set row to be ignored if the user is not found.

Answer

Use a script in the 'on before' transform script to find the user.

Question 8

A developer is creating a REST API in ServiceNow to expose incident data. The API must return only incidents with 'state' = 2 (in progress) and limit results to 50. Which implementation is correct?

Accepted Answer

In the script, use 'gr.addQuery('state', 2); gr.setLimit(50);' and return the records.. It uses the standard GlideRecord pattern to query the incident table with an 'addQuery' filter for state=2 and 'setLimit' to restrict results to 50, which is the proper server-side approach when building a custom REST API endpoint in a Scripted REST API or similar. The other options misuse table API syntax or GlideRecord methods in ways that would not work as intended.

Answer

Use the ServiceNow table API with endpoint '/api/now/table/incident?state=2&sysparm_limit=50'.

Answer

Use a REST API endpoint with path /api/incidents and set the query parameter 'sysparm_query=state=2' and 'sysparm_limit=50'.

Answer

In the script, use 'gr.get('state', 2)' and then limit via 'gr.setLimit(50)'.

Question 9

A company is using a MID Server to run a discovery probe. The probe fails with a timeout error. The developer checks the MID Server logs and sees 'Connection refused'. What is the most likely issue?

Accepted Answer

The target host's firewall is blocking the port used by the probe.. The 'Connection refused' error in the MID Server logs indicates that the target host actively rejected the connection attempt on the specified port. This is most commonly caused by a firewall on the target host blocking the port used by the discovery probe, as the firewall sends a TCP RST packet to refuse the connection. Incorrect credentials would result in an authentication failure, not a connection refusal, and an unreachable host would produce a 'No route to host' or timeout error.

Answer

The MID Server credentials are incorrect.

Answer

The MID Server's SSL certificate is expired.

Answer

The target host is unreachable from the MID Server network.

Question 10

A ServiceNow instance has a custom table 'u_integration_log' that stores integration transactions. A flow in Flow Designer logs errors by creating records in this table. The flow is running with high volume, and the table is growing quickly causing performance issues. What is the best design to mitigate this?

Accepted Answer

Configure a scheduled job to archive and delete records older than 30 days.. It directly addresses the root cause of performance degradation—uncontrolled table growth—by implementing a scheduled job to archive and delete records older than 30 days. This reduces table size, improves query performance, and maintains the ability to retain recent logs for debugging. In ServiceNow, scheduled jobs can use GlideRecord to delete records based on a date condition, and archiving can be done via export to CSV or a separate archive table.

Answer

Disable error logging in the flow.

Answer

Use a 'Log to file' action in the flow instead of a table.

Answer

Store logs in a separate instance via MID Server.

Question 11

A developer is implementing a custom integration using the ServiceNow REST API Explorer. The endpoint requires an API key in the header. Which approach should be used to secure the API key?

Accepted Answer

Create an authentication profile of type 'API Key' and reference it in the REST message.. The ServiceNow REST API Explorer and REST messages support authentication profiles, which securely store and manage API keys. By creating an 'API Key' authentication profile and referencing it in the REST message, the API key is automatically injected into the request header without exposing it in scripts or system properties. This approach follows ServiceNow best practices for credential management and ensures the key is encrypted and centrally managed.

Answer

Hardcode the API key in the script.

Answer

Store the API key in a system property encrypted.

Answer

Use a REST message variable and set the header directly.

Question 12

Which TWO actions are valid for handling errors in a Flow Designer integration action? (Choose two.)

Accepted Answer

Configure the action to log error details to a local log table.. Option A is correct because Flow Designer integration actions can write error details to a custom log table, giving a persistent audit trail of failures for later troubleshooting. Option B is correct because an 'if' condition can evaluate the HTTP status code returned by the REST step and branch the flow to different error-handling paths. Option C is not a valid error-handling action because integration actions do not expose a configurable error-code output variable for this purpose. Option D is not the intended mechanism for handling errors within an integration action, as notifications are separate flow actions rather than error handling. Option E is incorrect because automatic retries require explicit configuration and are not enabled by default.

Answer

Return a specific error code as a flow variable.

Answer

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

Answer

Set the action to automatically retry on failure without configuration.

Question 13

Which TWO approaches are valid for importing data from an external database into ServiceNow on a recurring basis? (Choose two.)

Accepted Answer

Set up a MID Server to run a scheduled transform map from an external SQL query.. Option A is correct because a MID Server can execute a scheduled JDBC/SQL query against an external database and feed the results into a transform map, which is a standard pattern for recurring imports from systems that are not directly reachable from the instance. Option E is correct because configuring a JDBC data source (via a MID Server) and attaching it to a scheduled import set is the canonical ServiceNow mechanism for pulling external database records on a recurring schedule. Option B is not the intended answer here since a REST API flow is typically used for real-time or event-driven integrations rather than a scheduled bulk database import, and it is not the standard recurring-import approach. Option C is wrong because business rules execute on record operations within the instance, not on external events, and cannot by themselves import external database data. Option D is wrong because inbound email parsing of CSV attachments is an ad hoc, email-driven method, not a reliable recurring database import mechanism.

Answer

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

Answer

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

Answer

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

Question 14

Which THREE considerations are important when designing a ServiceNow REST API for external consumption? (Choose three.)

Accepted Answer

Implement rate limiting to protect the instance from overload.. Option A is correct because rate limiting is essential for externally consumed REST APIs to prevent a single consumer or a burst of traffic from exhausting instance resources and degrading performance for other users. Option B is correct because embedding a version in the API path (e.g., /api/now/v1/table) allows the API to evolve without breaking existing external clients, which is a core API design principle. Option E is correct because meaningful error messages in the response body (with appropriate HTTP status codes and descriptive details) help external developers diagnose and correct their requests quickly. Option C is not correct because GlideAggregate is a server-side scripting optimization for aggregate queries and is not a design consideration specific to external REST API consumption. Option D is not correct because, while OAuth 2.0 is a strong authentication choice, it is not mandatory for all external APIs; basic authentication, mutual TLS, and other methods may be appropriate depending on the use case.

Answer

Use GlideAggregate for performance in the API script.

Answer

Always use OAuth 2.0 for authentication.

Question 15

A ServiceNow instance integrates with an external inventory system via a scheduled REST import job. Recently, the import started failing intermittently with HTTP 429 (Too Many Requests) errors. The external system enforces a rate limit of 100 requests per minute. The existing job pulls 1500 records at a time using a single REST message. Which design change would best resolve this issue while ensuring the import completes successfully?

Accepted Answer

Reduce the batch size to 50 records and add a 1-second delay between consecutive REST calls. Reducing the batch size to 50 records ensures that each REST call stays within the external system's rate limit of 100 requests per minute. Adding a 1-second delay between consecutive calls further prevents bursts that could trigger HTTP 429 errors, while still allowing the import to complete by making multiple smaller requests over time.

Answer

Increase the number of threads in the import set table loader to process records faster

Answer

Increase the batch size to 5000 records per request to reduce the number of calls

Answer

Switch the REST message to use Basic Authentication instead of OAuth to reduce overhead

Question 16

A developer needs to create a flow in Flow Designer that sends an email to a manager when a high-priority incident is created. The flow should retrieve the manager's email from the caller's user record. Which data pill should be used to access the caller's manager's email in the 'Send Email' action?

Accepted Answer

{{trigger.caller.manager.email}}. In Flow Designer, the dot-walking syntax `trigger.caller.manager.email` navigates from the incident record's caller field to the user record, then to the manager reference field (which is a sys_user record), and finally retrieves the email attribute of that manager's user record. This directly accesses the caller's manager's email address without needing an intermediate lookup.

Answer

Answer

Answer

Question 17

A ServiceNow instance needs to expose a REST API endpoint for external applications to query incident data. The developer creates a Scripted REST API and needs to ensure that only authorized applications can access it. Which THREE methods can be used to secure the Scripted REST API?

Accepted Answer

Require the request to include a valid ServiceNow username and password (Basic Authentication). Option A is correct because ServiceNow Scripted REST APIs can be secured by requiring HTTP Basic Authentication, where the external application supplies a valid ServiceNow username and password that the instance validates against its user records. Option C is correct because ServiceNow supports OAuth 2.0 for REST API authentication, requiring the caller to present a valid access token in the Authorization header (Bearer token) that the instance validates before granting access. Option D is correct because ServiceNow provides an API Keys application (com.glide.token_based_auth or the API Key module) that allows administrators to generate API keys and validate them from the incoming request header, restricting access to authorized applications. Option B is incorrect because SAML 2.0 assertions are used for federated SSO browser-based authentication, not for securing inbound REST API calls to a Scripted REST API. Option E is incorrect because LDAP is a directory service protocol for user authentication and lookup, not an IP-address-based access control mechanism for REST endpoints.

Answer

Require a valid SAML 2.0 assertion in the request body

Answer

Require that the request originates from an IP address within a specified LDAP directory

Question 18

An organization has a ServiceNow instance that integrates with an external HR system using a scheduled job that runs every hour. The job uses a REST message to fetch new hire records and creates user accounts in ServiceNow via a transform map. Recently, the number of new hires has increased significantly, and the job now takes over an hour to complete, causing the next job to start before the previous one finishes. The administrator notices that the transform map is using 'Coalesce' set to 'false' because the external system does not provide a unique identifier. The job also creates a large number of intermediate records that are later updated. The administrator wants to optimize the process to prevent overlapping job runs. Which course of action should the administrator take?

Accepted Answer

Set the 'Maximum rows to load' property on the transform map to a value that ensures the job finishes within 60 minutes. Setting the 'Maximum rows to load' property on the transform map limits the number of rows processed per run, ensuring the job completes within the 60-minute window. This prevents overlapping runs by capping the workload, allowing the scheduled job to finish before the next trigger, without requiring changes to the integration logic or external system.

Answer

Increase the scheduled job's interval to run every 2 hours to avoid overlap

Answer

Change the transform map to run asynchronously using a flow triggered by the import set row

Answer

Configure the import set table loader to run in multiple parallel threads to process records faster

Question 19

A ServiceNow administrator is configuring Single Sign-On (SSO) using SAML 2.0 with a corporate identity provider. Users report that after authenticating, they are redirected back to ServiceNow but see an error: 'Unable to process SAML response. Invalid user.' The administrator checks the SSO log and sees the message: 'No user found with username: [user@company.com]'. The username format in the SAML assertion is userPrincipalName (e.g., user@company.com). ServiceNow user records use the 'User ID' field (e.g., 'user'). What configuration change should the administrator make to resolve this issue?

Accepted Answer

Set the 'User Field' property to 'User ID' in the SAML2 configuration to match users based on their User ID. The SAML assertion contains the userPrincipalName (user@company.com), but ServiceNow's default user matching field is the 'User ID' field, which stores only the username (e.g., 'user'). By setting the 'User Field' property to 'User ID' in the SAML2 configuration, ServiceNow will extract the username portion from the NameID (or a custom attribute) and match it against the 'User ID' field, resolving the mismatch. This avoids the need to change user records or the NameID format.

Answer

Change the 'NameID format' from 'Unspecified' to 'EmailAddress' in the SAML2 configuration

Answer

Create an LDAP integration to automatically create ServiceNow users from the identity provider

Answer

Update all ServiceNow user records to have the 'User ID' field populated as full email addresses

Question 20

An organization has a ServiceNow instance that integrates with a third-party monitoring tool using a webhook. The monitoring tool sends HTTP POST requests to a Scripted REST API in ServiceNow to create incidents automatically. Recently, the monitoring tool started sending duplicate requests due to a retry mechanism. The developer wants to ensure that duplicate incidents are not created. The Scripted REST API currently creates a new incident record for every request without checking for duplicates. The request payload includes a unique 'alert_id' field. The developer decides to implement idempotency logic. Which approach should the developer use to prevent duplicate incident creation?

Accepted Answer

In the Scripted REST API, use a GlideRecord to query the incident table with a condition on the 'alert_id' field before inserting a new record; if a record exists, skip creation and return the existing record's sys_id. It implements idempotency directly within the Scripted REST API by querying the incident table using GlideRecord with a condition on the unique 'alert_id' field before inserting. If a record with that 'alert_id' already exists, the API skips creation and returns the existing sys_id, ensuring no duplicate incidents are created despite duplicate webhook requests.

Answer

Create a GlideAggregate script that counts incidents with the same 'alert_id'; proceed only if count is zero

Answer

Add a before-insert business rule on the incident table that checks for duplicates using the 'alert_id' field

Answer

Use a flow in Flow Designer triggered by the REST API that creates an incident only if the 'alert_id' is not already present in a custom table