UiPath-ADAv1 Logging Practice Question
A developer wants to log the start and end time of a long-running process for performance analysis. What is the most reliable way to achieve this?
⚠ Common exam trap
Candidates often rely solely on basic timestamps without including a unique identifier, making it impossible to accurately pair start and end times in parallel or high-volume runs.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Log the time using 'Log Message' with a unique process ID
Using the 'Log Message' activity at the start and end of the workflow is the standard approach. However, for true performance analysis, including a consistent process ID or unique instance ID is essential to ensure that the start and end entries can be paired correctly. This allows for simple duration calculations by subtracting the start timestamp from the end timestamp in an external analytics tool.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use the 'Write Line' activity at the start and end
Why it's wrong here
The 'Write Line' activity is not suited for performance monitoring because these logs are not stored in Orchestrator. Consequently, they cannot be retrieved for long-term trend analysis or auditing, rendering them useless for building performance dashboards or calculating the execution duration of processes running in the production environment.
- ✓
Log the time using 'Log Message' with a unique process ID
Why this is correct
By using 'Log Message', the entries are captured in Orchestrator. Including a unique process ID allows developers to isolate the start and end logs for a single execution instance, enabling the accurate calculation of process duration, which is crucial for identifying bottlenecks and optimizing the automation for better performance.
- ✗
Enable 'Trace' logging in Orchestrator for the duration
Why it's wrong here
Enabling 'Trace' logging captures excessive amounts of data, which can negatively impact system performance and clutter logs. It is an inefficient and impractical way to measure duration. Targeted 'Log Message' entries provide the necessary data points without the significant overhead and storage issues associated with enabling trace-level logging globally.
- ✗
Use the Robot's system-generated job status logs
Why it's wrong here
While Orchestrator captures job start and end times automatically, these logs may not align perfectly with specific business workflow steps. Custom logging provides more flexibility, allowing developers to measure the duration of specific activities or sub-processes rather than just the entire job duration, which is often needed for detailed process optimization.
About these practice questions
This UiPath-ADAv1 question is part of Courseiva's 285-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official UiPath exam blueprint
This UiPath-ADAv1 practice question is part of Courseiva's free UiPath certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the UiPath-ADAv1 exam.