The correct answer is that the trigger is making API calls in a loop, which causes governor limit issues. Each synchronous call to the Einstein prediction API inside a trigger that iterates over multiple new leads consumes one of the 100 available callouts per transaction, and when that limit is exceeded, Salesforce throws a 'Too many SOQL queries' error—even though the real culprit is the callout count, not SOQL queries. On the Salesforce AI Associate exam, this question tests your understanding of how synchronous callouts interact with trigger bulkification and governor limits; a common trap is assuming the error message is literal, when in fact it often masks a callout limit breach. Remember the memory tip: "Looping callouts burn your limit—batch them or go async to win it."
AI Associate AI Capabilities in CRM Practice Question
This AI Associate practice question tests your understanding of ai capabilities in crm. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Apex Trigger:
trigger LeadScoringTrigger on Lead (after insert) {
for(Lead l : Trigger.new) {
l.Score__c = Einstein_Prediction_API.predict('Lead_Score', l.Id);
}
}
Refer to the exhibit. A developer wrote a trigger to call an Einstein prediction API on lead insert. When new leads are created, the trigger fails with a 'Too many SOQL queries' error. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The trigger is making API calls in a loop, causing governor limit issues
Option C is correct because the trigger is making synchronous API calls to the Einstein prediction service inside a loop that iterates over each new lead. Each API call counts against the 'Number of callouts' governor limit (default 100 per transaction), and if more leads are inserted than the limit allows, the transaction fails with a 'Too many SOQL queries' error—though the error message is misleading, the root cause is exceeding the callout limit, not SOQL queries. The trigger should batch the API calls or use asynchronous processing to stay within limits.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
The trigger is executed before the lead is saved
Why it's wrong here
It's after insert, so lead is saved.
✗
The trigger is querying a related object without an index
Why it's wrong here
No query is shown; the trigger uses API call.
✓
The trigger is making API calls in a loop, causing governor limit issues
Why this is correct
Looping API calls can exceed limits.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The Score__c field is not writeable
Why it's wrong here
The error is not about field writeability.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Salesforce often tests the misconception that 'Too many SOQL queries' always means too many SOQL queries, but in this context it actually masks a callout limit issue—candidates may overlook the fact that API calls count against a different governor limit that produces the same error message.
Trap categories for this question
Command / output trap
No query is shown; the trigger uses API call.
Detailed technical explanation
How to think about this question
Under the hood, Salesforce enforces a 'Number of callouts' limit of 100 per synchronous transaction, and each Einstein API call consumes one of those callouts. If the trigger loops over a collection of leads and makes a separate HTTP callout for each, inserting more than 100 leads will hit the limit. A common real-world scenario is using a batch class or Queueable to process predictions asynchronously, or collecting lead IDs and making a single batch API call to Einstein, which avoids the per-record callout limit.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the AI Associate exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
AI Capabilities in CRM — This question tests AI Capabilities in CRM — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: The trigger is making API calls in a loop, causing governor limit issues — Option C is correct because the trigger is making synchronous API calls to the Einstein prediction service inside a loop that iterates over each new lead. Each API call counts against the 'Number of callouts' governor limit (default 100 per transaction), and if more leads are inserted than the limit allows, the transaction fails with a 'Too many SOQL queries' error—though the error message is misleading, the root cause is exceeding the callout limit, not SOQL queries. The trigger should batch the API calls or use asynchronous processing to stay within limits.
What should I do if I get this AI Associate question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AI Associate practice question is part of Courseiva's free Salesforce certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AI Associate exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.