Exam PL-600 topic 2 question 41 discussion

To store unique IDs belonging to records from the third-party application in Microsoft Dataverse, you can use two column types: Single Line of Text: You can use this column to store alphanumeric IDs, such as order numbers or customer IDs, from the third-party application. GUID: You can use this column to store unique identifiers generated by the third-party application, such as unique IDs for customers, orders, or invoices. By using these two column types, you can ensure that the unique IDs belonging to records from the third-party application are accurately and reliably stored in Microsoft Dataverse.

Cannot use unique identifier field. That is system generated during the import. Cannot use lookup, what are you looking up to? You are only required to store the Unique Identifier value, not link to another record

Why not the others? B. Text Area: Meant for longer text entries like descriptions or notes, not ideal for storing IDs. C. Float: Not suitable for IDs due to potential precision loss with large numbers. E. Rich Text: Used for formatted content, not for storing identifiers. F. Lookup: Used to create relationships between tables, not for storing external IDs directly.

answer is A D

Correct answer is A&D

I agree with Skada, and CoPilot picked this one as well.

I used AF option in one of my solution, reason is when it comes data integration between two tabled or references is must lookup is required. And it worked too

Vote AD

A & F. The unique id from the external system might not be a GUID.

AF. Only these kinds of columns can be used to create alternate keys: Decimal Whole Number (Integer) Single line of Text (String) Date and Time Lookup Choice

AF is the right answer. Unique identifier is internal reserved data type cannot be used to store external data. Text Area (Multi-text) cannot support as an alterative key

My opinion is that: - BEF should be excluded by default - D should be included by default So it remains to choose between A & C... but usually IDs if are numeric are integer types not float... so it remains A. That's why my final answer would be A&D.

The question mentions unique IDs not Global unique IDs. https://en.wikipedia.org/wiki/Unique_identifier Storing these examples is not possible in the guid (primary key column)

I say A and F because they are the only possible field type for an alternate key.

Since it states that each answer represent a complete solution, I would stay with A and B How could the others be a complete solution?

DecimalAttributeMetadata Decimal Number IntegerAttributeMetadata Whole Number StringAttributeMetadata Single line of text DateTimeAttributeMetadata Date Time LookupAttributeMetadata Lookup PicklistAttributeMetadata Option Set

its A and F. The only supported data types for Alt Keys is DecimalAttributeMetadata Decimal Number IntegerAttributeMetadata Whole Number StringAttributeMetadata Single line of text DateTimeAttributeMetadata Date Time LookupAttributeMetadata Lookup PicklistAttributeMetadata Option Set