Exam Integration-Architect Topic 4 Question 68 Discussion

To translate abstract business needs into a functional Integration Architecture, an architect must move beyond "what" the business wants to "how" the data will technically flow. The details in Option B represent the fundamental building blocks of any integration design.
* Source and Target Systems: Determining which systems are involved dictates the available APIs (REST, SOAP, Bulk) and required security protocols (OAuth, Mutual SSL).
* Directionality: Knowing if the update is unidirectional or bidirectional is critical for record mastering, identifying the "System of Record," and preventing infinite data loops.
* Data Volume: This is a primary driver for selecting the Integration Pattern. High volumes (millions of records) require the Bulk API, while low-volume, real-time updates are better suited for Streaming or REST APIs.
* Transformation Complexity: If data must be heavily massaged or merged from multiple sources, it justifies the need for Middleware (ESB/iPaaS).
Option A focuses on user interface and licensing, which are implementation details rather than architectural integration requirements. Option C deals with project management and resource allocation. While these are important for the project's success, they do not help the architect decide between a Request-Reply or Fire- and-Forget pattern. By focusing on systems, data direction, and volume, the architect ensures that the proposed solution is technically viable, scalable, and adheres to Salesforce platform governor limits.