UiPath-ADAv1 Logging Practice Question
A developer notices that a UiPath automation is producing an excessive number of log entries in Orchestrator, making it difficult to identify errors. The developer wants to reduce the volume of logs without losing important error information. Which action should the developer take?
⚠ Common exam trap
The trap here is thinking that removing custom Log Message activities is the best way to reduce log volume, when adjusting the logging level filters all entries uniformly and retains errors.
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
✓
Change the robot's logging level from Information to Warning in Orchestrator.
Adjusting the robot's logging level to Warning in Orchestrator raises the minimum severity for log entries, filtering out lower-level messages such as Information and Verbose. This reduces log volume while ensuring that Warning, Error, and Critical entries are still captured, preserving important error information for troubleshooting.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Change the robot's logging level from Information to Warning in Orchestrator.
Why this is correct
Raising the minimum log level to Warning filters out Information, Verbose, and Trace entries, significantly reducing log volume while still capturing Warning, Error, and Critical messages. This preserves important error information and is a standard configuration change in Orchestrator for production robots to keep logs manageable.
- ✗
Remove all Log Message activities from the workflows and rely solely on automatic logging.
Why it's wrong here
Removing Log Message activities eliminates custom diagnostic entries but does not control the volume of automatic logs, which can still be verbose. It also removes valuable context that could help troubleshoot issues. The better approach is to adjust the logging level, which filters both custom and automatic entries uniformly.
- ✗
Disable logging entirely for the robot by setting the logging level to None.
Why it's wrong here
Disabling logging entirely prevents any log entries, including errors, from being recorded. This would eliminate the ability to diagnose failures and is not a viable option for production monitoring. The developer needs to reduce volume while retaining error information, so a level like Warning is appropriate.
- ✗
Set the logging level to Verbose to capture all details, then use Orchestrator's filtering to find errors.
Why it's wrong here
Setting the level to Verbose increases log volume dramatically, as it captures the most detailed entries. While Orchestrator can filter, the sheer volume can impact performance and storage. This is the opposite of reducing log volume and would make it harder to identify errors among the noise.
About these practice questions
One of 285 original UiPath-ADAv1 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.