Diagnosing landscape pain points and platform constraints
Reading an existing landscape for the constraint behind a symptom: API usage against the 70% headroom ceiling, which org pays for cross-org Salesforce Connect callouts, OData join and throttling limits, the daily async Apex limit, synchronous coupling, org-bound platform events, browser-side Omniscript callouts and source systems that only export nightly files.
Given an existing system landscape, analyze for constraints and/or pain-points to satisfy a business requirement(s).
~8 min read · 8 practice questions ·
What the exam expects
- Compare normal-day API usage with the org's allocation and the Well-Architected 70% ceiling, and recommend batching and monitoring when headroom is too thin.
- Explain which org's allocation Salesforce Connect callouts consume, and which Connect limits (joins, external throttling) explain a symptom.
- Diagnose the daily asynchronous Apex execution limit and fix one-job-per-record designs by bulkifying.
- Recognize synchronous coupling to an unreliable system as the pain point, and decouple through durable middleware.
- Spot designs that assume platform events cross orgs, run Omniscript callouts in the browser, or expect real-time access to a nightly-file source.
Key terms: allocation (the org's total inbound API calls per 24 hours), headroom (capacity kept free below a limit for spikes), provider org (the org whose data the cross-org adapter reads), tight coupling (one system can't work when the other is down), Integration Procedure (server-side OmniStudio data processing).
Key facts
- Detail
- Target 70% of limits under normal load; 70-85% is warning, above 85% red
- Detail
- Whole org per 24 hours; a Full sandbox not created from a template has its own 5,000,000
- Detail
- Each callout counts toward the provider org's API usage
- Detail
- Maximum 4 per query across external and other objects
- Detail
- No Salesforce callout limit; external system may limit traffic
- Detail
- 100,000 new external record IDs per hour, each for long-term and short-term mapping (OData 2.0 and 4.0)
- Detail
- 250,000 or licenses × 200, whichever is greater; shared by all async types
- Detail
- Can't listen between orgs
- Detail
- Not available for external-to-Salesforce
Sources for this section (6)
- Well-Architected: Reliabilityarchitect.salesforce.com (opens in a new tab)
- API Request Limits and Allocationsdeveloper.salesforce.com (opens in a new tab)
- General Limits for Salesforce Connecthelp.salesforce.com (opens in a new tab)
- General Limits for Salesforce Connect OData Adaptershelp.salesforce.com (opens in a new tab)
- Execution Governors and Limitsdeveloper.salesforce.com (opens in a new tab)
- Data Integration with Salesforcearchitect.salesforce.com (opens in a new tab)
- Why does a 320,000-call day on a 400,000 allocation need redesign?
- When does a Salesforce Connect callout consume API allocation?
- What is the daily async Apex limit for an org with 2,000 licenses?
- Why can't a service-org trigger receive a sales-org platform event?
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 (8 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams