Salesforce Certified Platform Data Architect (Plat-Arch-201) Exam - Topic 5 Question 57 Discussion

Actual exam question for Salesforce's Salesforce Certified Platform Data Architect (Plat-Arch-201) exam

Question #: 57
Topic #: 5

[All Salesforce Certified Platform Data Architect (Plat-Arch-201) Questions]

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 Salesforce Certified Platform Data Architect (Plat-Arch-201) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Dana

2 months ago

Not so sure about that, what if the customer reference isn't unique?

upvoted 0 times

...

Kayleigh

2 months ago

Agree, that would definitely speed up searches!

upvoted 0 times

...

Kasandra

3 months ago

I think setting Customer_Reference__c as an External ID (unique) is the best option.

upvoted 0 times

...

Chana

3 months ago

Wow, 5 million records a year? That's a lot!

upvoted 0 times

...

Allene

3 months ago

Archiving after three years sounds reasonable too.

upvoted 0 times

...

Jesse

3 months ago

I believe setting Customer_Reference__c as a non-unique External ID might help with searches, but I’m not clear on how that compares to the unique option.

upvoted 0 times

...

Lenny

3 months ago

I vaguely recall that archiving records can improve performance, but I can't remember the exact timeframes we talked about. Three years or five years?

upvoted 0 times

...

Janessa

4 months ago

I think we practiced a similar question about optimizing search in Salesforce. I feel like making it a unique External ID could be beneficial, but I’m not entirely certain.

upvoted 0 times

...

Nickie

4 months ago

I remember we discussed the importance of indexing fields for searchability, but I'm not sure if setting Customer_Reference__c as an External ID would help with that.

upvoted 0 times

...

Iola

4 months ago

This is a great opportunity to show my understanding of Salesforce best practices. I think the unique external ID is the way to go - it will provide the most efficient search and reporting capabilities for the support team.

upvoted 0 times

...

Viva

4 months ago

I'm a bit confused by the external ID options. Do they have different implications for how the data is stored and accessed? I'll need to research that a bit more before deciding.

upvoted 0 times

...

Kimberlie

4 months ago

External ID, huh? That could work, but making it unique might cause issues if customers accidentally enter the same reference. I'd have to weigh the pros and cons of each approach.

upvoted 0 times

...

Hana

5 months ago

Okay, let's see. With 5 million records per year, archiving after 3 or 5 years could get really messy. I'm leaning more towards the external ID options to make searching and reporting easier.

upvoted 0 times

...

Ria

5 months ago

Hmm, this seems like a tricky one. I'll need to think carefully about the implications of each option and how they might impact the user experience and data management.

upvoted 0 times

...

Leana

9 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

Kandis

8 months ago

D) Set Customer-Reference_c as an External ID (unique).

upvoted 0 times

...

Alishia

8 months ago

B) Implement an archiving process for shipment records created after three years.

upvoted 0 times

...

Blossom

8 months ago

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

upvoted 0 times

...

Talia

8 months ago

A) Implement an archiving process for shipment records created after five years.

upvoted 0 times

...

Una

10 months ago

Archiving? That's for the weak! I say we go big or go home - option A, 5 years! Who needs to find those old shipments anyway?

upvoted 0 times

Gladys

8 months ago

Yeah, let's focus on the present and future shipments. Option A for sure.

upvoted 0 times

...

Zoila

9 months ago

I agree, let's keep it simple and clean. Option A it is!

upvoted 0 times

...

Glendora

9 months ago

Option A sounds like the way to go. We don't need those old shipment records cluttering up our searches.

upvoted 0 times

...

Rodney

10 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

8 months ago

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

upvoted 0 times

...

Iluminada

8 months ago

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

upvoted 0 times

...

Tegan

8 months ago

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

upvoted 0 times

...

Lenita

10 months ago

I'm not sure about that. With 5 million shipment records, a unique external ID could get messy. Maybe option C, a non-unique external ID, would be better to handle the volume?

upvoted 0 times

Thurman

9 months ago

Let's go with setting Customer-Reference_c as a non-unique External ID then.

upvoted 0 times

...

Jeff

9 months ago

I agree, it could make it easier for support agents to find the right shipment records.

upvoted 0 times

...

Isabella

9 months ago

Yeah, that could be a good solution to handle the high volume of shipment records.

upvoted 0 times

...

Michael

9 months ago

I think setting Customer-Reference_c as a non-unique External ID could work well for searching.

upvoted 0 times

...

Arthur

9 months ago

Yeah, having a non-unique external ID might be more practical with that many records.

upvoted 0 times

...

Elvis

10 months ago

Option C sounds like a good idea. It could help with searching for shipment records.

upvoted 0 times

...

Marg

10 months ago

I'm not sure, maybe implementing an archiving process for shipment records created after three years could also help with performance.

upvoted 0 times

...

Mollie

11 months ago

I agree with Caprice, having it as a unique External ID would make searching for shipment records much easier.

upvoted 0 times

...

Fabiola

11 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

9 months 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

9 months 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

9 months ago

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

upvoted 0 times

...

Chaya

9 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

11 months ago

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

upvoted 0 times

...