Enrich processor in Elasticsearch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define an enrich policy named 'user-policy'.

Elasticsearch

PUT /_enrich/policy/[1]

Drag options to blanks, or click blank then click option'

Auser-policy

Bproduct-policy

Corder-policy

Dcustomer-policy

Attempts:

3 left

💡 Hint

Common Mistakes

Using a policy name unrelated to users.

Leaving the name blank.

The enrich policy name must be 'user-policy' to match the example.

2fill in blank

medium

Complete the code to create an enrich index from the policy.

Elasticsearch

POST /_enrich/policy/[1]/_execute

Drag options to blanks, or click blank then click option'

Aproduct-policy

Bcustomer-policy

Cuser-policy

Dorder-policy

Attempts:

3 left

💡 Hint

Common Mistakes

Using a wrong policy name.

Misspelling the policy name.

The enrich index is created by executing the 'user-policy'.

3fill in blank

hard

Fix the error in the enrich processor configuration to use the correct policy name.

Elasticsearch

"enrich": {
  "policy_name": "[1]",
  "field": "user_id",
  "target_field": "user_info"
}

Drag options to blanks, or click blank then click option'

Auser-data

Busers

Cuser_index

Duser-policy

Attempts:

3 left

💡 Hint

Common Mistakes

Using the index name instead of policy name.

Using a made-up name.

The enrich processor uses the policy name 'user-policy'.

4fill in blank

hard

Fill both blanks to complete the enrich processor in an ingest pipeline.

Elasticsearch

{
  "processors": [
    {
      "enrich": {
        "policy_name": "[1]",
        "field": "user_id",
        "target_field": "[2]"
      }
    }
  ]
}

Drag options to blanks, or click blank then click option'

Auser-policy

Buser_info

Cuser_data

Dprofile

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong policy names.

Using inconsistent target field names.

The enrich processor must use the correct policy name 'user-policy' and a target field like 'user_info' to store enriched data.

5fill in blank

hard

Fill all three blanks to create a complete enrich processor with a match field and ignore missing option.

Elasticsearch

{
  "processors": [
    {
      "enrich": {
        "policy_name": "[1]",
        "field": "[2]",
        "ignore_missing": [3]
      }
    }
  ]
}

Drag options to blanks, or click blank then click option'

Auser-policy

Buser_id

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Setting 'ignore_missing' to false causing errors.

Using wrong field names.

The enrich processor uses 'user-policy' as the policy, 'user_id' as the match field, and 'ignore_missing' set to true to avoid errors if the field is missing.