UiPath Exam UiPath-ARDv1 Topic 9 Question 75 Discussion

Actual exam question for UiPath's UiPath-ARDv1 exam

Question #: 75
Topic #: 9

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?

ALevel: Warn
Message: exception.Message + 'at' + exception.Source

BLevel: Error
Message: 'Exception occurred at' + exception.Source

CLevel: Fatal
Message: exception.Message

DLevel: Info
Message: 'Application Exception at' + exception.Source

Show Suggested 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

2 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

Rana

2 days ago

C: D) Level: Info Message: 'Application Exception at' + exception.Source

upvoted 0 times

...

Maryln

15 days ago

B: I think that sounds like a good plan, let's try it out.

upvoted 0 times

...

Brett

1 months ago

A: B) Level: Error Message: 'Exception occurred at' + exception.Source

upvoted 0 times

...

Hyun

2 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

2 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

26 days ago

Yeah, I think Option B is the best choice for clear and concise log messages.

upvoted 0 times

...

Ezekiel

29 days ago

I agree, keeping it simple with just the error level and exception source is the way to go.

upvoted 0 times

...

Glenn

1 months ago

Yeah, Option B seems like the most straightforward choice.

upvoted 0 times

...

Hector

2 months ago

I agree, keeping it simple is always better.

upvoted 0 times

...

Dyan

2 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

2 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

...