Kvíz spojený s průvodcem · Střední úroveň

Nondeterminism in LLM Outputs Quiz

Understand why repeated LLM calls vary and which controls improve reproducibility without guaranteeing identical outputs across systems.

Související vodicí cestyNondeterminism In LLM Outputs
Otázka 1 z 8

Why might an LLM return different text for the same prompt on two runs?

Náhled každé otázky8 otázky

Odpovědi a vysvětlení se zobrazují, jak budete v kvízu.

  1. Why might an LLM return different text for the same prompt on two runs?
    • A prompt can only ever have one possible continuation
    • Sampling, backend changes, numerical execution, or different tool results can affect generation
    • Temperature zero guarantees identical output everywhere
    • A model never uses probabilities
  2. What does a seed parameter generally provide in a supported API?
    • A guarantee of identical output across providers
    • A guarantee that an answer is correct
    • A way to pin tool results automatically
    • Best-effort repeatability under matching request and backend conditions
  3. What can a system fingerprint help a developer detect?
    • A change in backend configuration that may affect reproducibility
    • Whether the generated answer is true
    • Whether users like the answer
    • The prompt’s character count
  4. Why might temperature zero still fail to guarantee identical hosted outputs?
    • Temperature zero disables the model
    • The API ignores every prompt
    • Infrastructure and numerical execution can vary despite deterministic sampling settings
    • Tokens are not probabilistic
  5. What should an experiment log to help reproduce an output?
    • Only the response text
    • Model identifier, prompt, sampling settings, seed, fingerprint, and tool state
    • Only the user’s account name
    • Pouze konečné skóre
  6. When is exact-string matching most appropriate in an evaluation?
    • When the task explicitly requires exact formatting or a fixed output
    • For every open-ended response
    • When model versions change often
    • When no reference output exists
  7. How can teams evaluate variation when exact matching is too brittle?
    • Ignore all failures
    • Compare only response length
    • Assume every paraphrase is wrong
    • Use structured fields, semantic criteria, or task outcomes
  8. Does recording a seed make a system correct or secure?
    • Yes, it guarantees factual answers
    • Yes, it encrypts prompts
    • No; it only helps control generation variation in supported conditions
    • No, because seeds have no use