Fuzzy matching in Elasticsearch - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Fuzzy query with max_expansions effect

What is the output of this Elasticsearch fuzzy query when searching for the term "roam" with max_expansions set to 2?

Elasticsearch

{
  "query": {
    "fuzzy": {
      "name": {
        "value": "roam",
        "fuzziness": 1,
        "max_expansions": 2
      }
    }
  }
}

A Matches documents with terms like "roam", "foam", but limits to 2 expanded terms

B Matches only exact term "roam" ignoring fuzziness

C Matches all terms within fuzziness 1 without limit on expansions

D Raises an error because max_expansions cannot be set to 2

💡 Hint

Think about how max_expansions limits the number of fuzzy variations Elasticsearch considers.

The max_expansions parameter limits how many fuzzy variations Elasticsearch will try. Setting it to 2 means it will consider only two possible fuzzy matches like "foam" and "roam". It does not disable fuzziness or cause errors.

🧠 Conceptual

intermediate

Understanding fuzziness parameter

Which statement correctly describes the fuzziness parameter in Elasticsearch fuzzy queries?

A It controls the maximum number of terms returned by the fuzzy query.

B It sets the minimum number of characters a term must have to be fuzzy matched.

C It defines the maximum Levenshtein edit distance allowed between the query term and matching terms.

D It disables fuzzy matching and forces exact matches only.

💡 Hint

Fuzziness relates to how different the matched words can be from the query word.

Fuzziness defines the maximum number of single-character edits (insertions, deletions, substitutions) allowed to consider a term a match.

🔧 Debug

advanced

Why does this fuzzy query return no results?

Given this fuzzy query searching for "aple" with fuzziness 1, why does it return no results?

Elasticsearch

{
  "query": {
    "fuzzy": {
      "name": {
        "value": "aple",
        "fuzziness": 1,
        "prefix_length": 3
      }
    }
  }
}

A Because the field "name" is not analyzed, so fuzzy matching fails

B Because prefix_length 3 requires first 3 characters to match exactly, but "aple" and "apple" differ in first 3 chars

C Because fuzzy queries do not support prefix_length parameter

D Because fuzziness 1 is too low to match "apple" from "aple"

💡 Hint

Check how prefix_length affects which characters must match exactly.

prefix_length 3 means the first 3 characters must be identical. "aple" and "apple" differ at the third character, so no match occurs despite fuzziness.

📝 Syntax

advanced

Identify the syntax error in this fuzzy query

Which option contains the correct syntax for a fuzzy query searching for "color" with fuzziness 2?

A { "query": { "fuzzy": { "color": { "value": "color", fuzziness: 2 } } } }

B { "query": { "fuzzy": { "color": { value: "color", "fuzziness": 2 } } } }

C { "query": { "fuzzy": { "color": { "value": "color", "fuzziness" = 2 } } } }

D { "query": { "fuzzy": { "color": { "value": "color", "fuzziness": 2 } } } }

💡 Hint

Remember JSON requires keys and string values to be in double quotes and colons to separate keys and values.

Option D uses correct JSON syntax with quoted keys and values and colons. Options A and D miss quotes on keys, and C uses '=' instead of ':', all invalid JSON.

🚀 Application

expert

Optimizing fuzzy search for typo tolerance in product names

You want to allow fuzzy matching on product names to tolerate up to 2 typos but avoid too many irrelevant matches. Which query configuration best balances fuzziness and performance?

A { "query": { "fuzzy": { "product_name": { "value": "sneaker", "fuzziness": 2, "max_expansions": 50, "prefix_length": 1 } } } }

B { "query": { "fuzzy": { "product_name": { "value": "sneaker", "fuzziness": 2, "max_expansions": 1000, "prefix_length": 0 } } } }

C { "query": { "fuzzy": { "product_name": { "value": "sneaker", "fuzziness": 1, "max_expansions": 10, "prefix_length": 3 } } } }

D { "query": { "fuzzy": { "product_name": { "value": "sneaker", "fuzziness": 3, "max_expansions": 5, "prefix_length": 2 } } } }

💡 Hint

Consider how fuzziness, max_expansions, and prefix_length affect match tolerance and query speed.

Option A allows up to 2 typos (fuzziness=2), limits expansions to 50 to avoid performance issues, and requires first character to match exactly (prefix_length=1) to reduce irrelevant matches. Other options either allow too many expansions, too low fuzziness, or too high fuzziness causing poor balance.