A large enterprise is using Einstein Lead Scoring and notices that the model score is not updating for leads created via a web-to-lead form. The leads have all required fields populated. The admin has verified that the model is active and the data source includes the Lead object. What could be causing the score to remain static?
Einstein requires a critical mass of scored records to calibrate the model before scoring new leads.
Why this answer
Einstein Lead Scoring requires a minimum number of scored leads (typically 500) before it begins scoring new leads. Until that threshold is met, the model remains in a 'training' or 'pending' state and will not update scores for any leads, including those from web-to-lead forms. The admin has confirmed the model is active and the Lead object is included, so the most likely cause is that the model has not yet processed enough leads to start scoring.
Exam trap
Salesforce often tests the concept that Einstein AI models require a minimum data threshold before they become operational, and candidates mistakenly assume that an 'active' model immediately scores all leads, ignoring the training/pending state requirement.
How to eliminate wrong answers
Option A is wrong because the data source for Einstein Lead Scoring includes all leads in the Lead object by default; there is no option to exclude leads based on creation method (e.g., web-to-lead). Option B is wrong because Einstein AI fully supports leads created via web-to-lead forms; there is no restriction on lead source. Option C is wrong because the admin has already verified that the model is active, so the model is not in an 'inactive' or 'not yet activated' state.