Elasticsearch MigrationClickHouse Workshops

04 Validate your knowledge

Test ClickHouse fundamentals and apply them to production-scale migration scenarios.

Estimated time: 60–75 minutes No infrastructure changes — this part is purely assessment.

Overview

Part 4 tests whether you understand why each Elasticsearch-to-ClickHouse migration choice was made and can select a defensible design for a workload you have not seen before.

The questions focus on:

  • ClickHouse fundamentals — MergeTree mechanics, sparse indexes, sort keys, native types, dictionaries, and incremental materialized views
  • OpenTelemetry data modeling — resource attributes, signal correlation, and span semantics
  • Migration trade-offs — dual-write, schema evolution, compliance retention, and rollback
  • Production debugging — distinguishing data differences from query and indexing problems

Assessment format

ComponentQuestionsPass threshold
Core knowledge15≥ 11 correct
Applied migration scenarios20≥ 16 correct

Both components save progress in this browser. Answers and explanations remain hidden until every question in that component is answered and submitted.

Core knowledge

Loading assessment...

Applied scenario MCQs

Use the production-scale scenarios to choose the strongest ClickHouse designs. The options are intentionally plausible: select the answer that best matches the workload and ClickHouse's physical behavior, not merely one that contains familiar terminology.

Loading assessment...

Complete the workshop

After both assessment components pass, tear down the Part 1 and Part 3 infrastructure:

bash "$(git rev-parse --show-toplevel)/workshops/elasticsearch_migration_lab/common/cleanup.sh"

You do not need a running ClickHouse service for this module; every scenario includes the facts needed to decide.

本页内容

Track your progress?

Optional. We email a link to confirm your address; progress records once you open it.

Please use your work email address, not a personal one.

Progress tracking also requires accepting the current Terms of Service in Privacy settings.

ZH