When a query is ambiguous, what should you consider when judging results?

• A. Look for context signals and prefer results that offer broad usefulness or indicate ambiguity.
• B. Focus on exact keywords only.
• C. Always choose the most popular result.
• D. Use only the top result.

Answer: (A)

When a query is ambiguous, the best approach is to look for context signals in the results and favor those that stay useful across different interpretations or explicitly acknowledge the ambiguity. Context signals can come from the surrounding words, the domain of the site, or any snippets that hint at multiple meanings. A result that clarifies the different possible meanings or offers guidance on how to disambiguate—perhaps by suggesting what information you might need to specify—is especially helpful because it keeps you moving toward the right interpretation rather than locking you into one guess.

For example, a query like “bank” could refer to a financial institution or a riverbank. A strong result would either present both meanings and help you decide which is intended, or ask a clarifying question to narrow the focus. That flexibility is exactly what you want when intent isn’t clear.

Why the other approaches fit less well: focusing only on exact keywords can miss important context and lead you down a narrow or incorrect path; relying on the most popular result doesn’t guarantee it matches your actual need; and using only the top result might overlook alternative interpretations that are more relevant to your goal.