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 Exam AD01 Topic 1 Question 92 Discussion

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

A Blue Prism Process attempts to call an Action named 'Get Nasdaq Data' however it keeps causing the Process to fail

The Developer attempts to recreate the problem in the Development environment and discovers the following Exception is thrown:

Which of the following responses would explain the reason for this exception bang thrown?

Show Suggested Answer Hide Answer
Suggested Answer: C

Understanding the Exception:

The error message indicates that the read stage 'Read Nasdaq Data' failed because it was not connected.

This suggests that the business object might not be correctly attached to the application or not launched.

Analyzing Possible Causes:

Option A: Internal errors do not always indicate a Blue Prism product problem; they can also result from configuration issues.

Option B: If the action was not published, the error would likely indicate that the action could not be found, not an attachment issue.

Option D: If the action no longer existed, the process would not be able to call it, and the error would reflect that the action was missing.

Option E: The process flow shows the stages are connected, and an unconnected stage would not specifically cause an attachment error.

Most Likely Cause:

Option C is the most likely reason. If the business object is not associated with the application (either by launching or attaching to it), the action cannot be performed because Blue Prism does not have the necessary context to interact with the application.


Blue Prism Developer Documentation: Exception Handling and Troubleshooting

Blue Prism Training Material on Application Modelling and Object Association

Contribute your Thoughts:

Wait, there's a 'Read Nasdaq Data' stage? I thought this was all about 'Get Nasdaq Data'! Blue Prism needs to work on their naming conventions.
upvoted 0 times
...
Stevie
4 days ago
Haha, I bet the dev who wrote this code was having a bad day. Sounds like a classic case of 'forgot to save my changes' to me!
upvoted 0 times
Renea
1 days ago
B) The 'Get Nasdaq Data' Action is not published
upvoted 0 times
...
...
Thad
13 days ago
I'm going with B. The 'Get Nasdaq Data' Action is not published, so the Process can't access it. That's a pretty common issue, right?
upvoted 0 times
Brittni
24 hours ago
Yes, that's a common issue. Make sure to publish the 'Get Nasdaq Data' Action before using it in the Process.
upvoted 0 times
...
...
Georgene
17 days ago
I think contacting the Blue Prism support team as mentioned in option A could also help in resolving the issue
upvoted 0 times
...
Elly
24 days ago
D seems more likely to me. If the 'Get Nasdaq Data' Action no longer exists in the Business Object, then the Process would naturally fail to find it.
upvoted 0 times
...
Mattie
28 days ago
I believe option B could also be a possible reason for the exception
upvoted 0 times
...
Ettie
28 days ago
I think the correct answer is C. The Business Object containing the Action has not been associated with the application by either launching it or attaching to it. This explains why the Action is not found and the exception is thrown.
upvoted 0 times
Talia
7 days ago
The correct answer is C. The Business Object containing the Action has not been associated with the application by either launching it or attaching to it.
upvoted 0 times
...
...
Mitsue
1 months ago
I agree with Hubert, the Business Object needs to be associated with the application
upvoted 0 times
...
Hubert
2 months ago
I think the reason for the exception is option C
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