Platform Features and Integration practice questions

JSON.parse(request.body)

Why wrong: request.body must be parsed, but JSON.parse is used; however, the correct method is request.body.dataString? Actually, the correct answer is D. This explanation is for A: It is actually correct? Wait, I need to adjust. Let me fix: The correct answer is D: request.body.dataString? No. I earlier set D as correct. Let me re-evaluate: In Scripted REST API, request.body is a string. JSON.parse(request.body) is correct. So the correct should be A. But I assigned D. I need to change the correct answer and explanations accordingly. Let me rewrite this question properly. I'll put correct as A. So adjust explanation and options.

The MID Server credentials are incorrect.

Why wrong: Incorrect credentials would lead to authentication failure, not connection refused.

The MID Server's SSL certificate is expired.

Why wrong: SSL certificate issues occur after connection is established, not at the TCP level.

The target host is unreachable from the MID Server network.

Why wrong: Unreachable would show 'No route to host' or similar.

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

Why wrong: Password complexity does not affect API authentication if credentials are correct.

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

Why wrong: 'rest_service' is the correct role; 'rest_api' does not exist.

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

Why wrong: ACL denial typically returns 403 Forbidden, not 401.

Enable the Email Integration plugin.

Why wrong: The plugin is often enabled by default or not required for basic inbound email.

Create an inbound email action.

Why wrong: Inbound email actions are created after the email account is set up.

Create an ACL to allow email processing.

Why wrong: ACLs are not the first step for email integration.

Wrap the payload in a CDATA section.

Why wrong: CDATA can be used but is not the best practice for all characters; escaping is more standard.

Encode the entire payload in Base64.

Why wrong: Base64 encoding is not necessary for special characters and adds complexity.

Use URL encoding for the payload.

Why wrong: URL encoding is for URLs, not XML content.

Email Account

Why wrong: Email accounts define the mailbox, not field mapping.

Inbound Email Script

Why wrong: 'Inbound Email Script' is not a standard component; the correct term is Inbound Email Action.

Email Notification

Why wrong: Email notifications are for outgoing emails.

Use the 'sysparm_display_value' parameter.

Why wrong: sysparm_display_value controls display value, not filtering.

Use the 'sysparm_limit' parameter to limit results.

Why wrong: sysparm_limit limits the number of records, not filters.

Use the 'sysparm_fields' parameter to specify fields.

Why wrong: sysparm_fields selects fields to return, not filters.

SAML assertion authentication.

Why wrong: SAML is for SSO, not direct REST API authentication.

LDAP authentication.

Why wrong: LDAP is for user authentication, not API calls.

API Key authentication.

Why wrong: ServiceNow does not use API keys for REST API authentication.

REST Message

Why wrong: REST Message is a legacy feature, not part of IntegrationHub.

Data Source

Why wrong: Data Source is for reporting, not IntegrationHub.

The request method should be PUT instead of POST.

Why wrong: POST is correct for creating records.

The field 'short_description' is misspelled.

Why wrong: It is correctly spelled.

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

Why wrong: ACL denial would return 403 Forbidden.

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

Why wrong: Client callable is for GlideAjax, not for Script Include REST endpoints.

The function name 'getOpenIncidents' is not exposed.

Why wrong: The function name is correct, but the Script Include type is wrong.

The GlideRecord query returns no results.

Why wrong: The query is valid; if there are active incidents, it should return results.

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

Why wrong: Increasing rate limit may worsen performance and cause instability.

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

Why wrong: The external system may not be able to reduce its rate, and 500 might still be too high.

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

Why wrong: Authentication method does not affect rate limiting.

Navigate to System Definition > Tables, then click New, then set attributes (extends, access, etc.), then define table properties (label, name, etc.), then submit.

Why wrong: This is incorrect because attributes like 'extends' depend on the table name and label being defined first. You must define properties before setting attributes.

Navigate to System Definition > Tables, then define table properties (label, name, etc.), then click New, then set attributes, then submit.

Why wrong: This is incorrect because you must first click 'New' to create a new table record before you can define its properties. The 'New' button generates a blank form to fill.

Navigate to System Definition > Tables, then click New, then define table properties, then submit, then set attributes.

Why wrong: This is incorrect because attributes must be set before submitting the record. Once submitted, the table is created and attributes cannot be easily changed later.

Navigate to Scheduled Jobs, Create new, Define schedule, Set name and type, Write script/select report, Submit

Why wrong: This is incorrect because you should set the name and type before defining the schedule, as the schedule options depend on the job type.

Navigate to Scheduled Jobs, Create new, Set name and type, Write script/select report, Define schedule, Submit

Why wrong: This is incorrect because the schedule should be defined before writing the script or selecting the report, as the script/report may need to be aligned with the schedule.

Create new, Navigate to Scheduled Jobs, Set name and type, Define schedule, Write script/select report, Submit

Why wrong: This is incorrect because you must first navigate to the Scheduled Jobs module before creating a new job; otherwise, you cannot access the creation form.

Virtual Agent: Service Portal

Why wrong: Incorrect — Virtual Agent is associated with AI Search, not Service Portal. Service Portal is for user interface delivery.

Performance Analytics: Knowledge Management

Why wrong: Incorrect — Performance Analytics is about data analysis and dashboards, not knowledge management.

PATCH: Create a new record

Why wrong: Incorrect — PATCH is used for partial updates, not creation.

HEAD: Update an existing record

Why wrong: Incorrect — HEAD is used to retrieve headers, not update data.

The client secret is not base64 encoded.

Why wrong: Base64 encoding is not required for client credentials; it is for basic auth.

The token URL is missing the grant_type parameter.

Why wrong: grant_type is sent in the POST body, not as a URL parameter.

The REST message is set to POST instead of GET.

Why wrong: POST is the correct HTTP method for OAuth token requests.

Set the source field as coalesce on the transform map.

Why wrong: Coalesce is set on the target field, not source field.

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

Why wrong: This would skip the row without matching, not correct for reference resolution.

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

Why wrong: Using an 'on before' transform script to find the user record fails because Import Sets require a dedicated **coalescence field** or **exact match condition** defined on the table map to automatically link incoming data to existing records; a script alone cannot establish the persistent matching rule that the import engine uses for deduplication. This approach is tempting because 'on before' scripts are commonly employed to populate or transform field values before the record is written, and they would be correct if the goal were to derive a user's sys_id from a lookup table rather than to define the matching criterion itself.

Use a REST API exposed by the external database.

Why wrong: Many databases do not expose a REST API; requires custom development.

Use a SOAP web service with a MID Server.

Why wrong: SOAP would require a web service interface on the database side, which is uncommon.

Use an email-based integration to send CSV files.

Why wrong: Email is not reliable for scheduled large data sync.

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

Why wrong: The table API uses sysparm_query, not direct URL parameters.

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

Why wrong: The sysparm_ prefix is used for table API, not for custom scripted REST APIs.

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

Why wrong: gr.get() is for retrieving a single record by sys_id, not for queries.