Practice Free Plat-Arch-204 Exam Online Questions
Question #41
A new Salesforce program requires data updates between internal systems and Salesforce.
Which relevant details should a Salesforce integration architect seek to solve for the integration architecture needs of the program?
- A . Core functional and non-functional requirements for User Experience design, Encryption needs, Community, and license choices
- B . Source and Target system, Directionality, and data volume & transformation complexity, along with any middleware that can be leveraged
- C . Integration skills, SME availability, and Program Governance details
Correct Answer: B
B
Explanation:
To design a robust and scalable integration architecture, a Salesforce architect must first define the
technical scope and "plumbing" of the data flow.
The most critical details for solving integration architecture needs include:
Source and Target Systems: Identifying which systems are involved determines the available APIs (REST, SOAP, etc.) and the necessary security protocols.
Directionality: Knowing whether the integration is unidirectional (Salesforce to System X) or bidirectional is vital for managing record mastering and avoiding "infinite loops" in data synchronization.
Data Volume & Transformation Complexity: High volumes may require asynchronous batch processing via the Bulk API, while complex transformations (e.g., mapping custom external IDs to Salesforce Account Numbers) may necessitate a middleware layer like MuleSoft to act as the "central nervous system".
Option A focuses on UI/UX and licensing, which are general program concerns rather than architectural integration requirements.
Option C deals with project management and governance, which are important for execution but do not inform the choice between a Request-Reply or Fire-and-Forget pattern. By focusing on systems, data direction, and transformation complexity, the architect can select the correct pattern and tools that satisfy business requirements while staying within platform limits.
B
Explanation:
To design a robust and scalable integration architecture, a Salesforce architect must first define the
technical scope and "plumbing" of the data flow.
The most critical details for solving integration architecture needs include:
Source and Target Systems: Identifying which systems are involved determines the available APIs (REST, SOAP, etc.) and the necessary security protocols.
Directionality: Knowing whether the integration is unidirectional (Salesforce to System X) or bidirectional is vital for managing record mastering and avoiding "infinite loops" in data synchronization.
Data Volume & Transformation Complexity: High volumes may require asynchronous batch processing via the Bulk API, while complex transformations (e.g., mapping custom external IDs to Salesforce Account Numbers) may necessitate a middleware layer like MuleSoft to act as the "central nervous system".
Option A focuses on UI/UX and licensing, which are general program concerns rather than architectural integration requirements.
Option C deals with project management and governance, which are important for execution but do not inform the choice between a Request-Reply or Fire-and-Forget pattern. By focusing on systems, data direction, and transformation complexity, the architect can select the correct pattern and tools that satisfy business requirements while staying within platform limits.