Salesforce Certified Data Architecture Practice Test

When modeling invoices in Salesforce for integration with an ERP system, what should the data architect recommend?

1. Use Streaming API to get the current status from the ERP and display on the Opportunity page.

2. Create an external object Invoice_x with a Lookup relationship with Opportunity.

3. Create a custom object Invoice_c with a master-detail relationship with Opportunity.

4. Create a custom object Invoice_c with a lookup relationship with Opportunity.

The correct answer is: Create an external object Invoice_x with a Lookup relationship with Opportunity.

The recommendation to create an external object, Invoice_x, with a Lookup relationship with Opportunity aligns well with the purpose of integrating Salesforce with an ERP system. By using external objects, a data architect can model the invoices as references to the existing data managed within the ERP, rather than duplicating that data within Salesforce. This approach allows for real-time access to the invoice information stored in the ERP system without the need for heavy data replication, ensuring that users always have the most current data displayed on the Opportunity page. Furthermore, the Lookup relationship supports the flexibility needed in integration scenarios. With a Lookup, the connection to the Opportunity can be maintained without enforcing strict ownership rules associated with a master-detail relationship. This can be particularly advantageous if the ERP system manages invoices independently and those invoices need to be linked to multiple opportunities over time or if a more loosely coupled relationship between the objects is desired. This approach leverages Salesforce's capabilities to integrate and present external data, making it more efficient for users who need to view invoice statuses in conjunction with their opportunities without dealing with the complexities associated with data duplication and synchronization that would arise from creating a custom object for invoices.