You have an Azure subscription that contains an Azure Cosmos DB database. Azure Synapse Link is implemented on the database.
You configure a full fidelity schema for the analytical store.
You perform the following actions:
• Insert {"customerID": 12, "customer": “Tailspin Toys"} as the first document in the container.
• Insert {"customerID": "14", "customer": "Contoso"} as the second document in the container.
How many columns will the analytical store contain?
When using a full fidelity schema in Azure Synapse Link for Azure Cosmos DB, the analytical store will maintain columns for each unique data type present in the documents. In this scenario, the 'customerID' appears both as an integer and as a string, necessitating two separate columns to represent these two different data types. Additionally, there will be one column for the 'customer' field, which is always a string. Consequently, the analytical store will contain three columns.
C - With a full fidelity schema, the analytical store will track both the data and their types accurately. This means different types for the same field will be stored in separate columns. Specifically: There will be one column for customerID as an integer. There will be another column for customerID as a string. There will be one column for customer as a string.
The above explained is correct answer must be C. 3. 12 and "14" being different datatypes will have separate columns in full fidelity schema.
Answer C
C, a third column will be added for the change in datatype.