Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Blue Prism Exam AD01 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.

Contribute your Thoughts:

Cristen
3 months ago
I think the Main Page flow should adhere to the basic Process Template for better handling of exceptions.
upvoted 0 times
...
Leatha
3 months ago
I believe the Exception Block should be removed as per best practices.
upvoted 0 times
...
Helaine
3 months ago
I bet the developer who wrote this code is the same one who named their variables 'x' and 'y'.
upvoted 0 times
Angelo
2 months ago
B) The exception handling does not contain any consecutive exception logic
upvoted 0 times
...
Malcolm
3 months ago
A) The Main Page flow adheres to best practice in the basic Process Template
upvoted 0 times
...
...
Johanna
3 months ago
I agree, there should be logic to reset the application between Recover and Resume stages.
upvoted 0 times
...
Leatha
3 months ago
I think the exception handling is not correct in the Main Page.
upvoted 0 times
...
Kayleigh
3 months 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
3 months ago
But shouldn't there be logic to reset the application between Recover and Resume stages?
upvoted 0 times
...
Cherry
3 months ago
I think the exception handling should be in the sub-pages.
upvoted 0 times
...
...
Florinda
3 months ago
A is definitely wrong. This is not following best practices for exception handling.
upvoted 0 times
...
Willis
4 months ago
D seems like a valid option too. Handling exceptions in the sub-pages could be a better approach.
upvoted 0 times
Karon
2 months 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
2 months ago
B) The exception handling does not contain any consecutive exception logic
upvoted 0 times
...
Lonny
2 months ago
A) The Main Page flow adheres to best practice in the basic Process Template
upvoted 0 times
...
...
Billy
4 months 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
2 months ago
Thanks for clarifying, I see now. C makes sense for handling exceptions.
upvoted 0 times
...
Felix
2 months ago
No, it's actually C. The application needs to be reset between Recover and Resume stages.
upvoted 0 times
...
Ashanti
3 months ago
I think it's B. The exception handling should have consecutive logic.
upvoted 0 times
...
Percy
3 months ago
Agreed, C is the correct answer. The application needs to be reset before moving on.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77