UiPath-ADPv1 Generic Automation Development Practice Question
When designing an automation that interacts with a web-based portal requiring MFA, what is the recommended approach to handle the dynamic authentication prompts while maintaining security?
⚠ Common exam trap
Candidates often try to automate MFA by hardcoding codes or using insecure workarounds, failing to realize that human interaction is required for security compliance.
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 the Get Credential activity and implement a Wait for Element for the MFA prompt.
Using Orchestrator Credentials or secure Vault integration ensures that sensitive data is not exposed within the workflow. Handling MFA prompts usually requires a human-in-the-loop strategy using Action Center or waiting for specific UI elements indicating the MFA request. This approach balances security compliance with automation requirements, ensuring that credentials remain encrypted while allowing the process to pause and resume securely once the human component provides the necessary authorization.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Store the MFA token in a hardcoded text file inside the project folder.
Why it's wrong here
Storing credentials or tokens in local files is a severe security violation. Such files can be accessed by unauthorized users or exposed in source control systems. Automation must always use encrypted, enterprise-grade storage mechanisms like Orchestrator Assets or CyberArk to maintain security compliance for sensitive authentication information.
- ✓
Use the Get Credential activity and implement a Wait for Element for the MFA prompt.
Why this is correct
This approach uses secure credential retrieval and enables the robot to monitor the UI for the MFA prompt. It allows the automation to gracefully wait for the human user to provide the token, ensuring a secure and reliable integration with portals requiring multi-factor authentication without compromising credential integrity.
- ✗
Bypass MFA by hardcoding the device ID into the browser's cookies.
Why it's wrong here
Bypassing security controls like MFA is prohibited in production environments as it exposes the enterprise to significant risk. Automation should always adhere to established security protocols. Manipulating browser cookies or device IDs to circumvent authentication is technically unstable and violates standard security and compliance policies for automated processes.
- ✗
Use the Type Into activity to send the password and MFA code sequentially.
Why it's wrong here
Sending MFA codes via Type Into is unreliable, as MFA codes are time-sensitive and dynamic. Attempting to automate the entry of a dynamic code generated by a user or device defeats the purpose of multi-factor authentication, which is designed to require a human-present verification step for improved security.
About these practice questions
This UiPath-ADPv1 question is part of Courseiva's 276-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-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.