Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Blue Prism AD01 Exam - Topic 2 Question 75 Discussion

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

The Process Controller needs to be able to view Exception items from both the Work Queue screen within the Control room, and from the Session Logs According to best practice, which TWO options would the Developer recommend?

Show Suggested Answer Hide 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.

Contribute your Thoughts:

0/2000 characters
Kenneth
4 months ago
I thought A was the go-to for filtering exceptions?
upvoted 0 times
...
Ollie
4 months ago
C is definitely a good choice too, looping helps.
upvoted 0 times
...
Derick
4 months ago
Wait, are we sure about option D? Seems a bit off.
upvoted 0 times
...
Laurene
4 months ago
Totally agree with B! Tagging is super important.
upvoted 0 times
...
Amie
5 months ago
I think options B and E are the best practices here.
upvoted 0 times
...
Kathrine
5 months ago
I feel like enabling Stage logging in Exception Properties is crucial, but I’m not confident if it’s one of the top two recommendations.
upvoted 0 times
...
Tori
5 months ago
Looping through Work Queue items to tag them sounds familiar, but I wonder if that might be too complex for what they need.
upvoted 0 times
...
Carman
5 months ago
I think using the column filters in the Process Log settings was mentioned in a practice question, but I can't recall if it was specifically for viewing exceptions.
upvoted 0 times
...
Lilli
5 months ago
I remember we discussed the importance of tagging Exception details, but I'm not sure if it's better to do it before or after marking the item as an exception.
upvoted 0 times
...
Myra
5 months ago
I'm a bit unsure about some of these options. I'll need to do some research on the best practices for handling exceptions in Blue Prism before I can make a solid recommendation.
upvoted 0 times
...
Mollie
5 months ago
I'm feeling pretty confident about this one. I think the best approach is to use the column filters in the Audit settings, as well as ensure that the stage logging is enabled for each exception. That should give the process controller the visibility they need.
upvoted 0 times
...
Ivette
5 months ago
Okay, I've got this. The key is to focus on the requirement to view exceptions from both the Work Queue and the Session Logs. Options A and E seem like the best choices to address that.
upvoted 0 times
...
Antonio
5 months ago
Hmm, I'm a bit confused by the wording of this question. I'll need to re-read it a few times and make sure I understand the requirements before I start answering.
upvoted 0 times
...
Tamekia
6 months ago
This looks like a tricky question, but I think I can tackle it. I'll need to carefully review the options and think about the best practices for handling exceptions in Blue Prism.
upvoted 0 times
...
Kirk
6 months ago
No problem, I've got this. I've used Trivy before, so I know the basic workflow. I'll just run the scan, identify the problematic images, and then delete the pods using kubectl. Should be a quick and easy task.
upvoted 0 times
...
Lili
6 months ago
I might be confused, but I don't remember us discussing user views in detail. Isn't it more about overall database management, like in option D?
upvoted 0 times
...
Ronny
6 months ago
I feel pretty confident about this one. The details provided, like the aqueous chloride solution and sensitized stainless steel, point strongly to chloride stress corrosion cracking as the right answer. I'll select option C and move on.
upvoted 0 times
...
Lavera
2 years ago
I believe option B and D could also be useful in tagging and identifying exception items.
upvoted 0 times
...
Sharika
2 years ago
I agree with Letha, having stage logging enabled and using column filters would be helpful.
upvoted 0 times
...
Timothy
2 years ago
I don't know, man. This is starting to sound like a lot of work. Maybe we should just ask the Process Controller to juggle the exception items while riding a unicycle. That would be a real show-stopper!
upvoted 0 times
Micheal
2 years ago
C) Loop through the Work Queue items in Exception and tag with the Exception Details
upvoted 0 times
...
Elenora
2 years ago
B) Call the Exception Stage details and tag them to the Item prior to Mark Item as Exception
upvoted 0 times
...
Marica
2 years ago
A) Use the column filters available within Blue Prism Settings > Audit > Process Log settings
upvoted 0 times
...
...
Tora
2 years ago
Woah, hold up! Why are we even bothering with all these options? Let's just use the 'Scan Processes' feature and call it a day. D is the way to go, my dudes!
upvoted 0 times
Tom
2 years ago
True, combining both options could provide a more comprehensive view of Exception items.
upvoted 0 times
...
Leslie
2 years ago
That's a good point, we should consider enabling Stage logging as well.
upvoted 0 times
...
Loreta
2 years ago
But wouldn't it be better to also enable Stage logging for more detailed information?
upvoted 0 times
...
Krissy
2 years ago
I agree, using the 'Scan Processes' feature seems like the most efficient option.
upvoted 0 times
...
...
Letha
2 years ago
I think option A and E are the best recommendations.
upvoted 0 times
...
Lashunda
2 years ago
Hmm, I'm not sure about that. Shouldn't we be able to view the exception details directly from the Work Queue? I'd go with options B and C to handle that.
upvoted 0 times
Sean
2 years ago
I agree, option C would also be helpful to loop through the Work Queue items and tag them with Exception details.
upvoted 0 times
...
Erasmo
2 years ago
I think option B would be the best choice to tag the Exception details before marking it.
upvoted 0 times
...
...
Domingo
2 years ago
I think options A and E are the way to go. The column filters and the stage logging will make it easy to view the exceptions from both the Work Queue and the Session Logs.
upvoted 0 times
Angella
2 years ago
That sounds like a good plan. It will definitely help the Process Controller view the Exception items easily.
upvoted 0 times
...
Jesusa
2 years ago
E) Ensure that the Stage logging is enabled within each Exception Properties
upvoted 0 times
...
German
2 years ago
A) Use the column filters available within Blue Prism Settings > Audit > Process Log settings
upvoted 0 times
...
...

Save Cancel