Learn to discuss precision, recall, F1, confusion matrix, and AUC-ROC in technical and non-technical contexts.
0 / 10 completed
1 / 10
A 'false positive' in a classification model means:
A false positive is a Type I error: the model incorrectly flagged a negative case as positive — for example, a spam filter marking a legitimate email as spam.
2 / 10
Recall (also called sensitivity) measures:
Recall = TP / (TP + FN). It measures how many of the actual positive cases the model successfully detected — critical when missing a positive case is costly.
3 / 10
The F1 score is:
F1 is the harmonic mean of precision and recall: 2*(P*R)/(P+R). It balances both metrics and is useful when classes are imbalanced.
4 / 10
AUC-ROC measures:
AUC-ROC (Area Under the ROC Curve) summarises model discrimination ability across all thresholds — an AUC of 0.5 is random, 1.0 is perfect.
5 / 10
Which phrase correctly describes a model with high recall and low precision?
High recall / low precision: the model catches nearly all actual positives (high recall) but also flags many negatives incorrectly (low precision — many false positives).
6 / 10
Review Comment: 'This model's precision is terrible – it's flagging almost every transaction as fraudulent. The recall seems okay, but the false positives are overwhelming our security team.' What does 'precision' in this context primarily indicate?
Precision focuses on the accuracy of the positive predictions a model makes. It measures how many of the transactions flagged as fraudulent were *actually* fraudulent – minimizing false positives is key. A low precision score means the model is making a lot of incorrect 'fraud' calls, even when it's correctly identifying genuine fraud.
7 / 10
Slack Message: 'Hey team, running some final checks on the new churn prediction model. The ROC curve shows a great AUC – around 0.85 – but we're seeing a recall of only 60%. We need to prioritize improving this.' What does a recall value of 60% suggest about the model's performance?
Recall (also known as sensitivity) measures the proportion of actual positive cases that the model correctly identifies. A recall of 60% means the model only successfully identified 60% of all customers who were predicted to churn – a significant number are being missed, indicating an opportunity for improvement.
8 / 10
PR Description: 'Implemented model evaluation metrics. AUC-ROC is 0.92, F1 score is 0.75, and Log Loss is 0.23. Further analysis needed to understand the trade-offs.' What does an F1 score of 0.75 primarily tell you about the model?
The F1 score harmonizes precision and recall into a single metric. A score of 0.75 indicates a moderate balance between the two – the model isn't exceptionally precise or highly sensitive, suggesting there's room for optimization in either direction to better suit the specific application.
9 / 10
Standup Update: 'I've been working on improving the fraud detection model. The AUC-ROC is now 0.88, but I'm still getting a lot of false positives – about 30% of our transactions are flagged as suspicious. We need to fine-tune the thresholds.' What action should be taken regarding the high false positive rate?
A high false positive rate means the model is incorrectly flagging legitimate transactions as suspicious. Increasing the prediction threshold will make the model more conservative in its predictions, reducing the number of false positives but potentially at the cost of some genuine fraud detection (decreasing recall).
10 / 10
Code Review Comment: 'This model has excellent recall – it catches almost all the bots. However, it's also flagging a huge number of legitimate users as suspicious. It's a classic trade-off.' Which statement best describes this situation?
This scenario highlights the inherent trade-off between recall and precision. High recall (catching almost all bots) comes at the expense of low precision (flagging many legitimate users). Understanding this balance is crucial for selecting a model that meets the specific needs of your application.
What will I practise in "Model Evaluation Language"?
This module focuses on ML Language — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this ML Language exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around ml language — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more ML Language exercises?
See the ML Language hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.