Blue Prism AD01 Exam - Topic 1 Question 85 Discussion

Actual exam question for Blue Prism's AD01 exam

Question #: 85
Topic #: 1

[All AD01 Questions]

Look at this flow diagram from the Main Page of a process in Process Studio:

Thinking about the standard Blue Prism Process Templates, what is wrong with how this Mam Page is handling exceptions?

AThere is nothing wrong with the Main Page flow shown in the image, it is a copy of Blue Prism's standard Process Template.

BThe Exception Block in the image should be extended to cover all stages in the flow rather than just 4 sub-pages.

CIt would be better to remove the Exception Block and recover, resume logic, and instead handle any exceptions in the sub-pages. Flag data items could instead be passed up as output parameters from the sub-pages informing the Main Page flow if an exception has occurred.

DThe exception handling in the image does not contain any concurrent exception logic. This means there is nothing stopping every item in the Work Queue being marked with the exact same System Exception.

EBetween the Recover and Resume stages there should be logic to reset the application ready for the next case to be worked For example, this could call the Close Down and Start Up pages.

Show Suggested Answer

Suggested Answer: B, E

Tagging Exception Items:

By calling the Exception Stage details and tagging them to the item before marking it as an exception, it ensures that detailed information about the exception is captured and can be viewed later. This helps in identifying the cause of the exception and provides valuable context.

Stage Logging:

Enabling stage logging within each exception properties ensures that all exception details are logged. This allows the Process Controller to view detailed exception information from the session logs, providing a comprehensive view of what went wrong.

Benefits:

These two approaches ensure that exception details are both tagged to the work queue items and logged in the session logs, making it easier for the Process Controller to review and analyze exceptions from different interfaces within Blue Prism.

Blue Prism documentation on exception handling, tagging, and logging.

by Kami at Dec 08, 2024, 12:59 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Marjory

4 months ago

I thought the reset logic was already included in the standard templates?

upvoted 0 times

...

Madelyn

4 months ago

Yeah, the lack of concurrent exception logic is a big issue here.

upvoted 0 times

...

Yen

4 months ago

Wait, are we sure removing the Exception Block is a good idea?

upvoted 0 times

...

Rocco

4 months ago

I agree, extending it makes total sense!

upvoted 0 times

...

Kendra

5 months ago

The Exception Block should definitely cover all stages, not just 4.

upvoted 0 times

...

Rosio

5 months ago

I think option E makes sense about resetting the application, but I can't recall if that's standard practice in Blue Prism templates.

upvoted 0 times

...

Frank

5 months ago

I feel like the flow diagram is missing some concurrent exception logic, which could lead to issues. Is that what option D is suggesting?

upvoted 0 times

...

Craig

5 months ago

I remember a practice question that mentioned handling exceptions at the sub-page level. Maybe option C is a good approach?

upvoted 0 times

...

Heike

5 months ago

I think the Exception Block should cover all stages, but I'm not entirely sure if it needs to be extended to all sub-pages.

upvoted 0 times

...

Gerardo

5 months ago

Option E seems like a good suggestion. Resetting the application between Recover and Resume is an important step I hadn't considered.

upvoted 0 times

...

Hester

5 months ago

Option D is interesting. The lack of concurrent exception logic could definitely lead to issues. I'll need to think that one through.

upvoted 0 times

...

Donte

5 months ago

I think option C makes the most sense. Handling exceptions in the sub-pages and passing up flags seems like a cleaner approach than the Exception Block.

upvoted 0 times

...

Dominga

5 months ago

The image shows a standard Blue Prism process template, so I'm not sure there's anything wrong with it. I might just go with option A.

upvoted 0 times

...

Vincenza

6 months ago

Hmm, this looks like a tricky one. I'll need to carefully analyze the flow diagram and the options to figure out what's wrong with the exception handling.

upvoted 0 times

...

Brittni

10 months ago

This question is like a game of 'Spot the Exception' - the more you look, the more you find! I hope the real exam isn't this much of a minefield.

upvoted 0 times

Kanisha

9 months ago

E) Between the Recover and Resume stages there should be logic to reset the application ready for the next case to be worked For example, this could call the Close Down and Start Up pages.

upvoted 0 times

...

Rodney

9 months ago

C) It would be better to remove the Exception Block and recover, resume logic, and instead handle any exceptions in the sub-pages. Flag data items could instead be passed up as output parameters from the sub-pages informing the Main Page flow if an exception has occurred.

upvoted 0 times

...

Stefany

9 months ago

B) The Exception Block in the image should be extended to cover all stages in the flow rather than just 4 sub-pages.

upvoted 0 times

...

Jamey

11 months ago

Between Recover and Resume, don't forget to reset the application. You don't want the next case to inherit the mess from the previous one. Maybe a trip to the 'Close Down and Start Up' pages would do the trick.

upvoted 0 times

Demetra

9 months ago

E) Between the Recover and Resume stages there should be logic to reset the application ready for the next case to be worked. For example, this could call the Close Down and Start Up pages.

upvoted 0 times

...

Raul

10 months ago

upvoted 0 times

...

Mel

11 months ago

Wait, there's no concurrent exception logic? That's just asking for trouble. Every item in the Work Queue could end up with the same System Exception. Yikes!

upvoted 0 times

Lai

10 months ago

D) The exception handling in the image does not contain any concurrent exception logic. This means there is nothing stopping every item in the Work Queue being marked with the exact same System Exception.

upvoted 0 times

...

Frank

10 months ago

upvoted 0 times

...

Arlie

11 months ago

B) The Exception Block in the image should be extended to cover all stages in the flow rather than just 4 sub-pages.

upvoted 0 times

...

Michael

11 months ago

I think option C is the way to go. Handling exceptions in the sub-pages and passing up relevant data items is a better approach than the centralized Exception Block.

upvoted 0 times

Aja

10 months ago

Yes, that could provide a more robust exception handling process.

upvoted 0 times

...

Novella

10 months ago

That's a good point. Maybe a combination of handling exceptions in sub-pages and adding concurrent exception logic would be the best approach.

upvoted 0 times

...

Laquanda

11 months ago

But what about the concurrent exception logic mentioned in option D?

upvoted 0 times

...

Lynelle

11 months ago

I agree, handling exceptions in the sub-pages seems more efficient.

upvoted 0 times

...

Dana

11 months ago

The main issue here seems to be the limited scope of the Exception Block. Covering just 4 sub-pages is not enough, it should be extended to handle exceptions across the entire process flow.

upvoted 0 times