Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce ADX-201 Exam - Topic 1 Question 92 Discussion

What should an administrator use as an identifier when importing and updating records from aseparate financial system?
B) External ID
A) Auto-Number field?
C) Rich text field
D) Record ID

Salesforce ADX-201 Exam - Topic 1 Question 92 Discussion

Actual exam question for Salesforce's ADX-201 exam
Question #: 92
Topic #: 1
[All ADX-201 Questions]

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

separate financial system?

Show Suggested Answer Hide Answer
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


by Devorah at Nov 20, 2025, 05:07 AM

Limited Time Offer

25%

Off

Get Premium ADX-201 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Willard
2 months ago
External ID keeps data consistent.
upvoted 0 times
...
Winfred
2 months ago
Rich text field? That's not practical.
upvoted 0 times
...
Frederica
2 months ago
Record ID is too specific to one system.
upvoted 0 times
...
Harris
2 months ago
External ID is unique across systems.
upvoted 0 times
...
Winfred
2 months ago
Why not Auto-Number? Seems easy.
upvoted 0 times
...
Wilda
3 months ago
Really? I thought Record ID was the standard. This is confusing!
upvoted 0 times
...
Renay
3 months ago
D) Record ID is solid, but I still prefer External ID for updates.
upvoted 0 times
...
Pedro
3 months ago
Wait, why would anyone choose C) Rich text field? That seems pointless.
upvoted 0 times
...
Candida
4 months ago
Definitely go with B) External ID. It's the best choice!
upvoted 0 times
...
Roxane
4 months ago
Lol, rich text field? Might as well use a random number generator. B is the only sensible option.
upvoted 0 times
...
Ludivina
4 months ago
B all the way. Record ID? That's just asking for trouble when importing data.
upvoted 0 times
...
Junita
4 months ago
Haha, rich text field? What is this, the 90s? B is the clear choice here.
upvoted 0 times
...
Ernest
4 months ago
I'd go with B. Can't imagine trying to use a rich text field as an identifier - way too messy.
upvoted 0 times
...
Ty
4 months ago
Definitely B. Using an auto-number field would be a nightmare to sync up. External ID is the way to go.
upvoted 0 times
...
Jamal
5 months ago
B) External ID is the correct answer. It's the most reliable way to ensure records are properly matched across systems.
upvoted 0 times
...
Cordie
5 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.
upvoted 0 times
...
Lorean
5 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.
upvoted 0 times
...
Delbert
5 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.
upvoted 0 times
...
Annette
5 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.
upvoted 0 times
...
Trina
5 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.
upvoted 0 times
...
Skye
6 months ago
I’m not so sure about the Auto-Number field; it seems like it wouldn’t be stable enough for updates.
upvoted 0 times
...
Linette
6 months ago
I think External ID is the best choice.
upvoted 0 times
...
Junita
6 months ago
I think A) Auto-Number field could work too, but not as reliable.
upvoted 0 times
...
Mattie
6 months ago
I think the External ID might be the right choice since it’s often used for linking records between systems.
upvoted 0 times
...
Joni
6 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.
upvoted 0 times
...
Yaeko
7 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.
upvoted 0 times
Rosita
24 days ago
External ID ensures consistency and reliability.
upvoted 0 times
...
Annette
30 days ago
Rich text field is not suitable for identification.
upvoted 0 times
...
Penney
1 month ago
Record ID might not match across systems.
upvoted 0 times
...
Theola
1 month ago
Auto-Number field could cause issues with duplicates.
upvoted 0 times
...
Tandra
2 months ago
I agree, External ID is definitely the way to go.
upvoted 0 times
...
...

Save Cancel