UiPath-ADAv1 Logging Practice Question
Which log level should be used when logging sensitive information such as user passwords or personal identification numbers in a production environment?
⚠ Common exam trap
Candidates often select 'Trace' or 'Debug' assuming that lower severity log levels safely hide sensitive data, forgetting that any log level will still expose plain-text credentials in the output.
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
✓
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 analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Trace
Why it's wrong here
Trace logs capture highly granular details often used during local debugging. While this level records much data, it is not an excuse to log sensitive information. Security best practices mandate that passwords and PII must never be stored in plain text within log files regardless of the chosen severity level.
- ✗
Verbose
Why it's wrong here
Verbose logging provides extensive diagnostic data about variable states and activity flow. While useful for complex troubleshooting, it remains subject to strict security policies. Sensitive data must be excluded from all logs, as verbose logging is frequently forwarded to centralized systems where unauthorized personnel might gain access to logs.
- ✓
None of the above
Why this is correct
No log level is appropriate for logging sensitive information. Security standards explicitly prohibit exposing passwords or PII in logs, as these files are often accessible to support teams and monitoring systems. Developers must implement data masking or use secure credential stores to handle sensitive data without writing it to disk.
- ✗
Error
Why it's wrong here
Error logs capture events that prevent the automation from proceeding normally. Even during an error, developers must ensure that data dumped to the log file does not contain plain-text credentials or sensitive user data. Logging sensitive information at an error level is still a critical security vulnerability that requires mitigation.
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.