Exam Certified Platform Developer II topic 1 question 78 discussion

Trigger runs for all updated records in bulk and loops through each updated Account and calls AccountTriggerHelper.notifyExternalSystem(updatedAccount.Id) inside the loop. Every account update creates a separate future call. If more than 50 accounts are updated in one transaction, the code will hit the "System.LimitException: Too many future calls"

D is not of type limit exception. Hence, A.

D is the correct answer because notinyxternalSystem is not marked as @future. So it was fun pulling this apart to be able to read it. Yes, it is written incorrectly. The 'callout=true' is on the wrong line is missing @future. I filled in the gap knowing the intention. So let's look at the governor limits and see what hits first. SOQL Query: 100 per transaction Callouts: 100 per transaction @future: 50 per transaction The too many future callouts hits first, hence A. THAT is what this question is asking about. In reality, as is, I don't believe the code will even compile. Reference: https://developer.salesforce.com/docs/atlas.en-us.salesforce_app_limits_cheatsheet.meta/salesforce_app_limits_cheatsheet/salesforce_app_limits_platform_apexgov.htm

if the syntax for annotation is fixed to @future(callout=true) then the answer is A - SOQL is used in future so it's a different transaction with a separate 200 limit - 100 callouts again from single transaction, not an issue and the winner is future invocation , which could be only 50

So it was fun pulling this apart to be able to read it. Yes, it is written incorrectly. The 'callout=true' is on the wrong line is missing @future. I filled in the gap knowing the intention. So let's look at the governor limits and see what hits first. SOQL Query: 100 per transaction Callouts: 100 per transaction @future: 50 per transaction The too many future callouts hits first, hence A. THAT is what this question is asking about. In reality, as is, I don't believe the code will even compile. Reference: https://developer.salesforce.com/docs/atlas.en-us.salesforce_app_limits_cheatsheet.meta/salesforce_app_limits_cheatsheet/salesforce_app_limits_platform_apexgov.htm

It has been tested and the correct answer is D.

https://help.salesforce.com/s/articleView?id=000330691&type=1

B Because without implementing Database.AllowCallouts callout limit is 0 https://salesforce.stackexchange.com/questions/31859/too-many-callouts-1-in-salesforce-batch

This question is confusing because it's not even a valid code. But if we stick to the question, it should be A since D is not a LimitException.

notinyxternalSystem is not marked as @future. 'Callout from triggers are currently not supported' error will occure. https://help.salesforce.com/s/articleView?id=000330691&type=1

Too many future calls limit (per transaction): 50 will be fired before the other ones.

D is correct answer