Discuss Salesforce Plat-Arch-201 Exam Topic 3 Question 5

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.)

AStandard list view in-line editing.

BLimitations on Org data storage.

CBulk API limitations on picklist fields.

DLimitations on master-detail relationships.

Suggested Answer: B, C

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.

Get Premium Plat-Arch-201 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

24 comments · newest first

Tommy 2 days ago

True, but D matters too. Master-detail limits can complicate things.

Gwenn 8 days ago

C is also important. Bulk API has restrictions on picklists.

Herminia 13 days ago

Agreed! B is a must. We can't run out of space.

Shannan 18 days ago

I think B is crucial. Data storage limits can impact performance.

Gilbert 23 days ago

Right, A seems minor. Focus on B and C for sure!

Tayna 28 days ago

I feel like A is less relevant here. In-line editing isn’t a priority.

Madalyn 1 month ago

D is important as well. Master-detail limits can complicate things.

Moon 1 month ago

I lean towards C too. Bulk API can be tricky with picklists.

Anisha 1 month ago

Agreed! B is a must. Can't ignore storage issues.

Danica 2 months ago

I think B is crucial. Data storage limits can really impact performance.

Felix 2 months ago

B is a must, can't overlook storage limits with so many transactions!

Sabra 2 months ago

I disagree, D isn’t really a big deal here.

Hayley 2 months ago

Wait, can picklist fields really affect Bulk API? That’s surprising!

Lilli 2 months ago

I think A is also important for user experience.

Melissia 2 months ago

Definitely B and C, those are crucial!

Marion 3 months ago

D could be an issue too, but not as pressing as the others.

Glory 3 months ago

I agree with B, data storage is always a concern.

Lorriane 3 months ago

Wait, are we really worried about picklist limits? Seems odd.

Lindsay 3 months ago

I think A is also important for user experience.

Vilma 3 months ago

Definitely B and C, those are crucial!

Nu 4 months ago

I feel like in-line editing could be relevant too, but I'm not sure if it's as critical as the storage limitations. It’s tough to decide!

Jess 4 months ago

This reminds me of a practice question we did on master-detail relationships. I wonder if those limitations could impact how we structure the data model.

Yolando 4 months ago

I'm a bit unsure about the implications of picklist fields with the Bulk API. I think it could affect performance, but I need to double-check that.

Terrilyn 5 months ago

I remember we discussed the importance of data storage limits in class, especially with so many transactions. That might be a key consideration here.

Salesforce Plat-Arch-201 Exam - Topic 3 Question 5 Discussion