DATA-ARCHITECT practice question 29 of 35

UC has one SF org (Org A) and recently acquired a secondary company with its own Salesforce org (Org B). UC has decided to keep the orgs running separately but would like to bidirectionally share opportunities between the orgs in near-real time. Which 3 options should a data architect recommend to share data between Org A and Org B? Choose 3 answers.

Full set: 257 questions
Answer options
A: Leverage Heroku Connect and Heroku Postgres to bidirectionally sync Opportunities. Correct answer
B: Install a 3rd party AppExchange tool to handle the data sharing
C: Develop an Apex class that pushes opportunity data between orgs daily via the Apex schedule.
D: Leverage middleware tools to bidirectionally send Opportunity data across orgs. Correct answer
E: Use Salesforce Connect and the cross-org adapter to visualize Opportunities into external objects Correct answer
Correct Answer:
A. Leverage Heroku Connect and Heroku Postgres to bidirectionally sync Opportunities.; D. Leverage middleware tools to bidirectionally send Opportunity data across orgs.; E. Use Salesforce Connect and the cross-org adapter to visualize Opportunities into external objects
Explanation

To achieve near-real-time, bidirectional data sharing between two Salesforce orgs, several architectural patterns are suitable. Heroku Connect (A) provides a robust, bidirectional synchronization between Salesforce and a Heroku Postgres database. By connecting both orgs to the same database, it can act as a central hub for data replication. Middleware tools (D) like MuleSoft or Dell Boomi are purpose-built for complex, near-real-time integrations, handling data transformation, orchestration, and error management between systems. Salesforce Connect (E) with the cross-org adapter allows for data virtualization. It lets users in one org view and interact with data in the other org in real-time without physically replicating it, which satisfies the bidirectional sharing requirement.

Why Incorrect

B. While a valid approach, it is a subset of option D (Middleware). Options A, D, and E represent more distinct architectural patterns.
C. A daily Apex schedule is a batch process, which does not meet the "near-real time" requirement and is a less robust integration method.

References

1. Salesforce Developer Documentation. Heroku Connect. "Heroku Connect provides both data replication and data proxying to support a variety of development patterns... synchronization between a Salesforce deployment and a Heroku Postgres database."

2. Salesforce Architects. (2022). Architect's Guide to Data Integration. Salesforce. Page 7, "Integration Patterns," describes the "Remote Process Invocation—Request and Reply" and "Data Synchronization" patterns, which are typically implemented with middleware (D).

3. Salesforce Help. (2023). Salesforce Connect Cross-Org Adapter. "The cross-org adapter for Salesforce Connect lets you see, search, and modify data that’s stored in another Salesforce org... You can also have read/write access to external objects."

Scroll to Top