The Salesforce architect exams are some of the most rewarding and interesting exams to get. I really enjoy them because they offer a rare chance to dive very deep into a specific area of the platform. These can expand your capabilities within Salesforce, and provide you valuable understanding as you progress your career towards Technical Architect. This is the study guide for the Integration Architecture Designer certification exam.
Each of these exams has a study guide (like all other certifications), as well as a resource guide which has linked articles, Trailhead modules, documentation and more. To get the most out of those guides, I have written down some important areas to study and understand. If you understand the concepts below, you’ll do well on your exam.
Integration Architecture Designer
The Salesforce Integration Architecture Designer exam focuses on your understanding of the architectural decisions necessary to facilitate integrations with external systems, options available for integration, and key considerations for developing integrations. This was one of my favorite exams because I was able to learn a lot of new concepts, all of which I have found very applicable. Understanding those items has made me a better consultant.
Integration Architecture Patterns
What patterns are available, and why would you recommend one over another? This PDF references the five main patterns we see in Salesforce, as well as the benefits and considerations to each. In the exam, you will be presented with sample scenarios, and you will be asked to recommend a pattern based on the requirements.
Salesforce provides several APIs, you will need to know which one to recommend given a situation. Also, you need to understand the limitations and considerations around them (record limits, call limits, timeouts, etc.). There are learning modules on each type:
Mashups and Composite Apps
When a full integration is not recommended, you may want a mashup or composite app. Understand the limitations of this option, and when you would recommend it to an organization.
There are two types of WSDL available. Learn which is preferred given a situation.
When two Salesforce orgs will be sharing data, you may recommend Salesforce-to-Salesforce. Make sure you understand what is required to use this, and key considerations behind the recommendation.
Understanding the concepts is important, but this certification is difficult to get without some good study combined with hands-on experience. The Trailhead superbadge around integration is a great place to start.
Universal Containers uses Sales Cloud for their sales process. Closed Won Opportunities must be sent to an external ERP system for order fulfillment. All the line items must also be sent along with Opportunities. The ERP system supports only SOAP-based messages for receiving orders. What limitation of outbound messages might present a problem in this scenario?
A. Outbound messaging does not support multiple objects.
B. Outbound messaging does not support SOAP.
C. Outbound messaging cannot be made secure.
D. Outbound messaging does not offer any reliability.
Why? One of the key considerations for outbound messaging is the limitation around multiple objects. The opportunity could be sent, but not line items.
What are the two considerations of Apex REST services that an integration architect should keep in mind when building custom integrations? Choose 2 answers.
A. They cannot utilize publisher actions.
B. They require unit and functional testing.
C. They cannot be built or maintained declaratively.
D. They consume more API limits than SOAP API.
Why? A key consideration for Apex is the additional testing required, as well as the long term maintenance as it requires code, not declarative. They don’t consume more API calls, and they can utilize publisher actions.
What are two benefits of utilizing Canvas that an integration architect should consider when exposing external systems from within Salesforce? Choose 2 answers.
A. Canvas can provide authentication information via the signed request.
B. The canvas SDK can be used to make an external systems UI look like Salesforce.
C. Canvas can send data to an external system asynchronously.
D. Canvas endpoint URLs can be dynamically changed via a Lifecycle Handler.
Why? Canvas doesn’t change the external system UI, but it does provide a signed request for authentication. The nature of Canvas is asynchronous.