Prompt Engineering Fundamentals
Last reviewed
Correct answer: C. It replaces a subjective qualifier with a limit that has a concrete, measurable definition
Explanation
The principle — A constraint you cannot check is not a constraint. If two people could disagree about whether the output complied, the model can disagree with you too.
Why the key is correct — Google's checklist tells you to avoid subjective or relative qualifiers that lack a concrete, measurable definition, and to provide objective constraints instead — giving this exact substitution as its example. "Three sentences or less" is verifiable by counting.
Why the others are wrong — Length and repetition do not add force. Adjectives are acted on rather than ignored, which is the problem. And precision buys consistency, not creativity.
Remember this — If you cannot check compliance by counting or looking, rewrite the constraint until you can.
Sources — Google Cloud, Overview of prompting strategies.
Sources
“Avoid using subjective or relative qualifiers that lack a concrete, measurable definition.”
Practise 10 questions on this topic
Take Prompt Engineering Fundamentals — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.