Question 670
An Azure SQL platform needs to store embeddings as typed vectors instead of comma-delimited text. Which result distinguishes a successful implementation from a cosmetic change?
Explanation
Correct Answer
Typed vector storage enables vector-specific operations; lexicographic text sorting is not semantic distance. The observation “Distances reflect numeric vector geometry and inserted vectors pass dimension validation” directly confirms the chosen action worked for this situation: An Azure SQL platform needs to store embeddings as typed vectors instead of comma-delimited text.
Incorrect Answers
Full-text search uses tokenization and linguistic features not available in basic substring matching. This observation would not establish that the required result occurred for An Azure SQL platform needs to store embeddings as typed vectors instead of comma-delimited text. The confirming test is: Distances reflect numeric vector geometry and inserted vectors pass dimension validation.
Index metric compatibility affects correctness and optimizer index selection; mismatches can force exact fallback. This observation would not establish that the required result occurred for An Azure SQL platform needs to store embeddings as typed vectors instead of comma-delimited text. The confirming test is: Distances reflect numeric vector geometry and inserted vectors pass dimension validation.
An external model cannot infer unpublished transactional state; it needs explicit scoped retrieved context. This observation would not establish that the required result occurred for An Azure SQL platform needs to store embeddings as typed vectors instead of comma-delimited text. The confirming test is: Distances reflect numeric vector geometry and inserted vectors pass dimension validation.