Where can we see the logs generated by running robots? Options are :
Correct Answer: A, B
Explanation:
Logs generated by running UiPath robots can be viewed in multiple places depending on how the process is executed and configured. If the robot is connected to UiPath Orchestrator, all execution logs are automatically sent and stored in the Orchestrator Logs, where they can be monitored centrally for all robots and processes. At the same time, logs are also saved locally on the machine in the Logs folder, which allows developers to review execution details even without Orchestrator connectivity. The Output panel (Option C) is only used inside UiPath Studio during debugging and does not store logs for robot execution in production. Therefore, the correct locations to view robot-generated logs are Orchestrator logs and the local Logs folder.
Question 2
When should the "Add Log Fields" activity be used? Options are :
Correct Answer: C
Explanation:
The Add Log Fields activity in UiPath is used to enhance or customize the default logging structure by adding additional contextual information to log entries. These extra fields become part of every log message generated after the activity is executed, allowing developers to include useful metadata such as transaction IDs, user details, process stages, or any custom identifiers that help in better tracking and debugging of automation workflows. It does not enable logging itself (so option A is incorrect), nor does it limit logs to a fixed number of visible fields like five (so option B is also incorrect). Instead, its primary purpose is to enrich standard log messages with custom fields, making option C the correct answer.
Question 3
In which workflow in the UiPath Robotic Enterprise Framework template is the retry mechanism implemented? Options are :
Correct Answer: B
Explanation:
In the UiPath Robotic Enterprise Framework (REFramework), the retry mechanism is implemented in the SetTransactionStatus workflow, specifically when handling failed transactions. If a transaction fails, the framework checks whether it is eligible for a retry based on the exception type and retry settings, and then updates the transaction status accordingly (Retry / Failed). This logic ensures that recoverable errors can be retried before marking a transaction as permanently failed. The Main workflow only controls the high-level orchestration of the process, while GetTransactionData is responsible for fetching the next transaction item and does not handle retries. Therefore, the retry mechanism is handled within SetTransactionStatus, making option A correct.
Demo Practice Mode
You are viewing only the questions marked as Demo.