Standard analyzer in Elasticsearch - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of the standard analyzer on the text?

Given the text "The Quick Brown Foxes jumped over the lazy dogs.", what tokens does the standard analyzer produce?

Elasticsearch

{
  "analyze": {
    "analyzer": "standard",
    "text": "The Quick Brown Foxes jumped over the lazy dogs."
  }
}

A ["the", "quick", "brown", "fox", "jumped", "over", "the", "lazy", "dog"]

B ["The", "Quick", "Brown", "Foxes", "jumped", "over", "the", "lazy", "dogs"]

C ["the", "quick", "brown", "foxes", "jumped", "over", "lazy", "dogs"]

D ["the", "quick", "brown", "foxes", "jumped", "over", "the", "lazy", "dogs"]

💡 Hint

The standard analyzer lowercases all tokens and splits on punctuation and whitespace.

The standard analyzer lowercases all words and splits on whitespace and punctuation. It does not stem words, so 'foxes' and 'dogs' remain plural.

🧠 Conceptual

intermediate

Which feature is NOT part of the standard analyzer?

Select the feature that the standard analyzer does NOT perform on input text.

A Removing English stop words by default

B Lowercasing all tokens

C Splitting text on punctuation and whitespace

D Tokenizing text into terms

💡 Hint

Think about whether the standard analyzer removes common words like "the" or "and".

The standard analyzer does not remove stop words by default. It lowercases, tokenizes on punctuation and whitespace, but keeps all tokens including stop words.

🔧 Debug

advanced

Why does this standard analyzer output include the token "can't" split into two tokens?

Given the text "I can't do this." analyzed with the standard analyzer, the output tokens are ["i", "can't", "do", "this"]. Why is "can't" not split into "can" and "t"?

Elasticsearch

{
  "analyze": {
    "analyzer": "standard",
    "text": "I can't do this."
  }
}

A The standard analyzer treats apostrophes inside words as part of the token.

B The standard analyzer removes apostrophes, so "can't" becomes "cant".

C The standard analyzer splits tokens on apostrophes, so "can't" becomes "can" and "t".

D The standard analyzer converts contractions into full words automatically.

💡 Hint

Consider how the standard analyzer treats punctuation inside words.

The standard analyzer keeps apostrophes inside words as part of the token, so "can't" remains one token.

📝 Syntax

advanced

What error occurs with this standard analyzer JSON request?

Identify the error in this JSON request to analyze text with the standard analyzer:

{
  "analyze": {
    "analyzer": "standard",
    "text": ["Hello", "world"]
  }
}

A No error, the request is valid and returns tokens for both words

B RuntimeError: Analyzer 'standard' does not support arrays

C TypeError: 'text' field must be a string, not an array

D SyntaxError: JSON array not allowed for 'text' field

💡 Hint

Check the expected data type for the 'text' field in the analyze API.

The 'text' field must be a string. Passing an array causes a type error.

🚀 Application

expert

How many tokens does the standard analyzer produce for this text?

Analyze the text "E-mail addresses like [e-mail] are tokenized." with the standard analyzer. How many tokens are produced?

Elasticsearch

{
  "analyze": {
    "analyzer": "standard",
    "text": "E-mail addresses like [e-mail] are tokenized."
  }
}

A 7

B 8

C 9

D 6

💡 Hint

The standard analyzer keeps hyphenated words like 'E-mail' as a single token but splits emails on punctuation like @ and ..

The tokens are: ["e-mail", "addresses", "like", "test", "example", "com", "are", "tokenized"] totaling 8 tokens. The hyphenated "E-mail" remains one token, while "[e-mail]" splits into "test", "example", "com".