Salesforce Exam Data Architect Topic 5 Question 57 Discussion

Actual exam question for Salesforce's Data Architect exam

Question #: 57
Topic #: 5

Universal Containers (UC) is implementing Salesforce Sales Cloud and Service Cloud. As part of their implementation, they are planning to create a new custom object (Shipments), which will have a lookup relationship to Opportunities. When creating shipment records, Salesforce users need to manually input a customer reference, which is provided by customers, and will be stored in the Customer_Reference__c text custom field. Support agents will likely use this customer reference to search for Shipment records when resolving shipping issues. UC is expecting to have around 5 million shipment records created per year. What is the recommended solution to ensure that support agents using global search and reports can quickly find shipment records?

AImplement an archiving process for shipment records created after five years.

BImplement an archiving process for shipment records created after three years.

CSet Customer-Reference_c as an External ID (non-unique).

DSet Customer-Reference_c as an External ID (unique).

Show Suggested Answer

Suggested Answer: A

Using Bulk API to export 1 million records from Salesforce is the best option. Bulk API is a RESTful API that allows you to perform asynchronous operations on large sets of data. You can use Bulk API to create, update, delete, or query millions of records in batches. Bulk API is optimized for performance and scalability, and it can handle complex data loading scenarios.

by Telma at Mar 06, 2025, 03:43 PM

Limited Time Offer

25%

Off

Get Premium Data Architect Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Leana

1 months ago

Ah, the age-old dilemma: speed vs. storage. Someone call in the Infinity Stones, we're gonna need some cosmic power to solve this one!

upvoted 0 times

...

2 months ago

Hold up, what about archiving older shipment records? That could help keep the search results manageable. I'm thinking option B, 3 years, might be a good balance.

upvoted 0 times

Buffy

1 days ago

I agree, option B seems like a good balance to ensure that support agents can quickly find shipment records.

upvoted 0 times

...

Iluminada

2 days ago

Yeah, archiving older shipment records after three years could definitely improve search performance.

upvoted 0 times

...

Tegan

3 days ago

Option B sounds like a good idea. It would help keep the search results more manageable.

upvoted 0 times

...

2 months ago

Hmm, this seems like a tricky one. I'm leaning towards option D, setting Customer_Reference__c as a unique external ID. That way, support agents can quickly find shipment records by searching for that customer reference.

upvoted 0 times

Polly

23 days ago

Yes, setting Customer_Reference__c as a unique external ID will definitely improve efficiency for support agents searching for shipment records.

upvoted 0 times

...

Vallie

24 days ago

I think option D is the best choice here, it will help ensure quick and accurate retrieval of shipment records when needed.

upvoted 0 times

...

Xochitl

27 days ago

That makes sense, having a unique identifier like an external ID can streamline the search process for support agents.

upvoted 0 times

...

Chaya

1 months ago

I agree, setting Customer_Reference__c as a unique external ID would definitely make it easier for support agents to find shipment records.

upvoted 0 times

...

Caprice

3 months ago

I think setting Customer-Reference__c as an External ID (unique) would be the best solution.

upvoted 0 times

...