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.
Provided an integration scenario, describe requirements and issues that the Architect must consider to select the right pattern (Layer, Timing, Direction, and Volume).
In a customer scenario containing business requirements, summarize which implementation pattern will achieve those goals.
Compare and contrast the advantages and drawbacks (design trade-offs) of using various patterns, such as Remote Process Invocation—Request and Reply, Remote Process Invocation—Fire and Forget, Batch Data Synchronization, Remote Call-In, and UI Update Based on Data Changes.
Given a customer scenario containing business requirements for integrating Salesforce with other enterprise back-office systems, recommend the appropriate integration architecture.
Analyze and determine when and where to use data cleaning, standardization, deduplication, and data transformation as part of data integration.
Analyze and determine the various considerations while performing data migration (including but not limited to: platform handle bulk data load vs. SOAP data load, monitoring the data loads, and error handling).