What are two important considerations for the Data Architect in this scenario?

DreamHouse Realty has a legacy system that captures Branch Offices and Transactions.

DreamHouse Realty has 15 Branch Offices. Transactions can relate to any Branch Office.

DreamHouse Realty has created hundreds of thousands of Transactions per year.

A Data Architect needs to denormalize this data model into a single Transaction object with a Branch Office picklist.

What are two important considerations for the Data Architect in this scenario? (Choose two.)
A . Standard list view in-line editing.
B . Limitations on Org data storage.
C . Bulk API limitations on picklist fields.
D . Limitations on master-detail relationships.

Answer: B,C

Author