Prompt Engineering Basic to Advance

A: You need a defensible budget number to explain spend, and ~1.3 tokens/word gets you there with headroom. B doubles a typical English mapping without evidence. C assumes provider-side caching semantics that don't apply at billing time. D mixes up input/output accounting with legacy streaming myths.

A: You want a numeric feel for output variability, and scaling entropy by temperature gets you close enough for control discussions. B ignores that top_p truncates tails after temperature reshapes them. C compounds effects that don't multiply in practice. D reverses the direction of entropy change.

A: You're mapping safeguard to consequence, and reframing attacks bypass intent without violating literal constraints. B describes overblocking, not residual risk. C confuses safety controls with sampling controls. D assumes absolute priority without considering indirect elicitation.

A: You need repeatability against a known layout, and concrete examples anchor the model tightly. B trades control for flexibility you don't need. C adds verbosity and leakage risk without improving extraction. D increases variance against the stated constraint.