Integration & REST APIs Questions
Build integrations using REST APIs, web services, and data import tools. Master inbound and outbound REST, Import Sets, and Transform Maps.
Newest question added: AI-assisted drafts, not yet individually reviewedHow questions are made
About Integration & REST APIs
ServiceNow provides comprehensive integration capabilities through REST APIs, SOAP web services, Import Sets, and Integration Hub. Developers can create Scripted REST APIs for inbound integrations, use RESTMessageV2 for outbound calls, and leverage Import Sets with Transform Maps for bulk data loading.
Why This Matters for Your Exam
Questions cover building REST integrations, creating Scripted REST APIs, configuring Import Sets and Transform Maps, and understanding authentication methods for web services.
Key Concepts to Master
Understand the difference between inbound and outbound integrations. Know how to create Scripted REST APIs with custom endpoints. Master RESTMessageV2 for outbound REST calls. Learn Import Sets and Transform Maps for data loading workflows.
Exam Tips
Know the difference between Table API (standard) and Scripted REST API (custom). Understand REST authentication methods (Basic, OAuth, mutual TLS). Remember that Import Sets create staging tables and Transform Maps define the mapping to target tables. Be familiar with coalesce fields for update-or-insert logic.
Practice Questions
21 questions availableA team is reviewing the inbound web services ServiceNow supports, including REST, SOAP, JSONv2, and RSS. What does the acronym REST stand for?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: A. REpresentational State Transfer
The ServiceNow web services documentation defines REST as REpresentational State Transfer, a simple stateless architecture that provides standards between computer systems on the web so they can communicate more easily. ServiceNow offers REST for both inbound and outbound web services.
- Why B is wrong: Remote Execution Service Transfer is not the expansion. The docs define REST as REpresentational State Transfer, a stateless web architecture.
- Why C is wrong: Resource Exchange Standard Transport is not a real expansion of REST. The documented expansion is REpresentational State Transfer.
- Why D is wrong: Reliable Endpoint Service Technology is not what REST stands for; the docs expand it as REpresentational State Transfer.
An integration developer must update the State of an existing incident through the Table API, sending only the state name-value pair in the request body. The record's sys_id is known. Which request should the integration send?
👆 Click an option above to select your answer
Show answer and explanation
Correct answer: B. PATCH /now/table/incident/{sys_id}
The Table API PATCH endpoint, /now/table/{tableName}/{sys_id}, updates the specified record with the name-value pairs included in the request body. Because the integration is changing an existing incident it already has the sys_id for, PATCH against that record is the matching call.
- Why A is wrong: GET /now/table/{tableName}/{sys_id} retrieves the record identified by the sys_id; it reads data and does not apply the new State value.
- Why C is wrong: DELETE /now/table/{tableName}/{sys_id} deletes the specified record from the table, which removes the incident rather than updating it.
- Why D is wrong: POST /now/table/{tableName} inserts one new record in the table, so it would create a new incident instead of updating the existing one.