Exam Integration-Architect Topic 1 Question 102 Discussion
Actual exam question for Salesforce's Integration-Architect exam
Question #: 102
Topic #: 1
Question #: 102
Topic #: 1
Northern Trail Outfitters (NTO) uses different shipping services for each of the 34 countries it serves.
Services are added and removed frequently. Sales representatives globally need to select between valid service (s) for the customer's country and request shipping estimates. Which solution should an architect propose?
Services are added and removed frequently. Sales representatives globally need to select between valid service (s) for the customer's country and request shipping estimates. Which solution should an architect propose?
Suggested Answer: B Vote an answer
When external services are highly volatile (added/removed frequently), the goal is to decouple the Salesforce UI from the underlying service logic. An Integration Architect should propose invoking a middleware service to retrieve the valid shipping methods.
By using middleware (such as an ESB or MuleSoft) as an abstraction layer, Salesforce doesn't need to "know" the details of the 34 different shipping providers. When a sales rep selects a country, Salesforce makes a single callout to the middleware. The middleware then performs the routing logic to identify which shippers are active for that region and returns a standardized list to Salesforce.
Option A is a "maintenance nightmare"; every time a shipping service changes in any of the 34 countries, an admin would need to manually update picklist values and dependencies in Salesforce, which is not scalable.
Option C (Platfor31m Events) is an asynchronous pattern unsuitable for a real-time "request-reply" scenario where a rep is waiting for an estimate during a live customer interaction. Utilizing middleware centralizes the logic, simplifies Salesforce configuration, and allows NTO to change shipping providers without any code deployments or metadata updates in the Salesforce org.
By using middleware (such as an ESB or MuleSoft) as an abstraction layer, Salesforce doesn't need to "know" the details of the 34 different shipping providers. When a sales rep selects a country, Salesforce makes a single callout to the middleware. The middleware then performs the routing logic to identify which shippers are active for that region and returns a standardized list to Salesforce.
Option A is a "maintenance nightmare"; every time a shipping service changes in any of the 34 countries, an admin would need to manually update picklist values and dependencies in Salesforce, which is not scalable.
Option C (Platfor31m Events) is an asynchronous pattern unsuitable for a real-time "request-reply" scenario where a rep is waiting for an estimate during a live customer interaction. Utilizing middleware centralizes the logic, simplifies Salesforce configuration, and allows NTO to change shipping providers without any code deployments or metadata updates in the Salesforce org.
by Buck at Aug 15, 2026, 02:32 AM
0
0
0
10
Comments
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Report Comment
Commenting
You can sign-up / login (it's free).