When debugging a consumer module, how do we ensure that the execution stops at the breakpoints defined in the producer module?
A) We just need to set breakpoints in the producer module. Execution will stop at its breakpoints automatically.
B) We also need to start the debugger on the producer module.
C) Nothing, just leave Service Studio open.
D) At the producer, set the Input Module property to the consumer module.
I have no idea what this question is asking.
Hello.
You are placing a lot of questions. Maybe you should take more time to read the material.
That question is about this 3 minute content. it is basic training.
https://learn.outsystems.com/training/journeys/web-developer-662/debugging-apps/o11/202
Hi @TravelerAutumn ,
Have you checked the below posts:
https://www.outsystems.com/forums/discussion/89678/unable-to-debug-producer-and-selected-entry-module-not-saving/
https://success.outsystems.com/documentation/11/debugging_apps/
Regards,
Manish Jawla
Hi,
Copy-pasting exam practice questions here on the forum is NOT the most effective way to get familiar with OutSystems, nor the best use of the community's time.
Most of these questions can be answered by going through the official OutSystems training materials. That’s where you’ll gain the foundational understanding needed for both the exam and real-world development.
Even if you do post a question, I would expect you to share your own thoughts on the possible answer and explain your reasoning. That shows you’ve made an effort to understand the topic, instead of relying on the community to do the work for you.
Memorising answers might get you through a certification, but it won’t make you a better developer. If you truly have no idea how to approach a question, that’s a clear signal to pause and invest time in the documentation, training, and platform fundamentals.
Put in the work now, and it will pay off later, not just in passing the exam, but in building real solutions with confidence.
Daniel
Hi @TravelerAutumn,
Option D - Correct
If you're debugging a producer module (like a core module or library), and it's being called from a consumer module (like a UI or orchestration module), then
You must set the "Entry Module" of the producer to the consumer module.
This tells the debugger to trace execution starting from the consumer, so breakpoints in the producer will be hit correctly.