What is a key advantage of using the Salesforce SOAP API over REST API for integration?

SOAP API supports built-in error handling and retry logic

SOAP API provides a standardized, extensible messaging framework with built-in security standards like WS-Security

SOAP API is simpler to use and requires less configuration

SOAP API is faster and more lightweight than REST

What is a key advantage of using the Streaming API for integration?

It supports synchronous request-response communication

It is ideal for transferring large volumes of historical data

It provides real-time event notifications to subscribers without polling

It guarantees delivery of every event exactly once

Which of the following is a drawback of using @future methods for integration?

They cannot be used to make HTTP callouts

They run synchronously and block the user

They are limited to one execution per day

They do not support parameters of standard or custom objects

Which of the following is a drawback of Workflow Outbound Messages?

They are limited to one-way communication and do not support a response from the external system

They require complex Apex code to configure

They are deprecated and no longer supported

They can only be used with REST endpoints

SalesforceCertified Integration Architect

Domain 1Objective 2

Compare and Contrast the Advantages and Drawbacks (design Trade-Offs) of Using API-based Integrations Such as SOAP, REST, Bulk, Streaming, Canvas, Workflow Outbound, APEX (Callouts, @future, Etc.) and Lightning Connect. INTEGRATION-ARCHITECT Practice Questions (Page 2)

Part of the SALESFORCE INTEGRATION CAPABILITIES domain, which accounts for 28% of the INTEGRATION-ARCHITECT exam.

31questions here

7free pages

11concepts

28%of the exam

Curriculum map

SALESFORCE INTEGRATION CAPABILITIES
- In a given scenario, recommend when to use API-based integrations, such as SOAP, REST, Bulk, Streaming, Canvas, Workflow outbound, APEX (Callouts, @ future, etc.) and Lightning Connect to achieve business requirements.
- Compare and contrast the advantages and drawbacks (design trade-offs) of using API-based integrations such as SOAP, REST, Bulk, Streaming, Canvas, Workflow outbound, APEX (Callouts, @future, etc.) and Lightning Connect.
  ‹123 7 ›
SALESFORCE INTEGRATION PATTERNS
ENTERPRISE INTEGRATION ARCHITECTURE CONCEPTS
SALESFORCE INTEGRATION TESTING
INTEGRATING WITH SALESFORCE: SECURITY
2 more domains
- TOOLS
- MONITORING

11 Concepts in This Objective

API Integration Overview
SOAP API Trade-offs
REST API Trade-offs
Bulk API Trade-offs
Streaming API Trade-offs
Canvas Trade-offs
Workflow Outbound Message Trade-offs
Apex Callouts Trade-offs
@future and Async Apex Trade-offs
Lightning Connect Trade-offs
Design Trade-off Analysis

Questions 6–10

6foundation · easy
What is a key advantage of using the Salesforce SOAP API over REST API for integration?
Select an answer first
7foundation · easy
What is a key advantage of using the Streaming API for integration?
Select an answer first
8foundation · easy
An integration needs to load millions of records into Salesforce overnight. Which API-based integration is most appropriate?
Select an answer first
9foundation · easy
Which of the following is a drawback of using @future methods for integration?
Select an answer first
10foundation · easy
Which of the following is a drawback of Workflow Outbound Messages?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to INTEGRATION-ARCHITECT

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Salesforce. “INTEGRATION-ARCHITECT” is a trademark of its owner, used for identification only.