Which format is commonly used for efficient, columnar storage of training data?
Why B is the answer
Apache Parquet
Columnar formats such as Parquet read faster and compress well.
In detail
- Parquet is an efficient, columnar format.
- Columnar files also compress well.
Use case
An illustrative scenario, not a real incident.
A team stores training data as Parquet, so a job reads only the columns it needs.
See it in different ways
mindmap
root((Data preparation))
Missing values
Impute
Categories
One-hot encoding
Ranges
Scaling
Imbalance
Resampling
Class weights
Leakage
Remove future dataflowchart TD
Q{"How is the data read?"}
Q -->|"A few columns at a time"| A0["Columnar, Parquet"]
Q -->|"Whole rows"| A1["Row-based format"]Key point: Parquet is efficient columnar storage.
Why the other options are wrong
- A. Pickle files
- Pickle is not a columnar format.
- C. CSV with no compression
- CSV is row based, and is larger.
- D. A single JSON array
- A JSON array is row based.