Solution components: Salesforce Connect, Flow and middleware
Which building blocks make up an integration once the pattern is chosen: Salesforce Connect adapters and external object relationships, External Services, flow invocable actions and Flow Orchestration, platform event and Change Data Capture payload design, WSDL proxy classes, ETL design elements, Heroku Connect, and the middleware capabilities each pattern needs.
Given a use case, define the components which create a solution that meets business requirements.
~8 min read · 17 practice questions ·
What the exam expects
- Assemble a Data Virtualization solution: the right Salesforce Connect adapter, the right external object relationship, and the High Data Volume option when rate limits bite.
- Build declarative outbound and inbound components: External Services from an OpenAPI spec, the invocable actions REST endpoint for an autolaunched flow, and Flow Orchestration for long-running multi-step work.
- Design event payloads: custom platform events vs Change Data Capture, enrichment and custom channels, record IDs for callbacks, loop prevention and the 1 MB limit.
- Pick the component for special endpoints: WSDL proxy classes for SOAP-only systems, Heroku Connect for Heroku Postgres, ETL with control tables for batch.
- Name the middleware capabilities a pattern makes mandatory.
Key terms: external object (maps to a table outside the org and is fetched in real time); indirect lookup (links an external child to a standard or custom parent through a unique External ID field); External Services (turns an OpenAPI spec into invocable actions); enriched field (added to change events even when unchanged); control table (ETL table that stores last run time and restart values).
Key facts
- Detail
- Extra cost in Enterprise, Performance, Unlimited; included in Developer Edition
- Detail
- Apex Connector Framework, for any HTTP/REST API when other adapters don't fit
- Detail
- External child; parent matched on a custom External ID + Unique field
- Detail
- High Data Volume bypasses most rate limits
- Detail
- OpenAPI 2.0 or 3.0 schema
- Detail
/actions/custom/flow/<name>; returns interview status and output variables
- Detail
- 1 MB maximum
- Detail
- Included in update and delete change events even when unchanged
- Detail
- Created with Metadata API or Tooling API, not in Setup
- Detail
- Syncs Heroku Postgres and Salesforce, bidirectional available
Sources for this section (7)
- Salesforce Connecthelp.salesforce.com (opens in a new tab)
- Integration Patterns Overviewarchitect.salesforce.com (opens in a new tab)
- External Serviceshelp.salesforce.com (opens in a new tab)
- Flow Actionsdeveloper.salesforce.com (opens in a new tab)
- PlatformEventChannelMemberdeveloper.salesforce.com (opens in a new tab)
- Custom Channelsdeveloper.salesforce.com (opens in a new tab)
- Data Integration with Salesforcearchitect.salesforce.com (opens in a new tab)
- Why does an indirect lookup, not a standard lookup, link ERP orders to Account?
- When does a remote system call the custom invocable actions endpoint for a flow?
- Why include the Salesforce record ID in a Fire and Forget event when the remote system masters the key?
- Which two middleware capabilities does Fire and Forget make mandatory for a Pub/Sub API subscriber that feeds an unreliable ERP?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 25 lessons of the Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (17 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams