Discuss Salesforce ADX-201 Exam Topic 1 Question 92

What should an administrator use as an identifier when importing and updating records from a

separate financial system?

AAuto-Number field?

BExternal ID

CRich text field

DRecord ID

Suggested Answer: B

An external ID is a custom field that has the external ID attribute enabled, which means it can be used as an identifier when importing and updating records from an external system. It allows administrators to match records based on a unique ID value from another system instead of using Salesforce record IDs, which may not be available or consistent across systems. An auto-number field is a custom field that automatically assigns a unique numeric value to each record, but it cannot be used as an identifier when importing and updating records from an external system because it is generated by Salesforce and may not match with the external system's IDs. A rich text field is a custom field that allows users to enter formatted text, images, and links, but it cannot be used as an identifier when importing and updating records from an external system because it is not unique or consistent across systems. A record ID is an internal ID assigned by Salesforce to each record, but it cannot be used as an identifier when importing and updating records from an external system because it may not be available or consistent across systems. Reference: https://help.salesforce.com/s/articleView?id=sf.custom_field_attributes.htm&type=5

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

31 comments · newest first

Willard 7 months ago

External ID keeps data consistent.

Winfred 7 months ago

Rich text field? That's not practical.

Frederica 7 months ago

Record ID is too specific to one system.

Harris 7 months ago

External ID is unique across systems.

Winfred 7 months ago

Why not Auto-Number? Seems easy.

Wilda 8 months ago

Really? I thought Record ID was the standard. This is confusing!

Renay 8 months ago

D) Record ID is solid, but I still prefer External ID for updates.

Pedro 8 months ago

Wait, why would anyone choose C) Rich text field? That seems pointless.

Candida 9 months ago

Definitely go with B) External ID. It's the best choice!

Roxane 9 months ago

Lol, rich text field? Might as well use a random number generator. B is the only sensible option.

Ludivina 9 months ago

B all the way. Record ID? That's just asking for trouble when importing data.

Junita 9 months ago

Haha, rich text field? What is this, the 90s? B is the clear choice here.

Ernest 9 months ago

I'd go with B. Can't imagine trying to use a rich text field as an identifier - way too messy.

Ty 9 months ago

Definitely B. Using an auto-number field would be a nightmare to sync up. External ID is the way to go.

Jamal 10 months ago

B) External ID is the correct answer. It's the most reliable way to ensure records are properly matched across systems.

Cordie 10 months ago

Rich text field definitely doesn’t seem like it would work for this; I’m leaning towards External ID too, but I’m not completely confident.

Lorean 10 months ago

External ID is the way to go. It's the most robust option for maintaining consistent record identification, even when importing from another system.

Delbert 10 months ago

I'm a bit confused by the options here. Is an auto-number field stable enough to use as an identifier? I'll have to think this through carefully.

Annette 10 months ago

Definitely going with External ID on this one. It's designed specifically for integrating data between systems, so that's the way to go.

Trina 10 months ago

I remember a practice question where Record ID was mentioned as a unique identifier, but I feel like External ID is more relevant here.

Skye 11 months ago

I’m not so sure about the Auto-Number field; it seems like it wouldn’t be stable enough for updates.

Linette 11 months ago

I think External ID is the best choice.

Junita 11 months ago

I think A) Auto-Number field could work too, but not as reliable.

Mattie 11 months ago

I think the External ID might be the right choice since it’s often used for linking records between systems.

Joni 11 months ago

Hmm, I'm not sure about this one. I'm leaning towards the Record ID, but I'll need to double-check the differences between that and an External ID.

Yaeko 12 months ago

I think the best approach here is to use an External ID. That seems like the most reliable way to uniquely identify records across systems.

Rosita 6 months ago

↳ replying to Yaeko

External ID ensures consistency and reliability.

Annette 6 months ago

↳ replying to Yaeko

Rich text field is not suitable for identification.

Penney 6 months ago

↳ replying to Yaeko

Record ID might not match across systems.

Theola 6 months ago

↳ replying to Yaeko

Auto-Number field could cause issues with duplicates.

Tandra 7 months ago

↳ replying to Yaeko

I agree, External ID is definitely the way to go.

Salesforce ADX-201 Exam - Topic 1 Question 92 Discussion