nerdexam
Salesforce

PDI · Question #48

A primaryid_c custom field exists on the candidate_c custom object. The filed is used to store each candidate's id number and is marked as Unique in the schema definition. As part of a data…

The correct answer is C. Update the primaryid__c field definition to mark it as an External Id. To efficiently upload a CSV file with updated candidate data and map it correctly using the unique primaryid__c field, the developer should mark primaryid__c as an External ID.

Submitted by fatema_kw· Apr 18, 2026Data Modeling and Management

Question

A primaryid_c custom field exists on the candidate_c custom object. The filed is used to store each candidate's id number and is marked as Unique in the schema definition. As part of a data enrichment process. Universal Containers has a CSV file that contains updated data for all candidates in the system, the file contains each Candidate's primary id as a data point. Universal Containers wants to upload this information into Salesforce, while ensuring all data rows are correctly mapped to a candidate in the system. Which technique should the developer implement to streamline the data upload?

Options

  • ACreate a Process Builder on the Candidate_c object to map the records.
  • BCreate a before Insert trigger to correctly map the records.
  • CUpdate the primaryid__c field definition to mark it as an External Id
  • DUpload the CSV into a custom object related to Candidate_c.

How the community answered

(32 responses)
  • B
    3% (1)
  • C
    91% (29)
  • D
    6% (2)

Why each option

To efficiently upload a CSV file with updated candidate data and map it correctly using the unique `primaryid__c` field, the developer should mark `primaryid__c` as an External ID.

ACreate a Process Builder on the Candidate_c object to map the records.

Process Builder is an automation tool for workflow processes and cannot be directly used to map or reconcile incoming data during a CSV file upload.

BCreate a before Insert trigger to correctly map the records.

While a `before Insert` trigger could programmatically attempt to find and update existing records, it is a less efficient and more complex solution for bulk data uploads compared to leveraging the built-in External ID functionality with an upsert operation.

CUpdate the primaryid__c field definition to mark it as an External IdCorrect

By updating the `primaryid__c` field definition to mark it as an External ID, data loading tools like Data Loader can use this unique identifier from the CSV file to perform an upsert operation, matching existing `Candidate__c` records and updating them, or creating new ones if no match is found, thereby ensuring accurate data mapping and preventing duplicates.

DUpload the CSV into a custom object related to Candidate_c.

Uploading the CSV into a custom object related to `Candidate__c` would create separate, new records and not directly update the existing `Candidate__c` records, leading to fragmented data and not achieving the goal of updating existing candidate information.

Concept tested: External ID for Data Loading/Upsert

Source: https://help.salesforce.com/s/articleView?id=sf.fields_about_external_id.htm

Topics

#External ID#Data Loading#Upsert#Custom Fields

Community Discussion

No community discussion yet for this question.

Full PDI Practice