ExamTopics Logo
Mail Us[email protected]
Menu
Uipath Discussions
exam questions

Exam UiARD All Questions

View all questions & answers for the UiARD exam
Go to Exam

Exam UiARD topic 6 question 68 discussion

Actual exam question from UiPath 's UiARD
Question #: 5
Topic #: 6
[All UiARD 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?

  • A. Level: Warn -
    Message: exception.Message + "at" + exception.Source
  • B. Level: Error -
    Message: "Exception occurred at" + exception.Source
  • C. Level: Fatal -
    Message: exception.Message
  • D. Level: Info -
    Message: "Application Exception at" + exception.Source
Show Suggested Answer Hide Answer
Suggested Answer: A 🗳️
by Engineer24 at April 19, 2023, 1:23 p.m.

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Submit Cancel
Biero
3 months, 3 weeks ago
Selected Answer: A
"Warn" level is commonly used for recoverable exceptions or situations where the process can continue. Since the exception is being handled and does not necessarily stop the process, "Warn" is appropriate.
upvoted 1 times
...
Hamossa
9 months, 4 weeks ago
It’s error I’m 100% sure from uipath docs
upvoted 1 times
...
Ingvarn
11 months, 1 week ago
Answer A I think
upvoted 1 times
...
Nrhn
1 year, 1 month ago
B is the correct answer - see course "logging levels" in Uipath Academy"
upvoted 1 times
...
Mirjalol
1 year, 3 months ago
Selected Answer: A
Log message is in catch block, I think we can go with Warning. If error was too serious, question would put intonation on it. If bot supposed to be stopped, then it would be mentioned in question as well, therefore Fatal is not also the best solution here.
upvoted 1 times
...
Mariemily
1 year, 3 months ago
Selected Answer: A
A. Level: Warn - Message: exception.Message + "at" + exception.Source
upvoted 1 times
...
Mariemily
1 year, 3 months ago
A. Level: Warn - Message: exception.Message + "at" + exception.Source
upvoted 1 times
...
Riga
1 year, 5 months ago
Selected Answer: C
Fatal error message is logged in the Process - Catch block of exception in RE FW
upvoted 1 times
...
soulebi
1 year, 6 months ago
Selected Answer: A
Answer should be A because this is the best practice when you encounter an exception it will have detailed information of the exception and where it occurred. https://forum.uipath.com/t/try-catch-exception/154655
upvoted 1 times
...
BotLearner
1 year, 6 months ago
Option - D looks more appropriate It's application exception and workflow is not stopped i.e. only information
upvoted 1 times
Mirjalol
1 year, 3 months ago
No it is not! Info log level is NOT for app exception!
upvoted 1 times
...
...
Engineer24
1 year, 6 months ago
Selected Answer: C
C is the correct answer !
upvoted 1 times
Mirjalol
1 year, 3 months ago
Again you smart guy misleading people! You set log level type to Fatal when it is not possible to recover... and question is specifically mentioning that you are placing log message inside catch block of try catch activity right? So tell me how try catch works? What will bot do after performing catch block? Bot will go to finally block and goes to next activity in case no failure in finally block. So bot WILL go to finally block, it means your error WAS NOT fatal you dummy
upvoted 1 times
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
exam
Someone Bought Contributor Access for:
SY0-701
London, 1 minute ago