Salesforce Exam Platform Developer II Topic 7 Question 86 Discussion

Actual exam question for Salesforce's Platform Developer II exam

Question #: 86
Topic #: 7

[All Platform Developer II Questions]

A developer creates an application event that has triggered an infinite loop.

What may have caused this problem?

AThe event is fired from a custom renderer.

BThe event has multiple handlers registered in the project.

CThe event handler calls a trigger.

DAn event is fired 'ontouchend'' and is unhandled.

Show Suggested Answer

Suggested Answer: B

by Jose at Mar 21, 2024, 07:03 PM

Limited Time Offer

25%

Off

Get Premium Platform Developer II Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Donette

2 months ago

Wait, what if the Donettent handler is just an endless loop in itself? That would be a real brainteaser!

upvoted 0 times

Rolland

14 days ago

C) The event handler calls a trigger.

upvoted 0 times

...

Terrilyn

25 days ago

C) The event handler calls a trigger.

upvoted 0 times

...

Raelene

29 days ago

B) The event has multiple handlers registered in the project.

upvoted 0 times

...

Martha

2 months ago

A) The event is fired from a custom renderer.

upvoted 0 times

...

Sheridan

2 months ago

B) The event has multiple handlers registered in the project.

upvoted 0 times

...

Kathrine

2 months ago

A) The event is fired from a custom renderer.

upvoted 0 times

...

Melissia

2 months ago

You know, I've heard of devs creating custom renderers that fire off events like crazy. Option A might be the culprit here.

upvoted 0 times

...

Laurel

2 months ago

Haha, unhandled 'ontouchend' event? That's a good one! Sounds like a rookie mistake to me.

upvoted 0 times

Mertie

22 days ago

User 4: Gotta be careful with those event handlers.

upvoted 0 times

...

Jarvis

1 months ago

User 3: I've seen that happen before, always causes trouble.

upvoted 0 times

...

Noel

1 months ago

User 2: Definitely, rookie move for sure.

upvoted 0 times

...

Jade

2 months ago

User 1: Yeah, that's a classic mistake.

upvoted 0 times

...

Latonia

3 months ago

Hmm, I'd say it's definitely the event handler calling a trigger. That's a classic recipe for an infinite loop disaster!

upvoted 0 times

Clarence

1 months ago

Yeah, that's a sure way to get stuck in an infinite loop. Better fix that quickly!

upvoted 0 times

...

Maile

2 months ago

Oh no, that's a common mistake. The event handler should never call a trigger.

upvoted 0 times

...

Hershel

3 months ago

Oh dear, an infinite loop? That's a tricky one. I'm guessing it might be option B - too many handlers registered for the event.

upvoted 0 times

Lizbeth

1 months ago

Maybe the event being fired 'ontouchend' and being unhandled is causing the issue as well.

upvoted 0 times

...

Cecily

1 months ago

True, calling a trigger in the event handler could also lead to an infinite loop.

upvoted 0 times

...

Vicky

2 months ago

But it could also be that the event is fired from a custom renderer, that's another possibility.

upvoted 0 times

...

Marvel

2 months ago

I think you might be right, having multiple handlers could definitely cause an infinite loop.

upvoted 0 times

...

Pete

3 months ago

I think it could also be option D, firing an event 'ontouchend' that is unhandled.

upvoted 0 times

...

Tonja

3 months ago

I disagree, I believe the issue is with option B, having multiple handlers registered.

upvoted 0 times

...

Blythe

3 months ago

I think the problem may be caused by option C, the event handler calling a trigger.

upvoted 0 times

...