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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

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

by Tonette at Oct 17, 2023, 10:52 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Nickolas
3 months ago
Forget the log level, I just want to know if the process can survive an exception by downing a cup of coffee and taking a 15-minute break.
upvoted 0 times
Kimbery
28 days ago
A: Let's hope the coffee break does the trick and the process survives the exception.
upvoted 0 times
...
Rana
1 months ago
C: D) Level: Info Message: 'Application Exception at' + exception.Source
upvoted 0 times
...
Maryln
2 months ago
B: I think that sounds like a good plan, let's try it out.
upvoted 0 times
...
Brett
2 months ago
A: B) Level: Error Message: 'Exception occurred at' + exception.Source
upvoted 0 times
...
...
Hyun
3 months ago
Option A all the way! Logging the exception message and source is the best way to ensure meaningful logs. UiPath knows what they're talking about.
upvoted 0 times
...
Giuseppe
3 months 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
Annamae
2 months ago
Yeah, I think Option B is the best choice for clear and concise log messages.
upvoted 0 times
...
Ezekiel
2 months ago
I agree, keeping it simple with just the error level and exception source is the way to go.
upvoted 0 times
...
Glenn
2 months ago
Yeah, Option B seems like the most straightforward choice.
upvoted 0 times
...
Hector
3 months ago
I agree, keeping it simple is always better.
upvoted 0 times
...
...
Dyan
3 months 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
3 months 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
4 months ago
I see your point, but I still think Level: Error is more appropriate for this scenario.
upvoted 0 times
...
Ilona
4 months 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
4 months 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