UiPath-ADPv1 Advanced Debugging Practice Question
You are debugging a workflow that interacts with a legacy desktop application. The process frequently hangs at a specific input field. Which TWO debugging actions should you take to diagnose the cause of the hang?
⚠ Common exam trap
Candidates restart the entire legacy application instead of inspecting the frozen state live using UI Explorer and step execution tools.
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
✓
Use 'Step Into' to observe the exact activity causing the hang.
Diagnosing application hangs requires observing the interaction between the robot and the UI thread. By using the 'Step Into' feature in conjunction with the 'UI Explorer' validation, you can determine if the application is failing to respond to input commands. These steps help isolate whether the issue is a selector timeout or a blocked UI thread in the target application.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable 'Tracing' in the Project Settings.
Why it's wrong here
Tracing provides excessive log data that often obscures the specific moment of the hang. It is not an effective tool for diagnosing UI thread blocking issues, as it records events after they happen rather than allowing direct interaction with the execution state of the target application.
- ✓
Use 'Step Into' to observe the exact activity causing the hang.
Why this is correct
Step Into allows you to execute the workflow one activity at a time. This is the most effective way to identify the exact activity where the process hangs, narrowing down the potential conflict between the robot's input command and the target application's responsiveness at that moment.
- ✓
Validate the selector using the UI Explorer while the application is in the 'hang' state.
Why this is correct
Validating the selector while the app is hung reveals if the UI layer is responsive or locked. If the selector fails to highlight or validate during the hang, it confirms that the application's UI thread is blocked, which is a critical piece of diagnostic information for developers.
- ✗
Restart the UiPath Robot service.
Why it's wrong here
Restarting the robot service is a general troubleshooting step that disrupts the current debugging context. It does not help in identifying why a specific activity is causing a hang; instead, it clears the environment and prevents you from observing the specific conditions leading to the issue.
- ✗
Run the process in 'Background' mode.
Why it's wrong here
Running in background mode prevents the UI from being rendered, making it impossible to observe the interaction and verify where the hang occurs. This mode is the opposite of what is needed for debugging a UI-related hang in a legacy desktop application during runtime.
About these practice questions
Courseiva writes every UiPath-ADPv1 question from scratch — 276 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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-ADPv1 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-ADPv1 exam.