Reversing the effect of temperature
The wrong answers move temperature the wrong way. To make wording consistent they raise it, and to widen variety they lower it. Lowering temperature sharpens the distribution so the most probable tokens dominate, converging towards greedy decoding at zero. Raising it flattens the distribution so lower-probability tokens are sampled more often. Consistent, reproducible output needs a low temperature; a wider spread of ideas needs a higher one.
See it in a sample questionConfusing temperature, top-p and top-k
The wrong answers swap what each control does. Temperature rescales the probability of every token, making the distribution flatter or sharper. Top-p truncates, keeping the smallest set of top tokens whose cumulative probability reaches a threshold, so the candidate count varies with the distribution. Top-k keeps a fixed count of the most probable tokens. Describing top-p as a fixed count, or temperature as a cutoff, misattributes the mechanism.
See it in a sample questionExpecting a model setting to supply current facts
The wrong answers reach for a setting to fix stale or inaccurate answers: a different temperature, a larger context window or a longer output limit. None of these puts the current document in front of the model, so a lower temperature only repeats an outdated figure more consistently. Grounding retrieves the verified source text and supplies it in the prompt at inference time, so the answer is anchored to that material rather than to what the weights encoded in training.
See it in a sample questionSwapping Trainium and Inferentia
The wrong answers give each AWS accelerator the other's job. Trainium is the purpose-built chip for training deep learning and generative AI models, so it suits a lengthy training run. Inferentia is built to run trained models in production with high throughput and low cost per inference. Offering Inferentia for training, Trainium for serving, or Graviton as a training chip reverses or ignores that split.
See it in a sample questionPricing a request by anything other than tokens
The wrong answers price a request by something other than tokens: the word count of the visible answer, processing time, a flat charge, or retraining. Hosted models bill the input and output tokens processed. A large supplied document or retrieved reference block raises cost even when the reply is short, and a request for five full versions multiplies the output tokens. Inference calls never retrain the model.
See it in a sample question