INTEGRATION-ARCHITECTURE-DESIGNER practice question 10 of 25

Northern Trail Outfitters needs to make synchronous callouts "available to promise" services to query product availability and reserve inventory during customer checkout process. Which two considerations should an integration architect make when building a scalable integration solution? Choose 2 answers

Full set: 106 questions

Domain Design an Integration Solution

Answer options
A: The typical and worst-case historical response times. Correct answer
B: The number batch jobs that can run concurrently.
C: How many concurrent service calls are being placed. Correct answer
D: The maximum query cursors open per user on the service.
Correct Answer:
A. The typical and worst-case historical response times.; C. How many concurrent service calls are being placed.
Explanation

For a scalable, synchronous integration during a critical user process like checkout, the two most important factors are performance and the ability to handle load.
1. Response Times (A): The "available to promise" service's response time directly impacts the user experience and the technical viability of the solution. A slow response leads to a long wait for the customer, potentially causing cart abandonment. Furthermore, synchronous Apex callouts have a hard timeout limit (e.g., 120 seconds). Understanding the typical and worst-case response times is crucial to prevent hitting this limit and to ensure the system performs well under load.
2. Concurrency (C): Scalability requires the system to handle numerous simultaneous requests, especially during peak shopping times. The architect must consider how many concurrent calls the remote service can handle and how many Salesforce will generate. This impacts Salesforce limits (e.g., concurrent long-running requests) and the remote system's capacity, preventing service failures during high traffic.

Why Incorrect

B. The number batch jobs that can run concurrently. Batch jobs are asynchronous and used for bulk data processing, which is irrelevant to a real-time, synchronous callout initiated by a single user's checkout action.
D. The maximum query cursors open per user on the service. This is a specific, internal implementation detail of the remote service's database. It is not a primary integration design consideration for a simple, transactional request-reply callout from Salesforce.

References

1. Salesforce Architects Documentation

Integration Patterns and Practices: The "Remote Process Invocation—Request and Reply" pattern is the relevant pattern for this scenario. The documentation emphasizes that key considerations for this pattern include "Performance and scale of the remote system" and "Callout timeouts." This directly supports evaluating response times (A) and concurrency (C). (See section: Remote Process Invocation—Request and Reply

Considerations).

2. Salesforce Developer Documentation

Apex Governor Limits: The "Execution Governors and Limits" page details several limits critical to this scenario. The "Maximum cumulative timeout for all callouts (HTTP requests or Web services calls) in a transaction" and the "Concurrent Apex" limits (e.g.

"Total number of synchronous concurrent requests for long-running API requests") directly tie the success of a scalable solution to managing response times (A) and concurrency (C).

3. Patterson

D. A.

& Hennessy

J. L. (2017). Computer Organization and Design RISC-V Edition: The Hardware Software Interface. Morgan Kaufmann. In Chapter 1

"Computer Abstractions and Technology

" performance and scalability are discussed. A key measure of performance is response time. Scalability is defined by a system's ability to handle a growing amount of work

which directly relates to handling concurrent requests. This foundational computer science principle validates considering response time (A) and concurrency (C) as primary architectural concerns.

Scroll to Top