Guide-linked quiz · Hard Level
XGBoost Algorithm Quiz
Review XGBoost's additive tree boosting, objective and regularization choices, tuning interactions, missing data and fair evaluation.
Question 1 of 8
How does gradient boosting generally build its predictor?
Preview every question8 questions
Answers and explanations appear as you take the quiz.
- How does gradient boosting generally build its predictor?
- By averaging independent trees with unchanged fitting targets
- By replacing earlier trees entirely at every round
- By adding learners sequentially to improve the current objective
- By optimizing a single full-depth tree without additive updates
- Which parameter pair captures the tradeoff between the size of each additive update and how many updates are made?
- Maximum depth and minimum child weight
- Learning rate and number of boosting rounds
- Column subsampling and row subsampling
- Leaf regularization and split-gain threshold
- What role do complexity penalties and tree limits play?
- They guarantee probabilities are calibrated on every population
- They determine the ground-truth labels before fitting
- They replace the need to measure held-out performance
- They constrain model complexity and can reduce overfitting
- Why does early stopping require a separate final test evaluation?
- The monitored validation metric participates in choosing an iteration
- Early stopping makes the validation set unused during selection
- Stopping rounds should be chosen directly from final-test outcomes
- A chosen stopping point guarantees performance on any later population
- Which claim about XGBoost on tabular data is justified?
- It always beats every baseline
- It requires no data split
- It can be a strong candidate, but performance depends on the task and evaluation
- It guarantees production accuracy from a leaderboard result
- Why record the library version and objective with a trained model?
- The algorithm name alone fixes all defaults across releases
- Behavior and available options can vary by version and task setup
- An objective replaces the need to record the data split
- Native missing-value support establishes what every missing value means
- When are row or feature subsampling settings most defensibly chosen?
- By assuming any subsampling improves accuracy
- By selecting against final test labels
- By setting them without considering data size
- By measuring them within the validation protocol
- At training and inference time, what should remain consistent about the model inputs?
- Keep feature and missing-value conventions consistent with training
- Assign new category codes independently after deployment
- Recompute learned feature transformations separately for each inference batch without validation
- Change the meaning of missing values while retaining the same model artifact
Keep testing yourself
More quizzes picked for your level.