Quiz collegato alla guida · Medio Livello

Reindicizzare gli incorporamenti quando i modelli cambiano Quiz

Pianifica le migrazioni di incorporamento con spazi vettoriali con versione, indici paralleli, riempimenti, controlli di pertinenza, cutover e rollback sicuri.

Domanda 1 di 8

Perché gli embedding di modelli vecchi e nuovi dovrebbero generalmente essere mantenuti in versioni di indice separate?

Anteprima di ogni domanda8 domande

Le risposte e le spiegazioni vengono visualizzate mentre rispondi al quiz.

  1. Perché gli embedding di modelli vecchi e nuovi dovrebbero generalmente essere mantenuti in versioni di indice separate?
    • Use an index migration instead of checking vector compatibility
    • Assume equal vector dimensions mean matching semantic coordinates
    • The two models may define different vector spaces even when dimensions match
    • Store old query vectors with new candidate vectors because both are embeddings
  2. Quale strategia di migrazione mantiene il servizio corrente disponibile durante un nuovo backfill di embedding?
    • Delete the old index before generating replacement vectors
    • Backfill a second index while the current index continues serving
    • Switch the query encoder before rebuilding candidate vectors
    • Mix both models’ vectors without storing their model versions
  3. Quale controllo previene direttamente un errore di dimensione quando si scrivono nuovi vettori?
    • Confirm the input token count equals the index vector dimension
    • Confirm query and document encoders have the same display name
    • Confirm the training checkpoint dimension without checking index configuration
    • Confirm each output vector dimension matches the configured index
  4. Cosa aiuta a valutare il shadow querying?
    • Send old and new queries to separate evaluators without changing user-visible responses
    • Compare only the raw text before either embedding model runs
    • Route all live requests to the new index while retaining the old results
    • Compare training gradients for the two embedding models
  5. Why reconcile updates that arrive during a long backfill?
    • Change the query vector dimension during the backfill
    • Skip query evaluation after vectors are written
    • Remove the stable document identifiers before reconciliation
    • Ensure source changes made during the scan are included before cutover
  6. What should a rollback restore after a failed migration?
    • Restore the previous dashboard configuration only
    • Restore a compatible old query encoder and old index pair
    • Keep the new query encoder pointed at old vectors
    • Roll back the unrelated training checkpoint
  7. Quale evidenza dovrebbe guidare un taglio dell'indice?
    • The new model has lower training loss than the old model
    • Vector generation completed for all records
    • Index creation returned a ready status
    • Check retrieval quality and operational metrics on representative queries
  8. What makes a backfill safer to retry?
    • Use stable record IDs and idempotent writes
    • Generate random IDs on every retry
    • Ignore failed records and mark the scan complete
    • Switch indexes after the first batch succeeds