UiPath-ADAv1 Logging — Timed 10 Questions

Question 1

A developer needs to add a custom log entry that includes a transaction ID and a status message. The entry must be visible in the Orchestrator Logs page and must be tagged with a custom log field named 'TransactionId' so it can be filtered later. Which activity should be used to achieve this?

10 minute time limit — choose an answer to begin.

Accepted Answer

Log Entry. The Log Entry activity is designed to write custom log messages that can include additional fields beyond the standard message and level. When the developer specifies a field named 'TransactionId', that field becomes part of the structured log data and is visible in Orchestrator, enabling filtering. Other activities either do not write to Orchestrator logs or do not support adding custom fields.

Answer

Add Log Fields

Answer

Log Message

Answer

Write Line

Question 2

A developer is troubleshooting a long-running automation that intermittently fails during execution. The developer needs to capture detailed diagnostic information without overwhelming the Orchestrator logs in production. The robot is connected to Orchestrator and uses the default logging configuration. Which two actions should the developer take? (Choose two.)

Accepted Answer

Configure the robot's log level to Trace in Orchestrator.. To troubleshoot intermittent failures without overwhelming production logs, the developer should temporarily increase the log level to Trace for the specific robot and enable verbose logging for that robot. These actions provide detailed diagnostic data while limiting the scope to the affected robot. After resolving the issue, the developer can revert the settings to avoid excessive log volume.

Answer

Set the robot's log level to Verbose in Orchestrator.

Answer

Use the Log Entry activity to log custom diagnostic messages at the Information level.

Answer

Add a Log Message activity with Level set to Error before each potential failure point.

Question 3

A developer is building a UiPath automation that processes invoices. After each invoice is successfully uploaded to a finance system, the developer wants to record a message that includes the invoice number and the upload timestamp, but only when the robot runs in development mode so that production logs remain concise. Which approach should the developer use to conditionally write this custom log entry?

Accepted Answer

Use the Log Message activity with Level set to Verbose, and configure the robot's logging level to Verbose only in development and to Information in production.. Using a Log Message activity with Level set to Verbose allows the message to be emitted only when the robot's effective logging level is Verbose or lower. In production, where the level is typically Information, Verbose messages are suppressed, achieving conditional logging without extra workflow branches. This is the standard approach for development-only diagnostics in UiPath.

Answer

Use the Add Log Fields activity to attach the invoice number and timestamp as custom fields, then use a separate Log Message activity at Error level to ensure the entry is always recorded.

Answer

Use the Write Line activity to output the invoice details to the console, then rely on Orchestrator to capture console output automatically as robot logs.

Answer

Use the Log Message activity with Level set to Info and place it inside an If activity that checks whether the robot is running in development mode.

Question 4

A developer is reviewing the logging configuration for an unattended automation. They want to ensure that all logs generated by the robot are sent to Orchestrator for auditing, but they also need to avoid performance degradation. Which two factors should they consider when configuring logging? (Choose two.)

Accepted Answer

The robot's log level setting in Orchestrator determines the minimum severity of logs that are transmitted.. When configuring logging for auditing, the robot's log level in Orchestrator determines which logs are transmitted; setting it appropriately is crucial to capture required data without excessive volume. Additionally, Add Log Fields can enrich logs but increases size and overhead, so it should be used thoughtfully. These two factors directly impact both the completeness of audit logs and the performance of the automation.

Answer

Setting the log level to 'Error' ensures that all logs, including Information and Verbose, are captured.

Answer

Logs are only sent to Orchestrator when the robot is connected via the Robot tray, not when executed from Orchestrator.

Answer

The 'Log Message' activity automatically sends logs to Orchestrator regardless of the robot's log level.

Question 5

A developer is building a UiPath automation that reads data from a web application. They need to record the exact URL of each page visited during execution for auditing purposes. They want these entries to be visible in Orchestrator logs without changing the project's default logging configuration. Which activity should they use?

Accepted Answer

Log Message. The Log Message activity is designed to write custom messages to the UiPath logs at a chosen level. When set to Information level, these messages appear in Orchestrator logs by default. This directly fulfills the need to record page URLs for auditing without modifying the project's logging configuration.

Answer

Add Log Fields

Answer

Write Line

Answer

Invoke Workflow File

Question 6

Which log level should be used when logging sensitive information such as user passwords or personal identification numbers in a production environment?

Accepted Answer

None of the above. Logging sensitive information in production environments is a security violation that can lead to data breaches or non-compliance with privacy regulations like GDPR. Regardless of the log level, sensitive data should never be written to logs. Instead, developers should use secure assets or encrypted variables to handle credentials, ensuring that logs remain clean of confidential data while still providing enough context for troubleshooting automation execution flows.

Answer

Trace

Answer

Verbose

Answer

Error

Question 7

Which TWO of the following are primary benefits of using structured logging in UiPath Orchestrator?

Accepted Answer

Improved searchability and filtering of logs in external platforms. Structured logging allows developers to parse and analyze process data efficiently using external log management tools like Elasticsearch or Splunk. By treating logs as data rather than plain text, organizations can correlate process events, track business KPIs, and generate automated alerts based on specific metadata. This is essential for enterprise-grade monitoring, as it transforms raw log messages into actionable business intelligence that improves process transparency and enables proactive maintenance of automated workflows.

Answer

Reduced disk space usage on the local robot machine

Answer

Automatic encryption of all log entries before storage

Answer

Elimination of the need for log levels

Question 8

Where can a developer configure the logging level for a specific robot connected to Orchestrator?

Accepted Answer

In the Orchestrator Robot or Machine settings. The logging level for an unattended or attended robot is primarily controlled via the Orchestrator settings for that specific robot or machine template. By adjusting the 'Logging Level' in the Robot settings, developers can dynamically control the verbosity of logs generated during execution. This centralized control is vital for balancing the need for detailed troubleshooting data during development and minimizing storage overhead in stable, high-volume production environments.

Answer

In the UiPath.settings file on the Robot machine

Answer

Inside the UiPath Studio Project settings

Answer

In the Windows Event Viewer

Question 9

Refer to the exhibit. Based on the log output, what is the most likely reason the process failed and then continued?

Accepted Answer

The workflow utilized a Retry Scope activity for the failed activity. The exhibit displays a standard error-handling pattern often implemented with a Retry Scope activity. The 'ERROR' log entry indicates a transient failure during UI interaction, likely a timing issue where the element was not immediately available. The subsequent 'Retrying action' log confirms that the workflow caught the exception and entered a retry cycle, successfully continuing the execution flow without crashing the entire process instance.

Answer

The developer manually stopped the process and restarted it

Answer

The process is configured to ignore all exceptions by default

Answer

The application crashed and auto-restarted the workflow

Question 10

When designing a custom logging framework, which approach is most effective for ensuring consistent log correlation across multiple workflows?

Accepted Answer

Pass a unique Correlation ID through arguments across workflows. For effective log correlation in large-scale automations, developers should pass a unique 'Correlation ID' or 'Transaction ID' through arguments between workflows. By including this ID in every log message, the logs become traceable, allowing administrators to filter messages by the specific process instance across disparate components. This practice is vital for troubleshooting complex, modularized automation projects where child workflows are invoked frequently and independently of the parent.

Answer

Log the timestamp of every activity execution

Answer

Use the Robot ID to group all logs together

Answer

Write logs to a local text file and sort by file size