Q: 4
In the simplified workflow for managing and querying vector data, what is the role of indexing?
Options
Discussion
B . Indexing's core use here is efficient retrieval, not compression like C which is a trap.
Definitely B, indexing is all about structuring vectors for quick similarity search. Not storage reduction or format conversion. Pretty sure that's what every vector DB doc says too.
Seen this in a few practice tests, official doc explains B as the key. Indexing = faster retrieval.
B , indexing lets you search vectors way faster by mapping them into a structure optimized for queries. It isn't about compression or categorizing types, it's all about retrieval speed. Seen this logic in other generative AI DB questions so feels right. Someone correct me if I'm off?
Yeah B is right here.
Isn't D about categorization, not search? Indexing is more tied to retrieval speed.
B tbh, indexing is all about making the search faster by organizing the vectors so you don’t have to brute force everything. D looks tempting because you do sometimes categorize data, but that's not what 'indexing' specifically means here. I’ve seen similar questions in other AI/vector DB practice sets. If anyone’s picking C for compression, pretty sure that’s a distraction.
Its B, indexing creates a structure so you can search vectors way faster. Is the question asking for "the main" role though, or could it be about storage too? If storage size was the requirement, C would make sense instead.
Be respectful. No spam.