New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Blue Prism AD01 Exam - Topic 2 Question 76 Discussion

Actual exam question for Blue Prism's AD01 exam
Question #: 76
Topic #: 2
[All AD01 Questions]

Please refer to the exhibit.

The Developer is using the basic Blue Prism Process Templates

What is wrong with how this Main Page is handling exceptions''

Show Suggested Answer Hide Answer
Suggested Answer: C

Exception Handling Best Practices:

Proper exception handling involves not only recovering from an error but also ensuring the system is ready for subsequent operations.

This typically includes resetting the application or any global data to a known good state.

Issue in the Main Page:

In the provided diagram, the flow directly connects the Recover stage to the Resume stage without any intermediate logic.

This is problematic because the system might be left in an inconsistent state after an error.

Required Logic:

Implement logic between the Recover and Resume stages to reset the application or any relevant data.

This ensures that after handling an exception, the system is in a known good state and can continue processing new items reliably.


Blue Prism documentation on best practices for exception handling and process design.

by Deeanna at Aug 24, 2024, 11:34 PM

Limited Time Offer

25%

Off

Get Premium AD01 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Gerry
3 months ago
Yeah, I agree with B, can't just skip exception handling logic.
upvoted 0 times
...
Andra
4 months ago
Wait, are we really saying D is a good idea? That seems risky!
upvoted 0 times
...
Pearly
4 months ago
A is misleading, there's definitely room for improvement.
upvoted 0 times
...
Brice
4 months ago
I think C makes a lot of sense too, resetting the app is crucial.
upvoted 0 times
...
Lenny
4 months ago
B is definitely the issue here, no consecutive exception logic!
upvoted 0 times
...
Jutta
5 months ago
I’m leaning towards option D, but I’m not entirely confident that exceptions should only be handled in sub-pages.
upvoted 0 times
...
Winfred
5 months ago
I feel like I’ve seen a question about consecutive exception logic before, but I can’t recall if it was specifically about the Main Page.
upvoted 0 times
...
Catherin
5 months ago
I think option C sounds familiar; we practiced that there should be a reset logic between Recover and Resume stages.
upvoted 0 times
...
Dorothea
5 months ago
I remember we discussed that exception handling is crucial, but I'm not sure if the Main Page should have its own logic or if it should all be in the sub-pages.
upvoted 0 times
...
Harrison
5 months ago
Ah, I see what they're getting at. The exception handling could be improved to better reset the application for the next case. I've got an idea on how to approach that.
upvoted 0 times
...
Kristine
5 months ago
The key seems to be understanding how the exception logic should be structured. I'll focus on that and try to identify the right approach.
upvoted 0 times
...
Doretha
5 months ago
This looks like a tricky one, but I think I can figure it out if I take a close look at the process flow.
upvoted 0 times
...
Vinnie
5 months ago
Hmm, I'm a bit confused by the exception handling here. I'll need to review the best practices for Blue Prism Process Templates.
upvoted 0 times
...
Iesha
5 months ago
I remember we talked about pop-up blockers in class. I think enabling that could help prevent future malware infections.
upvoted 0 times
...
Cristen
1 year ago
I think the Main Page flow should adhere to the basic Process Template for better handling of exceptions.
upvoted 0 times
...
Leatha
1 year ago
I believe the Exception Block should be removed as per best practices.
upvoted 0 times
...
Helaine
2 years ago
I bet the developer who wrote this code is the same one who named their variables 'x' and 'y'.
upvoted 0 times
Angelo
1 year ago
B) The exception handling does not contain any consecutive exception logic
upvoted 0 times
...
Malcolm
1 year ago
A) The Main Page flow adheres to best practice in the basic Process Template
upvoted 0 times
...
...
Johanna
2 years ago
I agree, there should be logic to reset the application between Recover and Resume stages.
upvoted 0 times
...
Leatha
2 years ago
I think the exception handling is not correct in the Main Page.
upvoted 0 times
...
Kayleigh
2 years ago
Ah, the age-old question of where to put the exception logic. I say we just throw the whole thing out and start over!
upvoted 0 times
Staci
1 year ago
But shouldn't there be logic to reset the application between Recover and Resume stages?
upvoted 0 times
...
Cherry
2 years ago
I think the exception handling should be in the sub-pages.
upvoted 0 times
...
...
Florinda
2 years ago
A is definitely wrong. This is not following best practices for exception handling.
upvoted 0 times
...
Willis
2 years ago
D seems like a valid option too. Handling exceptions in the sub-pages could be a better approach.
upvoted 0 times
Karon
1 year ago
C) Between the Recover and Resume stages there should be logic to reset the application ready for the next case
upvoted 0 times
...
Leeann
1 year ago
B) The exception handling does not contain any consecutive exception logic
upvoted 0 times
...
Lonny
1 year ago
A) The Main Page flow adheres to best practice in the basic Process Template
upvoted 0 times
...
...
Billy
2 years ago
I think the correct answer is C. The exception handling should include logic to reset the application before resuming the process.
upvoted 0 times
Mitsue
1 year ago
Thanks for clarifying, I see now. C makes sense for handling exceptions.
upvoted 0 times
...
Felix
1 year ago
No, it's actually C. The application needs to be reset between Recover and Resume stages.
upvoted 0 times
...
Ashanti
2 years ago
I think it's B. The exception handling should have consecutive logic.
upvoted 0 times
...
Percy
2 years ago
Agreed, C is the correct answer. The application needs to be reset before moving on.
upvoted 0 times
...
...

Save Cancel