ElasticSearch Professional Standards & Competencies 5

Question 1

A professional deploying Elasticsearch in a regulated industry must ensure data at rest is encrypted. Which approach is correct?

Accepted Answer

Use OS-level disk encryption (e.g., LUKS) or cloud provider encryption, since Elasticsearch does not encrypt data at rest natively

Answer

Elasticsearch does not provide native at-rest encryption; disk-level encryption via the OS or cloud provider is required to satisfy regulatory mandates.

Question 2

Which Elasticsearch competency is demonstrated by choosing a 'keyword' field type over 'text' for a status field used only in filter aggregations?

Accepted Answer

Keyword fields store exact values without analysis, making them correct and efficient for filtering and aggregating categorical data

Answer

Keyword fields bypass the analysis pipeline and store raw values, which is the correct choice for exact-match filtering and terms aggregations on low-cardinality fields.

Question 3

What professional obligation does an Elasticsearch engineer have when discovering that a production index has no snapshot policy configured?

Accepted Answer

Immediately create and test a snapshot lifecycle management (SLM) policy and report the gap to stakeholders

Answer

Replicas protect against node failure but not against accidental deletion or corruption; professional practice requires verified, automated snapshot policies.

Question 4

When a search query returns unexpectedly low relevance scores, which professional debugging step should be taken first?

Accepted Answer

Use the Explain API to inspect how scores are computed for specific documents

Answer

The Explain API (GET //_explain/) provides a detailed breakdown of how relevance scores were calculated, enabling targeted tuning.

Question 5

A professional Elasticsearch engineer is asked to implement multi-tenancy for different client organizations. Which approach best balances isolation and resource efficiency?

Accepted Answer

Use a single index with a 'client_id' field and document-level security to enforce tenant isolation

Answer

Document-level security (DLS) with a tenant identifier field provides logical isolation within a shared index, balancing cost efficiency with access control.

ElasticSearch Practice Test

ElasticSearch Practice Test

ElasticSearch Professional Standards & Competencies 5