Elastic Certified Engineer study materials
Elastic Certified Engineer study resources

Elastic Certified Engineer study plan

Elastic Certified Engineer · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Installation and Configuration

  • Install Elasticsearch from the binary tarball and via Docker, then start a single node with a corrected JVM heap setting

  • Configure elasticsearch.yml for a three-node cluster: cluster.name, node.roles, discovery.seed_hosts, and initial master nodes

  • Enable security with TLS on the transport and HTTP layers, then create a custom role and user and verify access with curl

  • Inspect the running cluster using _cluster/health, _cat/nodes, _cat/shards, and _nodes/stats to confirm a green status

Your checkpoint

A repeatable startup script (or compose file) that brings up a secure 3-node cluster; _cluster/health returns status green with number_of_nodes = 3

Week 2

Installation and Configuration & Cluster Administration

  • Compose a component template plus an index template with settings, mappings, and aliases, and apply it to rollover-ready indices

  • Register a filesystem snapshot repository, take a snapshot of two indices, delete one locally, and restore it

  • Build an ILM policy with hot, warm, and delete phases and attach it to an index using rollover alias

  • Diagnose and fix a yellow or red cluster by inspecting unassigned shards and adjusting allocation or disk watermark settings

Your checkpoint

A restored index recovered from snapshot plus an ILM policy that rolled over at least once, demonstrated with _ilm/explain output

Week 3

Data Modeling

  • Write explicit mappings with correct types (keyword, text, date, scaled_float, ip) for a realistic product dataset

  • Define three custom analyzers with character filters, tokenizers, and token filters, and compare their _analyze output

  • Model one relation three ways: nested objects, join field parent-child, and denormalized documents, and state the trade-offs

  • Add runtime fields and a dynamic template, then verify that new documents map the way you intended

Your checkpoint

A mapping file plus _analyze snippets proving all three analyzers behave as designed on the same sample input

Week 4

Data Ingestion & Data Modeling

  • Build an ingest pipeline with grok, date, convert, rename, and set processors that parses three different log formats

  • Bulk index 10,000 documents and inspect every item-level error until the bulk response reports zero failures

  • Reindex a legacy index into a new mapping using a Painless script and an ingest pipeline

  • Ship data with Logstash or Filebeat into the new index and verify document counts with _count

Your checkpoint

A versioned pipeline and bulk loader that ingests 10,000 documents across three formats with zero bulk errors

Week 5

Search

  • Compose compound bool queries mixing must, filter, should, must_not, and minimum_should_match

  • Tune relevance with function_score, boost, and a rescore phase, comparing results before and after

  • Paginate a large result set with search_after plus point-in-time, and contrast it with from/size limits

  • Debug slow or wrong queries using the _explain, _validate/query, and _profile APIs

Your checkpoint

A file of ten working queries, each paired with the _explain or _profile output that justifies why it returns the expected top hit

Week 6

Aggregations

  • Run and interpret bucket aggregations: terms with size and order, date_histogram with calendar and fixed intervals, and range

  • Aggregate nested documents with nested plus reverse_nested and verify counts against raw queries

  • Chain metric and pipeline aggregations such as avg_bucket, derivative, and cumulative_sum over a date_histogram

  • Use filter, filters, and global aggregations together so filtered and unfiltered counts appear in one response

  • Page deep aggregation results with the composite aggregation plus after_key

Your checkpoint

A set of eight aggregation requests with saved responses, each annotated with the expected value so they can be re-run as a regression check

Week 7

Developing Search Applications

  • Implement an index-and-search client in Python or Java that handles connection pooling, retries, and 4xx versus 5xx errors

  • Add highlighting, a completion suggester, and search_after pagination to the application

  • Use the async search API for a long-running query and poll for partial results

  • Write integration tests that index a fixture and assert exact hit order and snippet contents

Your checkpoint

A runnable CLI application with index, search, highlight, suggest, and paginate commands, covered by at least three passing tests

Week 8

Machine Learning & Cluster Administration

  • Start a trial license, then create a single-metric anomaly detection job with a datafeed and review the bucket results

  • Create a multi-metric job with a split field and explain why a given bucket was flagged as anomalous

  • Configure an inference ingest pipeline that runs an NLP model on documents at index time

  • Take a timed 60-question mock exam across all eight domains and review every missed item

Your checkpoint

A working anomaly detection job with exported results plus an inference pipeline, and a mock exam score of at least 75%

Milestones

Week 2: You can stand up a secure three-node cluster, apply an index template, and restore an index from snapshot without consulting notes

Week 4: Mappings, analyzers, and an ingest pipeline work together: 10,000 documents ingest with zero bulk errors into a correctly modeled index

Week 6: You write a nested aggregation with a pipeline sub-aggregation and its paging variant from scratch in under ten minutes each

Week 8: Mock exam score of 75% or higher with no single domain below 60%, and a demonstrated anomaly detection job