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

UiPath Exam UiPath-ARDv1 Topic 9 Question 75 Discussion

Actual exam question for UiPath's UiPath-ARDv1 exam
Question #: 75
Topic #: 9
[All UiPath-ARDv1 Questions]

A developer wants to ensure that a process they are developing includes coherent logs with meaningful log messages. During the execution of the process, an application exception is caught and stored in a local variable called exception.

Based on UiPath best practices, how should the Log Message activity in the Catch section of this exception be configured?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

Giuseppe
2 days ago
Haha, 'Application Exception at' sounds a bit too formal, don't you think? I'd keep it simple with Option B - Error level and the exception source.
upvoted 0 times
...
Dyan
5 days ago
Really? Fatal log level for an application exception? That's a bit overkill, don't you think? I'd go with Option B - Error level and a more concise message.
upvoted 0 times
...
Arthur
5 days ago
Level: Error and Message: exception.Message + \'at\' + exception.Source seems like the most appropriate choice to me. Providing the exception message along with the source is crucial for troubleshooting.
upvoted 0 times
...
Lang
13 days ago
I see your point, but I still think Level: Error is more appropriate for this scenario.
upvoted 0 times
...
Ilona
15 days ago
I disagree, I believe Level: Fatal and Message: exception.Message would be a better choice for the Log Message activity.
upvoted 0 times
...
Lang
17 days ago
I think the Log Message activity should be configured with Level: Error and Message: 'Exception occurred at' + exception.Source.
upvoted 0 times
...

Save Cancel