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.)
The Data Architect should consider the limitations on Org data storage and the Bulk API limitations on picklist fields when denormalizing the data model into a single Transaction object with a Branch Office picklist.The Org data storage limit is the total amount of data that can be stored in a Salesforce Org, and it depends on the edition and license type of the Org1.The Bulk API limit on picklist fields is the maximum number of values that can be imported or exported using the Bulk API, and it is 1,000 values per picklist field2. These limitations could affect the performance and scalability of the data model, and the Data Architect should plan accordingly.
Currently there are no comments in this discussion, be the first to comment!