Test your InfluxDB knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
Why is understanding tag/field design upfront especially important in InfluxDB, compared to adding an index to a relational database table after the fact?
Questions in this quiz
Why is understanding tag/field design upfront especially important in InfluxDB, compared to adding an index to a relational database table after the fact?
What is InfluxDB's "bucket" concept in InfluxDB 2.x, and how does it relate to the older 1.x concepts of "database" and "retention policy"?
Why might a team choose a purpose-built time-series database like InfluxDB over storing timestamped metrics in a general-purpose relational database?
What does the `aggregateWindow()` function commonly do in a Flux query pipeline?
What is a "point" in InfluxDB's data model?
What is Flux, in the context of InfluxDB (particularly InfluxDB 2.x)?
Why might writing extremely high-frequency data (e.g. millions of points per second) into InfluxDB benefit from batching writes rather than sending one HTTP write request per individual point?
What does it mean that field values in InfluxDB are "not indexed," and what is the practical query-performance consequence of filtering on a field value versus a tag value?
What is the difference between a "tag" and a "field" in InfluxDB's data model?
What is InfluxDB, at a high level?
What is "line protocol" in InfluxDB?
How would you write a basic Flux query to select data from a bucket called "metrics" over the last hour?