Integration23% of the exam
Integration patterns for volume, latency and failure
How to pick request-reply, fire-and-forget, batch, event or virtualization patterns from a requirement's timing and volume, and how B2C Commerce services, outbound messages, change events, Composite requests, Engagement triggers, Data 360 and Omnichannel Inventory imports behave under load and failure.
Given business requirements and use cases, recommend appropriate integration patterns based on data volume, latency, and system limitations.
~8 min read · 17 practice questions
What the exam expects
- Choose request-reply, fire-and-forget, batch, remote call-in or data virtualization from who waits, how fresh the data must be and how much there is.
- Protect a B2C Commerce storefront from slow or rate-limited partners with service profile settings.
- Design receivers for outbound messages and change events that survive retries, gaps and partial payloads.
- Cut API calls and partial writes with Composite, and keep external data external with Salesforce Connect.
- Account for timing limits in Engagement triggers, Data 360 publishing and Omnichannel Inventory imports.
Key terms:
- Request and Reply: Salesforce calls a remote process and waits for it to finish before acting on the response.
- Fire and Forget: the remote system acknowledges the request and Salesforce carries on without waiting for completion.
- Service profile: the B2C Commerce setting that controls a web service's timeout, rate limiter and circuit breaker.
- Replay ID: the opaque position of an event in the stream, used to resubscribe after a gap.
- Omnichannel Inventory: the service that holds availability across locations and location groups.
Key facts
Rate limit or open circuit
- Detail
- ServiceUnavailableException, no call made
Outbound message retries
- Detail
- Up to 24 hours, 15 seconds growing to 60 minutes
Event retention
- Detail
- 72 hours
Unchanged fields in a Pub/Sub update event
- Detail
- Present and empty
Composite
- Detail
- One API call; up to 25 subrequests
Data 360 standard publish
- Detail
- Every 12 or 24 hours; deferred at the concurrency limit
File matching two File Drop triggers
- Detail
- One trigger chosen at random
Inventory Impex file
- Detail
- Up to 100 MB, JSON or GZIP
Inventory import mode
- Detail
- UPDATE; omitted entries kept
Sources for this section (8)
- Web Servicesdeveloper.salesforce.com (opens in a new tab)
- Fire and Forgetdeveloper.salesforce.com (opens in a new tab)
- Event Durabilitydeveloper.salesforce.com (opens in a new tab)
- Change Event Bodydeveloper.salesforce.com (opens in a new tab)
- Compositedeveloper.salesforce.com (opens in a new tab)
- Publish a Segmenthelp.salesforce.com (opens in a new tab)
- File Drophelp.salesforce.com (opens in a new tab)
- Availability Importshelp.salesforce.com (opens in a new tab)
- Which field identifies a platform event message uniquely when replay IDs might repeat after an org migration?
- Why can a published platform event sometimes never reach its subscribers?
- When must you request a new Omnichannel Inventory import before uploading a file?
- What should you define during an initial Omnichannel Inventory implementation to avoid overselling?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the B2C Solution Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 20 lessons of the B2C Solution Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (17 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both